Bug#431657: automatic wlan connection at bootprocess on Etch only on second try
Hi Jurij,
Am Freitag, 3. August 2007 23:21 schrieb Jurij Smakov:
Ok, that looks pretty regular. Another thing I can suggest is to try
to add a delay (like 'sleep 5') to the start/pre-up branch in the
/etc/wpa_supplicant/ifupdown.sh, right after conf_wpa_supplicant line.
That delay should give the WPA authentication some time to settle
before the dhclient is invoked to obtain an DHCP lease. Let me know if
it helps.
I modified the file this way:
...
case $MODE in
start)
case $PHASE in
pre-up)
kill_wpa_supplicant
init_wpa_supplicant || exit 1
conf_wpa_supplicant || {
kill_wpa_supplicant; exit 1; }
sleep 5
;;
post-up)
init_wpa_cli|| {
kill_wpa_supplicant; exit 1; }
;;
esac
;;
...
your suggestion works.
I think this way the boot process is a few seconds slower than with my
workaround.
Nevertheless I'd like to ask which is now the better respectively the more
Debian-like way?
Is it now a bug or only a specific problem of my hardware?
Thank you very much for your effort.
Best regards,
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431657: automatic wlan connection at bootprocess on Etch only on second try
Am Sonntag, 29. Juli 2007 15:49 schrieb Jurij Smakov:
Hi,
After reading the thread on debianhelp [0], I wonder whether your
problems might be related to wpa_supplicant configuration. Maybe it
fails to authenticate to access point the first time during some race
condition? Could you post the output of your wpa_supplicant
configuration file (after stripping out sensitive information), and
check whether you get any error messages from wpa in the logs (dmesg,
/var/log/messages, /var/log/syslog, /var/log/kern.log).
[0] http://www.debianhelp.org/node/8512
Etch-nb:~# cat /etc/wpa_supplicant/wpa_supplicant.mynet.conf
# WPA-PSK/TKIP
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=allnet
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
psk=generated WPA PSK with wpa_passphrase
}
There are no error messages from wpa in the logs:
Etch-nb:~# dmesg | grep -i wpa
Etch-nb:~# grep -i wpa /var/log/syslog
Etch-nb:~# grep -i wpa /var/log/kern.log
Etch-nb:~# grep -i wpa /var/log/messages
Etch-nb:~#
Regards,
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431657: automatic wlan connection at bootprocess on Etch only on second try
Hi Jurij, - original Nachricht Betreff: Bug#431657: automatic wlan connection at bootprocess on Etch only on second try Gesendet: Mo, 16. Jul 2007 Von: Jurij Smakov[EMAIL PROTECTED] Hi Michael, There is a line sleep 3 in the start_daemon() function of the /etc/init.d/ipw3945d script. Can you try setting the number there to something like 10, and see if it helps? It will make the script to pause for 10 seconds instead of 3 after starting the daemon, to give it some more time to initialize. before sending my bug report I read http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405270 and also tried to set sleep to a higher number. But this doesn't solve the problem. May I ask for any further suggestions concerning this problem? Regards, Michael
Bug#431657: Is it really an ipw3945d package bug ?
Hello, Hello, I have exactly the same behaviour on my laptop with Etch installed and a device driven by madwifi module... I suspect that the DHCP client start too early, before connection / authentication is done... only a supposition... with regards, Frédéric. I must confess that I don't know if it's really an ipw3945d package bug. May I ask you about your solution concerning this problem? Regards, Michael
Bug#431657: automatic wlan connection at bootprocess on Etch only on second try
periodic command scheduler: crond. Mon Jul 2 21:51:52 2007: Checking battery state Mon Jul 2 21:51:52 2007: Starting K Display Manager: kdm. Mon Jul 2 21:51:52 2007: Configuring interface eth2=eth2 (inet) Mon Jul 2 21:51:52 2007: run-parts --verbose /etc/network/if-pre-up.d Mon Jul 2 21:51:52 2007: run-parts: executing /etc/network/if-pre-up.d/wireless-tools Mon Jul 2 21:51:52 2007: run-parts: executing /etc/network/if-pre-up.d/wpasupplicant Mon Jul 2 21:51:52 2007: wpa_supplicant: using default driver type: wpa-driver wext Mon Jul 2 21:51:52 2007: wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.eth2.pid -i eth2 -D wext -c /etc/wpa_supplicant/wpa_supplicant.mynet.conf -C /var/run/wpa_supplicant Mon Jul 2 21:51:52 2007: Starting /sbin/wpa_supplicant... Mon Jul 2 21:51:52 2007: wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth2 Mon Jul 2 21:51:52 2007: Mon Jul 2 21:51:52 2007: dhclient3 -pf /var/run/dhclient.eth2.pid -lf /var/lib/dhcp3/dhclient.eth2.leases eth2 Mon Jul 2 21:51:52 2007: Internet Systems Consortium DHCP Client V3.0.4 Mon Jul 2 21:51:52 2007: Copyright 2004-2006 Internet Systems Consortium. Mon Jul 2 21:51:52 2007: All rights reserved. Mon Jul 2 21:51:52 2007: For info, please visit http://www.isc.org/sw/dhcp/ Mon Jul 2 21:51:52 2007: Mon Jul 2 21:51:54 2007: Listening on LPF/eth2/00:1b:77:38:26:de Mon Jul 2 21:51:54 2007: Sending on LPF/eth2/00:1b:77:38:26:de Mon Jul 2 21:51:54 2007: Sending on Socket/fallback Mon Jul 2 21:51:56 2007: DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 4 Mon Jul 2 21:51:56 2007: DHCPOFFER from 192.168.0.1 Mon Jul 2 21:51:56 2007: DHCPREQUEST on eth2 to 255.255.255.255 port 67 Mon Jul 2 21:51:56 2007: DHCPACK from 192.168.0.1 Mon Jul 2 21:51:56 2007: bound to 192.168.0.3 -- renewal in 109194 seconds. Mon Jul 2 21:51:56 2007: run-parts --verbose /etc/network/if-up.d Mon Jul 2 21:51:56 2007: run-parts: executing /etc/network/if-up.d/avahi-daemon Mon Jul 2 21:51:56 2007: run-parts: executing /etc/network/if-up.d/mountnfs Mon Jul 2 21:51:56 2007: run-parts: executing /etc/network/if-up.d/ntpdate Mon Jul 2 21:51:56 2007: run-parts: executing /etc/network/if-up.d/wpasupplicant 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. Regards Michael Lansche
