AT&T normally rejects bogons such as RFC1918, urpf-detected forgeries
from customers,
traffic pointed at internal network routers, etc. However, AT&T's
network does support MPLS,
so if InsightBB is part of the Comcast cloud, it may be that this
_looks_ like the public internet
but is really an MP
At 05:02 PM 10/18/2004, Crist Clark wrote:
Jim Popovitch wrote:
From Comcast Cable, at my home in Atlanta, I can ping 10.10.1.1
which is pong'ed from a private client network hanging somewhere off of
Insight Broadband's network in the North Central part of the US. Why on
god's green earth do n
> From [EMAIL PROTECTED] Mon Oct 18 16:01:42 2004
> Subject: Re: ICMP weirdness
> From: Jim Popovitch <[EMAIL PROTECTED]>
> To: "Stephen J. Wilcox" <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Date: Mon, 18 Oct 2004 17:01:39 -0400
>
>
> On
Comcast uses parts of 10/8 for cable modem addressing, and these are
pingable from within the comcast network. Could this be some other
internal equipment address as well?
On Mon, 18 Oct 2004 17:01:39 -0400, Jim Popovitch <[EMAIL PROTECTED]> wrote:
>
> On Mon, 2004-10-18 at 15:54, Stephen J. Wi
Jim Popovitch wrote:
From Comcast Cable, at my home in Atlanta, I can ping 10.10.1.1
which is pong'ed from a private client network hanging somewhere off of
Insight Broadband's network in the North Central part of the US. Why on
god's green earth do network operators allow such nonsense as thi
On Mon, 2004-10-18 at 15:54, Stephen J. Wilcox wrote:
> why not that seems ok to me.. ?
>
> assuming you accept the 1918 assignment to your cable then its not unreasonable
> that you can get to other end users on that network
Across other non-private IP space? I am not all that familiar w/
RFC
>From Comcast Cable, at my home in Atlanta, I can ping 10.10.1.1
which is pong'ed from a private client network hanging somewhere off of
Insight Broadband's network in the North Central part of the US. Why on
god's green earth do network operators allow such nonsense as this?
-Jim P.
Tracer
