That should be correct.
Hi Andreas,
I have checked the source code for sctplib1.3.1. (Please see the attached .pdf file).
My understanding is that:
1- sctpd opens a raw socket and listens for incoming IP packets with protocol number 132 (SCTP) and hands them to the correct sctp instance.
That should be correct.
2- client_socket and unix_socket are two unix sockets opened on arbitrary ports for communication between sctpd and sctp instance.
The SCTP/NAT issue is not related to any particular SCTP implementation.
could you verify 1 and 2 ?
I am wondering if stplib1.3.1 works with NATs? Consider the case
132 is not a port number, but the protocol id in the IP header. Normally you can run
echo_server runs on a linux machine with one interface and global ip address.
terminal (client) runs on a linux redhat 9, behind a NAT, with one interface and ip address.
I tried this configuration, it did not work. Should I somehow config NAT (to work with port 132) or sctplib ?
That should be correct. Using this mechanism the sctpd can process all interface
Finally, as far as I see, sctpd opens a routing socket and hence whenever there is a change in the routing table (route/path added/deleted) sctpd is informed by the kernel with netlink/rtnetlink of this change. And this is the way to trigger sending asconf(add/delete-ip) chunks ??
Thanks,
Ilknur Aydin
DEGAS Networking Group
Dept. of Computer and Information Sciences
University of Delaware
http://www.cis.udel.edu/~aydin<port.q.to.andreas.pdf>
Archive powered by MHonArc 2.6.19+.