Sctp init not carrying the ipv4 address parameter when I am using "192.169.201.60" as primary address, but when i use "172.17.42.3" then it works fine.
It is happening consistently and I am confused with this behaviour.
So it work fine when source ip address is 172.17.42.3 but does not work when source ip address is 192.169.201.60.
See below chunk from tcpdump when "IPv4 address parameter" included:
Frame 2338: 100 bytes on wire (800 bits), 100 bytes captured (800 bits)
Linux cooked capture
Internet Protocol Version 4, Src: 172.17.42.3, Dst: 172.17.42.5
Stream Control Transmission Protocol, Src Port: 54314 (54314), Dst Port: 3868 (3868)
Source port: 54314
Destination port: 3868
Verification tag: 0x00000000
[Association index: 0]
Checksum: 0x00000000 [unverified]
[Checksum Status: Unverified]
INIT chunk (Outbound streams: 10, inbound streams: 65535)
Chunk type: INIT (1)
Chunk flags: 0x00
Chunk length: 52
Initiate tag: 0xc29ebee4
Advertised receiver window credit (a_rwnd): 32767
Number of outbound streams: 10
Number of inbound streams: 65535
Initial TSN: 3242577996
IPv4 address parameter (Address: 172.17.42.3)
IPv4 address parameter (Address: 192.169.201.60)
Supported address types parameter (Supported types: IPv4)
ECN parameter
Forward TSN supported parameter
See below chunk from tcpdump when "IPv4 address parameter" not included:
Frame 2340: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Linux cooked capture
Internet Protocol Version 4, Src: 192.169.201.60, Dst: 192.169.201.62
Stream Control Transmission Protocol, Src Port: 43213 (43213), Dst Port: 3868 (3868)
Source port: 43213
Destination port: 3868
Verification tag: 0x00000000
[Association index: 1]
Checksum: 0xcdb3ff13 [unverified]
[Checksum Status: Unverified]
INIT chunk (Outbound streams: 10, inbound streams: 65535)
Chunk type: INIT (1)
Chunk flags: 0x00
Chunk length: 36
Initiate tag: 0x1d8a2c1b
Advertised receiver window credit (a_rwnd): 32767
Number of outbound streams: 10
Number of inbound streams: 65535
Initial TSN: 3195157733
Supported address types parameter (Supported types: IPv4)
ECN parameter
Forward TSN supported parameter
So I feel sctp behaviour should be fine in both the cases.
User contributions licensed under CC BY-SA 3.0