I am running Red hat version 8. I installed lksctp-tools and checksctp returns "Protocol not supported"

I tried installing kernel-modules-extra as well. No luck. Restarted the server every time I installed these and checked.

Found these documents which say SCTP should be blocked and disabled in linux unless needed. Says must disable SCTP Says must block SCTP even if its installed.

I un-blocked it by commenting out the sctp_blacklist.conf, no luck. (Rebooted and tried.) I enabled ipv6, tested, restarted and re-tested. Still checksctp gives the same issue.

modprobe gives no error but module is not getting loaded.

[root@app01-p net]# uname -a
Linux app01-p 4.18.0-305.19.1.el8_4.x86_64 #1 SMP Tue Sep 7 07:07:31 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
[root@app01-p net]# 
[root@app01-p net]# modinfo sctp
filename:       /lib/modules/4.18.0-305.19.1.el8_4.x86_64/kernel/net/sctp/sctp.ko.xz
license:        GPL
description:    Support for the SCTP protocol (RFC2960)
author:         Linux Kernel SCTP developers <[email protected]>
alias:          net-pf-10-proto-132
alias:          net-pf-2-proto-132
rhelversion:    8.4
srcversion:     306E44C4A6F5501050C98E5
depends:        libcrc32c
intree:         Y
name:           sctp
vermagic:       4.18.0-305.19.1.el8_4.x86_64 SMP mod_unload modversions 
sig_id:         PKCS#7
signer:         Red Hat Enterprise Linux kernel signing key
sig_key:        6A:34:A3:C0:30:AF:24:58:38:BA:F1:FB:5C:05:9E:26:3B:EE:D8:25
sig_hashalgo:   sha256
signature:      15:27:23:A9:8E:51:F4:2F:31:E0:98:62:05:B5:D4:16:BB:84:23:79:
        73:8F:28:1A:9E:CD:89:21:13:BA:23:D1:F1:AF:92:F9:0C:A3:29:DC:
        BA:14:D1:8D:06:8C:CE:09:A0:AB:4F:BC:DF:99:28:0C:8A:E5:A4:B7:
        81:D0:0A:CE:95:C8:EE:17:55:38:B3:8C:32:C4:F6:44:0B:C3:7B:87:
        ED:F1:D6:B0:75:E6:40:70:6F:19:0A:5E:BA:44:98:12:5E:4D:21:27:
        C8:7D:D8:4E:14:96:99:42:A0:6A:43:D3:B1:4A:09:07:09:9A:25:30:
        83:70:E3:CB:91:D5:0A:A5:0C:47:9A:68:EB:58:64:26:39:65:78:CD:
        28:1D:0A:3A:62:80:8C:F2:4E:9C:46:20:DB:C2:67:22:70:EE:5E:61:
        31:B4:A4:D7:FB:C5:F9:08:8D:BD:49:84:91:58:2A:B9:F7:2F:D4:3A:
        31:89:ED:76:24:5D:D0:21:B3:B8:CC:E3:08:F1:F2:DD:47:45:0F:66:
        F8:C2:9F:82:6A:65:0D:C7:3A:6A:5E:81:64:30:4D:BF:D3:88:8F:8E:
        AD:39:FB:15:C3:FF:A6:06:6B:BD:CE:90:EF:AA:0F:80:CF:A0:80:43:
        B9:6D:AF:D7:65:46:94:A7:C7:7D:7B:14:1E:9A:98:93:77:98:6C:73:
        EB:77:0B:F7:17:B6:D5:3B:0F:43:C0:E5:F1:F6:F2:63:15:27:38:E0:
        C9:03:73:38:F3:EC:8D:26:78:D8:90:10:5D:C9:05:D3:29:29:B9:8E:
        9F:7A:66:DA:4A:D9:AE:F4:D6:B4:1E:B7:D3:E3:2A:65:44:A4:A9:60:
        D6:CE:87:C7:52:D7:84:65:D1:3A:E7:E8:AE:C7:13:FF:FC:13:C2:C4:
        35:CA:55:D4:D2:17:40:1E:DB:D0:04:8B:4C:14:6B:F9:55:D3:55:CA:
        AE:68:FC:54:20:85:7F:65:FF:8A:1E:81:30:BA:EB:E6:D4:BA:75:8F:
        2E:88:A4:DA
parm:           no_checksums:Disable checksums computing and verification (bool)
[root@app01-p net]# 
[root@app01-p net]# 
[root@app01-p net]# modprobe sctp
[root@app01-p net]# 
[root@app01-p net]# checksctp
checksctp: Protocol not supported

Does anyone know how to get SCTP enabled in this RHEL 8 server?

Trying to initiate the SCTP association, but no message is getting initiated. Checked in the redhat linux machine, couldn't see sctp.

checksctp

checksctp: Protocol not supported

lsmod | grep sctp

lksctp-tools-1.0.17-2.el7.x86_64 package is installed in server. Please help me how to resolve this.

Assuming timers set like in the Linux implementation or as suggested in RFC4960:

When does an idle SCTP association timeout, when the peer disappears?

a) let’s assume HEARTBEAT is switched off for all destination addresses.

I guess it never does, because nothing is sent, so nothing gets lost.

b) with normal HEARTBEATs, both peers single homed.

• Association.Max.Retrans is 10 times
• RTO.Max is 60 seconds

After HEARTBEAT kicks in (when?) the upper limit is something related to 10×60s (=10 minutes). Who knows the details?

c) is it different if one or both sides are multihomed? Or if the association has a lot of data to send?

I’m not sure if the multihoming case is different at all (timeouts faster or slower?). – And if data is to be sent: I guess the timeout is still the same minus average time for the HEARTBEAT to kick in.

I've ready a thread in russian Nginx maillist about implementing HTTP/SPDY over SCTP in future.

I realize that SCTP is completely unusable for public service at the moment, but what changes should happen for SCTP to replace TCP for public web?