John Navas hath wroth:
How did you do it? I tried to simulate the HughesNet FAP traffic control with ipfw and failed. I had some scripts running from cron every 5 minutes to update the traffic statistics and used the result to throttle the traffic to/from the IP address. I also tried the same thing use the MRTG database files. I never could get it working, probably because I'm a lousy programmist.
Quite correct. I've always found it rather pathetic when people start railing about "privacy" when they have no idea just how much they've already given up and continue to give up on a daily basis. Being able to run services with some degree of reliability requires an overview of what's active on the wire, so to speak. This doesn't mean acting UPON the knowledge of what's on that wire. I share, pun intented, your sentiments about the newness of the phenomenon and the emerging nature of the "rules" guiding it.
On Mon, 03 Jul 2006 20:34:28 -0700, Jeff Liebermann wrote in :
I used an inexpensive computer whose primary purpose was to be a firewall, writing my own code to monitor traffic volume and adjust speed caps by LAN address using (as best I can recall) tc and iproute2. For some background, see . (It's been some time since I did it, and I no longer have access to the system -- I'd have to start over from scratch to do it again.)
On Mon, 03 Jul 2006 18:22:37 -0700, Jeff Liebermann wrote in :
That privacy is being compromised in other ways doesn't mean further compromise is warranted. If my ISP were to publish anything about me, I'd promptly switch to a different ISP.
The issue is disclosure of usage to others, and even just the amount of traffic could be a significant problem. For example, when I'm working as an expert in complex litigation, the amount of data I'm sending and receiving could easily be used when I'm being deposed. No thanks.
That is of course you privilege, but I personally don't think that's a reasonable response.
Perhaps, but a sample of one isn't terribly compelling. I've seen unpleasantness arise in shared systems, and think it best to bend over backwards to avoid it.
What person A is doing is really of no concern of anyone else, and with automatic traffic shaping there's no need to make serious loss of privacy part of the price for service.
John Navas hath wroth:
I used the Linux Router HowTo as a reference guide for setting up the QoS part using the scripts from Chonox.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required