Kubuntu 6.06 final: cannot retrieve an ip via dhcp from my router

[Marco Cimmino]

I have a D-Link 500t with dhcp enabled, and my network eth0 an nforce4 ethernet card cannot retrieve an ip via dhcp at boot.
I have to disable and re-enable the network every time I boot to have an ip or use manual ips.

[Marco Cimmino (cimmo)]

^

[Stéphane Magnenat (stephane.magnenat)]

HI,

I've experienced a similar bug on two on my dapper installation (out of a total of 6). The problem is not constant. Sometimes, the IP is fetched but sometimes not. Disabling/reenabling the network always fixes the problem.

The common point of those two machines is that they have been debian in the past. One was:
debian sarge -> ubuntu dapper
The other was:
progeny -> debian woody -> debian sarge (testing) -> debian unstable -> debian sarge -> ubuntu breezy -> ubuntu dapper
The problem was not present in ubuntu breezy.

Have a nice day,

Steph

[Marco Cimmino (cimmo)]

I can confirm:
sometimes dhcp is released sometimes not, but for me they are more not than yes.

[David Nemeskey (nemeskeyd)]

I can also confirm this on Kubuntu Edgy.

It works in the following way for me:
I have a home network with a Linux and a Windows box connecting to the internet via a router. If the network cable is plugged in to the Linux box during startup, no problem -- network will work. I can even unplug the network cable, and as soon as I plug it back, Kubuntu detects it, and the network becomes available right away.

BUT if the network cable isn't plugged in at startup, this bug appears. Even if I plug it in, Ubuntu won't detect it. Maybe after minutes pass, it will work -- I've never had the patience to test it. So I have to disable/enable it, which is a pain, as the user has to be in the sudoers group.

I used Ubuntu and Xubuntu before Kubuntu (Dapper? Breezy? I don't remember), and I remember seeing this problem there as well. But as of Dapper (?), Gnome removed the need to sudo if I want to start the network manager, and I also remember as if the error disappeared in Gnome altogether; but maybe not.

Anyway, this is definitely a problem, which cannot be solved without a sudo (bad if you are not in the sudoers group). I am astonished by the fact that it is still unassigned. Please note that Windows XP has no problem of reacting immediately to the plugging of the network cable; how can Linux, a much more network-oriented OS not?

[David Nemeskey (nemeskeyd)]

It seems it is solved in Feisty by KNetworkManager.

[Visham (vish-owns-u)]

nope, not solved. i got the same prob with feisty :/

[gcordoba (glgcg)]

hi,
I join the group having problems with dhcp. I moved from Debian (sarge?) to Ubuntu Gutsy at my University. After few connection problems I fixed by choosing a fix IP. However, I move the computer to a place in which a fix IP is not possible. I modified the network setting and all seems to work properly, ...till I shut down... no useful internet connection. ifconfig reports the old IP! Thus, I temporary fixed the problem with
sudo ifdown eth0
followed by
sudo ifup eth0

I hope this bug becomes fixed some day. Meanwhile, please, any of you knows where can I put an scrip with those ifdown and ifup commands? At boot? I tried in init.d/myscripts and it does not work.

Thanks,
Gustavo

[Aswarp (aswarp2002)]

Hola:
I experience a similar trouble with wireless access within KUbuntu Hardy Heron v8.04: Wireless internet access sucks, to say the least. I even found basic ortographic errors in the window text, such as "inhalámbrico" for "inalámbrico".
I recommend this subsystem undergo a very thorough revision. Friends of mine are downgrading theirs to v7 or v6 due to the internet connection problems this new release brings.
knetworkmanager and dhcpclient seem to have some programmings bugs. I had to reinstall them from the CD. Lucky I was I had one near, but some many people could enter an infinite loop: no internet connection gets no upgrades, and no upgrades don't solve the connection problems.
Reinstallation somehow worked, but I still have some trouble: I seem to be connected to the internet through the ADSL wireless router (telefonica) but after some minutes, Firefox won't open any pages. I am forced to manually reconnect from knetworkmanager system tray icon every few minutes.
I even got DUPLICATE packets when I ping! What's going on? (details below).
A handheld Linux device of my own (N770) in the same room connects to that very same router without effort.
I therefore ask (beg) the developers for an inmediate, heavy revision of this subsystem which is a very important one and one of the keys to transmitting a good impression of the distro so as many people as possible adopt it as their own. Adding a user-friendly Wireless Internet Connection Wizard won't harm much either...

RESULTS of ping probes:
aswarp@aswkdesktop:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.6 icmp_seq=1 Destination Host Unreachable
From 192.168.1.6 icmp_seq=2 Destination Host Unreachable
From 192.168.1.6 icmp_seq=3 Destination Host Unreachable
From 192.168.1.6 icmp_seq=4 Destination Host Unreachable
From 192.168.1.6 icmp_seq=5 Destination Host Unreachable
From 192.168.1.6 icmp_seq=6 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
9 packets transmitted, 0 received, +6 errors, 100% packet loss, time 8032ms
, pipe 3
aswarp@aswkdesktop:~$ ping www.google.com
PING www.l.google.com (66.102.9.104) 56(84) bytes of data.
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=1 ttl=242 time=101 ms
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=1 ttl=242 time=107 ms (DUP!)
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=1 ttl=242 time=112 ms (DUP!)
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=2 ttl=244 time=105 ms
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=2 ttl=244 time=107 ms (DUP!)
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=2 ttl=244 time=123 ms (DUP!)
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=3 ttl=242 time=105 ms

[Aswarp (aswarp2002)]

Oh, yet another issue I wanted to comment over:
During the short and ephimereal periods I have my wireless internet connection working, I get a veru strange happening. Latency times are very high, I mean, even when I am connected to the 3mb ADSL router being the only user, over a 24mb wifi link. Http access is very slow and all pages take a whole shit load of time to open, when they do at all. FTP still gets about 50 kbps in average where it should be much higher (and is, when other systems are connected to the same gateway). It's a real pain in the ass (no metaphore here)...

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 alpha?

[Aswarp (aswarp2002)]

Sorry for the previous dirty language, a faulty internet connection really gets on my nerves...
I confirm the malfunction in KUbuntu 8.04 with kernel 2.6.24-19-generic.

[Pablo Castellano (pablocastellano)]

Could you try it booting from the live cd of ubuntu intrepid beta release?

[Aswarp (aswarp2002)]

Sorry, it gets really hard to download the live cd iso from here...

[Aswarp (aswarp2002)]

Finally I got a cabled internet connection to complete a full upgrade of my system. After that, the wireless connection would not work yet though. I could get a DHCP address from my router by editing my "interfaces" configuration file in nano from terminal, and then with ifdown <interface>, ifup <interface> and asking for an IP with dh-something <interface>. However this would work with the cabled Ethernet interface (eth0), it would not on the wi-fi interface (wlan0).

The previous DUP! packages seem to come from an scenario when I hade two woreless ethernet devices both plugged-in to the same machine. I did did in order to discard the hypothesis of a hardware malfunction or driver/firmware issue. I can not remember if I had both cards plugged-in at the time I received those DUPlicate packages but I am pretty sure it was like that.

My Wi-Fi is still kaput. It will show a zero coverage indicator even when from then same machine in Windows it shows an almost full coverage bar. And I can not get a DHCP IP either.

[Przemek K. (azrael)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? (9.10) Thanks in advance.

[Przemek K. (azrael)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!