Displaying 3 results from an estimated 3 matches for "ipw0".
Did you mean:
ipw
2006 Mar 07
2
ipw can not work in adhoc mode
...>
<dt><strong>Description</strong></dt><dd>
</dd>
<dd><pre>
The machine running windows is set to adhoc mode.
ssid is cat
On FreeBSD machine, I type:
----------------------------------
ipwcontrol -f /usr/local/share/ipw-firmware/ipw-i.fw
ifconfig ipw0 mediaopt adhoc
ifconfig ipw0 ssid cat
ifconfig ipw0 192.168.0.1 netmask 255.255.255.0
ifconfig ipw0 up
-------------------------------------
the led of wireless is on.
then the windows machine says that it has detected a wireless network..
I choose join..and it said that the signal is very good....
2006 Apr 06
0
How to clear the list returned by ifconfig ipw0 list scan
Hello,
when going mobile and scanning lots of APs, the old and no longer
reachable APs don't get flushed from the list. That means, the list can
only grow.
Thus, I currently have a list of 17 APs, yet none of them is even
remotely reachable. I already tried up/down'ing the interface and
reloading the firmware, yet no change.
Wouldn't such a feature be useful?
Ulrich Spoerlein
--
2006 Apr 06
1
[panic] ipw and kismet
...etimes kismet works, sometimes it doesn't. A sure way to
trigger the panic is to switch between bss/ibss/monitor mode prior to
running kismet. Perhaps there is a bug in the re-initialization when
loading a different firmware?
Is this panic known? Does the new firmware-framework address this?
ipw0: <Intel(R) PRO/Wireless 2100 MiniPCI> mem 0xfaffc000-0xfaffcfff irq 9 at device 3.0 on pci2
...
panic: mutex ipw0 recursed at /usr/src/sys/kern/kern_synch.c:177
KDB: enter: panic
[thread pid 1527 tid 100119 ]
Stopped at kdb_enter+0x2b: nop
db> tr
Tracing pid 1527 tid 100119 td 0xc5cca...