Bugtraq mailing list archives
Re: udp packet storms
From: newsham () zang kcc hawaii edu (Tim Newsham)
Date: Tue, 1 Nov 1994 15:04:19 -1000 (HST)
This leads to a bug I've literally been afraid to test: How about forging a ping packet with source and destination address YOUR.NET.HERE.255? Should cause a brief but interesting storm, while doing only minimal loading on the forger.
when you send out a ping it is a ICMP_ECHO packet. When the remote sends a reply it is a ICMP_ECHOREPLY packet. A host will not reply to an ICMP_ECHOREPLY so you're safe. Tim N.
Current thread:
- Re: udp packet storms Mike Raffety (Oct 31)
- Re: udp packet storms Perry E. Metzger (Oct 31)
- Re: udp packet storms Darren Reed (Nov 01)
- Re: udp packet storms Steve Simmons (Nov 01)
- Re: udp packet storms Perry E. Metzger (Nov 01)
- Re: udp packet storms Tim Newsham (Nov 01)
- Re: udp packet storms Pete Shipley (Nov 03)
- bizzare ftp stuff... Tim Scanlon (Nov 03)
- <Possible follow-ups>
- Re: udp packet storms Perry E. Metzger (Oct 31)
- Re: udp packet storms Charles Howes (Oct 31)
- Re: udp packet storms Mike Raffety (Nov 01)
- Re: udp packet storms David A. Wagner (Nov 01)
- Re: udp packet storms - ping death Charles Howes (Nov 02)
- Re: udp packet storms - ping death David A. Wagner (Nov 02)
- Re: udp packet storms - ping death Karl Strickland (Nov 03)
- Re: udp packet storms - ping death Perry E. Metzger (Nov 02)
- Re: udp packet storms David A. Wagner (Nov 01)
- Re: udp packet storms Perry E. Metzger (Oct 31)