Gianluca Montecchi <[EMAIL PROTECTED]> wrote: >I am some troubles with iproute2. > >I am working with the kernel versione 2.4.0-test9 on a laptop with a >pcmcia network card. > >I am trying to setup the laptop to have some control over the bandwidth, using >iproute2.
Heh, good luck. It took me a couple of weeks and a high "aargh!" factor to get it working really well at work. >Following the "Linux 2.4 Advanced Routing HOWTO", I try: > >tc qdisc add dev eth0 root handle 10: cbq bandwidth 10Mbit avpkt 1000 Looks sane, although you may also have to give the 'allot' option at the end there (1514 for Ethernet). >and as results, i get > >RTNETLINK answers: Invalid argument Unfortunately, rtnetlink has a bad habit of doing that if the options you give to tc are at all wrong. It can be *extremely* unhelpful sometimes. Now and then tc will warn you cryptically about a badly formatted command line, but not always (e.g. it tends not to spot options that are out of range). >I have compiled the kernel with all the networking option activated and >I have all the modules, but I cannot find where is the problem. Have you turned on the configure option CONFIG_EXPERIMENTAL, under "Code maturity level options", which asks the configure scripts to prompt you about development/incomplete code? You need that to get QoS support. You should have a menu at the end of "Networking options" which shows you quality-of-service-related stuff, and you might as well enable most of that. >Antother question: once I have set-up the traffic control, how I can >test it ? 'tc -s qdisc list dev eth0', 'tc -s class list dev eth0', and 'tc -s filter list dev eth0' will show you statistics on how much data has passed through your various qdiscs, classes, and filters respectively. Aside from that you just have to come up with some benchmarks. A nearby web server that you control is useful for this. -- Colin Watson [EMAIL PROTECTED]
