[network-admin] Changing ESSID requires reboot or, or manual iwconfig for changes to take effect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-system-tools (Ubuntu) |
Invalid
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: gnome-system-tools
Version: Dapper Drake 6.06 LTS i386
Steps to replicate:
1.) Boot with "old" access point configuration:
(HOMEACCESSPOINT, note - no WEP key)
$ cat /etc/network/
auto eth1
iface eth1 inet dhcp
wireless-essid HOMEACCESSPOINT
2.) Scan to find "new" access point essid:
$ iwlist eth1 scanning
eth1 Scan completed :
Cell 01 - Address: 00:20:A6:62:3E:11
3.) Run network-admin and configure:
$ gksu network-admin
Network name (ESSID): WORKACCESSPOINT
Key type: Plain (ASCII)
WEP key: WORKWEPKEY
Connection settings:
Configuration: DHCP
4.) After OK (twice) and a few minutes delay until network-admin closes:
But no IP address. I then check config:
$ cat /etc/network/
auto eth1
iface eth1 inet dhcp
wireless-essid WORKACCESSPOINT
wireless-key s:WORKWEPKEY
5.) Looks ok, so I try restarting networking:
$ sudo /etc/init.
One of the last messages is:
No DHCPOFFERS received.
6.) Make no changes and reboot
Then authenticates to access point and works great,
*** OR *****
6. (alternate) specify essid, channel, and key
$ sudo ifdown eth1
$ sudo iwconfig eth1 essid "WORKACCESSPOINT" key s:WORKWEPKEY channel 6
$ sudo ifup eth1
Then authenticates to access point and works great,
Expected behavior:
After changing configuration in network-admin, the new configuration settings should be used, just like they are used during boot.
I do know that doing iwconfig without explicitly setting "channel n" would not result in a connection. Not sure if it is relevant, HOMEACCESSPOINT is on a different channel than WORKACCESSPOINT, and HOMEACCESSPOINT does not have a WEP key whereas WORKACCESSPOINT does. When I go the other direction, use Wi-Fi at home, I need to do:
$ sudo iwconfig eth1 essid "HOMEACCESSPOINT" key off channel 1
Hardware: HP Pavilion zx5078cl
$ lspci |grep Broadcom
0000:02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
Changed in gnome-system-tools: | |
assignee: | nobody → desktop-bugs |
status: | Needs Info → Unconfirmed |
Thank you for your bug. The network-config job is to the change the config file and restart the network, if "sudo /etc/init. d/networking restart" doesn't apply the changes that's not a network-admin bug. The DHCP doesn't reply according to "No DHCPOFFERS received.", are you sure that's not a bug from your DHCP server? Do you have log from the server? Could you look if it receives a request for a new IP from the client?