Part of the problem is all the totally clueless ISPs which don't do proper egress filtering. That is, they don't filter out outgoing packets with falsified sender addresses.
Part of the problem is all the totally clueless ISPs which don't do proper egress filtering. That is, they don't filter out outgoing packets with falsified sender addresses >>
Clueless eh?
If I am assuming correctly, the general public in the world has had years to pick up trash in the ditches and fields left by a small percentage of the non-caring population. But I still see very few people doing this, possibly the same percentage of ISP's who perform these big brother techniques.
Come to think of it, what sysadmin is going to give you the time of day?
With internet service battling for the ~$4.95/mo arena, I don't see much use in hiring but one sysadmin for this position, and making sure he can handle hundreds of thousands of people a month with his setup, pay him $200k/yr, and outsource the tech support.
The day ISPs start keeping the bad guys away from you is the day you convince the general public that internet access is really worth that few extra bucks, and next time, choose your local ISP.
Once this is accomplished, I'll configure my router to that specification, and we can go on our merry ways.
Until then my routers stay the way they are, you can have your "Make the internet a safer place" cult, and we may see each other again.
My schema is designed for maximum scalibility, minimum filtering (due to load), and most of all, 99.999.
Egress filtering (Score:5, Insightful)
They've had years to do that, and still don't.
Re:Egress filtering (Score:1)
Clueless eh?
If I am assuming correctly, the general public in the world has had years to pick up trash in the ditches and fields left by a small percentage of the non-caring population. But I still see very few people doing this, possibly the same percentage of ISP's who perform these big brother techniques.
Come to think of it, what sysadmin is going to give you the time of day?
With internet service battling for the ~$4.95/mo arena, I don't see much use in hiring but one sysadmin for this position, and making sure he can handle hundreds of thousands of people a month with his setup, pay him $200k/yr, and outsource the tech support.
The day ISPs start keeping the bad guys away from you is the day you convince the general public that internet access is really worth that few extra bucks, and next time, choose your local ISP.
Once this is accomplished, I'll configure my router to that specification, and we can go on our merry ways.
Until then my routers stay the way they are, you can have your "Make the internet a safer place" cult, and we may see each other again.
My schema is designed for maximum scalibility, minimum filtering (due to load), and most of all, 99.999.