"Do you use the same keywords as I do in your /etc/network/interfaces? "
No. I use what is created by the networking tool.
"The configuration syntax for a linux-wlan-ng device (like prism2_usb)
is different from a normal wireless-tools device (like your atmel). The
Gnome tools only supports the latter. This is especially true for the
WEP setup. If the prism2_usb could be fixed to accept the IOCTLs used by
libiw28, everything would be simpler."
Perhaps I misunderstood the early responses to this bug, but I was under the assumption that this device is supposed to work out-of-the-box if linux-wlan-ng is installed and that my device was behaving differently than other prism2_usb devices in that respect.
I know that linux-wlan-ng uses different tools than the other wireless devices, but the debian scripts are supposed to wrap around the linux-wlan-ng commands and make the process the same.
So, has anyone plugged in a prism2_usb device and have it work out-of-the-box in ubuntu?
"Do you use the same keywords as I do in your /etc/network/ interfaces? "
No. I use what is created by the networking tool.
"The configuration syntax for a linux-wlan-ng device (like prism2_usb)
is different from a normal wireless-tools device (like your atmel). The
Gnome tools only supports the latter. This is especially true for the
WEP setup. If the prism2_usb could be fixed to accept the IOCTLs used by
libiw28, everything would be simpler."
Perhaps I misunderstood the early responses to this bug, but I was under the assumption that this device is supposed to work out-of-the-box if linux-wlan-ng is installed and that my device was behaving differently than other prism2_usb devices in that respect.
I know that linux-wlan-ng uses different tools than the other wireless devices, but the debian scripts are supposed to wrap around the linux-wlan-ng commands and make the process the same.
So, has anyone plugged in a prism2_usb device and have it work out-of-the-box in ubuntu?