Ubuntu
network-manager package

Network manager should not restart wifi network if static config is in use

Bug #105238 reported by Christophe Avare
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Brian Murray

Bug Description

I'm using an ACER 5620 with ipw3945 driver, but i think the problem is tied to the internal logic of the network manager.

When the network manager is not using the roaming mode, an interface is configured and setup in the boot process (often required if WPA is used).
This works fine, but when the gnome session is opened, the network manager fires and stops the already functional wifi network, then go on the reconnection process!

The network manager must detect the state of its interfaces before deciding to reconfigure the network.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. There is an update to network-manager that was released today, this should resolve the bug you have reported. Please test again with the newest version of network-manager and report back. Thanks in advance.

Revision history for this message
Christophe Avare (christophe-avare) wrote :

Hi again,

I just downloaded the updates.
Things gone bad after reboot: No network interface found!

It appears that a new restricted driver has been detected (Atheros HAL) in addition to ipw3945.
I disabled this in the restricted driver manager and rebooted.

This time, the interface was up, but neither at boot time, nor the network manager was able to connect to the network.

I removed the eth1 info in the /etc/network/interfaces config file and rebooted.
With the network manager gui, i then reconfigured the network and this time it goes fine, even if the connection takes more than a minute to establish!

But the network manager applet has now disappeared from the task bar!

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Now that the final version of Feisty Fawn is available we were wondering if this issue still exists. Thanks in advance.

Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in network-manager:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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