Not another internet question!

[toad]

Re: Not another internet question!

Thanks for that.

It is eth0 like a zero.

The crux of the matter is that your interface eth0 is not recognised and cannot be addressed. All other networking services appear to be running no probs.

Could you post the output of

cat /etc/network/interfaces

It should look exactly like so:

auto eth0
iface eth0 inet dhcp

If it doesn't, make a backup copy of your current file and create a new one which contains only the above lines. Now restart the networking daemon

sudo /etc/init.d/networking restart

And do a

sudo ifconfig eth0 up

Any good?

[Detonate]

Re: Not another internet question!

I'm here. Read the whole thread. His ethernet controller is recognized and has the proper driver loaded. But he is not getting a IP from his router. If it does not work after using Toad's last instructions, we will have to dig a little deeper. Waiting for reply to that.

[toad]

Re: Not another internet question!

Ah, good morning across the pond and glad that help is at hand

[dibl]

Re: Not another internet question!

Hi guys -- I just woke up and see there was about zero progress on this one (sometimes things magically get solved while I'm sleeping ).

I don't think his modem's DHCP is giving the computer an IP address, or something like that. That's about as deep as my networking skills go.

[maninagreentshirt]

Re: Not another internet question!

okay i dont know what happened but it seems dibl you are right. It got solved while you were sleeping actually it was solved while I was sleeping. I was just about to copy the info of the interface results! thought id try konqueror and its working.


Now if this has happened magicaly could it un happen again?
should i post some info so we can see what is different now so that it can be solved easyier if it goes down again?

here is the interface. sorry dont understand the back up file instructions.

paul@pauls-computer:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

[maninagreentshirt]

Re: Not another internet question!

Should I make any upgrades now that I am connected to the internet?
what would be a good idea?

[maninagreentshirt]

Re: Not another internet question!

thanks again so much for your help guys.
I'm going to re go through the thread and re do all the terminal comands and post them up.
also I just checked software updates and should I upgrade to 9.10 as i have 9.04? thanks again everyone

[dibl]

Re: Not another internet question!

Maybe it just takes your modem awhile to do its DHCP thing. I doubt it will "un-happen", although each time you boot you may get to sit on your hands for awhile waiting for it. To be honest, it's not a phenomenon that I can remember ever reading about before.

On the upgrade, it's kind of personal choice. 10.04 will be released in April, and it will be a LTS release. If you're happy with what you have, and especially if you are learning the ropes with it, you might want to just continue to develop your proficiency with it, and then maybe consider a new installation of 10.04 in April.

Or, you can push that "full upgrade" button and have a little learning experience in the here and now.

[maninagreentshirt]

Re: Not another internet question!

not sure about why its working but had it plugged in all the time yesterday and this morning i just turned it on and about 10 mins later tried the internet and it worked. now I dont want to turn it off cause it might not work again. I know i will have to turn it off at some point.


here is the stuff again

Not sure But could what i'm doing reset anything?
not going to do any more comands till I get an answer!

thanks again everyone

Lspci -v

00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
Flags: bus master, medium devsel, latency 32, IRQ 16
I/O ports at ec00 [size=256]
Memory at e7015000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: 8139too
Kernel modules: 8139too, 8139cp

note: last time I didn't enter network after -c
lshw -c network

paul@pauls-computer:~$ lshw -c network
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: c
bus info: pci@0000:00:0c.0
logical name: eth0
version: 10
serial: 00:48:54:6e:17:d6
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=8139too driverversion=0.9.28 ip=10.1.1.3 latency=32 maxlatency=64 mingnt=32 module=8139too multicast=yes
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: pan0
serial: a2:76:4d:5e:8b:0b
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A multicast=yes

sudo ifconfig

paul@pauls-computer:~$ lshw -c network
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: c
bus info: pci@0000:00:0c.0
logical name: eth0
version: 10
serial: 00:48:54:6e:17:d6
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=8139too driverversion=0.9.28 ip=10.1.1.3 latency=32 maxlatency=64 mingnt=32 module=8139too multicast=yes
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: pan0
serial: a2:76:4d:5e:8b:0b
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A multicast=yes

sudo ifup eth0

paul@pauls-computer:~$ sudo ifup eth0
ifup: interface eth0 already configured
ping www.google.com

paul@pauls-computer:~$ ping www.google.com
PING www.l.google.com (66.249.89.147) 56(84) bytes of data.
64 bytes from www.google.com (66.249.89.147): icmp_seq=1 ttl=54 time=4921 ms
^C
--- www.l.google.com ping statistics ---
6 packets transmitted, 1 received, 83% packet loss, time 4999ms
rtt min/avg/max/mdev = 4921.324/4921.324/4921.324/0.000 ms, pipe 5
ping localhost

paul@pauls-computer:~$ ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.038 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.026 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.041 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.036 ms
64 bytes from localhost (127.0.0.1): icmp_seq=5 ttl=64 time=0.043 ms
64 bytes from localhost (127.0.0.1): icmp_seq=6 ttl=64 time=0.039 ms
^C
--- localhost ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 4999ms
rtt min/avg/max/mdev = 0.026/0.037/0.043/0.006 ms

[Detonate]

Re: Not another internet question!

I can offer a possible explanation. When your router gives your machine an IP address, it "remembers" that address for a period of time. It will not issue that address again until that time has expired. Your computer also remembers the address in the processes pid file. When trying to reconnect without a normal shutdown, the pid file tells the dhclient to use the same address it had before, but the router won't issue it because it thinks it is already being used. So my next suggestion was going to be to reboot your router, which I am pretty sure would have fixed your problem.