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

Text archives Help


Re: [SCTP-Discussion] SACK trouble...


Chronological Thread 
  • From: Michael Tuexen <Michael.Tuexen AT micmac.franken.de>
  • To: Thorbjørn Jørgensen <thorbjorn AT softdoc.dk>
  • Cc: <discussion AT sctp.de>
  • Subject: Re: [SCTP-Discussion] SACK trouble...
  • Date: Wed May 12 10:27:02 2004
  • List-id: SCTP Discussions <discussion.sctp.de>
That behaviour is OK.

You need to run two networks, for example
10.1.1.0/24 and
10.1.2.0/24
Then it should work.

The reason is that the SCTP path handling must be in tune with the
IP forwarding and the source address selection. Since the sctplib
is a userland implementation it relies on the kernel to do forwarding
and source address selection. To get is in tune you must have an
appropriate network addressing.

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 “old” interface.

One workaround is to modify the routing table, but we don’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







Archive powered by MHonArc 2.6.19+.

Top of page