>Alexandros C. Couloumbis <alex <at> ozo.com> writes:
> iwconfig, ifconfig & iwlist wlan0 scan from the wrap board:
>
> wlan0 IEEE 802.11abgn ESSID:"awmn"
> Mode:Ad-Hoc Frequency:5.745 GHz Cell: 0E:18:12:1E:75:73
> Tx-Power=23 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
> iwconfig, ifconfig & iwlist wlan0 scan on the alix board:
>
> wlan0 IEEE 802.11abgn ESSID:"awmn"
> Mode:Ad-Hoc Frequency:5.745 GHz Cell: E6:FE:0E:A1:77:22
> Tx-Power=23 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
This reply is almost a year in the making, but it looks like
your ad-hoc interfaces are creating new cells(new IBSS)
on initialization (you'll see that the 48-bit cell IDs are different).
Thus, even though they are on the same channel, same ESS ("awmn")
and within wireless range, they can't talk.
The 802.11 standards for IBSS (ad-hoc) mode specifies that
this problem should be solved by having the first interface to
establish a BSS periodically broadcasting a beacon so that newer
nodes get this beacon and associate to that cell.
However, for some reason ath9k doesn't handle this problem
correctly (ath5k did a good job with it).
In the meantime, you can specifically set the cell ID using
the iw command on all your interfaces (in this case the cell
ID is the 48-bit value made up of twos).
iw dev wlan0 ibss join "awmn" 5745 22:22:22:22:22:22
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
