Hi again,
i was trying to add another virtual interface to a usb dongle wn722n,
(ath9k_htc driver)
the same way i'm used with ath9k (not _htc) interfaces
only to find out it's not supported in the _htc driver :(

# iw wlan1 interface add blah1 type adhoc
# iw dev
phy#1
        Interface blah1
                ifindex 13
                type IBSS
        Interface wlan1
                ifindex 10
                type managed
# ifconfig blah1 up
ifconfig: SIOCSIFFLAGS: No buffer space available
# dmesg |tail -n1
[15306.820000] ath: IBSS coexistence with other modes is not allowed

the same commands with wlan0 (driver ath9k) are successfull, and let
me have the two interfaces up,

Sadly, "iw phy" reports
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
        software interface modes (can always be added):
                 * AP/VLAN
                 * monitor
        interface combinations are not supported

And as try to be a good netizen :) , i googled for the changeset

This is required for allowing only one IBSS interface to be
configured. Signed-off-by: Sujith Manoharan <Sujith.Manoharan@xxxxxxxxxxx>
http://www.spinics.net/lists/linux-wireless/msg64995.html

I understand the reasons behind preventing two *IBSS* interfaces
configured on the same radio (driver should maintain separate TSF),
but i'm not so clear about why preventing the mix of "one IBSS +
Client" , or "one AP + one client" in ath9k_htc, since both
combinations are valid and possible in ath9k driver.

Maybe i'm missing something, or making a configuration mistake?
Any info will be greatly appreciated!

The context for this is the same as my last email, building a
community network, and if i can't get IBSS mode working correctly, at
least i would like to workaround it by mixing an AP and a client
interface on the same radio, thus creating a pseudo-mesh where each
router has an ap mode so that neighbouring nodes can "client-connect"
to it, and at the same time the router can "client-connect" to a
nearby ap node.

There's another another community MANET recently started in Cordoba,
Argentina: we're in fluid communication and they're facing the same
problems. So if any solution or help is provided, loads of good karma
will fly back in return :)

Guido
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to