Date: Mon, 17 Jan 2011 08:11:22 +0100 From: Schoch Christian <e0326715@student.tuwien.ac.at> To: freebsd-net@freebsd.org Subject: [SCTP] transport address unconfirmed instead of inactive Message-ID: <20110117081122.65833sa4wsdugdqy@webmail.tuwien.ac.at>
next in thread | raw e-mail | index | archive | help
I did some test with multihoming and failover. My problem is that if one transport failes it never comes back to active (no heartbeats are sent any more). My setup: FreeBSD 8.1 Linux 2.6.36 172.16.1.4 --------- 172.16.1.3 172.17.1.4 --------- 172.17.1.3 Packets from 16.1.4 to 17.1.3 and 17.1.4 to 16.1.3 are dropped. The transfer starts with 172.16.1.4 to 16.1.3 which is working as expected. If the transfer on this transport failes, it is switching to 17.1.4 & 17.1.3 as expected. 172.16.1.4 gets SCTP_UNCONFIRMED, 172.16.1.3 gets SCTP_INACTIVE Now, if the first connection is available again, the first transport address of FreeBSD stays at unconfirmed with no HB sent to 16.1.3 Linux sends HB from 16.1.3 to 16.1.4 with ACK coming back from 17.1.4 to 16.1.3 (which is dropped). So why are HBs sent from new primary instead of received address ? As specified in RFC it should sent back from address, it receives the HB packet. Regards, Christian ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110117081122.65833sa4wsdugdqy>