Airplane777
join:2004-06-20
4 edits | reply to cmaenginsb
Re: Monowall general Traffic Shaper queue approaches ?
said by cmaenginsb  :The one thing that breaks this is peer to peer since the software uses your computer to share files with others, so you are getting a lot of upload traffic because of it. You are incorrect as p2p traffic is the most important thing to reduce on your network. Thanks cmaenginsb for your reply.
Last night I set up my AP with DHCP again to make it available again to my neighbors. You might remember that I had one or two neighbors that were constantly sending and receiving data, as noted by the LED on my WISP interface. I checked the Traffic Graph last night and sure enough they were sending out way more data then they were receiving. Looks like they were doing P2P. I wonder if it was a virus on their machine, cause it was non-stop. Or maybe it could be a DOS attack. I don't know that Monowall can defend against DOS attacks?
I'm going to have to find a way to make that P2P stuff at the bottom of the low priority list.
Gee...that video really takes up a lot of BW. I may have to wait til I get a larger pipe.
Since WISPs routinely oversubscribe (as all ISPs usually do), I figure there will be congestion of the downloaded data at times. Maybe there isn't anything much Monowall can do about that with queues? Probably just try to get a larger pipe to the ISP?
If I didn't use hardly any queues at all, as you suggest, and only used up and down rate limits for WISP customers, then does it matter if I rate limit WISP customers by static pipes or virtual pipes? Or are virtual pipes still the best way to rate limit? |
