|
|||||||||||
|
Re: ICMP Unreachables
From: Jeff Nathan <jeff(at)snort.org>
Date: Tue Feb 25 2003 - 18:07:06 EST -----BEGIN PGP SIGNED MESSAGE-----
Greetings, I went through this very issue when working on the current version nemesis. While it uses the older libnet library, you can reference my solution to the problem. (http://www.snort.org/~jeff/nemesis) An ICMP unreachable will contain the original IP header (including options, so make sure to account for this when allocating memory and possibly adding IP options to your original IP header within the unreachable packet) and 8 bytes from the original packet's transport header. So, the idea is that instead of thinking of an unreachable as carrying 8 random bytes of payload, think of those 8 bytes as what would have been the first 8 bytes of the transport header that generated the ICMP unreachable packet. In the case of UDP, you can fit the entire header in the ICMP unreachable packet. In the case of TCP, you obviously won't get the entire header in there. I believe the purpose of those 8 bytes is to be informative as to what packet caused the error (debugging). The choice as to what is placed in those 8 bytes is dependent upon the packet that triggered the unreachable. Or in your case, the type of unreachable you want to simulate. I hope this helps.
-----BEGIN PGP SIGNATURE-----
iD8DBQE+W/cdEqr8+Gkj0/0RApFpAJ9a0G9L5uU7WwA/eRIEKuqovTpUSACcCqOY
XlP+vCrnK8guLNJvxq4K3Z0=
To unsubscribe, e-mail: libnet-unsubscribe@securityfocus.com For additional commands, e-mail: libnet-help@securityfocus.com Received on Tue Feb 25 18:07:12 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:02:22 EDT |
||||||||||
|
|||||||||||