Tracert Questions

Hi All,

I have been trying to solve a VPN problem I am having. While trying to
find the problem, I have performed several tracert's from the two
locations. I am not a IP genius, but I have noticed that when doing
the routing, Somewhere along the way, I always seem to see a local IP
address. In this case a 192.168.25.113

1 7 ms 1 ms <1 ms 192.168.2.1
2 20 ms 16 ms 16 ms h-69-3-229-1.chcgilgm.covad.net
[69.3.229.1]
3 19 ms 15 ms 16 ms 192.168.25.113
4 19 ms 16 ms 15 ms ge-4-1-166.ipcolo1.Chicago1.Level3.net
[166.90..81]
5 21 ms 16 ms 16 ms ae-14-53.car4.Chicago1.Level3.net
[4.68.101.72]
......

This does not seem normal to me. Am I correct? What would be causing
this type of routing?

Thanks for any input.

smlunatick
Tue Apr 22 09:49:41 PDT 2008

This is correct! You need to know that whenever you connect to a VPN
"service" end-point (server or VPN rouer) the default, normal setting is to
route "all" traffic (either the remote network requests or all Internet
requests) over to the remote network and use the remote network's "default"
gateway for Internet access.

Could you please post the problem you are having with the VPN so others
"responders" could guide you with possible better results.

On 22/04/2008 anonymous@mailinator.com wrote:
>Hi All,
>
>I have been trying to solve a VPN problem I am having. While trying to
>find the problem, I have performed several tracert's from the two
>locations. I am not a IP genius, but I have noticed that when doing
>the routing, Somewhere along the way, I always seem to see a local IP
>address. In this case a 192.168.25.113
>
> 1 7 ms 1 ms <1 ms 192.168.2.1
> 2 20 ms 16 ms 16 ms h-69-3-229-1.chcgilgm.covad.net
>[69.3.229.1]
> 3 19 ms 15 ms 16 ms 192.168.25.113
> 4 19 ms 16 ms 15 ms ge-4-1-166.ipcolo1.Chicago1.Level3.net
>[166.90..81]
> 5 21 ms 16 ms 16 ms ae-14-53.car4.Chicago1.Level3.net
>[4.68.101.72]
>......
>
>This does not seem normal to me. Am I correct? What would be causing
>this type of routing?
>
>Thanks for any input.

anonymous
Tue Apr 22 12:00:27 PDT 2008

Thanks,

The problem I am having with the VPN using Netgear Prosafe and a
Netgear router (I have not managed to find a solution from Netgear) is
that I can connect the client to the router. Both the client
connection monitor and the Router show a connection, but the client PC
can not see, ping or directly access anything on the router side.

Also, the 192.168.25.113 I mentioned on the tracert is not part of
either of my sub domains. I was not aware of the fact that IP traffic
would route through a private domain to get somewhere else as opposed
to only public addresses.

On Tue, 22 Apr 2008 12:49:41 -0400, "smlunatick" <yveslec@gmail.com>
wrote:

>This is correct! You need to know that whenever you connect to a VPN
>"service" end-point (server or VPN rouer) the default, normal setting is to
>route "all" traffic (either the remote network requests or all Internet
>requests) over to the remote network and use the remote network's "default"
>gateway for Internet access.
>
>Could you please post the problem you are having with the VPN so others
>"responders" could guide you with possible better results.
>
>On 22/04/2008 anonymous@mailinator.com wrote:
>>Hi All,
>>
>>I have been trying to solve a VPN problem I am having. While trying to
>>find the problem, I have performed several tracert's from the two
>>locations. I am not a IP genius, but I have noticed that when doing
>>the routing, Somewhere along the way, I always seem to see a local IP
>>address. In this case a 192.168.25.113
>>
>> 1 7 ms 1 ms <1 ms 192.168.2.1
>> 2 20 ms 16 ms 16 ms h-69-3-229-1.chcgilgm.covad.net
>>[69.3.229.1]
>> 3 19 ms 15 ms 16 ms 192.168.25.113
>> 4 19 ms 16 ms 15 ms ge-4-1-166.ipcolo1.Chicago1.Level3.net
>>[166.90..81]
>> 5 21 ms 16 ms 16 ms ae-14-53.car4.Chicago1.Level3.net
>>[4.68.101.72]
>>......
>>
>>This does not seem normal to me. Am I correct? What would be causing
>>this type of routing?
>>
>>Thanks for any input.

