Re: WLAN automatisch beim Booten?
Am Montag, 25. Juni 2007 20:51 schrieb Stefan Bauer:
> Michael Lansche schrieb:
> > ich habe es nochmal so versucht, leider vergeblich:
> >
> > auto eth2
> > iface eth2 inet dhcp
> > wpa-driver wext
> > wpa-ssid allnet
> > wpa-scan-ssid 1
> > wpa-proto WPA
> > wpa-key-mgmt WPA-PSK
> > wpa-pairwise TKIP
> > wpa-group TKIP
> > wpa-psk "MeinPWimKlartext"
>
> was sagt ifup --force -v eth2 ?
Funktioniert :-)
Configuring interface eth2=eth2 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via
pidfile /var/run/wpa_supplicant.eth2.pid
Stopped /sbin/wpa_supplicant (pid 2647).
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.eth2.pid -i
eth2 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth2
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "allnet" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: wpa-scan-ssid 1 -- OK
wpa_supplicant: enabling network block 0 -- OK
dhclient3 -pf /var/run/dhclient.eth2.pid -lf /var/lib/dhcp3/dhclient.eth2.leases
eth2
There is already a pid file /var/run/dhclient.eth2.pid with pid 2697
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth2/00:1b:77:38:26:de
Sending on LPF/eth2/00:1b:77:38:26:de
Sending on Socket/fallback
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 11
DHCPOFFER from 192.168.0.1
DHCPREQUEST on eth2 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.3 -- renewal in 126181 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant
Etch-nb:~# ping web.de
PING web.de (217.72.195.42) 56(84) bytes of data.
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=1 ttl=55 time=51.0 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=2 ttl=55 time=51.4 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=3 ttl=55 time=50.7 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=4 ttl=55 time=50.2 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=5 ttl=55 time=49.6 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=6 ttl=55 time=51.0 ms
>
> was sagt im Anschluss ps aux | grep wpa* ?
Etch-nb:~# ps aux | grep wpa*
root 3771 0.0 0.0 3664 984 ? Ss 21:39
0:00 /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.eth2.pid -i eth2 -D
wext -C /var/run/wpa_supplicant
root 3857 0.0 0.0 2872 764 pts/1 S+ 21:41 0:00 grep wpa*
>
> Läuft dort der wpa_supplicant?
>
> Was sagt wpa_cli ? (Starten und dann Debug-Level mitgeben)
>
> level 0
> status
Etch-nb:~# wpa_cli
wpa_cli v0.5.5
Copyright (c) 2004-2006, Jouni Malinen <jkmaline@cc.hut.fi> and contributors
This program is free software. You can distribute it and/or modify it
under the terms of the GNU General Public License version 2.
Alternatively, this software may be distributed under the terms of the
BSD license. See README and COPYING for more details.
Selected interface 'eth2'
Interactive mode
> level 0
OK
> status
bssid=00:0f:c9:02:3f:1c
ssid=allnet
id=0
pairwise_cipher=TKIP
group_cipher=TKIP
key_mgmt=WPA-PSK
wpa_state=COMPLETED
ip_address=192.168.0.3
Wenn Du mir jetzt noch verrätst, was ich tun muss, damit es auch beim Booten
klappt, bin ich echt glücklich ;-)))
Danke schon im voraus.
Gruß
Michael
Reply to: