Michael Richardson wrote:
"Alexandru" == Alexandru Petrescu
Alexandru> If my node has mode "managed" it will never attach to laptop
Alexandru> having same key same essid but mode ad-hoc.
No, that's isn't true.
It is true for:
"ad-hoc" = Lucent Ad-HOC mode (deprecated)
but not true for:
"ad-hoc" = 802.11 IBSS mode
Ok, it is true that that behaviour I mentioned above was with Lucent
cards and Cisco (which I don't know what chipset). Also, I didn't know
they call "ad-hoc" IBSS where I is for Infrastructure.
So I guess I was wrong.
So instead of forcing key+essid on the clients, would setting the AP's
MAC address on the clients be a solution?
In fact, the client can't tell the difference between IBSS and BSS.
Nor can Linux systems become IBSS systems without something like "hostap"
(hostap is one way, wireless bridging might be another way I think.)