smlunatick
Tue Apr 22 13:20:43 PDT 2008

On Apr 22, 3:00=A0pm, anonym...@mailinator.com wrote:
> Thanks,
>
> The problem I am having with the VPN using Netgear Prosafe and a
> Netgear router (I have not managed to find a solution from Netgear) is
> that I can connect the client to the router. Both the client
> connection monitor and the Router show a connection, but the client PC
> can not see, ping or directly access anything on the router side.
>
> Also, the 192.168.25.113 I mentioned on the tracert is not part of
> either of my sub domains. I was not aware of the fact that IP traffic
> would route through a private domain to get somewhere else as opposed
> to only public addresses.
>
> On Tue, 22 Apr 2008 12:49:41 -0400, "smlunatick" <yves...@gmail.com>
> wrote:
>
>
>
> >This is correct! =A0You need to know that whenever you connect to a VPN
> >"service" end-point (server or VPN rouer) =A0the default, normal setting =
is to
> >route "all" traffic (either the remote network requests or all Internet
> >requests) over to the remote network and use the remote network's "defaul=
t"
> >gateway for Internet access.
>
> >Could you please post the problem you are having with the VPN so others
> >"responders" could guide you with possible better results.
>
> >On 22/04/2008 anonym...@mailinator.com wrote:
> >>Hi All,
>
> >>I have been trying to solve a VPN problem I am having. While trying to
> >>find the problem, I have performed several tracert's from the two
> >>locations. I am not a IP genius, but I have noticed that when doing
> >>the routing, Somewhere along the way, I always seem to see a local IP
> >>address. In this case a 192.168.25.113
>
> >> 1 =A0 =A0 7 ms =A0 =A0 1 ms =A0 =A0<1 ms =A0192.168.2.1
> >> 2 =A0 =A020 ms =A0 =A016 ms =A0 =A016 ms =A0h-69-3-229-1.chcgilgm.covad=
.net
> >>[69.3.229.1]
> >> 3 =A0 =A019 ms =A0 =A015 ms =A0 =A016 ms =A0192.168.25.113
> >> 4 =A0 =A019 ms =A0 =A016 ms =A0 =A015 ms =A0ge-4-1-166.ipcolo1.Chicago1=
.Level3.net
> >>[166.90..81]
> >> 5 =A0 =A021 ms =A0 =A016 ms =A0 =A016 ms =A0ae-14-53.car4.Chicago1.Leve=
l3.net
> >>[4.68.101.72]
> >>......
>
> >>This does not seem normal to me. Am I correct? What would be causing
> >>this type of routing?
>
> >>Thanks for any input.- Hide quoted text -
>
> - Show quoted text -

The confusing part was / in the fact you trace "log" show 192.168.2.1
and 192.168.25.113. These are two valid private IP subnets that can /
should be used for Local Area Networks (LAN.) Domains are ignored.

Check both networks in order to see which correct IP subnets are used.

Bruce
Tue Apr 22 14:28:30 PDT 2008

>The confusing part was / in the fact you trace "log" show 192.168.2.1
>and 192.168.25.113. These are two valid private IP subnets that can /
>should be used for Local Area Networks (LAN.) Domains are ignored.
>
>Check both networks in order to see which correct IP subnets are used.


