kelsey hudson wrote:
[EMAIL PROTECTED] wrote:
Is this a driver issue or what??
Probably.
# iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning : Operation not supported
A lot of boards need to be in the 'UP' state to scan. If you do a,
'ifconfig eth0 up', then 'iwlist eth0 scanning', does this change the
behaviour?
ifconfig won't control the wireless connection. Use iwconfig instead.
(eth0 is my wifi card.) BTW, it is weird that eth0 is name
of my *wifi* interface.
nah, if you ask me, all ethernet-like interfaces (802.11 *is* ethernet)
should have an eth prefix. If not, we get into the same thing solaris
and the BSDs get into -- many different names for the same type of
interface. This keeps it simple and congruous across the board.
hope this helps ...
-kelsey
The interface is called whatever it's called. It depends on your
distribution, and the networking drivers being used. A commonly used
device name is wlan{n}.
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
