Index

Subject : Re: LUG: Old Newbie Question

From : Will Beers <whbeers@ncsu.[redacted]>

Date : Wed, 13 Apr 2005 19:02:20 -0400

Parent


Usually when the route command takes a really long time for me, it's a
cable problem...Have you tried using a different cable?

Will Beers

Ken Whichard wrote:
> I have still been unable to get the linux box to see the network. Below
> are the outputs from the commands indicated:
>
> As stated earlier, I have the linux box and a windoze box on a switch
> hooked to a wireless bridge - the win box works just fine but the linux
> box aparently doesn't see the network at all. If I ping an address on
> the lan, it says "Host Unreachable".
>
> Any ideas would be greatly appreciated
>
> Ken
>
>
> route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
> eth0
>
>
>
> ifconfig
>
> eth0 Link encap:Ethernet HWaddr 00:0B:6A:6B:BE:C4
> inet addr:192.168.1.140 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::20b:6aff:fe6b:bec4/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4867 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1438 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:484961 (473.5 Kb) TX bytes:62436 (60.9 Kb)
> Interrupt:10 Base address:0xcc00
>
>
>


Attachments :

(Please be wary of attachments - they have not been scanned for viruses)


Replies :