Re: Tracking down IP's
- To: Richard Cobbe <cobbe@directlink.net>
- Cc: debian-user@lists.debian.org
- Subject: Re: Tracking down IP's
- From: Nate Duehr <nate@natetech.com>
- Date: Wed, 3 Jan 2001 18:46:31 -0700
- Message-id: <[🔎] 20010103184631.C3046@natetech.com>
- In-reply-to: <14927.38753.180987.449942@minbar.directlink.net>; from cobbe@directlink.net on Sun, Dec 31, 2000 at 02:30:25PM -0600
- References: <20001231121659.A19593@starport.org> <14927.36654.853098.609075@minbar.directlink.net> <20001231201131.20FD64D846@bullfrog.shadypond.com> <14927.38753.180987.449942@minbar.directlink.net>
On Sun, Dec 31, 2000 at 02:30:25PM -0600, Richard Cobbe wrote:
> Either way, it's still a private IP address range. NOBODY should let
> packets with one of these addresses, either as source or destination, cross
> a network boundary. If the ISP is getting this traffic from its upstrea
> provider, it should configure the router between it and the provider to
> drop all private address ranges, and let the provider know it's leaking
> private IPs.
Hmmm. Wish my ISP followed those rules. I can root around their
10.x.x.x network without problems. And a friend on Qwest/USWest was
able to do the same. I originally became curious about it when I
realized that traces outbound show the 10.x.x.x network and my DSL
device is configured in a layer-2 bridging mode.
Someone was VERY lazy in their network design meetings. Tsk tsk.
Betcha' the router jocks at both places have CCNA certifcations
or higher from Cisco too. Boy howdy!
--
Nate Duehr <nate@natetech.com>
GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.
Reply to: