No internet on wired connection in Ubuntu Hardy

shivkiyer · 10-16-2011, 06:06 AM

I have a Ubuntu Hardy 8.04 installed on a Dell Inspiron 1525 laptop as a dual boot alongwith Microsoft Vista. It has been working fine for two years until last night when I found I couldn't connect to the internet using my wired internet connection. To use the wired connection, I need to login to the service provider's homepage. But I can't get that page. The service is OK as I can get the page from another laptop. Also, the network on my Inspiron is OK because I can get the homepage from my Microsoft Vista.

I have been trying out thousands of suggestions on forums but haven't got anywhere.

This is the output of my ifconfig:

Code:

eth0      Link encap:Ethernet  HWaddr 00:1d:09:53:0f:a1  
          inet addr:192.168.2.30  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::21d:9ff:fe53:fa1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1492  Metric:1
          RX packets:1901 errors:0 dropped:0 overruns:0 frame:0
          TX packets:181 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:143174 (139.8 KB)  TX bytes:19842 (19.3 KB)
          Interrupt:16

I tried to delete the "eth0" settings in my Network Manager, restart the machine and then create a new eth0 but have got nowhere. The connection is a DHCP connection where I enabled the roaming mode. I tried the command /etc/init.d/networking restart from a terminal but no luck. When I ping the IP of my service provider (1.254.254.254), I get no packets received.

In my Network configuration in "Administration", I found the following DNS servers automatically added - 192.168.2.1, 172.168.40.1, 125.22.47.125 and the Search domain "Belkin" after restart.

I have a USB modem and that works fine with usbmode_switch. Which is how I am posting this.

Any ideas on how to go about fixing this?

Thanks in advance.

Tux-Slack · 10-17-2011, 01:29 AM

Could you paste the output of:
route -n
and
traceroute 1.254.254.254

Search domain, belkin, is this the home router? I'm guessing the eth0 interface is connected to the router.

snowday · 10-17-2011, 09:45 AM

Personally I would not waste a lot of time trying to troubleshoot 8.04, since it is obsolete and "end of life." Why not grab the latest Live CD from ubuntu.com and see if it works OK with your wired connection?

shivkiyer · 10-17-2011, 12:06 PM

Thanks for your responses.

Code:

$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.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     1000   0        0 eth0
0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 eth0

and

Code:

$ traceroute 1.254.254.254
traceroute to 1.254.254.254 (1.254.254.254), 30 hops max, 40 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
<counts upto 30>
29  * * *
30  * * *

Still no login page

I have been scrambling for the past few hours trying to get my system back. I had Slackware 12.1 in another partition that I had been experimenting with for a while and was in pretty bad shape. So I thought I would replace Slackware with the latest Ubuntu and leave the Hardy as it is until I figure out what the problem is. I downloaded Ubuntu 11.10 and tried to burn a CD but found my DVD writer is messed up. I created a USB boot disk which got recognized at boot-up but froze during the install. I had to do a manual shutdown and found the bootloader had been overwritten. My old Ubuntu 8.04 CD was missing and all I could find was a Fedora 11 DVD. I installed Fedora 11 instead of the Ubuntu 11.10 and now I can triple boot with Hardy, Fedora 11 and Vista.

I'll check out how the wired connection is with my Fedora 11 and post back. I used Fedora Core 7 a while back for close to 2 years and I am not much a fan of Fedora. I'll look for some other distros and maybe try out something else.

shivkiyer · 10-18-2011, 12:02 AM

Update:
I can't get my wired connection working on Fedora Core 11 either. Can't understand whats happening. Called up the service provider at his local support center and he said nothing has changed.

In my Ubunut, I can see packets received and transmitted in my Network Manager applet. Does this mean the wired connection is setup OK? In that case, if I can't get the service providers IP 1.254.254.254, where could the problem lie? If I can't even get the IP I think other issues like DNS server should come later. What else could be the problem? Some routing issue?

Another suggestion is to install wicd and try that out. I was about to do so but when installing that using apt-get, it said network-manager would be uninstalled. Would that be wise?

Thanks in advance.

Tux-Slack · 10-18-2011, 02:31 AM

It would seem, from the traceroute, you can't even reach your router.

Your default gateway is set to 192.168.2.1, is this in fact the correct IP number of your router?
It's a bit unlikely, since it seems like DHCP is working, but have you checked your hardware connecting to the router?
Is there any chance that you are establishin a PPPoE connection to your ISP on your Windoze machine, and you forgot to configure that on the Ubuntu machine?

shivkiyer · 10-18-2011, 02:46 AM

Thanks for the response.

How do I find out the IP of the router? Do I ping it and check for a response?

How do I check the hardware connecting to the router? The cables are OK since I used them for my office laptop also. So the modem and cable are OK.

The Ubuntu Hardy was working fine until a few days back. It was always on DHCP with the "Enable Roaming mode" box checked. I can't understand what happened that caused this. I'll check my Windows settings again when I get back home.

Can I try to do something with the network driver in my Ubuntu? Maybe for some reason it got corruped? Anyway to check that?

Thanks again.

shivkiyer · 10-18-2011, 11:32 AM

I looked out for the file /etc/network/interfaces and found it to be empty. So I put in

Code:

auto eth0
iface eth0 inet dhcp

I tried to run an ifdown eth0 followed by an ifup eth0. The outputs are:

Code:

# ifup eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:1d:09:53:0f:a1
Sending on   LPF/eth0/00:1d:09:53:0f:a1
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.1.128 from 192.168.73.167
DHCPREQUEST of 192.168.1.128 on eth0 to 255.255.255.255 port 67
DHCPNAK from 172.168.50.1
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPOFFER of 192.168.1.128 from 192.168.73.167
DHCPREQUEST of 192.168.1.128 on eth0 to 255.255.255.255 port 67
DHCPNAK from 172.168.50.1
DHCPACK of 192.168.1.128 from 192.168.73.167
SIOCADDRT: Invalid argument
bound to 192.168.1.128 -- renewal in 338983 seconds.
root@addict1980:/etc#  * Stopping NTP server ntpd
   ...done.

Code:

# ifdown eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 10327
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:1d:09:53:0f:a1
Sending on   LPF/eth0/00:1d:09:53:0f:a1
Sending on   Socket/fallback
DHCPRELEASE on eth0 to 192.168.73.167 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.

There is an error message with ifup eth0. The "SIOCADDRT: Invalid argument". Also, it says "There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072".

Thanks in advance.

Tux-Slack · 10-18-2011, 12:49 PM

I'm a little confused right now.

So let's go from step one.

This is your configuration:
modem <-> router <-> trouble-causing-laptop

Now I'm only guessing,
172.168.50.1 is the IP of the modem?
192.168.73.167 is the IP of the router?

When you're sending DHCPDISCOVER on the broadcast, you get an offer from 192.168.73.167, then when you're trying to request that offer, 172.168.50.1 replies with DHCPNAK, then another discover is sent and again an offer from 192.168.73.167 and upon the second request of that offer, 172.168.50.1 again replies with DHCPNAK and right after that 192.168.73.167 replies with DHCPACK and you get assigned with IP 192.168.1.128. It would seem you have 2 devices connected to that laptop that act as a DHCP server in your network. What are those 2 devices?

After doing ifdown eth0, try manually removing /var/run/dhclient.eth0.pid before you run ifup eth0 again.
Have you looked at your configuration on that windows laptop/desktop? More specifically I'd be interested in:
ipconfig /all
and
tracert 1.254.254.254 (or whatever is the IP that you need to log in to)

And after you run ifup eth0 please inspect "route -n" again.

shivkiyer · 10-18-2011, 10:51 PM

Thank you for your response Tux-Slack. I appreciate your patiently going through my posts which might be getting a little annoying. Sorry if I am bothering you with contradictory information.

I'll respond as soon as I get back to my home. I'll check out the windows config and also try out removing the pid file.

Thanks again.

shivkiyer · 10-19-2011, 08:40 AM

This is the result of ipconfig /all:

Code:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : addict1980
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:



   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : domain.name
   Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
   Physical Address. . . . . . . . . : 00-1F-3C-26-EA-62
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes


Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Marvell Yukon 88E8040 PCI-E Fast Ethernet Controller
   Physical Address. . . . . . . . . : 00-1D-09-53-0F-A1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 172.168.50.227(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 19 October 2011 17:57:08
   Lease Expires . . . . . . . . . . : 19 October 2011 18:57:07
   Default Gateway . . . . . . . . . : 172.168.50.1
   DHCP Server . . . . . . . . . . . : 172.168.50.1
   DNS Servers . . . . . . . . . . . : 208.67.222.222
                                       208.67.220.220
   NetBIOS over Tcpip. . . . . . . . : Enabled


Tunnel adapter Local Area Connection* 6:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:ee:2eab:5357:cd1c(Preferred)
   Link-local IPv6 Address . . . . . : fe80::ee:2eab:5357:cd1c%8(Preferred)
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Disabled


Tunnel adapter Local Area Connection* 7:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{B42832A8-CC85-4CE6-8307-64000FE096E0}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::200:5efe:172.168.50.227%14(Preferred)
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 208.67.222.222
                                       208.67.220.220
   NetBIOS over Tcpip. . . . . . . . : Disabled


Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.domain.name
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes


Tunnel adapter Local Area Connection* 12:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : 6TO4 Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Temporary IPv6 Address. . . . . . : 2002:aca8:32e3::aca8:32e3(Preferred)
   Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
   DNS Servers . . . . . . . . . . . : 208.67.222.222
                                       208.67.220.220
   NetBIOS over Tcpip. . . . . . . . : Disabled

Result of tracert 1.254.254.254 before logging in at the homepage:

Code:

C:\Users\Shivkumar>tracert 1.254.254.254

Tracing route to 1.254.254.254 over a maximum of 30 hops

  1     3 ms     2 ms     2 ms  ACA83201.ipt.aol.com [172.168.50.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
<upto 30 times "Request times out.">

Result of tracert 1.254.254.254 after logging in at the homepage:

Code:

Tracing route to 1.254.254.254 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  ACA83201.ipt.aol.com [172.168.50.1]
  2     2 ms     1 ms     2 ms  ABTS-KK-Static-ILP-001.16.181.122.airtel.in [122.181.16.1]
  3     2 ms     2 ms     3 ms  172.20.10.113
  4     4 ms     2 ms     3 ms  172.20.10.97
  5     3 ms     2 ms     2 ms  172.20.3.5
  6     3 ms     3 ms     3 ms  172.20.3.1
  7     3 ms     3 ms     3 ms  172.20.0.18
  8     3 ms     2 ms     3 ms  ABTS-KK-Static-ILP-002.7.181.122.airtel.in [122.181.7.2]
  9     2 ms     3 ms     3 ms  ABTS-KK-Static-ILP-001.7.181.122.airtel.in [122.181.7.1]
 10     3 ms     3 ms     3 ms  AES-Static-005.99.22.125.airtel.in [125.22.99.5]
 11    42 ms    42 ms    42 ms  182.79.255.18
 12    42 ms    43 ms    42 ms  129.250.12.229
 13    42 ms    42 ms    43 ms  ae-2.r20.sngpsi02.sg.bb.gin.ntt.net [129.250.4.142]
 14   109 ms   109 ms   109 ms  as-1.r23.tokyjp01.jp.bb.gin.ntt.net [129.250.6.120]
 15   154 ms   154 ms   154 ms  p16-0.hanarotelecom.tokyjp01.jp.bb.gin.ntt.net [129.250.8.126]
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
<upto 30 times "Request timed out">

I don't know if the above is useful but it seems to have reached some very distant servers!

I removed the dhclient.eth0.pid file from /var/run and this is what I got from ifup eth0:

Code:

# ifup eth0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:1d:09:53:0f:a1
Sending on   LPF/eth0/00:1d:09:53:0f:a1
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 5
DHCPOFFER of 192.168.2.30 from 192.168.2.1
DHCPREQUEST of 192.168.2.30 on eth0 to 255.255.255.255 port 67
DHCPNAK from 172.168.50.1
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.2.30 from 192.168.2.1
DHCPREQUEST of 192.168.2.30 on eth0 to 255.255.255.255 port 67
DHCPNAK from 172.168.50.1
DHCPACK of 192.168.2.30 from 192.168.2.1
bound to 192.168.2.30 -- renewal in 828452659 seconds.
root@addict1980:/home/shivkvi#  * Stopping NTP server ntpd
   ...done.

The error I got before is gone. Result of route -n:

Code:

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.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     1000   0        0 eth0
0.0.0.0         192.168.2.1     0.0.0.0         UG    100    0        0 eth0

Result of traceroute is empty just asterisks. No connectivity yet.

Thanks in advance.

Tux-Slack · 10-20-2011, 01:54 AM

Is the "ipconfig /all" output before or after the logging in at the homepage?

It would seem, that you reach the wrong DHCP server with your Ubuntu.

So let us try to manually set up the interface, by doing so:

Code:

ifdown eth0
ifconfig eth0 172.168.50.228 netmask 255.255.255.0 up
route add default gw 172.168.50.1 eth0
echo nameserver 208.67.222.222 > /etc/resolv.conf
echo nameserver 208.67.220.220 > /etc/resolv.conf

Then you should be able to reach the login page, if the Ubuntu machine and the Windows machine are connected to the same network device.

shivkiyer · 10-20-2011, 08:02 AM

IT IS WORKING!!!

Thank you so much Tux-Slack. I am posting this from the wired connection on Ubuntu. I guess I'll just enjoy the high net speeds for a few days before figuring out what to do with the Fedora 11 on the other partition. Maybe I'll remove that and install Slackware 13.7. I was a slacker (12.1) for almost two years a while back and it was fantastic.

Thanks again.