[PLUG] Strange routing issue

[Chris Berry]

I could provide a diagram if necessary, but it's basically just a straight line. 

What I was saying was that we could reach the LAN interface on the remote router 192.168.6.15 but not the workstation at 192.168.6.5  The only time I've seen something like that previously was when the default gateway on the workstation wasn't configured properly but we re-verified that and it looks fine. 

I agree about testing one connection at a time, that's exactly what we did when it didn't work the way we expected.  I tried ping first because that's easy, but then traceroute of course to see where it was dying.
 
Starting from my workstation I could reach all the way to the remote router's local interface 6.15 just not that one last step to the remote workstation on 6.5 

So far the info on the software router looks pretty straightforward: 

Net  0            Gateway 192.168.3.1  Metric 1 Passive 
Net  192.168.5.0/255.255.255.0 Gateway 192.168.4.15 Metric 2 Passive 
Net  192.168.6.0/255.255.255.0 Gateway 192.168.4.15 Metric 3 Passive 

It's an old Netware 6.5 server we're trying to de-commission. 


Chris Berry
Linux Systems Administrator
Davis Tool
x521

>>> Ishak Micheil <isaacem at gmail.com> 6/25/2012 2:03 PM >>>
Is it possible to provide a diagram?
When you say "we could get to 6.15 on the remote router, but that we
couldn't reach 6.5,"  can you please elaborate on that?

To make it simple for you , draw a plan and the route of your traffic and
test it one connection at a time.
Example: can I get to my GW from local VLAN
Can you route to your upstream GW
and move up from there

Best advise I could give you is use "traceroute" as your primary testing,
vs, ping or ssh, telnet etc...since all that can be filtered by may many
elements

Good luck


On Mon, Jun 25, 2012 at 1:49 PM, Chris Berry <cberry at davistl.com> wrote:

>
> Our network is pretty small and the setup doesn't seem that complex.  The
> previous admin has this hackish setup where one of our remote facilities is
> bouncing through a file server acting as a software router.  There is no
> need for that as our hardware routers are perfectly capable of handling the
> traffic.  Here is the current setup in order:
>
> remote workstation (192.168.6.5 255.255.255.0 default gw 192.168.6.15)
>
> remote router - LAN SIDE (192.168.6.15 255.255.255.0)
>
> remote router - WAN SIDE (192.168.5.2 255.255.255.0)
>
> local edge router - WAN SIDE (192.168.5.1 255.255.255.0)
>
> local edge router - LAN SIDE (192.168.4.15 255.255.255.0)
>
> hackish software router - OUTSIDE (192.168.4.1 255.255.255.0)
>
> hackish software router - INSIDE (192.168.3.6 255.255.255.0)
>
> core router - (192.168.3.1 255.255.255.0)
>
> local workstation - (192.168.3.76 255.255.255.0 gw 192.168.3.1)
>
> That all works fine as currently setup.
>
> So the other night we went to do maintenance and remove the software
> router.  We changed the local edge router address from 4.15 to 3.230 and
> added the RIP info on the core router.  At first it seemed fine, the routes
> all got shared, however after a bit our testing showed that we could get to
> 6.15 on the remote router, but that we couldn't reach 6.5, in fact even the
> remote router couldn't reach 6.5 (from within a remote session) which is
> strange since that's on the same subnet.  We rolled back the changes and
> everything is fine, but I have to admit I'm a bit puzzled.  Can I buy a
> vowel?
> Chris Berry
> Linux Systems Administrator
> Davis Tool
> x521
>
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
_______________________________________________
PLUG mailing list
PLUG at lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug