[Gllug] Any clues

[Adrian McMenamin]

On Saturday 04 May 2002 11:52 pm, you wrote:
> SNIP
>
> > > > >From 192.168.62.123: Destination Host Unreachable
> > >
> > > Have you checked the basics?  What does ifconfig tell you about the
> > > interface?  Have you checked the routing table to see if there's a
> > > properly configured route?
> >
> > Well, I think the answer to both these questions is yes - and I know it's
>
> not
>
> > a cabling problem.
>
> Can you checked the other end.  This is a ping from .123 and the ifconfig
> is from .13.  Both will need for correct ip, netmask, route etc for it to
> work.
>
for what it's worth:

eth0      Link encap:Ethernet  HWaddr 00:10:B5:6E:6F:31
          inet addr:192.168.62.123  Bcast:192.168.62.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:55 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:4636 (4.5 Kb)  TX bytes:5476 (5.3 Kb)
          Interrupt:5 Base address:0xc000

But I don't think that's it. The bizarre thing is that the hub reports the 
link physically present until such time as the client configures it, 
whereupon the light on the hub just goes off.

-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug