Re: WLAN automatisch beim Booten?
Am Montag, 25. Juni 2007 23:42 schrieb Michael Lansche:
Ich verstehe es nicht :-(((
Mein neuster Versuch:
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
iface eth2 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.mynet.conf
wpa-driver wext
auto eth2
Etch-nb:~# cat /etc/wpa_supplicant/wpa_supplicant.mynet.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="allnet"
proto=WPA
pairwise=TKIP
psk="MeinPW"
priority=1
}
Auszug aus /var/log/boot/log:
Tue Jun 26 21:10:57 2007: Setting up networking....
Tue Jun 26 21:10:57 2007: Starting ipw3945 regulatory daemon: ipw3945d.
Tue Jun 26 21:11:00 2007: Configuring network interfaces...Internet Systems
Consortium DHCP Client V3.0.4
Tue Jun 26 21:11:01 2007: Copyright 2004-2006 Internet Systems Consortium.
Tue Jun 26 21:11:01 2007: All rights reserved.
Tue Jun 26 21:11:01 2007: For info, please visit http://www.isc.org/sw/dhcp/
Tue Jun 26 21:11:01 2007:
Tue Jun 26 21:11:02 2007: Listening on LPF/eth2/00:1b:77:38:26:de
Tue Jun 26 21:11:02 2007: Sending on LPF/eth2/00:1b:77:38:26:de
Tue Jun 26 21:11:02 2007: Sending on Socket/fallback
Tue Jun 26 21:11:03 2007: DHCPDISCOVER on eth2 to 255.255.255.255 port 67
interval 5
Tue Jun 26 21:11:08 2007: DHCPDISCOVER on eth2 to 255.255.255.255 port 67
interval 10
Tue Jun 26 21:11:18 2007: DHCPDISCOVER on eth2 to 255.255.255.255 port 67
interval 21
Tue Jun 26 21:11:39 2007: DHCPDISCOVER on eth2 to 255.255.255.255 port 67
interval 18
Tue Jun 26 21:11:57 2007: DHCPDISCOVER on eth2 to 255.255.255.255 port 67
interval 7
Tue Jun 26 21:12:04 2007: No DHCPOFFERS received.
Tue Jun 26 21:12:04 2007: No working leases in persistent database - sleeping.
Tue Jun 26 21:12:04 2007: done.
Wenn ich dann zunächst
ifdown -v eth2
und dann
ifup -v eth2
eingebe, bin ich sofort online:
Etch-nb:~# ifup -v eth2
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: wpa-driver wext
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
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth2
dhclient3 -pf /var/run/dhclient.eth2.pid -lf /var/lib/dhcp3/dhclient.eth2.leases
eth2
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 8
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 12
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 122902 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.
Was läuft hier falsch?
Es kann sich doch nur noch um einen winzig kleinen Schritt handeln, bis es
automatisch beim Booten klappt, oder?
Vielen Dank für Hinweise.
Gruß
Michael
Reply to: