[pkg-wpa-devel] Bug#431657: automatic wlan connection at bootprocess on Etch only on second try

Stefan Lippers-Hollmann s.L-H at gmx.de
Mon Sep 26 16:12:18 UTC 2011


tags 431657 + moreinfo
thanks

Hi

On Monday 26 September 2011, Michael Lansche wrote:
> Package: ipw3945d
> Version: 1.7.22-4
> 
> Debian release: 4.0
> Hardware: Dell Inspiron 6400
> 
> Hi,
> 
> my WLAN connection starts only at the second try.
> 
> Etch-nb:~# cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> allow-hotplug eth1
> iface eth1 inet dhcp
> 
> auto eth2
> iface eth2 inet dhcp
> wpa-conf /etc/wpa_supplicant/wpa_supplicant.mynet.conf
> 
> The first try never works:
> 
> /var/log/boot:
> 
> Fri Jun 29 18:51:01 2007: Setting up networking....
> Fri Jun 29 18:51:01 2007: Starting ipw3945 regulatory daemon: ipw3945d.
[...]
> Fri Jun 29 18:52:32 2007:
> 
> To get the second try working I added this line
> 
> /etc/init.d/networking restart
> 
> to /etc/rc.local
> 
> 
> If I modify /etc/network/interfaces this way:
> 
> iface eth2 inet dhcp
> wpa-conf /etc/wpa_supplicant/wpa_supplicant.mynet.conf
> #auto eth2
> 
> and /etc/rc.local:
> 
> Etch-nb:~# cat /etc/rc.local
> #!/bin/sh -e
> #
> # rc.local
> #
> # This script is executed at the end of each multiuser runlevel.
> # Make sure that the script will "exit 0" on success or any other
> # value on error.
> #
> # In order to enable or disable this script just change the execution
> # bits.
> #
> # By default this script does nothing.
> 
> ifup --verbose eth2
> exit 0
> 
> my WLAN connects at the first try
> without any errors.
> 
> /var/log/boot:
> 
> Mon Jul  2 23:51:35 2007: .
> Mon Jul  2 23:51:35 2007: Setting parameters of disc: (none).
[...]
> Mon Jul  2 21:51:56 2007: 
> 
> I think my solution is only a workaround and there must be a problem in the boot sequence of Etch belonging to ipw3945d.
> I didn't change anything on the standard Etch boot sequence after installation.
[...]

Given that this bug hasn't seen any activity within the last 4 
years - and in particular considering that ipw3945d fortunately doesn't
 exist anymore with totally different modules driving ipw3945 hardware 
these days, I'd like to ask if this is still an issue for you.

Regards
	Stefan Lippers-Hollmann





More information about the Pkg-wpa-devel mailing list