Re: laptop wireless setup, wpa_supplicant.conf, driver ipw not supported? CLI only
Thanks Brian-
I installed ifplugd. Still, the wireless does not work if I unplug the
Ethernet, but now if I do a ifdown eth1 | ifup eth1 the wireless will now
connect (most of the time). Following is a session where the process
worked, followed by my interfaces and ifplugd files. Note a couple of
"Invalid argument" lines:
********************
>>>>>>>>>>>>>Begin by booting machine with Ethernet cable plugged in...
root@eve:~# ping google.com
PING google.com (74.125.225.82) 56(84) bytes of data.
64 bytes from ord08s07-in-f18.1e100.net (74.125.225.82): icmp_req=1 ttl=52
time=36.5 ms
64 bytes from ord08s07-in-f18.1e100.net (74.125.225.82): icmp_req=2 ttl=52
time=36.0 ms
64 bytes from ord08s07-in-f18.1e100.net (74.125.225.82): icmp_req=3 ttl=52
time=37.2 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 36.031/36.603/37.259/0.504 ms
>>>>>>>>>OK, now unplug Ethernet3 cable, wait a few seconds, then...
root@eve:~# ping google.com
ping: unknown host google.com
root@eve:~# ifdown eth1 -v
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient -v -r -pf /var/run/dhclient.eth1.pid -lf
/var/lib/dhcp/dhclient.eth1.leases eth1
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth1/00:0e:35:af:99:c1
Sending on LPF/eth1/00:0e:35:af:99:c1
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
ifconfig eth1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile
/var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 1924).
wpa_supplicant: removing
/run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.eth1.pid
root@eve:~# ifup eth1 -v
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
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: using debug level: 3
wpa_supplicant: /sbin/wpa_supplicant -s -B -P
/var/run/wpa_supplicant.eth1.pid -i eth1 -D wext -t -ddd -C
/var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
1319837959.027310: WPS: UUID based on MAC address - hexdump(len=16): d6 d2
60 92 b2 76 5f 55 91 ae 92 c6 0b 2e 93 05
wpa_supplicant: waiting for "/var/run/wpa_supplicant.eth1.pid": 0 (max. 5)
wpa_supplicant: creating sendsigs omission pidfile:
/run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.eth1.pid
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth1
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "gojo1985" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: enabling network block 0 -- OK
dhclient -v -pf /var/run/dhclient.eth1.pid -lf
/var/lib/dhcp/dhclient.eth1.leases eth1
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth1/00:0e:35:af:99:c1
Sending on LPF/eth1/00:0e:35:af:99:c1
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.6 -- renewal in 33086 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/ethtool
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant
***********************
root@eve:~# 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 eth0 is for ethernet wired connection
allow-hotplug eth0
iface eth0 inet dhcp
# the following two lines allow wakeonlan
# this runs ethtool after every time eth0 is brought up or taken down,
# so WOL should work even if not brought down correctly
post-up /sbin/ethtool -s $IFACE wol g
post-down /sbin/ethtool -s $IFACE wol g
#this next stanza is for the wireless card
allow-hotplug eth1
iface eth1 inet dhcp
# wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
wpa-debug-level 3
wpa-driver wext
wpa-ssid "gojo1985"
wpa-psk e0609ee9b0f20c1393f815c9c11759f41ca4b3f078146e842ad48ab692097f5d
***************************
root@eve:~# cat /etc/default/ifplugd
#[SNIP comments]
INTERFACES="eth0 eth1"
HOTPLUG_INTERFACES="eth0 eth1"
ARGS="-q -f -u0 -d10 -w -I"
SUSPEND_ACTION="stop"
******************************
> On Fri 28 Oct 2011 at 10:01:41 -0700, keitho@strucktower.com wrote:
>
> [Snip]
>
>> If I boot the machine with the Ethernet connected, the system uses that
>> connection via eth0. If I unplug the Ethernet I then can't get the
>> wireless to work unless I reboot. I have tried:
>>
>> /etc/init.d/networking stop|start as well as ifdown eth1 ifup eth1
>
> There is a reason why the first command may not work but at this stage it
> is probably best you post your /etc/network/interfaces content. The other
> commands not working is puzzling. What do you get with -v added to the
> command line?
>
>> but still the wireless doesn't connect. How do I "reset" it or somehow
>> configure the system to use the wireless subsequent to having the
>> Ethernet
>> pulled out, without rebooting the system?
>
> ifplugd is very, very useful.
>
Reply to: