Thread: 127.0.0.1
View Single Post
Old 28-01-2004, 16:05   #10
Stuartbe
Inactive
 
Join Date: Jan 2023
Posts: 4,984
Stuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this point
Stuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this pointStuartbe is an unknown quantity at this point
Re: 127.0.0.1

Quote:
Originally Posted by altis
This prompts me to ask two questions:
1) Is the sender trying to achieve anything other than tie my router in knots (and if so, how can they expect a reply)?
2) Should NTL be passing me packets that have so obviously been spoofed?
Trouble is that spoofed packets can be generated to apear as they are from other sources as well as a loopback address.

The only way you can truly block these packets is to filter them as they leave the BGR of the isp. After this piont it is hard to identify them correctly.

If every isp in the world did this most dos, ddos and all rddos attacks would stop and the net would be a far better place.

Just my 2p's worth !
Stuartbe is offline   Reply With Quote