But that is what I am asking!dhardingham wrote:Even WEP security works (don't ask).
Oddly enough I don't want to use up lots of RAM and be slow.it takes a significant amount of ram when you connect to a network ( and it's not so fast )
Rubbish, that is the sort of overly geek attitude that is part of the problem with the Linux community.but WEP security is only marginally better than no security at all.
Code: Select all
auto wlan0 iface wlan0 inet static address 192.168.1.67 netmask 255.255.255.0 gateway 192.168.1.1 wireless-essid myssid wireless-key mykey
Code: Select all
# The loopback network interface auto lo iface lo inet loopback # The primary (wired) network interface iface eth0 inet dhcp # The wifi (wireless) network interface auto wlan0 allow-hotplug wlan0 iface wlan0 inet dhcp wireless-essid MyNetworkname wireless-key MyPassword
I don't bite you know(the feared and famous Grumpy Mike, no less)
ricsxn wrote:I spent a lot of time attempting to link my old router authenticating with WEP using wpa_supplicant.
The following configuration at the end was successful:
# cat /etc/network/interfaces
iface lo inet loopback
iface eth0 inet dhcp
iface wlan0 inet manual
iface default inet dhcp
# cat /etc/wpa_supplicant/wpa_supplicant.conf
ssid="<other wpa ssid>"
I had the problem that configuring manually the wlan0 interface with:
# iwconfig wlan0 essid '<wep ssid>' key '<mykey>' # 10 digits hex key
# dhclient wlan0
everithing was fine
while using wpa_supplicant not!
At the end I recognized that iwconfig was reporting a different output in:
In the case of the manual configuration I could read the clear WEP password; in the case of wpa_supplicant it was something encrypted.
At the end I recognized that providing the value:
solved the problem
I really hope to help someone else getting the same problem!
Users browsing this forum: DPaul and 32 guests