Re: [Sheflug] Re: Routing Problem

["Alex Hudson" <nospam [at] alexhudson.com>]

> > When tcpdumping, were you pinging from the *same* box? Run tcpdump on
the
> > gateway, and ping the laptop from another virtual console.
>
> tcpdump reveals on console 1 on the gateway.....
>
> 14:12:56.167335 arp who-has 194.247.40.126 tell pirhana.quark.org.uk
> (0:20:18:56:d3:4c)
>
> and it scrolls on forever down the screen.

Hmm. Are you sure you did a 'tcpdump -i eth0' ? That doesn't look like local
net output to me :))

> netstat -r on the notebook reveals.......
>
> Destination    Gateway   Genmask       Flags   MSS    Window   irtt
> Iface
> 192.168.1.0     *       255.255.255.0   U       0       0        0
> eth0
> loopback        *       255.0.0.0       U       0       0        0
> lo

This is correct.

> and the same on the gateway reveals.........
>
> Destination    Gateway   Genmask       Flags   MSS    Window   irtt
> Iface
>
> that's all.

This isn't. Should be the same as above. Forget the isdn deal for a moment,
and setup the networking properly. eth0 should be up all the time, as should
the relevant routes. With isdn down, try a ifconfig. If no interfaces show
up, it's your complete network config that is screwed. You could try a
'/sbin/rc.init/networking start' (or whereever it is in SuSE), but that will
probably make little difference. You will probably need to go into YaST or
whatever and redo the network card config. If 'ifconfig' *did* show some
interfaces, then it's just(!) the routing table which is stuffed, but I
think this is highly unlikely. (Do tell if it is this, though, 'cos that
means somethings really wrong ;)

> After connecting I get.......
>
> Destination    Gateway   Genmask       Flags   MSS    Window   irtt
> Iface
> amundsden.rack.a  *    255.255.255.255  UH      0       0        0
> ippp0
> 192.168.1.0       *    255.255.255.0    U       0       0        0
> eth0
> loopback          *    255.0.0.0        U       0       0        0
> lo
> default  amundsen.rack.a 0.0.0.0        UG      0       0        0
> ippp0
> default  pirhana.quark.o 0.0.0.0        UG      0       0        0
> eth0

Hmmm. This implies that you should be able to ping your laptop, at least
when the isdn interface is up. Try pinging with the interface down. Bring up
isdn, ping again. Bring isdn back down, and ping again. If it didn't work at
all, that comes under 'weird'. If it worked once (when isdn was up), it
comes under 'screwed'. If it worked when isdn came up, and continues to work
when isdn came down, that comes under '?!'.

The fact that you have two default gateways also makes me suspect something
is pretty seriously screwed ;) I would be tempted to declare "shenanigans" -
I think you computer may believe eth0 is an isdn device, or at least, the
configuration tells it that.

I think the easiest approach is to wipe the network slate clean. Remove all
the configuration, completely. Then, configure the network card. Make sure
that is working. Then, once that is done, configure the isdn.

> Hmm.. the weathers looking really bad outside just now :(  There was a
> BBC radio rumour about two hours ago that went on about floods in the
> south of England once again.

I'm in London at the moment - no floods that I can see, although I suspect
that's not exactly conclusive proof ;) It's definitely brass monkeys at the
mo' though...

Cheers,

Alex.



---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.