Sorry about the confusion.
192.168.2.1 is my dsl modem
The path then seems to head out to Covad
Then it seems to go into a private network within Covad. This is not
my Domain. Covad is my provider but once the trace exits 192.168.2.1 I
assume it is in the public sector.

It appears that Covad is routing through a private domain to send the
packets back to level3 on its way to the world.

I can only assume that even though I have a static address
(69.3.229.239) that the address must point to covads network not my
end point.

The reason I ask is that I was wondering if these other "networks" may
be interfering with my VPN connection.





On Tue, 22 Apr 2008 13:20:43 -0700 (PDT), smlunatick
<yveslec@gmail.com> wrote:

>On Apr 22, 3:00 pm, anonym...@mailinator.com wrote:
>> Thanks,
>>
>> The problem I am having with the VPN using Netgear Prosafe and a
>> Netgear router (I have not managed to find a solution from Netgear) is
>> that I can connect the client to the router. Both the client
>> connection monitor and the Router show a connection, but the client PC
>> can not see, ping or directly access anything on the router side.
>>
>> Also, the 192.168.25.113 I mentioned on the tracert is not part of
>> either of my sub domains. I was not aware of the fact that IP traffic
>> would route through a private domain to get somewhere else as opposed
>> to only public addresses.
>>
>> On Tue, 22 Apr 2008 12:49:41 -0400, "smlunatick" <yves...@gmail.com>
>> wrote:
>>
>>
>>
>> >This is correct!  You need to know that whenever you connect to a VPN
>> >"service" end-point (server or VPN rouer)  the default, normal setting is to
>> >route "all" traffic (either the remote network requests or all Internet
>> >requests) over to the remote network and use the remote network's "default"
>> >gateway for Internet access.
>>
>> >Could you please post the problem you are having with the VPN so others
>> >"responders" could guide you with possible better results.
>>
>> >On 22/04/2008 anonym...@mailinator.com wrote:
>> >>Hi All,
>>
>> >>I have been trying to solve a VPN problem I am having. While trying to
>> >>find the problem, I have performed several tracert's from the two
>> >>locations. I am not a IP genius, but I have noticed that when doing
>> >>the routing, Somewhere along the way, I always seem to see a local IP
>> >>address. In this case a 192.168.25.113
>>
>> >> 1     7 ms     1 ms    <1 ms  192.168.2.1
>> >> 2    20 ms    16 ms    16 ms  h-69-3-229-1.chcgilgm.covad.net
>> >>[69.3.229.1]
>> >> 3    19 ms    15 ms    16 ms  192.168.25.113
>> >> 4    19 ms    16 ms    15 ms  ge-4-1-166.ipcolo1.Chicago1.Level3.net
>> >>[166.90..81]
>> >> 5    21 ms    16 ms    16 ms  ae-14-53.car4.Chicago1.Level3.net
>> >>[4.68.101.72]
>> >>......
>>
>> >>This does not seem normal to me. Am I correct? What would be causing
>> >>this type of routing?
>>
>> >>Thanks for any input.- Hide quoted text -
>>
>> - Show quoted text -
>
>The confusing part was / in the fact you trace "log" show 192.168.2.1
>and 192.168.25.113. These are two valid private IP subnets that can /
>should be used for Local Area Networks (LAN.) Domains are ignored.
>
>Check both networks in order to see which correct IP subnets are used.

Jack
Tue Apr 22 15:13:33 PDT 2008

Hi
Internet traffic does not flow directly from your connection to the
destination.
It Router and re Router according to traffic demands and business
arrangement between ISPs.
Jack (MVP-Networking).

