Opened 7 months ago

Closed 4 months ago

#1118 closed System Defect (deferred)

wpa_supplicant.conf keeps getting clobbered

Reported by: bridger Owned by: kris
Priority: minor Milestone:
Component: Network Manager Version: 10.0-RELEASE
Keywords: wpa_supplicant Cc: trac-bugs@…

Description

Hi all,

That may sound like a hyperbolic summary, but my /etc/wpa_supplicant.conf is getting modified (networks are being removed) -- ~once every couple of weeks, consistently.

I am using a ThinkPad? T430s, with an Intel 6205 Advanced-N wifi chip:
iwn0@pci0:3:0:0: class=0x028000 card=0x13118086 chip=0x00858086 rev=0x34 hdr=0x00

vendor = 'Intel Corporation'
device = 'Centrino Advanced-N 6205 [Taylor Peak]'
class = network

Change History (7)

comment:1 Changed 6 months ago by bridger

Here is some potentially relevant output from dmesg:

wlan0: link state changed to DOWN
May 16 08:51:35 viaduct ntpd[1486]: sendto(15.185.186.215) (fd=28): Network is down
May 16 08:52:01 viaduct ntpd[1486]: sendto(208.75.88.4) (fd=28): Network is down
May 16 08:52:06 viaduct ntpd[1486]: sendto(67.18.187.111) (fd=28): Network is down
May 16 08:52:41 viaduct dhclient[1986]: receive_packet failed on wlan0: Device not configured
May 16 08:52:41 viaduct dhclient[1986]: ioctl(SIOCGIFFLAGS) on wlan0: Operation not permitted
May 16 08:52:41 viaduct dhclient[1986]: Interface wlan0 no longer appears valid.
May 16 08:52:41 viaduct dhclient[1986]: No live interfaces to poll on - exiting.
May 16 08:52:41 viaduct dhclient[1986]: exiting.
May 16 08:52:41 viaduct dhclient[1985]: connection closed
May 16 08:52:41 viaduct dhclient[1985]: exiting.
May 16 08:52:41 viaduct wpa_supplicant[725]: ioctl[SIOCS80211, op=25, val=0, arg_len=0]: Device not configured
May 16 08:52:41 viaduct wpa_supplicant[725]: ioctl[SIOCS80211, op=95, val=208, arg_len=0]: Device not configured
May 16 08:52:41 viaduct wpa_supplicant[725]: ioctl[SIOCS80211, op=17, val=0, arg_len=0]: Device not configured
May 16 08:52:41 viaduct wpa_supplicant[725]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Device not configured
May 16 08:52:41 viaduct wpa_supplicant[725]: ioctl[SIOCS80211, op=95, val=208, arg_len=0]: Device not configured
May 16 08:52:41 viaduct wpa_supplicant[725]: ioctl[SIOCS80211, op=17, val=0, arg_len=0]: Device not configured
May 16 08:52:41 viaduct wpa_supplicant[725]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Device not configured
May 16 08:52:41 viaduct wpa_supplicant[725]: ioctl[SIOCS80211, op=16, val=1, arg_len=0]: Device not configured
wlan0: Ethernet address: a4:4e:31:e9:ea:08
wlan0: link state changed to UP
pid 3106 (chrome), uid 1001: exited on signal 11
pid 7770 (chrome), uid 1001: exited on signal 11
wlan0: link state changed to DOWN
wlan0: link state changed to UP
wlan0: link state changed to DOWN
wlan0: link state changed to UP
wlan0: link state changed to DOWN
wlan0: link state changed to UP
wlan0: link state changed to DOWN
wlan0: link state changed to UP
wlan0: link state changed to DOWN
wlan0: link state changed to UP

Please let me know if there's additional information I can provide.
Thanks,
Bridger

comment:2 Changed 6 months ago by joshms

  • Owner set to kris

comment:3 Changed 6 months ago by kris

That is very odd. Are you doing anything relate to the network configuration at the time? Adding / Removing Wifi networks? Or does the network just go down and wipe the config?

comment:4 Changed 6 months ago by bridger

The config gets wiped. It's very strange; it only happens on boot, e.g. when I arrive at work or when I come home and boot the laptop, my work & home networks are gone and I have an empty file. It doesn't happen every day, but there are fairly regular occurrences.

I've wondered is this is some weird offshoot of an iwn driver bug or something, but I havent seen anything else about this on any of the lists.

comment:5 Changed 6 months ago by kris

Can you duplicate it fairly consistently? If so, right before you shutdown, make sure the file /etc/wpa_supplicant.conf exists with your settings. If it gets remove at startup, we can then have an idea on where to begin looking.

comment:6 Changed 6 months ago by bridger

It happens at boot and it seems (though I'm not sure) that it happens when dhclient fails to start during the boot process. So, definitely a problem at startup.

comment:7 Changed 4 months ago by joshms

  • Resolution set to deferred
  • Status changed from new to closed

ticket migrated. Closing.

Note: See TracTickets for help on using tickets.