caferace
Golden Member
Sounds pretty interesting.
From: http://spoofer.csail.mit.edu/
"Our methodology is simple. We make software to test spoofing publicly available and ask the community to run it from as many sites as possible. The spoofer program attempts to send a series of spoofed UDP packets to a server on our campus. These packets are designed to test:
* Different classes of spoofed traffic including bogons, RFC1918 and valid sources
* Ability to spoof neighboring, adjacent addresses
* Where along the path filtering is employed
* Presence of a NAT device along the path
Not all spoofed traffic may reach the server if a filter or other policy blocks or rewrites the packets. After sending the spoofed UDP packets, the program establishes a TCP connection with the server informing it of the spoofed packets it tried to send. Based on this transaction, the server records the success or failure of the machine's ability to send spoofed packets in a database. "
-jim
From: http://spoofer.csail.mit.edu/
"Our methodology is simple. We make software to test spoofing publicly available and ask the community to run it from as many sites as possible. The spoofer program attempts to send a series of spoofed UDP packets to a server on our campus. These packets are designed to test:
* Different classes of spoofed traffic including bogons, RFC1918 and valid sources
* Ability to spoof neighboring, adjacent addresses
* Where along the path filtering is employed
* Presence of a NAT device along the path
Not all spoofed traffic may reach the server if a filter or other policy blocks or rewrites the packets. After sending the spoofed UDP packets, the program establishes a TCP connection with the server informing it of the spoofed packets it tried to send. Based on this transaction, the server records the success or failure of the machine's ability to send spoofed packets in a database. "
-jim
