On Tue, 2013-06-25 at 00:20 -0400, jonsm...@gmail.com wrote:
Can this be made to work on Ralink? When I have the adhoc0 interface
up bringing up ap0 says interface busy.
Ralink is not good for supporting this type of setup. I had tried AP and
client mode, and after some hacking it sort-of
On Tue, Jun 25, 2013 at 8:25 AM, Conor O'Gorman i...@conorogorman.net wrote:
On Tue, 2013-06-25 at 00:20 -0400, jonsm...@gmail.com wrote:
Can this be made to work on Ralink? When I have the adhoc0 interface
up bringing up ap0 says interface busy.
Ralink is not good for supporting this
On 06/25/2013 11:09 AM, jonsm...@gmail.com wrote:
On Tue, Jun 25, 2013 at 8:25 AM, Conor O'Gorman i...@conorogorman.net wrote:
On Tue, 2013-06-25 at 00:20 -0400, jonsm...@gmail.com wrote:
Can this be made to work on Ralink? When I have the adhoc0 interface
up bringing up ap0 says interface
So how do you want batman-adv and allow normal clients to attach?
Maybe I should give 11S a try.
I loaded OpenWRT onto my AR9331 hardware It doesn't support mixing
adhoc (IBSS) and AP mode either.
valid interface combinations:
* #{ managed, WDS, P2P-client } = 2048, #{ AP, mesh point, P2P-GO }
Can this be made to work on Ralink? When I have the adhoc0 interface
up bringing up ap0 says interface busy.
Does it work on Atheros?
root@OpenWrt:/etc/config#
root@OpenWrt:/etc/config# ifconfig ap0 up
ifconfig: SIOCSIFFLAGS: Device or resource busy
root@OpenWrt:/etc/config#
