In tc, with egress you control outbound traffic, with ingress inbound. Usually only outbound traffic is controlled, as you can't really force others to send slower (see more here http://lartc.org/howto/lartc.qdisc.html) On Monday 09 August 2004 17:13, Bill Gradwohl wrote: > The recent thread titled: > working ftp shaping, i think > provided a script example where 100Mbps was specified as the rate for a > typical NIC. > > If that NIC is connected to a switch, chances are that it runs at > 100Mbps in each direction concurrently - duplexed Writing a rule that > specifies a 100Mbps rate and thereby a 100Mbps ceil, limits the > connection to half the available bandwidth. > > I haven't seen anything in tc (not iptables) that addresses direction - > inbound or outbound. > Is there a way of writing rules that take duplexing into account so that > you end up with 2 virtual devices, each capable of 100Mbps, but the > traffic is direction specific? _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
