Chronological Thread 

< Chronological >      < Thread >

---

Both NICs are in the same subnet, I suppose (if you are using
class C subnets). Then, your route to both destination adresses
will be configured such that your default interface/default route
is ALWAYS selected.
Since SCTPLIB does not influence host routing, you get behaviour
you saw.

Now, if both destinations are in different subnets,
AND both of your NICs are in different subnets, you can
configure your routing such that you will see a nice
failover.

Hope that helps,
Andreas


Zitat von Michael Tuexen
<Michael.Tuexen AT micmac.franken.de>:

> Please use IP-addresses in different networks.
>
> Best regards
> Michael
>
> On May 12, 2004, at 9:47 AM, Thorbjørn Jørgensen wrote:
>
> > Hi Michael
> > The server which is running a modified version of one of the sctplib
> > server
> > programs that continuously sends out packets, the IP is 10.8.4.249.
> > On the client two NIC are used with IP address 10.8.4.52 (Eth0
> > default), and
> > 10.8.4.151 (Eth1)
> > The client that runs a terminal, with the following parameters:
> > # ./Terminal -s 10.8.4.52 -s 10.8.4.151 -p 10.8.4.151 -d 10.8.4.249
> > We are changing the primarypath from Eth0 to Eth1, but still the client
> > sends out sacks on the default interface.
> >
> > Regards
> > Lars and Thorbjørn
> >
> > -----Original Message-----
> > From:
> > discussion-admin AT sctp.de
> >
> > [mailto:discussion-admin AT sctp.de]
> > On
> > Behalf
> > Of Michael Tuexen
> > Sent: 12. maj 2004 09:07
> > To:
> > lbpe02 AT kom.auc.dk
> > Cc:
> > discussion AT sctp.de
> > Subject: Re: [SCTP-Discussion] SACK trouble...
> >
> > Can you provide the IP-addresses you are using?
> >
> > Best regards
> > Michael
> >
> > On May 11, 2004, at 10:58 PM,
> > lbpe02 AT kom.auc.dk
> > wrote:
> >
> >> Hi!
> >>
> >> We are doing a project measuring handover times on different
> >> technologies
> >> including mSCTP. During our work we have noticed a problem regarding
> >> transmitting SACKs on the interface which communication is handed over
> >> to.
> >>
> >> This is how we do: We have a stream server continuously transmitting
> >> data to a
> >> client running the terminal program, which is included in the sctplib.
> >> When we
> >> want to perform the handover, we use the SETPRIM command, which
> >> transmits an
> >> ASCONF to the server updating its primary path. This works perfectly,
> >> however
> >> the SACKs from the server are still transmitted on the
> >> &#65533;old&#65533;
> >> interface.
> >>
> >> One workaround is to modify the routing table, but we don&#65533;t like
> >> this
> >> solution,
> >> so we hope that someone out there can help :)
> >>
> >> Best regards
> >> Thorbjørn and Lars Students at Aalborg University
> >> _______________________________________________
> >> discussion mailing list
> >> discussion AT sctp.de
> >> http://www.sctp.de/mailman/listinfo/discussion
> >>
> >
> > _______________________________________________
> > discussion mailing list
> > discussion AT sctp.de
> > http://www.sctp.de/mailman/listinfo/discussion
> >
> >
> >
> > _______________________________________________
> > discussion mailing list
> > discussion AT sctp.de
> > http://www.sctp.de/mailman/listinfo/discussion
> >
>
> _______________________________________________
> discussion mailing list
> discussion AT sctp.de
> http://www.sctp.de/mailman/listinfo/discussion
>


--
Dipl.-Ing. Andreas Jungmaier
Computer Networking Technology Group
University Duisburg-Essen
http://www.exp-math.uni-essen.de/~ajung
PGP Key-ID: D382 4AC0

---

• [SCTP-Discussion] SACK trouble..., lbpe02, 05/11/2004
  • Re: [SCTP-Discussion] SACK trouble..., Michael Tuexen, 05/12/2004
    • RE: [SCTP-Discussion] SACK trouble..., Thorbjørn Jørgensen, 05/12/2004
      • Re: [SCTP-Discussion] SACK trouble..., Michael Tuexen, 05/12/2004
      • Re: [SCTP-Discussion] SACK trouble..., Michael Tuexen, 05/22/2004
        • Re: [SCTP-Discussion] SACK trouble..., Andreas Jungmaier, 05/23/2004

---

Archive powered by MHonArc 2.6.19+.