Dummynet and limiting packets/upstream useage

Fargo Holiday galaxy.ranger at gmail.com
Mon Aug 9 14:36:45 PDT 2004


Hello everyone,
I'm still sort of new to FreeBSD, and totally new to any sort of
advanced networking, so bear with me please.

Here's the situation: Everything was running off of a D-Link 614
wireless router, but it was getting crushed despite very little actual
bandwidth being used. My buddy and I set up the FreeBSD machine (5.2)
as to act as a router, to serve the two cabled machines and D-Link.
This has improved the overall responsiveness of the internet
connection, but something about the D-Link is still slowing everything
down. I disable the wireless and ping times drop from around 400-800ms
to between 10 and 40ms. We're using WEP and MAC filtering, and use
NetStumbler to check for parasites, so I don't believe it is unknown
machines dragging me down. The one thing I can think of is that the
two laptops used here, both are using Bit Torrent and Shareaza, and
may be eating up the upstream bandwidth and/or generating some massive
quantity of packets.

With that in mind I've been looking into dummynet for some traffic
control. I set it up and it seems to be functioning ok, but it dosen't
seem to be helping. Here are my ipfw statements:

ipfw add pipe 1 ip from 10.0.0.8 to any
ipfw pipe 1 config bw 80Kbit/s queue 20pps delay 150ms
ipfw add pipe 2 ip from any to 10.0.0.8
ipfw pipe 2 config bw 180Kbit/s queue 20pps delay 150ms
ipfw add deny icmp from 10.0.0.8 to any
ipfw add deny icmp from 192.168.0.0/24 to any

I'm not sure if the pps is valid, but I've tried using the queue
number plain and denoting Kb, so I thought I'd give packets per second
a shot. The wired network is the 10.x range, while the wireless
clients are under the 192 net, with 10.0.0.8 being the D-Link "WAN"
interface.

So far, only the icmp rule has helped, and the effect is so marginal
that it could very well be some other factor. I tossed in the 192 rule
while I was tired, I don't think the BSD router has any awareness of
the D-Link's internal ip scheme, so correct me if I'm wrong. Any
thoughts on what else I can try? Am I using the right tool for the
job?

Thanks in advance,
Fargo


More information about the freebsd-net mailing list