Chronological Thread 

< Chronological >      < Thread >

---

Hi Mia,

please note that the sender can only send DATA on confirmed paths. So
it can send DATA on path 1 but not on path 0. It does not matter from
which path DATA is received.

So I would expect that the application below sends DATA only on path 1.

Only after path 0 is confirmed, that path can be used for sending DATA.

Best regards
Michael


On May 3, 2005, at 1:00 PM, Mia wrote:

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
_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion

---

• [SCTP-Discussion] Multihoming problem, Mia, 05/03/2005
  • Re: [SCTP-Discussion] Multihoming problem, Michael Tuexen, 05/03/2005

---

Archive powered by MHonArc 2.6.19+.