Comment 7 for bug 178775

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

I've added a gnome-system-tools component to this too until both NetworkManager AND gnome-system-tools agree how the interface should be managed.

Description of the problem:
Setting an interface to be manually configured will prevent the interface from being brought up on boot.

Steps to reproduce:
(assuming all your interfaces are initially set to roaming)
1. Left click on nm-applet .
2. Click on "Manual configuration...".
3. Click on Unlock.
4. Type password and click on Authenticate.
5. Select "Wireless connection (wlan0)" and then click on Properties.
6. Untick "Enable roaming mode".
7. Fill in ESSID box, network password (if required) and set the Configuration to "Automatic configuration (DHCP)".
8. Click OK.
9. Click on Close.
10. Reboot the computer.
11. Wait for Ubuntu Hardy to start, log in and start a terminal.
12. Run the following:
host ubuntu.com

Expected results:
Something like:
ubuntu.com has address 91.189.94.158
ubuntu.com mail is handled by 10 mx.canonical.com.
to be shown.

Actual results:
;; connection timed out; no servers could be reached

How reproducible is this problem?
It is reproducible every time.

Additional information:
Doing
ifup wlan0
results in the interface being correctly started. Interfaces could be manually configured in Gutsy and started on boot. If NetworkManager starts configuring manual interfaces too this will probably resolve bug #106508 too.

Version information:
Ubuntu hardy (development branch)
network-manager 0.6.6-0ubuntu5
gnome-system-tools 2.22.0-0ubuntu7