Most tier 1 and 2 ISPs upgrade their code in a timely fashion. They're also on a mix of Cisco, Juniper, and Foundry (and I hear someone actually uses Extreme). Some third-rate companies or pretenders might have problems in a situation like this, but the effect has been greatly exaggerated.
The disclosure aspect is sad, but it's not like this is anything new. Might want to get the lawyer hooked up *after* you quit your job to release the paper, and *before* you head out to the conference. Don't expect any different behavior from companies until the next regime change...
Thanks for the actual good reply to this - I wish there was a way to do it with Apache - I hope our developers' scripts mod well to work with Zeus;) We have been looking at it for a long time, but we have to make a case for it at work.
Are the Slashdot readers this ignorant? Everyone else suggested QoS methods that would do nothing to help *per* user connections. Are people really this obtuse? The first poster and I were very clear about we wanted to do, and people came up with pretty lame stuff that was way off the mark.
The problem with the IT industry is that there are so many clueless people that have the "experience", and make good money. They dilute the talent and make it hard for a real wiz to make money anymore. How many people do you know that fall in the category: "Knows enough to be dangerous"?
I am having the same problem, and I think you guys are missing the point. He said 4GB an hour, which means he probably has an OC-3, OC-12, or Gigabit Ethernet connection.
"Blocking" network appliances such as Packeteer can't handle these high rates, and even if they had gigabit interfaces, they would only be able to do 600-800mbps on them.
None of the kernel QoS/queueing options I've seen allow for anything other than classifying traffic or "fair" queueing. None of this seems to help someone that wants to limit all webserver connections to 2mbps - everything here is expecting an IP range, ports, or something to distinguish by. What if I don't want to?
Apache needs real per connection, per user, and per IP rate limiting. mod_throttle and everything else I've seen has to starve connections after they perform too well. How about something that hard limits connections to 2mbps/sec. I will pay for anything that can do that for Apache today...
Slashdot Mirror
Most tier 1 and 2 ISPs upgrade their code in a timely fashion. They're also on a mix of Cisco, Juniper, and Foundry (and I hear someone actually uses Extreme). Some third-rate companies or pretenders might have problems in a situation like this, but the effect has been greatly exaggerated.
The disclosure aspect is sad, but it's not like this is anything new. Might want to get the lawyer hooked up *after* you quit your job to release the paper, and *before* you head out to the conference. Don't expect any different behavior from companies until the next regime change...
Thanks for the actual good reply to this - I wish there was a way to do it with Apache - I hope our developers' scripts mod well to work with Zeus ;) We have been looking at it for a long time, but we have to make a case for it at work.
Are the Slashdot readers this ignorant? Everyone else suggested QoS methods that would do nothing to help *per* user connections. Are people really this obtuse? The first poster and I were very clear about we wanted to do, and people came up with pretty lame stuff that was way off the mark.
The problem with the IT industry is that there are so many clueless people that have the "experience", and make good money. They dilute the talent and make it hard for a real wiz to make money anymore. How many people do you know that fall in the category: "Knows enough to be dangerous"?
I am having the same problem, and I think you guys are missing the point. He said 4GB an hour, which means he probably has an OC-3, OC-12, or Gigabit Ethernet connection.
"Blocking" network appliances such as Packeteer can't handle these high rates, and even if they had gigabit interfaces, they would only be able to do 600-800mbps on them.
None of the kernel QoS/queueing options I've seen allow for anything other than classifying traffic or "fair" queueing. None of this seems to help someone that wants to limit all webserver connections to 2mbps - everything here is expecting an IP range, ports, or something to distinguish by. What if I don't want to?
Apache needs real per connection, per user, and per IP rate limiting. mod_throttle and everything else I've seen has to starve connections after they perform too well. How about something that hard limits connections to 2mbps/sec. I will pay for anything that can do that for Apache today...
Forgive me if I have overlooked the obvious...