[GRLUG] Routing Weirdness
Dave Chiodo
megadave at gmail.com
Wed Jan 29 03:32:10 EST 2014
I think if we want to get to the bottom of this, the following info will
help:
- a network diagram showing each router, and its
relationship/interconnections with other routers
- for each router, the output of "show ip route" (for cisco IOS devices -
or the equivalent for any other brand of router) (Feel free to mask the
first two octets of any public IP addresses, replace them with "A" or "B"
etc, if desired - make sure the physical interfaces on the network diagram
use the same convention, if so)
On Tue, Jan 28, 2014 at 4:53 PM, L. V. Lammert <lvl at omnitec.net> wrote:
> OK, .. we have two RVN042s onsite, and there is a wireless link between
> one (the 192.168.1.n) and a remote site (the 192.168.2.n) so remote users
> can access the server (192.168.1.145).
>
> *Most* of the time everything works fine, but randomly, traffic from the
> remote site gets routed through the Main site route to go out! For
> example, these traceroutes were done in sequence:
>
> Tracing route to ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms 192.168.2.254
> 2 1 ms <1 ms <1 ms 96-35-167-37.static.stls.mo.charter.com
>
> Trace complete.
>
> Good one!
>
> Tracing route to www.google.com [74.125.192.99]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms 192.168.2.254
> 2 2 ms 2 ms 1 ms 192.168.1.254
> 3 2 ms 2 ms 2 ms 24-182-144-137.static.olve.mo.charter.com
>
> Trace complete.
>
> Next one is bad!
>
> Tracing route to ds-any-fp3-real.wa1.b.yahoo.com [98.138.252.30]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms 192.168.2.254
> 2 1 ms 1 ms 2 ms 192.168.1.254
> 3 3 ms 2 ms 2 ms 24-182-144-137.static.olve.mo.charter.com
>
> Trace complete.
>
> Tracing route to ds-any-fp3-real.wa1.b.yahoo.com [98.138.252.30]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms 192.168.2.254
> 2 2 ms 2 ms 1 ms 192.168.1.254
> 3 2 ms 3 ms 2 ms 24-182-144-137.static.olve.mo.charter.com
>
> Trace complete.
>
> And will stay bad for a while. Try again in a few hours, and it's back to
> normal.
>
> Has anyone ever seen weirdness like this? Any thoughts on possible issues?
> The machines with problems are all XP, and my working theory is that after
> using a program on a network share (192.168.1.145), XP wants to use the
> 192.168.1 network for some strange reason, but I have not been able to
> prove it.
>
> TIA!
>
> Lee
> _______________________________________________
> grlug mailing list
> grlug at grlug.org
> http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shinobu.grlug.org/pipermail/grlug/attachments/20140129/17507b61/attachment.html>
More information about the grlug
mailing list