|
Quote:
What type of encryption does your router use? This is the entry that should contain your key if you are using WPA_PSK: WIRELESS_WPA_PSK='' The key needs to match the router's. Also fill in one of these lines: WIRELESS_CHANNEL='' WIRELESS_FREQUENCY='' You can monitor the authentication process with the command: sudo /usr/sbin/wpa_cli -p /var/run/wpa_supplicant -i wlan0 The -p parameter is the directory wpa_supplicant uses. The -i parameter is the interface name. --- Unless you have to use WEP because of older equipment, use WPA instead. WEP isn't secure. |
Thank you so much! It works now. It's like Chrismas again! :-)
Adding the channel and checking with the router did the trick. I don't know, when it happened, but the wlan was not activated today. I hope that this was not one of the causes for my problems the last two days as well. But without the channel it is not working, so this was necessary as well. I could use WPA. I tried it about a minute ago, but then it didn't work again. I added the password at WIRELESS_WPA_PASSWORD='' but I didn't know what to add at WIRELESS_WPA_PSK='' Is it very insecure to run it under WEP? |
i'm having the same problem i'm on debian etch i have a compaq c500 and the chipset of the card is bcm43xx i tryed the solution of useing bcmwl5 instead of bcmwl6 (it came with vista pre-loaded and i figured as well to use the driver bcmwl6 in the Swsetup folder)
# ndiswrapper -l installed drivers: bcmwl5 driver installed (alternate driver: bcm43xx) i'm so lost right now any help would be awsome |
Quote:
Look in the ndiswrapper wiki and see what they recommendfor your device. Quote:
You can also enter the WPA key in YaST2. Remember that the router needs the same key. Here is a one-liner that I wrote to generate a random 32 byte key: Code:
dd bs=1 count=32 if=/dev/random | od -t x1 | sed -n -e 's/^.\{8\}//' -e 's/ //g' -e 1pIn YaST2, there is a button indicating that the key is a hex key. In the router I just enter it in. Use the same key for each computer. Putting the key on a pen drive to distribute it is the easiest way to go. |
My "problem" with WPA is:
On the server side, i.e. FritzBox, I can choose between TKIP (WPA) and AES (WPA2) as modes, whereas on the client side, in YaST, I have the choice of using "open", "Shared Key", "WPA-EAP" and (as you have suggested "WPA-PSK". Maybe I trying to match different concept? Another problem is the passphrase. FritzBox accepts the 32 Byte key, produced in a term with your command string, but Yast rejects it, saying it should be 64 Byte long (with key input type Hexadecimal, maybe this is wrong? Just passphrase?) Thank you very much for your help! |
TKIP (WPA) and AES (WPA2) as modes, whereas on the client side, in YaST, I have the choice of using "open", "Shared Key", "WPA-EAP" and (as you have suggested "WPA-PSK".
TKIP (WPA) matches WPA_PSK. You can use that. I'm not certain if WPA2 is the same as WPA-EAP. I think for that one you may supply a certificate and the AP communicates with a key server. I don't understand how you enter the 32 byte key in the Fritz box. A 64 hexadecimal key is a representation of 32 bytes. My one-liner converted 32 random bytes to a 64 hexadecimal representation. On my Linksys router, if I enter a 64 hex digit number, it is taken as a 32 byte key and not an ASCII key phrase. |
I have a HP dv6226us I'm trying to get working. I had read the Vista drivers weren't good, so I tried to use the same one you did the bcmwl5.inf and when I tried to use ndiswrapper it told me that it was an invalid driver! Lucky soul, I still don't have mine working. When you got yours working, did the wireless light on the front turn blue like it does under windows? I can't tell if mine is going to work or not, there is no wireless around here, I am trying to get wireless working so I can take it to internet cafe & get updates for SUSE 10.1.
I had to use ndiswrapper and bcmwl6.inf which is the vista driver. |
wlan not working again
I am desolate. I tried for hours to get the wlan working again. The one I got working with the help of this forum last March.
When I start ifup eth0 I get the messages: eth0 device: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01) eth0 starting wpa_client Starting DHCP Client Daemon on eth0 ........... no IP address yet .... backgrounding That's it. No connection. iwlist eth0 scan gives me "eth0 No scan results" The wlan is working properly, as I can see with a Windows computer ;-( I am not sure, if YaST might have destroyed the ifcfg-eth0 in /etc/sysconfig/network In ifcfg-eth0 are entries for: BOOTPROTO='dhcp' IFPLUGED_PRIORITY='10' NAME='Hewlett-Packard Company BCM94311MCG wlan mini-PCI' STARTMODE='hotplug' USERCONTROL='yes' WIRELESS_AUTH_MODE='psk' WIRELESS_BITRATE='auto' WIRELESS_ESSID='FRITZ!Box Fon WLAN 7170' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_WPA_PSK='3225237878878887' What can I do now? Please help me! Best wises, Bernard |
Quote:
|
| All times are GMT -5. The time now is 07:37 AM. |