Network settings, SSID not remembered.

Bug #13972 reported by Martin Willemoes Hansen
8
Affects Status Importance Assigned to Milestone
gnome-system-tools (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

1. Open network settings
2. Set SSID for wireless nic
3. Close network settings
4. Open network settings, SSID back to default "ANY"

/etc/networking/interfaces is updated tho, but it is not reflected in the
graphical user interface.

Revision history for this message
Sebastien Bacher (seb128) wrote :

are you using warty or hoary ?

Revision history for this message
Martin Willemoes Hansen (mwh) wrote :

(In reply to comment #1)
> are you using warty or hoary ?

Hoary.

Revision history for this message
Carlos Garnacho (carlosg) wrote :

Hi,

could you tell if the ESSID is actually changed after closing the tool (iwconfig
should tell you this), and please also check that you can change the ESSID from
the command line (iwconfig <iface> essid <essid>) without problems

what's strange to me is that this "ANY" default ESSID isn't stored in any place
of the network tool

Revision history for this message
Martin Willemoes Hansen (mwh) wrote :

(In reply to comment #3)
> Hi,
>
> could you tell if the ESSID is actually changed after closing the tool (iwconfig
> should tell you this), and please also check that you can change the ESSID from
> the command line (iwconfig <iface> essid <essid>) without problems
>
> what's strange to me is that this "ANY" default ESSID isn't stored in any place
> of the network tool

As I wrote in the first post, the essid is stored in /etc/network/interfaces.

I have no problem in changing the essid on the commandline.

Bellow is the section from my /etc/network/interfaces file:

iface eth0 inet dhcp
        # wireless-* options are implemented by the wireless-tools package
        wireless-mode managed
        wireless-essid any
        wireless_essid tsunami

Seems like both any and my favourit essid is present. I guess that the network
tool just picks the first essid ie any.

Revision history for this message
Carlos Garnacho (carlosg) wrote :

Created an attachment (id=1660)
Patch to fix this

The problem is caused by the duality in the interfaces file syntax (wireless_*
vs. wireless-*) the attached patch (committed already in the gst CVS) deletes
wireless_essid and wireless_key, leaving wireless-essid and wireless-key with
the correct values

Revision history for this message
reh4c (gene-hoffler) wrote :

Does the patch address this problem: After setting up a wireless minipci card under network settings,
I deactivate the wired LAN and exit the settings dialogue. Then, I open Firefox and try to get on the
web. It fails to connect and will not show a web page, so I reopen Network Settings and find that the
wired LAN has incorrectly reactivated itself. There is the unresolved conflict--2 connections
activated. If I then deactivate the wired LAN again and exit settings, Firefox starts properly with
the wireless LAN. After a reboot with the wired LAN EITHER PLUGGED IN OR NOT PLUGGED IN, Network
settings show the wired LAN as active. It should not be active if its not plugged in. Only my
wireless LAN should be active based on my saved settings prior to rebooting.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Comment #6 seems to be a different issue.

Revision history for this message
Sebastien Bacher (seb128) wrote :

This upload fixes the bug, thanks for the patch Carlos:

 system-tools-backends (1.2.0-0ubuntu2) hoary; urgency=low
 .
   * debian/patches/06_wireless.patch:
     - fix the essid storage (Hoary: #7627).

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.