Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
laptop wireless setup, wpa_supplicant.conf, driver ipw not supported? CLI only
145 views
Skip to first unread message
kei...@strucktower.com
Oct 27, 2011, 6:10:03 PM10/27/11
to
Hi All-
I am trying to learn how to setup wireless on one of my old Dell C610
laptops with an Intel IPW2200 wireless card using command line only. I
have a fresh install of 7.0 Wheezy (3.0), all updated, and the ipw
firmware loaded. According to the Debian Reference Manual I need to
configure wpa_supplicant as a next step. When I try to invoke it I get a
message saying the ipw driver isn't supported, although the man page for
wpa_supplicant states that ipw _is_ supported...(for now I am running all
these as root):
root@eve:~# wpa_supplicant -Dipw -c/etc/wpa_supplicant.conf -ieth0 -d
Initializing interface 'eth0' conf '/etc/wpa_supplicant.conf' driver 'ipw'
ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=root'
Priority group 0
id=0 ssid='gojo1985'
Unsupported driver 'ipw'.
Failed to add interface eth0
Cancelling scan request
Cancelling authentication timeout
Here's wpa_supplicant:
root@eve:~# cat /etc/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
network={
ssid="gojo1985"
scan_ssid=1
key_mgmt=WPA-PSK
psk="secret_password"
}
Here's:
root@eve:~# lsmod | grep ipw
ipw2200 114371 0
libipw 26111 1 ipw2200
cfg80211 112970 2 ipw2200,libipw
lib80211 12870 2 ipw2200,libipw
So what's going on here? Am I missing a step or misunderstanding
something? BTW, direct Ethernet connection works fine (uses eth1).
Thanks,
Keith
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/7dfe3d3a752103e70677...@webmail.strucktower.com
I am trying to learn how to setup wireless on one of my old Dell C610
laptops with an Intel IPW2200 wireless card using command line only. I
have a fresh install of 7.0 Wheezy (3.0), all updated, and the ipw
firmware loaded. According to the Debian Reference Manual I need to
configure wpa_supplicant as a next step. When I try to invoke it I get a
message saying the ipw driver isn't supported, although the man page for
wpa_supplicant states that ipw _is_ supported...(for now I am running all
these as root):
root@eve:~# wpa_supplicant -Dipw -c/etc/wpa_supplicant.conf -ieth0 -d
Initializing interface 'eth0' conf '/etc/wpa_supplicant.conf' driver 'ipw'
ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=root'
Priority group 0
id=0 ssid='gojo1985'
Unsupported driver 'ipw'.
Failed to add interface eth0
Cancelling scan request
Cancelling authentication timeout
Here's wpa_supplicant:
root@eve:~# cat /etc/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
network={
ssid="gojo1985"
scan_ssid=1
key_mgmt=WPA-PSK
psk="secret_password"
}
Here's:
root@eve:~# lsmod | grep ipw
ipw2200 114371 0
libipw 26111 1 ipw2200
cfg80211 112970 2 ipw2200,libipw
lib80211 12870 2 ipw2200,libipw
So what's going on here? Am I missing a step or misunderstanding
something? BTW, direct Ethernet connection works fine (uses eth1).
Thanks,
Keith
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/7dfe3d3a752103e70677...@webmail.strucktower.com
Brian
Oct 27, 2011, 6:40:01 PM10/27/11
to
On Thu 27 Oct 2011 at 14:45:38 -0700, kei...@strucktower.com wrote:
> I am trying to learn how to setup wireless on one of my old Dell C610
> laptops with an Intel IPW2200 wireless card using command line only. I
> have a fresh install of 7.0 Wheezy (3.0), all updated, and the ipw
> firmware loaded. According to the Debian Reference Manual I need to
> configure wpa_supplicant as a next step. When I try to invoke it I get a
> message saying the ipw driver isn't supported, although the man page for
> wpa_supplicant states that ipw _is_ supported...(for now I am running all
> these as root):
The man page also says:
> I am trying to learn how to setup wireless on one of my old Dell C610
> laptops with an Intel IPW2200 wireless card using command line only. I
> have a fresh install of 7.0 Wheezy (3.0), all updated, and the ipw
> firmware loaded. According to the Debian Reference Manual I need to
> configure wpa_supplicant as a next step. When I try to invoke it I get a
> message saying the ipw driver isn't supported, although the man page for
> wpa_supplicant states that ipw _is_ supported...(for now I am running all
> these as root):
For a list of supported driver backends that may be used with the
-D option on your system, refer to the help output of wpa_supplicant
(wpa_supplicant -h).
You should find the README.Debian very useful.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Raf Czlonka
Oct 27, 2011, 7:50:01 PM10/27/11
to
On Thu, Oct 27, 2011 at 10:45:38PM BST, kei...@strucktower.com wrote:
> [...]
> root@eve:~# wpa_supplicant -Dipw -c/etc/wpa_supplicant.conf -ieth0 -d
> [...]
Drop -D option, wpasupplicant will use wext, which is the default -
should work just fine. You can also try nl80211.
> root@eve:~# cat /etc/wpa_supplicant.conf
On Debian, there's already a directory /etc/wpa_supplicant/, it might be
worth putting it there.
There's no need to run wpa_supplicant "by hand" - it integrates nicely
with ifupdown. You can simply put:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
into your /etc/network/interfaces (add "wpa-debug-level 3" if you're
having problems) and use ifupdown.
Already suggested - read documents in /usr/share/doc/wpasupplicant.
Regards,
--
Raf
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2011102723...@linuxstuff.pl
> [...]
> configure wpa_supplicant as a next step. When I try to invoke it I get a
> message saying the ipw driver isn't supported, although the man page for
> wpa_supplicant states that ipw _is_ supported...(for now I am running all
> these as root):
Clearly man page is out of date - file a bug.
> message saying the ipw driver isn't supported, although the man page for
> wpa_supplicant states that ipw _is_ supported...(for now I am running all
> these as root):
> root@eve:~# wpa_supplicant -Dipw -c/etc/wpa_supplicant.conf -ieth0 -d
Drop -D option, wpasupplicant will use wext, which is the default -
should work just fine. You can also try nl80211.
> root@eve:~# cat /etc/wpa_supplicant.conf
On Debian, there's already a directory /etc/wpa_supplicant/, it might be
worth putting it there.
There's no need to run wpa_supplicant "by hand" - it integrates nicely
with ifupdown. You can simply put:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
into your /etc/network/interfaces (add "wpa-debug-level 3" if you're
having problems) and use ifupdown.
Already suggested - read documents in /usr/share/doc/wpasupplicant.
Regards,
--
Raf
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
kei...@strucktower.com
Oct 27, 2011, 9:10:02 PM10/27/11
to
Thanks Brian-
Well, that's confusing... for the man page to say one thing and the
README.Debian file to say another...
OK, so I missed the section that says:
*****
A summary of supported drivers follows:
Driver Description
====== ===========
nl80211 Linux 802.11 netlink interface
wext Linux wireless extensions (generic)
wired wired Ethernet driver
*****
BUT... I had actually tried the wext driver as well...and it had failed
with this output:
root@eve:~# wpa_supplicant -Dwext -c/etc/wpa_supplicant.conf -ieth0 -d
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Operation not supported
ioctl[SIOCGIWMODE]: Operation not supported
ioctl[SIOCSIWAP]: Operation not supported
WEXT: Failed to set bogus BSSID/SSID to disconnect
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 00:08:74:47:75:4b
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
* many more similar lines snipped *
It does this even after I unload the ipw module... So I am still evidently
missing a step... Will a bad wpa_supplicant.conf or
/etc/network/interfaces cause this kind of error?
Keith
> On Thu 27 Oct 2011 at 14:45:38 -0700, kei...@strucktower.com wrote:
>
>> I am trying to learn how to setup wireless on one of my old Dell C610
>> laptops with an Intel IPW2200 wireless card using command line only. I
>> have a fresh install of 7.0 Wheezy (3.0), all updated, and the ipw
>> firmware loaded. According to the Debian Reference Manual I need to
Well, that's confusing... for the man page to say one thing and the
README.Debian file to say another...
OK, so I missed the section that says:
*****
A summary of supported drivers follows:
Driver Description
====== ===========
nl80211 Linux 802.11 netlink interface
wext Linux wireless extensions (generic)
wired wired Ethernet driver
*****
BUT... I had actually tried the wext driver as well...and it had failed
with this output:
root@eve:~# wpa_supplicant -Dwext -c/etc/wpa_supplicant.conf -ieth0 -d
Initializing interface 'eth0' conf '/etc/wpa_supplicant.conf' driver
'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=root'
Priority group 0
id=0 ssid='gojo1985'
ioctl[SIOCSIWMODE]: Operation not supported
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=root'
Priority group 0
id=0 ssid='gojo1985'
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Operation not supported
ioctl[SIOCGIWMODE]: Operation not supported
ioctl[SIOCSIWAP]: Operation not supported
WEXT: Failed to set bogus BSSID/SSID to disconnect
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 00:08:74:47:75:4b
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
* many more similar lines snipped *
It does this even after I unload the ipw module... So I am still evidently
missing a step... Will a bad wpa_supplicant.conf or
/etc/network/interfaces cause this kind of error?
Keith
> On Thu 27 Oct 2011 at 14:45:38 -0700, kei...@strucktower.com wrote:
>
>> I am trying to learn how to setup wireless on one of my old Dell C610
>> laptops with an Intel IPW2200 wireless card using command line only. I
>> have a fresh install of 7.0 Wheezy (3.0), all updated, and the ipw
>> firmware loaded. According to the Debian Reference Manual I need to
>> configure wpa_supplicant as a next step. When I try to invoke it I get a
>> message saying the ipw driver isn't supported, although the man page for
>> wpa_supplicant states that ipw _is_ supported...(for now I am running
>> all
>> these as root):
>
>> message saying the ipw driver isn't supported, although the man page for
>> wpa_supplicant states that ipw _is_ supported...(for now I am running
>> all
>> these as root):
>
> The man page also says:
>
> For a list of supported driver backends that may be used with the
> -D option on your system, refer to the help output of wpa_supplicant
> (wpa_supplicant -h).
>
> You should find the README.Debian very useful.
>
>
> For a list of supported driver backends that may be used with the
> -D option on your system, refer to the help output of wpa_supplicant
> (wpa_supplicant -h).
>
> You should find the README.Debian very useful.
>
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/a2dce2a70d3271515b95...@webmail.strucktower.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
J. Bakshi
Oct 28, 2011, 2:10:02 AM10/28/11
to
On Fri, 28 Oct 2011 00:43:08 +0100
Raf Czlonka <r...@linuxstuff.pl> wrote:
[....]
> There's no need to run wpa_supplicant "by hand" - it integrates nicely
> with ifupdown. You can simply put:
>
> iface eth0 inet dhcp
> wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
>
> into your /etc/network/interfaces (add "wpa-debug-level 3" if you're
> having problems) and use ifupdown.
[....]
I am doing it differently and it is complex.
1. I have following at /etc/rc.loacl
` ` ` `
wpa_supplicant -B -Dnl80211 -iwlan0 -c /usr/local/etc/my.wpa_supplicant.conf
` ` ` `
and at /etc/network/interfaces I have
` ` ` `
mapping wlan0
script guessnet-ifupdown
map default: office-wifi
map office-wifi open unknown
map timeout: 12
# map init-time: 12 # for slow drivers
map verbose: true
map debug: true
iface office-wifi inet dhcp
test wireless mac 00:1C:F0:3D:4C:C9
post-up /root/bin/FIREWALL start
# if all else fails: pick an open network
iface open inet dhcp
test wireless open
wireless-essid any
wireless-mode auto
` ` ` `
How can I remove the wpa related entry from rc.local and add directly at /etc/interfaces ?
Thanks
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20111028113...@shiva.selfip.org
Raf Czlonka <r...@linuxstuff.pl> wrote:
[....]
> There's no need to run wpa_supplicant "by hand" - it integrates nicely
> with ifupdown. You can simply put:
>
> iface eth0 inet dhcp
> wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
>
> into your /etc/network/interfaces (add "wpa-debug-level 3" if you're
> having problems) and use ifupdown.
I am doing it differently and it is complex.
1. I have following at /etc/rc.loacl
` ` ` `
wpa_supplicant -B -Dnl80211 -iwlan0 -c /usr/local/etc/my.wpa_supplicant.conf
` ` ` `
and at /etc/network/interfaces I have
` ` ` `
mapping wlan0
script guessnet-ifupdown
map default: office-wifi
map office-wifi open unknown
map timeout: 12
# map init-time: 12 # for slow drivers
map verbose: true
map debug: true
iface office-wifi inet dhcp
test wireless mac 00:1C:F0:3D:4C:C9
post-up /root/bin/FIREWALL start
# if all else fails: pick an open network
iface open inet dhcp
test wireless open
wireless-essid any
wireless-mode auto
` ` ` `
How can I remove the wpa related entry from rc.local and add directly at /etc/interfaces ?
Thanks
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Oct 28, 2011, 5:10:01 AM10/28/11
to
On Thu 27 Oct 2011 at 17:42:18 -0700, kei...@strucktower.com wrote:
> BUT... I had actually tried the wext driver as well...and it had failed
> with this output:
>
> root@eve:~# wpa_supplicant -Dwext -c/etc/wpa_supplicant.conf -ieth0 -d
> Initializing interface 'eth0' conf '/etc/wpa_supplicant.conf' driver
If the wireless interface is indeed eth0 there could be lots of debugging
> BUT... I had actually tried the wext driver as well...and it had failed
> with this output:
>
> root@eve:~# wpa_supplicant -Dwext -c/etc/wpa_supplicant.conf -ieth0 -d
> Initializing interface 'eth0' conf '/etc/wpa_supplicant.conf' driver
ahead of us. If not .....
As Raf Czlonka has already said, using /etc/network/interfaces and its
integration with wpa_supplicant is the way to go. You do not even need a
wpa_supplicant.conf file.
iface eth0 inet dhcp
wpa-ssid myssid
wpa-psk passphrase
should give a working setup.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Raf Czlonka
Oct 28, 2011, 7:40:02 AM10/28/11
to
On Fri, Oct 28, 2011 at 09:46:25AM BST, Brian wrote:
> As Raf Czlonka has already said, using /etc/network/interfaces and its
> integration with wpa_supplicant is the way to go. You do not even need a
> wpa_supplicant.conf file.
You don't, for simple setup that is indeed enough.
> As Raf Czlonka has already said, using /etc/network/interfaces and its
> integration with wpa_supplicant is the way to go. You do not even need a
> wpa_supplicant.conf file.
If you have several wireless networks you can keep your interfaces file
tidy and organised, not to mention that roaming mode won't work without
wpa_supplicant.conf file.
> iface eth0 inet dhcp
> wpa-ssid myssid
> wpa-psk passphrase
I also recommend actual PSK rather than passphrase.
> iface eth0 inet dhcp
> wpa-ssid myssid
> wpa-psk passphrase
man wpa_passphrase.
Regards,
--
Raf
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
J. Bakshi
Oct 28, 2011, 7:50:01 AM10/28/11
to
On Fri, 28 Oct 2011 12:36:26 +0100
Raf Czlonka <r...@linuxstuff.pl> wrote:
> On Fri, Oct 28, 2011 at 09:46:25AM BST, Brian wrote:
> > As Raf Czlonka has already said, using /etc/network/interfaces and its
> > integration with wpa_supplicant is the way to go. You do not even need a
> > wpa_supplicant.conf file.
>
> You don't, for simple setup that is indeed enough.
> If you have several wireless networks you can keep your interfaces file
> tidy and organised, not to mention that roaming mode won't work without
> wpa_supplicant.conf file.
>
> > iface eth0 inet dhcp
> > wpa-ssid myssid
> > wpa-psk passphrase
>
> I also recommend actual PSK rather than passphrase.
>
> man wpa_passphrase.
>
> Regards,
Raf Czlonka <r...@linuxstuff.pl> wrote:
> On Fri, Oct 28, 2011 at 09:46:25AM BST, Brian wrote:
> > As Raf Czlonka has already said, using /etc/network/interfaces and its
> > integration with wpa_supplicant is the way to go. You do not even need a
> > wpa_supplicant.conf file.
>
> You don't, for simple setup that is indeed enough.
> If you have several wireless networks you can keep your interfaces file
> tidy and organised, not to mention that roaming mode won't work without
> wpa_supplicant.conf file.
>
> > iface eth0 inet dhcp
> > wpa-ssid myssid
> > wpa-psk passphrase
>
> I also recommend actual PSK rather than passphrase.
>
> man wpa_passphrase.
>
> Regards,
I am doing it differently and it is complex.
1. I have following at /etc/rc.loacl
` ` ` `
wpa_supplicant -B -Dnl80211 -iwlan0 -c /usr/local/etc/my.wpa_supplicant.conf
` ` ` `
and at /etc/network/interfaces I have
` ` ` `
mapping wlan0
script guessnet-ifupdown
map default: office-wifi
map office-wifi open unknown
map timeout: 12
# map init-time: 12 # for slow drivers
map verbose: true
map debug: true
iface office-wifi inet dhcp
test wireless mac 00:1C:F0:3D:4C:C9
post-up /root/bin/FIREWALL start
# if all else fails: pick an open network
iface open inet dhcp
test wireless open
wireless-essid any
wireless-mode auto
` ` ` `
How can I remove the wpa related entry from rc.local and add directly at /etc/interfaces ?
Thanks
1. I have following at /etc/rc.loacl
` ` ` `
wpa_supplicant -B -Dnl80211 -iwlan0 -c /usr/local/etc/my.wpa_supplicant.conf
` ` ` `
and at /etc/network/interfaces I have
` ` ` `
mapping wlan0
script guessnet-ifupdown
map default: office-wifi
map office-wifi open unknown
map timeout: 12
# map init-time: 12 # for slow drivers
map verbose: true
map debug: true
iface office-wifi inet dhcp
test wireless mac 00:1C:F0:3D:4C:C9
post-up /root/bin/FIREWALL start
# if all else fails: pick an open network
iface open inet dhcp
test wireless open
wireless-essid any
wireless-mode auto
` ` ` `
How can I remove the wpa related entry from rc.local and add directly at /etc/interfaces ?
Thanks
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20111028171...@shiva.selfip.org
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Raf Czlonka
Oct 28, 2011, 8:10:02 AM10/28/11
to
On Fri, Oct 28, 2011 at 07:04:10AM BST, J. Bakshi wrote:
> How can I remove the wpa related entry from rc.local and add directly at /etc/interfaces ?
Please read /usr/share/doc/wpasupplicant/README.Debian.gz - you can find
> How can I remove the wpa related entry from rc.local and add directly at /etc/interfaces ?
all the answers there.
A couple of hints:
wpa-driver nl80211
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
in /etc/network/interfaces.
"id_str" in wpa_supplicant.conf
P.S. Please send only one reply, not four exactly the same ones.
--
Raf
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
kei...@strucktower.com
Oct 28, 2011, 1:20:02 PM10/28/11
to
Thank you Brian and Raf-
I learned several things from both of you, and I really appreciate it :-)
It took me several hours with your help- without your help I would still
be struggling with it.
Turns out, Brian was right to warn me about making sure I was using the
correct interface- I was not. Turns out that the wireless is eth1, not
eth0.
I have it working now with the wext driver- it would not work with the
nl80211 driver.
I can confirm that the wpa_supplicant.conf file is not needed in this very
simple setup. Thanks Raf for confirming that I will need it for setting up
roaming (when I get to that).
I'd like to ask one more question, not sure if I should start a new thread
for it since it is related to debugging the situation:
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
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?
Thanks,
Keith
> On Fri, Oct 28, 2011 at 09:46:25AM BST, Brian wrote:
>> As Raf Czlonka has already said, using /etc/network/interfaces and its
>> integration with wpa_supplicant is the way to go. You do not even need a
>> wpa_supplicant.conf file.
>
> You don't, for simple setup that is indeed enough.
> If you have several wireless networks you can keep your interfaces file
> tidy and organised, not to mention that roaming mode won't work without
> wpa_supplicant.conf file.
>
>> iface eth0 inet dhcp
>> wpa-ssid myssid
>> wpa-psk passphrase
>
> I also recommend actual PSK rather than passphrase.
>
> man wpa_passphrase.
>
> Regards,
I learned several things from both of you, and I really appreciate it :-)
It took me several hours with your help- without your help I would still
be struggling with it.
Turns out, Brian was right to warn me about making sure I was using the
correct interface- I was not. Turns out that the wireless is eth1, not
eth0.
I have it working now with the wext driver- it would not work with the
nl80211 driver.
I can confirm that the wpa_supplicant.conf file is not needed in this very
simple setup. Thanks Raf for confirming that I will need it for setting up
roaming (when I get to that).
I'd like to ask one more question, not sure if I should start a new thread
for it since it is related to debugging the situation:
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
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?
Thanks,
Keith
> On Fri, Oct 28, 2011 at 09:46:25AM BST, Brian wrote:
>> As Raf Czlonka has already said, using /etc/network/interfaces and its
>> integration with wpa_supplicant is the way to go. You do not even need a
>> wpa_supplicant.conf file.
>
> You don't, for simple setup that is indeed enough.
> If you have several wireless networks you can keep your interfaces file
> tidy and organised, not to mention that roaming mode won't work without
> wpa_supplicant.conf file.
>
>> iface eth0 inet dhcp
>> wpa-ssid myssid
>> wpa-psk passphrase
>
> I also recommend actual PSK rather than passphrase.
>
> man wpa_passphrase.
>
> Regards,
> --
> Raf
>
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2f609a15bac2b8e5c712...@webmail.strucktower.com
> Raf
>
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Oct 28, 2011, 1:40:02 PM10/28/11
to
On Fri 28 Oct 2011 at 12:36:26 +0100, Raf Czlonka wrote:
> On Fri, Oct 28, 2011 at 09:46:25AM BST, Brian wrote:
> > As Raf Czlonka has already said, using /etc/network/interfaces and its
> > integration with wpa_supplicant is the way to go. You do not even need a
> > wpa_supplicant.conf file.
>
> You don't, for simple setup that is indeed enough.
> If you have several wireless networks you can keep your interfaces file
> tidy and organised, not to mention that roaming mode won't work without
> wpa_supplicant.conf file.
Yes, I'd agree with that; it gives a very flexible and powerful
> On Fri, Oct 28, 2011 at 09:46:25AM BST, Brian wrote:
> > As Raf Czlonka has already said, using /etc/network/interfaces and its
> > integration with wpa_supplicant is the way to go. You do not even need a
> > wpa_supplicant.conf file.
>
> You don't, for simple setup that is indeed enough.
> If you have several wireless networks you can keep your interfaces file
> tidy and organised, not to mention that roaming mode won't work without
> wpa_supplicant.conf file.
configuration, especially if wpagui is also used. However, if one has
been stumbling along there is something to be said for walking before
running.
> > iface eth0 inet dhcp
> > wpa-ssid myssid
> > wpa-psk passphrase
>
> I also recommend actual PSK rather than passphrase.
converted to a 64 hex string internally anyway. A disadvantage is passing
an incomprehensible PSK on to someone to allow a connection to a network.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Oct 28, 2011, 2:00:03 PM10/28/11
to
On Fri 28 Oct 2011 at 10:01:41 -0700, kei...@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.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20111028173805.GA18382@desktop
[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
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?
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Oct 28, 2011, 6:10:02 PM10/28/11
to
On Fri 28 Oct 2011 at 18:38:05 +0100, Brian wrote:
> The other
> commands not working is puzzling.
Much too hasty a statement. When the ethernet cable is unplugged the
> The other
> commands not working is puzzling.
eth0 interface remains configured. '/sbin/route -n' and '/sbin/ifconfig'
before and afterwards will have the same outputs.
'ifup -v eth1' will bring up the wireless interface but the default
route will still be through eth0, as shown by the route command. This
goes nowhere because the cable is not connected and you can only get to
the local network through eth1.
'ifdown -v eth0' followed by 'ifup -v eth1' should be more fruitful.
The ifplugd package automates this.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
kei...@strucktower.com
Oct 28, 2011, 6:20:01 PM10/28/11
to
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, kei...@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.
>
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, kei...@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.
>
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/a2c6ffe72382f40c6276...@webmail.strucktower.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
J. Bakshi
Oct 29, 2011, 12:40:02 AM10/29/11
to
On Fri, 28 Oct 2011 14:54:38 -0700
kei...@strucktower.com wrote:
> Thanks Brian-
>
> I installed ifplugd. Still, the wireless does not work if I unplug the
> Ethernet,
assuming you have ifplugd + guessnet
kei...@strucktower.com wrote:
> Thanks Brian-
>
> I installed ifplugd. Still, the wireless does not work if I unplug the
> Ethernet,
edit * /etc/default/ifplugd *
INTERFACES="eth0 wlan0"
HOTPLUG_INTERFACES=""
#ARGS="-q -f -u0 -d10 -w -I"
ARGS="-f -u0 -d10 -w -I"
SUSPEND_ACTION="stop"
# wlan0 = wifi device, change accordingly
at /etc/network/interfaces
for wired connection add the following
` ` ``
pre-up /sbin/ifdown wlan0
pre-up /sbin/iwconfig wlan0 txpower off
down /sbin/iwconfig wlan0 txpower on
` ` `
I have made a autodetector based on ifplugd+guessnet which is working
for years for both wired and wifi
Thanks
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Oct 29, 2011, 6:00:02 AM10/29/11
to
On Fri 28 Oct 2011 at 14:54:38 -0700, kei...@strucktower.com wrote:
> 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:
I unconscienciously wrote my previous post with static addressing (which
> 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:
is what is on this machine for some connections) in mind. However, the
thrust of it is still correct: booting with the ethernet cable attached
gives you two operative interfaces and can lead to some messing about to
get just one in action.
> 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
> 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
> 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
A word about 'wpa-driver wext'. The supplicant takes care of choosing
the driver. On Squeeze the order is wext, nl80211. On testing and
unstable it is nl80211, wext. The line could be superfluous.
> INTERFACES="eth0 eth1"
INTERFACES=""
> HOTPLUG_INTERFACES="eth0 eth1"
HOTPLUG_INTERFACES="eth0"
You want to manage the interfaces by connecting and disconnecting the
ethernet cable. Disconnecting causes wpa_supplicant to bring eth1 up,
See /etc/wpa_supplicant/action_wpa.sh.
You may like this:
http://manual.aptosid.com/en/inet-ifplug-en.htm
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Raf Czlonka
Oct 29, 2011, 6:40:02 AM10/29/11
to
On Fri, Oct 28, 2011 at 06:22:00PM BST, Brian wrote:
> > You don't, for simple setup that is indeed enough.
> > If you have several wireless networks you can keep your interfaces file
> > tidy and organised, not to mention that roaming mode won't work without
> > wpa_supplicant.conf file.
>
> Yes, I'd agree with that; it gives a very flexible and powerful
> configuration, especially if wpagui is also used. However, if one has
> been stumbling along there is something to be said for walking before
> running.
Keeping things in one place is a good practice IMHO.
> > You don't, for simple setup that is indeed enough.
> > If you have several wireless networks you can keep your interfaces file
> > tidy and organised, not to mention that roaming mode won't work without
> > wpa_supplicant.conf file.
>
> Yes, I'd agree with that; it gives a very flexible and powerful
> configuration, especially if wpagui is also used. However, if one has
> been stumbling along there is something to be said for walking before
> running.
Security is another - /etc/network/interfaces is world readable by
default. Better keep settings like passphrase or PSK in one, root
readable file.
> > I also recommend actual PSK rather than passphrase.
>
> I'm unsure of the advantage this brings as an ASCII passphrase is
> converted to a 64 hex string internally anyway. A disadvantage is passing
> an incomprehensible PSK on to someone to allow a connection to a network.
filesystem.
PSK is precomputed from a passphrase for a specific SSID and passphrase
cannot be quantified from it.
There's no disadvantage as you can still use the passphrase, there's no
need to pass the long PSK.
Regards,
--
Raf
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Oct 30, 2011, 8:00:01 AM10/30/11
to
On Sat 29 Oct 2011 at 11:37:37 +0100, Raf Czlonka wrote:
> Main advantage - you're not keeping your passphrase in clear text on your
> filesystem.
> PSK is precomputed from a passphrase for a specific SSID and passphrase
> cannot be quantified from it.
What difference does that make? A file which is not world-readable for
> Main advantage - you're not keeping your passphrase in clear text on your
> filesystem.
> PSK is precomputed from a passphrase for a specific SSID and passphrase
> cannot be quantified from it.
one is not world-readable the other.
Having the psk in hex saves converting a passphrase internally, which
may be an advantage. I believe there are also devices which are unhappy
with being given an ASCII passphrase, so that also may be an advantage.
I really don't know, but security concerns don't appear to be a sound
reason.
> There's no disadvantage as you can still use the passphrase, there's no
> need to pass the long PSK.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages