Upgraded to 6.10 - IPW2200 Card Fails to Connect on Boot

Bug #69096 reported by Trip Ericson
4
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

I upgraded my laptop from 6.06.1, fully patched, to 6.10 and had several issues. I managed to resolve all of them myself, with this one exception.

Whenever I boot the system, my eth1 interface (an IPW2200 wireless card) is shown as up and functional, but has no IP address. I have to sudo ifdown eth1 and then sudo ifup eth1 in order to acquire one.

I see that Bug 34505 has an issue that appears to be similar, however I did not have this problem with Dapper. It occurred only after the upgrade to Edgy.

Revision history for this message
Peter Liedler (peter-liedler) wrote :

Two questions?
Are you using kde - kubuntu? See Bug 64841
Can you manually connect the card?

Revision history for this message
Trip Ericson (rovfan) wrote :

Yes, I am using Kubuntu. I don't tend to use GUI tools to do network management. I haven't tried using dhclient though, I'll have to try that next time I restart the system. (I can do that immediately if you want me to)

What do you mean by 'manually connect the card'? It will connect if I do ifdown and then ifup, but not on boot-up.

Revision history for this message
Peter Liedler (peter-liedler) wrote :

Thanks for your bug report.

Let me try to clear this out.
Your card has got no ip address from the router on boot up. Do you have a fixed ip address or are you using dhcp?
I myself am using dhcp and it only connects manually on edgy with and without wpa.

If dhcp works (no need to restart immideately), I will mark it as duplicate of 64841 in hope that it will be fixed soon.

But for me it seems to be an upstart/dhcp, not a wlassistant problem.

Thanks
Peter

Revision history for this message
Trip Ericson (rovfan) wrote :

Well, here's what happens. I'm using DHCP to get the address, but I have the DHCP server set to assign my laptop's MAC address the same IP (192.168.11.27) every time it connects. I use no encryption, as I live in the middle of nowhere.

I just restarted the system, and it once again did not acquire the IP but once logged in (and seeing Gaim fail to connect to anything), using 'sudo dhclient eth1' did acquire it, just as doing ifdown/ifup would have.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.