[45192] in North American Network Operators' Group
Re: traffic filtering
daemon@ATHENA.MIT.EDU (Jake Khuon)
Mon Jan 21 18:28:33 2002
Message-Id: <200201212327.g0LNR7Yv010498@llama.wooj.com>
From: "Jake Khuon" <khuon@NEEBU.Net>
To: Jared Mauch <jared@puck.Nether.net>
In-reply-to: Jared Mauch's message of Mon, 21 Jan 2002 18:01:44 -0500.
<20020121230144.GC4644@puck.nether.net>
Reply-To: khuon@NEEBU.Net (Jake Khuon)
Date: Mon, 21 Jan 2002 15:26:37 -0800
Errors-To: owner-nanog-outgoing@merit.edu
### On Mon, 21 Jan 2002 18:01:44 -0500, Jared Mauch <jared@puck.Nether.net>
### casually decided to expound upon Stephen Griffin
### <stephen.griffin@rcn.com> the following thoughts about "Re: traffic
### filtering":
JM> On Mon, Jan 21, 2002 at 05:53:16PM -0500, Stephen Griffin wrote:
JM> >
JM> > I'm curious about how many networks completely filter all traffic to
JM> > any ip address ending in either ".0" or ".255".
JM>
JM> they will have problems reaching people who are now using /31s
JM> on links that cover the last /31 and first /31 of the /24 that they reside
JM> in.
I guess depending on where one places the filter (and to whom it is
applied), one could argue that this is a good thing. It does make
troubleshooting a bit pesky however.
I once moved a router and forgot to reconfigure the IP address on its serial
interface. Most "everything" worked fine and didn't discover my mistake
until I was troubleshooting my VOIP tunnel. |8^)
--
/*===================[ Jake Khuon <khuon@NEEBU.Net> ]======================+
| Packet Plumber, Network Engineers /| / [~ [~ |) | | --------------- |
| for Effective Bandwidth Utilisation / |/ [_ [_ |) |_| N E T W O R K S |
+=========================================================================*/
