linuxthefish wrote:
> It looks like Debian will only connect to a wireless network when the
> ethernet cable has been plugged in and unplugged.
No. If you are seeing this it is either a bug or a configuration or
use problem. Works fine for most of us. So my guess is a
configuration or use problem.
> Both the wired and wireless connections are set to automatically
> come up - but wireless will not come up and fails to respond to ping
> unless a ethernet cable has been plugged in.
Very odd.
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet static
> address 172.16.0.4
> gateway 172.16.0.1
> netmask 255.255.0.0
Looks okay to me. It is 'auto' so will be a boot time action.
> allow-hotplug wlan0
> iface wlan0 inet static
> wpa-conf /etc/wpa_supplicant/wpa_supplicant0.conf
> address 172.16.0.5
> gateway 172.16.0.1
> netmask 255.255.0.0
What are the contents of /etc/wpa_supplicant/wpa_supplicant0.conf
file? Feel free to redact any passwords.
You have this interface set up to be 'allow-hotplug' which means it is
using the event driven interface. That should be fine for the WiFi
interface. But maybe things are simply out of sync with file edits?
It is pretty easy to get mixed up and have edited the file with the
interface up. Edits should always happen with the interface down.
Have you tried manually bringing the interface up and down? What
errors are shown?
ifup wlan0
Have you verified the device names are the ones you expect? It is
possible that /etc/udev/rules.d/70-persistent-net.rules has renamed
the interface. This has tripped me many times.
ip addr show
I am not currently using that style in any of my wifi configs. For
better or worse. Mine all look like this example:
allow-hotplug wlan0
iface wlan0 inet static
wpa-ssid CherryFarmLink
wpa-psk passwordredacted
address 10.10.223.2
netmask 255.255.255.0
gateway 10.10.223.1
dns-search example.com
dns-nameservers 10.10.223.1
That works okay for me. This has the disadvantage of having the wifi
password in the /etc/network/interfaces file. But that isn't critical
information in my environment and there isn't general logins on the
router system anyway.
Bob
Attachment:
signature.asc
Description: Digital signature