[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <E096369D937D3A4DB271B382850C5C5F44E71C@pysmail.eicon.com>
Date: Mon, 5 Feb 2007 12:26:14 -0500
From: "Steve Hill" <steve.hill@...logic.com>
To: "Vlad Yasevich" <vladislav.yasevich@...com>
Cc: <netdev@...r.kernel.org>,
<lksctp-developers@...ts.sourceforge.net>,
"Sridhar Samudrala" <sri@...ibm.com>
Subject: RE: [Lksctp-developers] Fw: Intermittent SCTP multihoming breakage
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@...logic.com
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists