First login?
Lost password?
 
 
sctp-discussion AT lists.franken.de 
SCTP Discussions

Text archives Help


[SCTP-Discussion] Multihoming problem


Chronological Thread 
  • From: Mia <mia.immonen AT gmail.com>
  • To: discussion AT sctp.de
  • Subject: [SCTP-Discussion] Multihoming problem
  • Date: Tue May 3 13:02:01 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=A2qmVbV/8BfUhMIegMmhNx1gpoy4x6J6W31ltLryG7JLIelSY9wf1rj4EB8CTwRH2klu3Sza5NG+MM/8HH4fqYkL4wYVsjBY2XStiRAMrszX+C0Yyr/jMClQNWxUu3DA5EHh1l2xIYSBlWjkfylgd6t6BcYhkzQP7s8w1Y/0KRY=
  • List-id: SCTP Discussions <discussion.sctp.de>
Hello!

I am trying out the multihoming feature. I have 2 ethernet interfaces
on 2 computers on different subnets and send data from one to the
other. But, what happens is that there is an "automatic" change to the
other path without me doing anything. I use the chargen_server to send
data to the terminal and this is what happens:

[root@CCSSER1 programs]# ./terminal -d 192.168.1.1 -d 192.168.2.1 -r
19 -V
1 : Communication up (2 paths, 1 In-Streams, 10 Out-Streams)
1 : Path Status of path 0 (towards 192.168.1.1): UNCONFIRMED.
1 : Path Status of path 1 (towards 192.168.2.1): REACHABLE.
1 : Network status change: path 1 (towards 192.168.2.1) is now REACHABLE
1 : Data arrived (200 bytes on path 0, ordered)
1 : Data arrived (200 bytes on path 0, ordered)
1 : Data arrived (200 bytes on path 0, ordered)
1 : Data arrived (200 bytes on path 0, ordered)

Then the data flow stops here until path 1 gets REACHABLE and then
according to the tcpdumpfile, all packets automatically get sent on
that path instead. And I cant figure out why???
The failover should happen when I put path 0 down.

Thanks for any help!

Best regards

Mia


Archive powered by MHonArc 2.6.19+.

Top of page