Hi, On Mon, 16 Apr 2007 09:00:04 -0700 Grant <[EMAIL PROTECTED]> wrote:
> > > After a lot of testing, these numbers seem to give me the best > > > performance as far as bittorrent download speed. > > > How can that be? Is DOWNLINK my upload and UPLINK my download? > > > > Hm, usually not. Are you by chance shaping the internal (i.e. LAN) > > interface on a router? Then, of course, it would make sense (except > > from the fact that shaping your actual bottle neck, i.e. Internet > > connection, would make more sense). > > Thanks a lot for that. I switched the interface to eth0 and reversed > the DOWNLINK and UPLINK values. :-) > I switched to wshaper from wshaper.htb and now ssh and browsing seem a > lot more responsive. Could that be because I'm missing something in > my kernel that I need for htb? I don't get any errors when restarting > the firewall. I'm not sure about that. I did only try wshaper.htb and didn't manage to fit it to my needs completely either (see below). The kernel configuration help tells a good bunch of info, IIRC. > One other thing is if I don't limit the upload rate within my > bittorrent client, it really goes nuts and everything else suffers. I > don't see how that's possible with UPLINK and the bittorrent source > and destination ports defined. Well, the problem is that limiting inbound traffic is absolutely unreliable. From the numbers given, I guess you're on DSL, right? (Just like me, BTW.) If you were on cable, well, there's not a lot you can do since the media is unreliable w/ regard to your share of it. But I think you're talking about stable bandwith. If you're not lucky, all those peers out there flood your inbound traffic line. You can't shape this on your side, it's absolutely an issue to be resolved on the DSLAM your DSL modem connects to. OTOH, those routers usually don't do very sophisticated packet inspection... So it's all about cutting expensive connections down very early. This is the even more true for applications that are somewhat hasty in changing their requested and incoming traffic. So first try cutting down the maximum even more. Take a few measures and see what is actually saturated: upstream or downstream. If it's in fact neither, it's a configuration issue. > What I'd really like to do is limit the bittorrent upload rate so > Verizon doesn't throttle my connection. Can I do that with The Wonder > Shaper without limiting the total upload rate? I don't trust the > bittorrent clients I use to limit it. Did you consider trickle? It's lightweight and easy and works on application layer (i.e. usermode) by overloading glibc functions... If you're not trying to manage a whole set of clients behind a router, that would be an option. And to be honest: I've dumped QoS on my linux-based router. I've never managed to fully saturize my link the way I wanted it using it. I'm not completely sure if I should blame it on the 125MHz the poor CPU's running at (it's a WiFi AP, the Linksys WAP54g) or the 8MB of RAM... -hwh -- [EMAIL PROTECTED] mailing list
