RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2033155 - tcpaccept didn't show anything when there's incoming connection
Summary: tcpaccept didn't show anything when there's incoming connection
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: bcc
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jerome Marchand
QA Contact: Jon Trossbach
URL:
Whiteboard:
Depends On:
Blocks: 2010412
TreeView+ depends on / blocked
 
Reported: 2021-12-16 04:04 UTC by Zhiqian Guan
Modified: 2023-05-09 09:04 UTC (History)
5 users (show)

Fixed In Version: bcc-0.25.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:47:21 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-105964 0 None None None 2021-12-16 04:06:29 UTC
Red Hat Product Errata RHBA-2023:2342 0 None None None 2023-05-09 07:47:33 UTC

Description Zhiqian Guan 2021-12-16 04:04:41 UTC 
Description of problem:
tcpaccept tool didn't show anything when I use ncat and ssh to test it, this only found on RHEL9, RHEL8.6 is fine.

## Terminal A:
[root@netqe1 ~]# ncat 192.168.123.1 12345
123
[root@netqe4 ~]# ncat -l 12345 -k
123

## Terminal B
[root@netqe4 tools]# ./tcpaccept
PID     COMM         IP RADDR            RPORT LADDR            LPORT


Version-Release number of selected component (if applicable):
[root@netqe4 tools]# uname -r
5.14.0-29.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1.run ./tcpaccept
2. use ncat to connect the host from another host

Actual results:
No output

Expected results:
# Output of the same test cases on RHEL8.6
PID     COMM         IP RADDR            RPORT LADDR            LPORT
387396  ncat         4  192.168.123.2    58620 192.168.123.1    54322



Additional info:
Comment 13 Jon Trossbach 2023-01-24 22:51:19 UTC 
Jerome, these were my results. If this is what you would expect or if you think this need further testing let me know. Otherwise, let me know I can move it to VERIFIED.

[root@netqe5 tools]# rpm -q bcc
bcc-0.25.0-2.el9.x86_64
[root@netqe5 tools]# uname -r
5.14.0-241.el9.x86_64
[root@netqe5 tools]# rpm -q nmap
nmap-7.91-11.el9.x86_64

-- first terminal --
[root@netqe5 tools]# ip r
default via * dev eno3 proto dhcp src 10.19.15.13 metric 100 
* dev eno3 proto kernel scope link src 10.19.15.13 metric 100 
[root@netqe5 tools]# ./tcpaccept & ncat -l 32323 -k 
[1] 50105
PID     COMM         IP RADDR            RPORT LADDR            LPORT
50106   ncat         4  10.19.15.81      34850 10.19.15.13      32323
testing 123
backatcha
the first fully open source chat app


-- other terminal -- 
[root@netqe41 ~]# ip r
default via * dev eno8303 proto dhcp src 10.19.15.81 metric 100 
* dev eno8303 proto kernel scope link src 10.19.15.81 metric 100 
[root@netqe41 ~]# ncat 10.19.15.13 32323
testing 123
backatcha
the first fully open source chat app
Comment 14 Jerome Marchand 2023-01-25 09:17:17 UTC 
(In reply to Jon Trossbach from comment #13)
> Jerome, these were my results. If this is what you would expect or if you
> think this need further testing let me know. Otherwise, let me know I can
> move it to VERIFIED.

Yes, that what's expected.

> 
> [root@netqe5 tools]# rpm -q bcc
> bcc-0.25.0-2.el9.x86_64
> [root@netqe5 tools]# uname -r
> 5.14.0-241.el9.x86_64
> [root@netqe5 tools]# rpm -q nmap
> nmap-7.91-11.el9.x86_64
> 
> -- first terminal --
> [root@netqe5 tools]# ip r
> default via * dev eno3 proto dhcp src 10.19.15.13 metric 100 
> * dev eno3 proto kernel scope link src 10.19.15.13 metric 100 
> [root@netqe5 tools]# ./tcpaccept & ncat -l 32323 -k 
> [1] 50105
> PID     COMM         IP RADDR            RPORT LADDR            LPORT
> 50106   ncat         4  10.19.15.81      34850 10.19.15.13      32323
> testing 123
> backatcha
> the first fully open source chat app
> 
> 
> -- other terminal -- 
> [root@netqe41 ~]# ip r
> default via * dev eno8303 proto dhcp src 10.19.15.81 metric 100 
> * dev eno8303 proto kernel scope link src 10.19.15.81 metric 100 
> [root@netqe41 ~]# ncat 10.19.15.13 32323
> testing 123
> backatcha
> the first fully open source chat app
Comment 15 Jon Trossbach 2023-01-25 18:22:07 UTC 
Okay, moving to VERIFIED.

And for future reference sake. The same image was provisioned on both machines in my above test.
Comment 18 errata-xmlrpc 2023-05-09 07:47:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (bcc bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2342
Note You need to log in before you can comment on or make changes to this bug.