Chronological Thread 

< Chronological >      < Thread >

---

Hi Micheal and Andreas,

I am now working on a 'monitoring' program running within the terminal
program as you guys may know. I am running pre 12 now.
I have two unix machines which are dual homed. One of them is running echo
tool and the other is running my 'monitor cum terminal' program. After the
association have been established, I pulled out one of the cables to
simulate a Network status change. From my program, I found out that after a
Network status change event has been called, the state of the path which has
gone inactive remains 0 (SCTP_PATH_ACTIVE) instead of being changed to
1(SCTP_PATH_INACTIVE).
Also, when I made the primary path inactive, the SCTP library did not assign
the next active path as the primary path like it did in Pre 9 release.
Instead, the terminal program still tries to send sctp packets thru the
primary path (which has gone inactive) after a networkstatus changed has
been registered. As a results, the packets are only sent via the active path
after a number of attempts to send it on the primary path (now inactive) has
failed.
I did not have this problem when I was working in Pre 9. I only experienced
this after upgrading to pre 11 and above. I don't know if this is a bug or I
have done something wrong. Could you guys pls verify that?

Best regards,

eric.

---

• [SCTP-Discussion] Network status change in Pre 12, Yeo Choon Kiat ICM CA MS MI E7 Extern, 06/19/2001
  • Re: [SCTP-Discussion] Network status change in Pre 12, Andreas Jungmaier, 06/19/2001
  • Re: [SCTP-Discussion] Network status change in Pre 12, Andreas Jungmaier, 06/21/2001
    • [SCTP-Discussion] Discard server's incorrect behaviour, Marjan Bozinovski, 06/28/2001
      • Re: [SCTP-Discussion] Discard server's incorrect behaviour, Michael Tüxen, 06/28/2001

---

Archive powered by MHonArc 2.6.19+.