From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tobias Geiger Date: Thu, 21 Mar 2002 13:28:02 +0000 Subject: Re: [LARTC] Sharing incoming traffic Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org For me ingress works great. ok, i more or less copy/pasted from the "wondershaper" :) I guess it's not good to have a rate of 8000bps AND a burst of 10k=20 I'm also not shure, if the iptables-marks get noticed, but it seems so, as you said there is a shaping effect. but as your iptable-rule is so generally i'd say there's no reason not to use the appropriate u32 filter instead of fw. VMWare shouldn't be the problem, at least i never had ones. Tell me, if tuning rate/burst helped Greetings=20 Tobias On Thu, Mar 21, 2002 at 12:29:09PM +0000, Juli=E1n Mu=F1oz wrote: >=20 > I've done my first test with ingress, >=20 > 2 ftps, and I've seen that the bandwidth is not shared "very well". >=20 > From the point of view of a user, his transfer stops suddenly, and > restarts 20 seconds (or more!) later. Then the other has to wait !! I > observ a kind of feedback process, beeing the interval of stopped traffic > bigger each time, during the transference. >=20 > The bandwidth is limited to 64.000 bit per second, killing packets. >=20 > In fact it is not a real ethernet link, and the filter is on a vmware > machine computer, so maybe this test is not valid. >=20 > Anyone knows more about this behaviour ?? >=20 > Could I optimize it playing with burst and mpu ? >=20 > Or am I doing something really bad ? >=20 > Thank you, >=20 > Here's my filter: >=20 > iptables -A PREROUTING -i eth0 -t mangle --protocol all -j MARK --set-mark > 1 >=20 > tc qdisc add dev eth0 handle ffff: ingress >=20 > tc filter add dev eth0 parent ffff: protocol ip prio 5 handle 1 fw \ > police rate 8000bps burst 10k mpu 64b drop flowid :1 >=20 >=20 > --=20 >=20 > __o > _ \<_ > (_)/(_) >=20 > Saludos de Juli=E1n > EA4ACL > -.- >=20 > Foro Wireless Madrid > http://opennetworks.rg3.net >=20 >=20 >=20 > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/