<anonymous@mailinator.com> wrote in message
news:imor0458t049f5d2dedu23a3ln1k3k0mml@4ax.com...
> Hi All,
>
> I have been trying to solve a VPN problem I am having. While trying to
> find the problem, I have performed several tracert's from the two
> locations. I am not a IP genius, but I have noticed that when doing
> the routing, Somewhere along the way, I always seem to see a local IP
> address. In this case a 192.168.25.113
>
> 1 7 ms 1 ms <1 ms 192.168.2.1
> 2 20 ms 16 ms 16 ms h-69-3-229-1.chcgilgm.covad.net
> [69.3.229.1]
> 3 19 ms 15 ms 16 ms 192.168.25.113
> 4 19 ms 16 ms 15 ms ge-4-1-166.ipcolo1.Chicago1.Level3.net
> [166.90..81]
> 5 21 ms 16 ms 16 ms ae-14-53.car4.Chicago1.Level3.net
> [4.68.101.72]
> ......
>
> This does not seem normal to me. Am I correct? What would be causing
> this type of routing?
>
> Thanks for any input.

smlunatick
Tue Apr 22 15:50:26 PDT 2008

On Apr 22, 5:28=A0pm, Bruce
<cr...@removeme.interaccess.removemeagain.com> wrote:
> >The confusing part was / in the fact you trace "log" show 192.168.2.1
> >and 192.168.25.113. =A0These are two valid private IP subnets that can /
> >should be used for Local Area Networks (LAN.) =A0Domains are ignored.
>
> >Check both networks in order to see which correct IP subnets are used.
>
> Sorry about the confusion.
> 192.168.2.1 is my dsl modem
> The path then seems to head out to Covad
> Then it seems to go into a private network within Covad. This is not
> my Domain. Covad is my provider but once the trace exits 192.168.2.1 I
> assume it is in the public sector.
>
> It appears that Covad is routing through a private domain to send the
> packets back to level3 on its way to the world.
>
> I can only assume that even though I have a static address
> (69.3.229.239) that the address must point to covads network not my
> end point.
>
> The reason I ask is that I was wondering if these other "networks" may
> be interfering with my VPN connection.
>
> On Tue, 22 Apr 2008 13:20:43 -0700 (PDT), smlunatick
>
>
>
> <yves...@gmail.com> wrote:
> >On Apr 22, 3:00=A0pm, anonym...@mailinator.com wrote:
> >> Thanks,
>
> >> The problem I am having with the VPN using Netgear Prosafe and a
> >> Netgear router (I have not managed to find a solution from Netgear) is
> >> that I can connect the client to the router. Both the client
> >> connection monitor and the Router show a connection, but the client PC
> >> can not see, ping or directly access anything on the router side.
>
> >> Also, the 192.168.25.113 I mentioned on the tracert is not part of
> >> either of my sub domains. I was not aware of the fact that IP traffic
> >> would route through a private domain to get somewhere else as opposed
> >> to only public addresses.
>
> >> On Tue, 22 Apr 2008 12:49:41 -0400, "smlunatick" <yves...@gmail.com>
> >> wrote:
>
> >> >This is correct! =A0You need to know that whenever you connect to a VP=
N
> >> >"service" end-point (server or VPN rouer) =A0the default, normal setti=
ng is to
> >> >route "all" traffic (either the remote network requests or all Interne=
t
> >> >requests) over to the remote network and use the remote network's "def=
ault"
> >> >gateway for Internet access.
>
> >> >Could you please post the problem you are having with the VPN so other=
s
> >> >"responders" could guide you with possible better results.
>
> >> >On 22/04/2008 anonym...@mailinator.com wrote:
> >> >>Hi All,
>
> >> >>I have been trying to solve a VPN problem I am having. While trying t=
o
> >> >>find the problem, I have performed several tracert's from the two
> >> >>locations. I am not a IP genius, but I have noticed that when doing
> >> >>the routing, Somewhere along the way, I always seem to see a local IP=

