Hide Forgot
Description of problem: When there's a sctp server running on system, `ss` doesn't list it in its output. Trying to specify `sctp` protocol explicitly also fails. Version-Release number of selected component (if applicable): iproute-3.10.0-11.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. modprobe sctp; yum install -y lksctp-tools 2. sctp_darn -H 0 -P 2500 -l 3. ss -an | grep 2500 4. ss -n -A sctp Actual results: *no output* and for 4.: ss: "sctp" is illegal socket table id Expected results: Infor about server running on port 2500 Additional info: # netstat -na | grep 2500 sctp 0.0.0.0:2500 LISTEN
`ss' currently doesn't support SCTP at all. Marking as FutureFeature.
There's a usable procfs interface. Requesting devel ack.
Discussion regarding sctp_diag kernel interface has started already, so it should be possible to accomplish this for RHEL7.3.
Patch series implementing sctp_diag support in 'ss' has been sent upstream: http://marc.info/?l=linux-netdev&m=146983127501267&w=2 Please note though that it requires a few kernel changes for full functionality, tracked in Bug 1361728.
Sadly, upstream has not accepted the submitted patch yet, which is why this ticket was left untouched for so long. On the other hand, it is not a good idea to import a large change like this one at this point, especially since it didn't see any upstream testing at all yet.
Finally, upstream accepted my patches: commit 5dec02d7b4b70128a661bab1ff991c605ba28b3f Author: Phil Sutter <phil> Date: Wed Nov 9 12:12:23 2016 +0100 include: Add linux/sctp.h Add sanitized UAPI linux/sctp.h header file. Signed-off-by: Phil Sutter <phil> commit f89d46ad63f6f606f777da964205bc53b2197cfa Author: Phil Sutter <phil> Date: Wed Nov 9 12:12:24 2016 +0100 ss: Add support for SCTP protocol This makes use of the sctp_diag interface recently added to the kernel. Joint work with Xin Long who provided the PoC implementation which I merely polished up a bit. Signed-off-by: Phil Sutter <phil>
Hi Phil, I found one, simple, documentation issue. There is no mention about sctp in -A option in ss man-page and ss help, where all socket types are listed. I think, it should be there. Would be possible to fix it?
Hi Jaroslav, (In reply to Jaroslav Aster from comment #27) > I found one, simple, documentation issue. There is no mention about sctp in > -A option in ss man-page and ss help, where all socket types are listed. I > think, it should be there. Would be possible to fix it? Good catch, thanks! I've quickly prepared a patch for upstream and submitted it: http://marc.info/?l=linux-netdev&m=148907572801154&w=2 Thanks, Phil
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, 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-2017:2171
Arrived here because of bug 1544898 ("ss indiscriminately loads sctp kernel modules") - does anyone know why the latter is locked?