Re: Weired routing error

[david@qednet.biz]

Can you post the routing table output with regard to the two instances, ie
the output of "route -n"

d

> Hi!
>
> I have a weired network problem. I have an ISDN router on 192.168.0.1
> and a DSL router on 192.168.0.2. Both work nicely from other OS. Now I
> set up the default route to point to teh ISDN router with "route add
> default gw 192.168.0.1" and everything is up and running over ISDN.
> Traceroute to some host shows the first hop to go to 192.168.0.1 and
> then over a few more steps to the target. ftp,lynx, apt-get update and
> so on work fine. A traceroute to 192.168.0.1 shows just that one hop
> (this is correct). So far so good, now let's try to speed things up a bit
>
> Now to the weired part: I Delete the default route and add it back using
> "route add default gw 192.168.0.2". Try to ping some host and it works
> nicely. Try to ping 192.168.0.2 and it is OK. Try a traceroute to some
> host, this time the list *misses* the hop to 192.168.0.2 and goes
> directly to the follwing hosts reaching the target eventually.
>
> Trying to ftp somewhere yields no connection now. Access within the
> local network is OK, but besides ping (which works when trying to access
> anything beyond the router nicely) and traceroute does not give a
> connection.
>
> Both routers are netgear devices and work nicely from Knoppix, Windows,
> MacOS 8 and 9 give a good connection on first attempt. Any ideas?
>
> Regards
>
> Matthias
>
>
> --
> To UNSUBSCRIBE, email to debian-powerpc-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>
>


-------------------
david howe
www.qednet.biz
-------------------