Bugtraq mailing list archives
Re: udp packet storms
From: perry () imsi com (Perry E. Metzger)
Date: Tue, 01 Nov 1994 09:05:20 -0500
Steve Simmons says:
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.
The RFCs specify that you must never respond to an ICMP request with a broadcast. However, this may work with UDP echo ports on hosts with defective behavior of the sort we've just been noting. Perry
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 David A. Wagner (Nov 01)
- Re: udp packet storms Perry E. Metzger (Oct 31)