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 2027232 - mptcpize apparently not mptcpizing iperf3
Summary: mptcpize apparently not mptcpizing iperf3
Keywords:
Status: CLOSED DUPLICATE of bug 2015623
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: mptcpd
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Davide Caratti
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-29 07:39 UTC by Christian Horn
Modified: 2021-11-29 14:04 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-29 14:04:48 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-104111 0 None None None 2021-11-29 07:40:02 UTC

Description Christian Horn 2021-11-29 07:39:20 UTC 
Description of problem:
mptcpize apparently not mptcpizing iperf3

Version-Release number of selected component (if applicable):
mptcpd-0.8-1-el9

How reproducible:
always

Steps to Reproduce:
1. setup 2 KVM guests with rhel9, I used a build from 20211123. 3 NICs in both, terminated in 3 bridges (virbd0-2) on the hypervisor.
2. setup systemtap, run "stap -vg mptcp-app.stp iperf3" on both systems, run "iperf -s" on one box, "iperf -c <ip>" on the other box
3. setup basic mptcp on both systems, to verify operation:
  Server # ip mptcp limits set subflow 1
  Client # ip mptcp limits set subflow 1 add_addr_accepted 1
  Server # ip mptcp endpoint add 198.51.100.1 dev enp2s0 signal
4. "dnf -y install pcp-zeroconf"
5. run "pmrep network.interface.in.bytes", observe that 2 NICs are used, so systemtap works for mptcpizing
6. on one of both systems, stop the systemtap script, and run "mptcpize run -c iperf -s" or "mptcpize run -d iperf3 -c"

Actual results:
- mptcpize is not outputting a message that the tcp socket got mptcpized
- connection can not be established

Additional info:
Running netcat, mptcpize is reporting that mptcpization is happening. 
Is this a limitation, mptcpize just working for certain socket operations?  The man page does not hint on it.
Comment 1 Davide Caratti 2021-11-29 10:05:02 UTC 
maybe it's because iperf3 does socket(<family>, SOCK_STREAM, 0) instead of socket(<family>, SOCK_STREAM, 6). If so, then we can fix this as a dup of https://bugzilla.redhat.com/show_bug.cgi?id=2015623: I'll check and let you know.
Comment 2 Davide Caratti 2021-11-29 14:02:49 UTC 
(In reply to Davide Caratti from comment #1)
> maybe it's because iperf3 does socket(<family>, SOCK_STREAM, 0) instead of
> socket(<family>, SOCK_STREAM, 6). If so, then we can fix this as a dup of
> https://bugzilla.redhat.com/show_bug.cgi?id=2015623: I'll check and let you
> know.


confirmed by the output of strace:


# strace -o strace.out  -f  iperf3 -s -p 1234 

[...]

# cat strace.out

[...]

35221 socket(AF_INET6, SOCK_STREAM, IPPROTO_IP) = 3
35221 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
35221 setsockopt(3, SOL_IPV6, IPV6_V6ONLY, [0], 4) = 0
35221 bind(3, {sa_family=AF_INET6, sin6_port=htons(1234), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "::", &sin6_addr), sin6_scope_id=0}, 28) = 0
35221 listen(3, 2147483647)             = 0
Comment 3 Davide Caratti 2021-11-29 14:04:48 UTC 

*** This bug has been marked as a duplicate of bug 2015623 ***
Note You need to log in before you can comment on or make changes to this bug.