#770550 ifupdown: No network after standby

Package:
ifupdown
Source:
ifupdown
Description:
high level tools to configure network interfaces
Submitter:
Thomas Fischbach
Date:
2014-11-24 15:00:05 UTC
Severity:
wishlist
#770550#5
Date:
2014-11-22 11:06:13 UTC
From:
To:
Dear Maintainer,

after standby I have no wireless access.

I use the following commands to fix it every time.
ifdown wlan0
ifup wlan0

Here my configuration for the interface

allow-hotplug wlan0
iface wlan0 inet dhcp

wpa-ssid name
wpa-psk secret
#770550#10
Date:
2014-11-22 11:18:47 UTC
From:
To:
Hello,

This is something expected and something I'm afraid I can't fix easily.
Try installing and using ifplugd or netplug. One more thing to help
with this is a udev rule to bring interfaces up and down when RF-kill
state changes:

SUBSYSTEM=="rfkill", ACTION=="change", ENV{RFKILL_STATE}=="1", ENV{RFKILL_NAME}=="phy*", ENV{RFKILL_TYPE}=="wlan", RUN+="ifup ..."
SUBSYSTEM=="rfkill", ACTION=="change", ENV{RFKILL_STATE}=="0", ENV{RFKILL_NAME}=="phy*", ENV{RFKILL_TYPE}=="wlan", RUN+="ifdown ..."
#770550#17
Date:
2014-11-22 16:16:29 UTC
From:
To:
Hello,

strange it need such work arounds for, what I thought, a basic task.

A couple of weeks/month ago it was working fine. Except of apt-get
update/upgrade I haven't changed anything at the configuration.

What I also do not understand is that the interface is still up after
standby
$ sudo ifup wlan0
ifup: interface wlan0 already configured

$ ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:19:7e:38:f4:87
           UP BROADCAST MULTICAST  MTU:1500  Metric:1
           RX packets:189889 errors:0 dropped:0 overruns:0 frame:0
           TX packets:125388 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:204461922 (194.9 MiB)  TX bytes:16860680 (16.0 MiB)

But with dhclient I do not get an IP address.
$ sudo dhclient wlan0
<takes long and no output>
$

Only networking restarts or ifdown/ifup works.
#770550#20
Date:
2014-11-22 17:20:25 UTC
From:
To:
Andrew Shadura wrote:

I thought I would note that I have been using 'wicd' for WiFi control
with very good results.  It works well with laptop standby mode and
rfkill switch handling.  It would be a good alternative to ifupdown
for wireless device handling.

Bob
#770550#25
Date:
2014-11-24 11:38:01 UTC
From:
To:
wicd was already installed. But no configured to "automatically connect
to this network".
After setting this option it is working like I would expect it.

Maybe this option should be enabled by default.
#770550#30
Date:
2014-11-24 14:57:05 UTC
From:
To:
Maybe to soon. After reboot and first standby it is the same problem
again.
wicd tried to obtain an IP address and failed.

Not sure what information I should provide.

$ dmesg
[  679.196136] b43-phy0: Loading firmware version 666.2 (2011-02-23
01:15:07)
[  679.296881] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

$ rfkill list
0: dell-wifi: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: dell-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: dell-wwan: Wireless WAN
	Soft blocked: yes
	Hard blocked: no
4: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
5: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

just in case I unblocked the Wireless WAN it didn't help.

ifplugd, netplug and the udev rule also didn't work. But maybe I did
something wrong.