Ubuntu
network-manager package

Wifi settings getting lost over reboot

Asked by Gaurish Sharma on 2008-01-08

i using wifi but still there is no wlan0 connection. also the settings are getting lost like the network passowrd & WPA type. which i have to setup everytime i boot up, and settings get reset after reboot.

Even with all settings given the wifi link goes down on its automatically.
sometimes the network key gets erased, sometimes the WPA type is set to WPA personnel from WPA2 personnel. sometimes the default route get sets to eth0 instead of eth1.

right now there is no fixed procedure to get the netowork up, sometimes i need to add the values & default route, some time restarting networking help, sometimes the wifi does not come up at all no matter how hard i try.

i am changing settings by GUI network-admin.
>>>>>>>>>>>>>>>>>>>>>>>>>EDIT>EDIT>EDIT>edit>edit>>>>>>>>>>>>>>>>>>>>>.
ITs a bug :|
also its not still fixed

----------------------------------------------------------------------------------------------------------------
ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:B0:D4:BE:FB
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:22 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 00:1B:77:4E:7A:AE
          inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::21b:77ff:fe4e:7aae/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:4817 errors:2 dropped:176 overruns:0 frame:0
          TX packets:4595 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4968053 (4.7 MB) TX bytes:973934 (951.1 KB)
          Interrupt:16 Base address:0x8000 Memory:d0000000-d0000fff

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:478 errors:0 dropped:0 overruns:0 frame:0
          TX packets:478 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:44692 (43.6 KB) TX bytes:44692 (43.6 KB)
----------------------------------------------------------------------------------------------
~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
05:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
05:04.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01)
05:06.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
05:06.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
05:06.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 01)
05:06.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
05:06.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)

deepak@deepak-laptop:~$cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eth1 inet static
address 192.168.1.4
netmask 255.255.255.0
gateway 192.168.1.1
wpa-psk be196908f45ff6f6955d935036eb8dfd8f7ff74476ef2d3ea77ec9cc77f9389e
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA2
wpa-ssid GaurishNET

auto eth1
-----------------------------------------------------------------------------------------------------------
now there is no wlan0 created still i am posting this question from the same notebook

Question information

Language:: English Edit question

Status:: Solved

For:: Ubuntu network-manager Edit question

Assignee:: No assignee Edit question

Solved by:: Bhavani Shankar

Solved:: 2008-03-25

Last query:: 2008-03-25

Last reply:: 2008-01-26

Revision history for this message

Bhavani Shankar (bhavi) said on 2008-01-08:

My experience has been that putting the laptop to sleep or hotplugging the card causes 'weird things' to happen. If you treat your laptop like a desktop (power it down and have the card inserted when you turn it on) then you'll probably have a lot less trouble.

I'm not sure where to begin with helping you troubleshoot because I don't know what driver your card uses. Perhaps look in dmesg the next time that it works?

dmesg | grep wlan

You should add wlan0 to the 'auto' line:

sudo nano /etc/network/interfaces

Ctrl+W, Y, Enter to save.

Hope it helps

Bhavani Shankar.

Revision history for this message

Bhavani Shankar (bhavi) said on 2008-01-08:

OK got it you use realtek one... Sorry for overlooking that line....... anyways try out the answer given above...

Revision history for this message

Bhavani Shankar (bhavi) said on 2008-01-08:

This link might also help you out.....

http://ubuntuforums.org/showthread.php?p=1862091#post1862091

anyways have a try and keep us informed.

Hope it helps

Bhavani Shankar.

Revision history for this message

Gaurish Sharma (gslive) said on 2008-01-09:

its a inbuilt, which is not even realtek, its "Intel Corporation PRO/Wireless 3945ABG"

-:$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth1

Revision history for this message

Bhavani Shankar (bhavi) said on 2008-01-09:

OK the network controller part.. Got it....I confused it with Ethernet controller...
Try out my previous answers.....
i.e,
add wlan0 to the 'auto' line
and this link given above might also interest you i.e,
http://ubuntuforums.org/showthread.php?p=1862091#post1862091
have a try at the above and keep us informed.

Hope it helps

Bhavani Shankar.

Revision history for this message

Bhavani Shankar (bhavi) said on 2008-01-09:

