[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Sheflug] Re: Routing Problem



Alex

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

Yep... that's definitely correct :))


> > 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.

ifconfig eth0 reveals.....

Link encap: Ethernet  HWaddr  00:20:18:56:D3:4C
inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
inet6 addr: fe80::220:18ff:fe56:d34c/10 Scope:Link
inet6 addr: fe80::20:1856:d34c:/10 Scope:Link
UP BROADCAST RUNING MULTICAST MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:30
TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interupt:10 Base address:0x6300

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 ;)

Hmm... I've put more than a few networks together and I've not seen
anything like this before.  All the hardware is OK.  Just can't
understand where I've gone wrong.

> 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 '?!'.

Tried pinging 192.168.1.3 from the gateway when connected and it
doesn't see the laptop at all.
 
> 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.

Yes, I was wondering about that when I looked at it.  Not quite sure
what to do.  Think I'll have to ditch YaST and do a manual config.  If
I can work it out.  
 
> 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...


Yes,  might be an idea to wander up the road and buy half a bottle of
whisky ??

Thanks


-- 
Richard

---------------------------------------------------------------------
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.