Summary: | ndiswrapper fails if ESSID contains a space | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jakob Schiotz <schiotz> |
Component: | [OLD] Unspecified | Assignee: | Mobile Herd (OBSOLETE) <mobile+disabled> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jakob Schiotz
2005-05-11 08:12:51 UTC
Yes it can. Read the /etc/conf.d/wireless.example file. You need to use a _ rather then the space. My ESSIDs all have space and it's always worked for me. It probably works if you specify the ESSID with a _ instead of a space, but I have my machine set up to connect to any wireless network, so I do not specify an ESSID anywhere. That works fine if I use the prism54 driver or the hostap driver, but not if I use the ndiswrapper. On another net, it works fine, and the only difference seems to be the space in the ESSID. In an alternative setup, I use wpa_supplicant. There, I have to specify all networks I want to be able to connect to, encrypted or unencrypted. Replacing the space with a _ does not work. But again, it appears to be connected to ndiswrapper, since my other laptop connects fine using the hostap driver and another network card. Best regards Jakob I use any as well. It works. Read the configuration files and check your configs, all I've got to say. OK, I will experiment. But I use the stable baselayout, so the file you referred to does not exist. I will unpack a copy of the latest ~x86 baselayout for inspiration. /Jakob |