Network connection off on all my linux distros

Fredosaurus · 02-04-2008, 04:30 PM

I have a box with Windows XP and 3 linux distros installed (Mepis, PClinuxOS 07, SuSE 10). When I installed the distros, they all saw my network card and setup the connection automatically. I had access to the net. Lately, I have not been able to access the internet. The system sees the network card but cannot connect to it (it happens for all 3 distros). Anyone can tell me what's going on? I'm able to access the internet through Windows XP just fine, though.
P.S.: My network is connected to a router that is connected to the DSL modem, if that's any help.

sydney-troz · 02-04-2008, 05:30 PM

Post the output of:

Code:

$ route
$ ifconfig
$ iptables -L

Fredosaurus · 02-05-2008, 12:53 PM

Here are the results:

Code:

[root@linuxpc freddy]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
127.0.0.0       *               255.0.0.0       U     0      0        0 lo


[root@linuxpc freddy]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:40:CA:7A:BE:FA
          inet6 addr: fe80::240:caff:fe7a:befa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:20

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:156 errors:0 dropped:0 overruns:0 frame:0
          TX packets:156 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12704 (12.4 KiB)  TX bytes:12704 (12.4 KiB)


[root@linuxpc freddy]# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Thank you for any help you can provide.

unixfool · 02-05-2008, 01:45 PM

No gateway appears to be defined within the routing table, looking at the output you provided.

Fredosaurus · 02-05-2008, 02:27 PM

Quote:

Originally Posted by unixfool

No gateway appears to be defined within the routing table, looking at the output you provided.

How do I fix that?

sydney-troz · 02-05-2008, 07:41 PM

It also looks like your NIC isn't configured -- do you have a dhcp server? If so, is it running? If so, try getting your dhcp client to update your IP addr. I'm not sure how to do this with the distros your using, but it's probably

Code:

# The argument is a number one, not a lower case L
$ dhclient -1

Hope this helps

Fredosaurus · 02-06-2008, 07:41 AM

Quote:

Originally Posted by sydney-troz

It also looks like your NIC isn't configured -- do you have a dhcp server? If so, is it running? If so, try getting your dhcp client to update your IP addr. I'm not sure how to do this with the distros your using, but it's probably

Code:

# The argument is a number one, not a lower case L
$ dhclient -1

Hope this helps

Yes I do have a dhcp server. It's running when I'm in XP. It's supposed to autorun when I start Linux but it fails on all 3 distros. And when I try to connect it manually it says can't connect.
I'll try what you suggested above. Cross my fingers ;-)

Fredosaurus · 02-06-2008, 11:58 AM

Quote:

Originally Posted by sydney-troz

It also looks like your NIC isn't configured -- do you have a dhcp server? If so, is it running? If so, try getting your dhcp client to update your IP addr. I'm not sure how to do this with the distros your using, but it's probably

Code:

# The argument is a number one, not a lower case L
$ dhclient -1

Hope this helps

It did not work

sydney-troz · 02-06-2008, 12:49 PM

What was the error message? Also, what kind of dhcp server are you using? (I'm assuming it's on your router, in which case what kind of router do you have?)

Fredosaurus · 02-06-2008, 01:41 PM

Quote:

Originally Posted by sydney-troz

What was the error message? Also, what kind of dhcp server are you using? (I'm assuming it's on your router, in which case what kind of router do you have?)

My server setup consist of a DSL modem hooked to a router (D-Link DI-604) that is hooked to my PC. I'm not sure what type of DHCP server it is. Any help in figuring it out? Following is the result of me runing dhclient -1:

Code:

[root@localhost freddy]# dhclient -1
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:40:ca:7a:be:fa
Sending on   LPF/eth0/00:40:ca:7a:be:fa
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.

Loosewheel · 02-06-2008, 01:57 PM

Hi Fredosaurus,
Did XP happen to update you NIC driver? If so roll back the driver in 'Device Manager'.
Also, I don't see any IPv4 addresses... are you running IPv6? Not all routers will run IPv6.

sydney-troz · 02-06-2008, 05:06 PM

That's strange -- I'm not sure why you're not getting an ip addr, what if you try configuring a static ip, and seeing if you can ping out then?

Code:

$ ifconfig eth0 xxx.xxx.xxx.xxx

Check the output of "route" again, if there is no line with default, run

Code:

$ route add default gw yyy.yyy.yyy.yyy

where xxx.xxx.xxx.xxx is your machine's ip addr, and yyy.yyy.yyy.yyy is your gateway. If you can ping your router after that, it looks like a problem with dhcp -- if not, it's something else.