> >> >>address. In this case a 192.168.25.113
>
> >> >> 1 =A0 =A0 7 ms =A0 =A0 1 ms =A0 =A0<1 ms =A0192.168.2.1
> >> >> 2 =A0 =A020 ms =A0 =A016 ms =A0 =A016 ms =A0h-69-3-229-1.chcgilgm.co=
vad.net
> >> >>[69.3.229.1]
> >> >> 3 =A0 =A019 ms =A0 =A015 ms =A0 =A016 ms =A0192.168.25.113
> >> >> 4 =A0 =A019 ms =A0 =A016 ms =A0 =A015 ms =A0ge-4-1-166.ipcolo1.Chica=
go1.Level3.net
> >> >>[166.90..81]
> >> >> 5 =A0 =A021 ms =A0 =A016 ms =A0 =A016 ms =A0ae-14-53.car4.Chicago1.L=
evel3.net
> >> >>[4.68.101.72]
> >> >>......
>
> >> >>This does not seem normal to me. Am I correct? What would be causing
> >> >>this type of routing?
>
> >> >>Thanks for any input.- Hide quoted text -
>
> >> - Show quoted text -
>
> >The confusing part was / in the fact you trace "log" show 192.168.2.1
> >and 192.168.25.113. =A0These are two valid private IP subnets that can /
> >should be used for Local Area Networks (LAN.) =A0Domains are ignored.
>
> >Check both networks in order to see which correct IP subnets are used.- H=
ide quoted text -
>
> - Show quoted text -

What does Covad say about this? 192.168.xxx.yyy IP addresses should
not appear within the middle of the trace route (outside of the LAN
network.) Can be at the beginning (192.168.2.1) or at the end.

CuriousGeorge
Tue Apr 22 18:34:01 PDT 2008

> > >> >On 22/04/2008 anonym...@mailinator.com wrote:
> > >> >>Hi All,
> >
> > >> >>I have been trying to solve a VPN problem I am having. While trying to
> > >> >>find the problem, I have performed several tracert's from the two
> > >> >>locations. I am not a IP genius, but I have noticed that when doing
> > >> >>the routing, Somewhere along the way, I always seem to see a local IP
> > >> >>address. In this case a 192.168.25.113
> >
> > >> >> 1 7 ms 1 ms <1 ms 192.168.2.1
> > >> >> 2 20 ms 16 ms 16 ms h-69-3-229-1.chcgilgm.covad.net
> > >> >>[69.3.229.1]
> > >> >> 3 19 ms 15 ms 16 ms 192.168.25.113
> > >> >> 4 19 ms 16 ms 15 ms ge-4-1-166.ipcolo1.Chicago1.Level3.net
> > >> >>[166.90..81]
> > >> >> 5 21 ms 16 ms 16 ms ae-14-53.car4.Chicago1.Level3.net
> > >> >>[4.68.101.72]
> > >> >>......
> >
> > >> >>This does not seem normal to me. Am I correct? What would be causing
> > >> >>this type of routing?
> >
> > >> >>Thanks for any input.

> > >> On Tue, 22 Apr 2008 12:49:41 -0400, "smlunatick" <yves...@gmail.com>
> > >> wrote:
> >
> > >> >This is correct! You need to know that whenever you connect to a VPN
> > >> >"service" end-point (server or VPN rouer) the default, normal setting is to
> > >> >route "all" traffic (either the remote network requests or all Internet
> > >> >requests) over to the remote network and use the remote network's "default"
> > >> >gateway for Internet access.

> On Apr 22, 5:28 pm, Bruce
> <cr...@removeme.interaccess.removemeagain.com> wrote:

> > It appears that Covad is routing through a private domain to send the
> > packets back to level3 on its way to the world.
> >

"smlunatick" wrote:

> What does Covad say about this? 192.168.xxx.yyy IP addresses should
> not appear within the middle of the trace route (outside of the LAN
> network.) Can be at the beginning (192.168.2.1) or at the end.
>

Seems to me that this was the OP's original question. [Posts edited and
rearranged for clarity]. So much for "This is correct!"

anonymous
Wed Apr 23 08:31:13 PDT 2008

