From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Steve Hill <steve.hill@dialogic.com>
Cc: netdev@vger.kernel.org, lksctp-developers@lists.sourceforge.net,
Sridhar Samudrala <sri@us.ibm.com>
Subject: Re: [Lksctp-developers] Fw: Intermittent SCTP multihoming breakage
Date: Mon, 05 Feb 2007 15:34:32 -0500 [thread overview]
Message-ID: <45C794D8.30304@hp.com> (raw)
In-Reply-To: <E096369D937D3A4DB271B382850C5C5F44E71C@pysmail.eicon.com>
Hi Steve
would you mind terribly, changing the -d "$net" to the
-i "$net", and run the script with the interface name instead?
The reason is, that I see 2 different behaviors between blocking
by interface and blocking by IP and would like to find out if
you see it too.
When I block at the interface ( -i eth1 in my case), I see
the path failover happen and flow if resumed.
When I block at the ip address, I see the path failover
in an odd state. It looks like it happened, but the flow is
not resumed. Receive still doesn't get traffic. I think I might
be running a buggy receiver, but I am not 100% sure. In my
case, the sender if running 2.6.10-rc7 and receiver is running
Ubuntu 2.6.17-10.
I'll try running against a different receiver as well.
-vlad
Steve Hill wrote:
> Vlad Yasevich wrote on 05 February 2007 17:08:
>
>> 1. What did you set the sinfo_timetolive to?
>
> I presume you mean the timetolive parameter of sctp_sendmsg()? - this
> was set to 1400ms (as previously mentioned, this was in error but it
> does appear to have highlighted a problem with the stack itself).
>
>> 2. What specific netfilter rule to do use to simulate
>> network outage?
>> I was using '-t filter -A INPUT -i eth0 -p sctp -j DROP'
>
> iptables -A INPUT -d 192.168.2.0/24 -p sctp -j DROP
>
>> Just trying to get more info to simulate this. My prior attempts
>> recovered quickly with my patch.
>
> I usually (but not always - sometimes it happens on the first attempt)
> have to add and remove the iptables rule a few times while running
> traffic over the association in order to reproduce the problem. I'm
> running traffic at a rate of around 500 data chunks per second. Each
> data chunk has a 44 octet payload.
>
> The script I'm using to toggle the iptables rule is below:
>
> ----------
> #!/bin/sh
>
> net="$1"
>
> flush() {
> iptables -F
> echo "Flush"
> exit
> }
>
> trap flush EXIT
>
> while true; do
> iptables -A INPUT -d "$net" -p sctp -j DROP
> echo "set"
> sleep 5
> iptables -F
> echo "flushed"
> sleep 5
> done
> ----------
>
> - Steve Hill
> Software Engineer
> Dialogic
> Fordingbridge, Hampshire, UK
> +44-1425-651392
> steve.hill@dialogic.com
>
next prev parent reply other threads:[~2007-02-05 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 17:26 [Lksctp-developers] Fw: Intermittent SCTP multihoming breakage Steve Hill
2007-02-05 20:34 ` Vlad Yasevich [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-06 9:26 Steve Hill
2007-02-06 21:48 ` Vlad Yasevich
2007-02-07 20:45 ` Vlad Yasevich
2007-02-08 14:07 ` Steve Hill
2007-02-08 14:15 ` Vlad Yasevich
2007-02-05 16:53 Steve Hill
2007-02-05 17:07 ` Vlad Yasevich
2007-02-05 14:13 Steve Hill
2007-02-05 16:39 ` Vlad Yasevich
2007-01-03 23:46 Andrew Morton
2007-01-04 0:59 ` Sridhar Samudrala
2007-01-10 11:55 ` Steve Hill
2007-01-10 20:10 ` Sridhar Samudrala
2007-01-11 10:10 ` Steve Hill
2007-01-25 16:32 ` [Lksctp-developers] " Vlad Yasevich
2007-01-25 16:37 ` Vlad Yasevich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45C794D8.30304@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
--cc=steve.hill@dialogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).