nanog mailing list archives
Re: New IPv4 Allocation to ARIN
From: Petri Helenius <pete () he iki fi>
Date: Sun, 18 Jan 2004 15:03:22 +0200
jlewis () lewis org wrote:
It's those dang Nachi-sized ICMP echo/echo-replies. We block those at all our transit points and dial-up ports. Nachi was killing our cisco access-servers until we did this to stop the spread.Unfortunately, this breaks Windows tracert as it uses 92-byte echo requests. Use a "real" traceroute, and you won't see this problem.
I know what they are and how to get around them. I just look down on people dropping my packets in their backbones without reason. Pete
Current thread:
- Re: New IPv4 Allocation to ARIN, (continued)
- Re: New IPv4 Allocation to ARIN Richard A Steenbergen (Jan 19)
- Re: New IPv4 Allocation to ARIN Owen DeLong (Jan 19)
- Re: New IPv4 Allocation to ARIN william (Jan 19)
- 1/8 and 2/8 (was Re: New IPv4 Allocation to ARIN) John Palmer (Jan 19)
- Re: 1/8 and 2/8 (was Re: New IPv4 Allocation to ARIN) Petri Helenius (Jan 19)
- Re: New IPv4 Allocation to ARIN Petri Helenius (Jan 16)
- Re: New IPv4 Allocation to ARIN jlewis (Jan 16)
- Re: New IPv4 Allocation to ARIN william (Jan 16)
- Nachi (was Re: New IPv4 Allocation to ARIN) Michael Lewinski (Jan 16)
- Re: New IPv4 Allocation to ARIN Petri Helenius (Jan 18)
- Re: New IPv4 Allocation to ARIN Pete Templin (Jan 18)
- Re: New IPv4 Allocation to ARIN Petri Helenius (Jan 18)
- Re: New IPv4 Allocation to ARIN william (Jan 19)
- Re: New IPv4 Allocation to ARIN Pete Templin (Jan 19)