On Tue, 22 Apr 2008 18:34:01 -0700, Curious George
<CuriousGeorge@discussions.microsoft.com> wrote:

>> > >> >On 22/04/2008 anonym...@mailinator.com wrote:
>> > >> >>Hi All,
>> >
>> > >> >>I have been trying to solve a VPN problem I am having. While trying to
>> > >> >>find the problem, I have performed several tracert's from the two
>> > >> >>locations. I am not a IP genius, but I have noticed that when doing
>> > >> >>the routing, Somewhere along the way, I always seem to see a local IP
>> > >> >>address. In this case a 192.168.25.113
>> >
>> > >> >> 1 7 ms 1 ms <1 ms 192.168.2.1
>> > >> >> 2 20 ms 16 ms 16 ms h-69-3-229-1.chcgilgm.covad.net
>> > >> >>[69.3.229.1]
>> > >> >> 3 19 ms 15 ms 16 ms 192.168.25.113
>> > >> >> 4 19 ms 16 ms 15 ms ge-4-1-166.ipcolo1.Chicago1.Level3.net
>> > >> >>[166.90..81]
>> > >> >> 5 21 ms 16 ms 16 ms ae-14-53.car4.Chicago1.Level3.net
>> > >> >>[4.68.101.72]
>> > >> >>......
>> >
>> > >> >>This does not seem normal to me. Am I correct? What would be causing
>> > >> >>this type of routing?
>> >
>> > >> >>Thanks for any input.
>
>> > >> On Tue, 22 Apr 2008 12:49:41 -0400, "smlunatick" <yves...@gmail.com>
>> > >> wrote:
>> >
>> > >> >This is correct! You need to know that whenever you connect to a VPN
>> > >> >"service" end-point (server or VPN rouer) the default, normal setting is to
>> > >> >route "all" traffic (either the remote network requests or all Internet
>> > >> >requests) over to the remote network and use the remote network's "default"
>> > >> >gateway for Internet access.
>
>> On Apr 22, 5:28 pm, Bruce
>> <cr...@removeme.interaccess.removemeagain.com> wrote:
>
>> > It appears that Covad is routing through a private domain to send the
>> > packets back to level3 on its way to the world.
>> >
>
>"smlunatick" wrote:
>
>> What does Covad say about this? 192.168.xxx.yyy IP addresses should
>> not appear within the middle of the trace route (outside of the LAN
>> network.) Can be at the beginning (192.168.2.1) or at the end.
>>
>
>Seems to me that this was the OP's original question. [Posts edited and
>rearranged for clarity]. So much for "This is correct!"

After contacting Covad, they claim this is correct. Apparently a Covad
DSl travels back through their private network. The appearance of the
routing looks a bit deceptive. It seems my packets need to get through
several hops prior to actually starting their route to a destination.

The same seems to occur if you are trying to get to my destination
(IE, you end up going through the private IP).

My question is then, doesn't this create a possibility of having
duplicate Private IP addresses within my own network due to the Covad
private network?

Steve
Wed Apr 23 09:27:21 PDT 2008

On Wed, 23 Apr 2008 10:31:13 -0500, anonymous@mailinator.com wrote:

>After contacting Covad, they claim this is correct. Apparently a Covad
>DSl travels back through their private network. The appearance of the
>routing looks a bit deceptive. It seems my packets need to get through
>several hops prior to actually starting their route to a destination.
>
>The same seems to occur if you are trying to get to my destination
>(IE, you end up going through the private IP).
>
>My question is then, doesn't this create a possibility of having
>duplicate Private IP addresses within my own network due to the Covad
>private network?

There's no problem, even if your network uses the same private IP
addresses as Covad's private network.

Internet sites and routers don't see your private IP addresses. They
use your public IP address to send packets to you.

After packets arrive at your network, your router uses your private IP
addresses to send the packets to your computers. Your router doesn't
see Covad's private network.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com