Next up some interesting info:
I'm not sure I follow. Network Manager adds the passphrase for you network to the keyring and the first time you use the keyring you are asked to create a password for it. When logging in, network manager needs access to the keyring so you are prompted for the keyring password. Is this what you are referring to or is network manager not storing your password and you are being asked for the actual passphrase to the network? Based on your description it sounds like the latter. Were you prompted to save the passphrase to the keyring? Did you do that or click deny? If you denied adding it that could be the reason you are repeatedly asked.
secondly WPA Key should be stored in the /etc/network/interfaces file, so try editing this file.
as I said above for disappearing wlan0
Bear in mind that the key is stored in it's hex form, so it will look different to to the passphrase you enter in the gui. If you wast to check the key use the wpa_passphrase command line interface utility.
Thirdly,The passphrase for the WPA should get stored in the keyring. That has been the behaviour in the past. Gutsy seems a bit different. It still saves it in the keyring but no longer asks for a keyring password (although I'm not seeing consistent behaviour with this across installs). If it's not getting into the keyring then I'd say that's the problem. (I presume you are on Gutsy)
And Last but not the least though, I have faced similar problems with gutsy...
The key seems to disappear completely when you disable/enable the interface after a reboot. I'm not sure why this happens or what can done to workaround except to not use network-admin at all.

If you open a terminal and use 'sudo ifup eth1' and 'sudo ifdown eth1' then it works fine. This will allow you to use static settings, for dhcp just stick with roaming mode aka Network Manager (NM).

There are loads of outstanding bugs in network-admin and I fear few of them will ever get fixed. Particularly when it's scheduled to be largely replaced by NM soon.

For Your Information: The passphrase is only stored in the keyring by NM, network-admin just uses plain text in the interfaces file.

Hope this long info helps

Bhavani Shankar.

Next up some interesting info:
I'm not sure I follow. Network Manager adds the passphrase for you network to the keyring and the first time you use the keyring you are asked to create a password for it. When logging in, network manager needs access to the keyring so you are prompted for the keyring password. Is this what you are referring to or is network manager not storing your password and you are being asked for the actual passphrase to the network? Based on your description it sounds like the latter. Were you prompted to save the passphrase to the keyring? Did you do that or click deny? If you denied adding it that could be the reason you are repeatedly asked.
secondly WPA Key should be stored in the /etc/network/interfaces file, so try editing this file.
as I said above for disappearing wlan0 
Bear in mind that the key is stored in it's hex form, so it will look different to to the passphrase you enter in the gui. If you wast to check the key use the wpa_passphrase command line interface utility.
Thirdly,The passphrase for the WPA should get stored in the keyring. That has been the behaviour in the past. Gutsy seems a bit different. It still saves it in the keyring but no longer asks for a keyring password (although I'm not seeing consistent behaviour with this across installs). If it's not getting into the keyring then I'd say that's the problem. (I presume you are on Gutsy)
And Last but not the least though, I have faced similar problems with gutsy...
 The key seems to disappear completely when you disable/enable the interface after a reboot. I'm not sure why this happens or what can done to workaround except to not use network-admin at all.

If you open a terminal and use 'sudo ifup eth1' and 'sudo ifdown eth1' then it works fine. This will allow you to use static settings, for dhcp just stick with roaming mode aka Network Manager (NM).

There are loads of outstanding bugs in network-admin and I fear few of them will ever get fixed. Particularly when it's scheduled to be largely replaced by NM soon.

For Your Information: The passphrase is only stored in the keyring by NM, network-admin just uses plain text in the interfaces file.

Hope this long info helps

Bhavani Shankar.

Revision history for this message

Gaurish Sharma (gslive) said on 2008-01-09:

how clear the keyring?

Revision history for this message

Bhavani Shankar (bhavi) said on 2008-01-10:

You mean how to clear the keyring? Do this:
Open a terminal (Applications menu > Accessories > Terminal) and type:

rm ~/.gnome2/keyrings/default.keyring

Warning: only do this if you know all the passwords you had keyring saving for you. If I'm right, this will clear your keyring entirely.

Bhavani Shankar.

Revision history for this message

Gaurish Sharma (gslive) said on 2008-01-16:

my problem still not solved :(

Revision history for this message

Bhavani Shankar (bhavi) said on 2008-01-18:

#10

If you open a terminal and use 'sudo ifup eth1' and 'sudo ifdown eth1' then it works fine. This will allow you to use static settings, for dhcp just stick with roaming mode aka Network Manager (NM).

Revision history for this message

Bhavani Shankar (bhavi) said on 2008-01-26:

#11

Network Manager In Feisty was buggy with WPA encrypted networks, and dropped and reconnected every few mintues (particularly with Intel and Atheros chipsets). Apparently it still is a bit buggy in Gutsy (although I have stuck with it and had no problems).

If this is a problem - try Wicd instead of NM: http://wicd.sourceforge.net/

Revision history for this message

Gaurish Sharma (gslive) said on 2008-03-25:

#12

Thanks Bhavani Shankar, that solved my question.

Revision history for this message

Bhavani Shankar (bhavi) said on 2008-03-26:

#13

Hi Gaurish..

Glad it worked out.... :)

To post a message you must log in.

Ask a question

Edit question

Ubuntunetwork-manager package

Wifi settings getting lost over reboot

Question information

Related bugs

Related FAQ:

Subscribers

Ubuntu
network-manager package