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.
addresses had a
netmask of 255.255.0.0 so both addresses were located in the same
subnet. Did the same test with 2 Vmware machines and other addresses
which was successful.
Regards,
Christian
On Jan 17, 2011, at 8:11 AM, Schoch Christian wrote:
I did some test with multihoming and
Hi,
While porting a SCTP test tool, I figured out, that connect with
SOCK_SEQPACKET (SCTP 1-to-many style socket) is always returning 0,
regardless if the connection could be established or not.
The problem is that this result is responsible for client or server
mode of the tools.
If th
RTO.
This behavior is triggered by a returning heartbeat message when no
ICMP unreachable by data is sent quite before.
Test system are two multi-homed hosts with FreeBSD8.1 and a WANem host
between.
A wireshark log can be provided on demand (quite large).
Regards,
Schoch Christian
Zitat von Michael Tüxen :
On Apr 30, 2011, at 9:11 AM, Schoch Christian wrote:
During a measurement with CMT-SCTP and PF i figured out, that
sometimes a ICMP Destination unreachable message triggers a message
transmission on an inactive data path that has been primary before.
It looks
On Apr 30, 2011, at 12:15 PM, Schoch Christian wrote:
On Apr 30, 2011, at 9:11 AM, Schoch Christian wrote:
During a measurement with CMT-SCTP and PF i figured out, that
sometimes a ICMP Destination unreachable message triggers a
message transmission on an inactive data path that has been
Zitat von Michael Tüxen:
On May 1, 2011, at 1:10 PM, Schoch Christian wrote:
On Apr 30, 2011, at 12:15 PM, Schoch Christian wrote:
On Apr 30, 2011, at 9:11 AM, Schoch Christian wrote:
During a measurement with CMT-SCTP and PF i figured out, that
sometimes a ICMP Destination unreachable
