On 22/12/17 03:21, Bob Haddleton wrote:

> Hi Daniel:
>
> On 12/21/17 4:58 PM, Daniel Golle wrote:
>> Hi Bob,
>>
>> On Thu, Dec 21, 2017 at 03:29:51PM -0600, Bob Haddleton wrote:
>>> Does anyone have LiMe working on a Raspberry Pi 3?  I can boot up
>>> the latest
>>> RPI-3 image and get the eth0 port connected to my WAN uplink, but
>>> the mesh
>>> doesn't work and the AP is not broadcasting any SSIDs.  The SSIDs
>>> all show
>>> "//Wireless is disabled or not associated" //and the wlan0-mesh_13
>>> interface
>>> shows DOWN on the BMX6 Status page.
>>>
>>> I get two errors during init:
>>>
>>> [   10.862080] brcmfmac: brcmf_cfg80211_add_iface: iface validation
>>> failed:
>>> err=-16
>>> [   12.117179] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed
>>> (-1)
>>>
>>> The brcmf_cfg80211_add_iface error traces back to this code in
>>> cfg80211_change_iface() in net/wireless/util.c:
>>>
>>>>          /* if it's part of a bridge, reject changing type to
>>>> station/ibss */
>>>>          if ((dev->priv_flags & IFF_BRIDGE_PORT) &&
>>>>              (ntype == NL80211_IFTYPE_ADHOC ||
>>>>               ntype == NL80211_IFTYPE_STATION ||
>>>>               ntype == NL80211_IFTYPE_P2P_CLIENT))
>>>>                  return -EBUSY;
>>> which seems to imply that this can't work (bridging an AdHoc
>>> interface).  Or
>>> maybe the AdHoc mode has to be set before the bridge is added?
>> We do not directly add the Ad-Hoc (or 11s mesh) interface to the bridge
>> but rather run batman-adv and bmx6 on top of it in order to provide
>> local layer-2 routing (batman-adv) as well as a layer-3 routed backbone
>> (bmx6). That should work as long as the wifi chip supports running an
>> Ad-Hoc or 11s mesh interface along with an access point interface.
>> More modern fullmac hardware (like brmcfmac) is more likely to work
>> with 11s than Ad-Hoc because the vendors stopped putting any effort
>> into Ad-Hoc mode long ago... Hence the question:
>> Are you trying Ad-Hoc or 802.11s mesh mode?
> I tried the stock RPI3 image from the Downloads page, and I also tried
> a Chef-built 11s image, and they both have the same symptoms.
>
> I'll try using an external wifi adapter as suggested by Mark and see
> if that works.
>

Meshing with a non well supported WiFi device can be painful, even if
the driver is able to load a 802.11s WiFi device, it might end up in a
very low performance mesh network. So before using it I'd recommend to
check on the Internet how good or bad is the support for this chip in
802.11s or Ad-Hoc modes.

Actually I'm not aware of any well supported USB WiFi dongle for
meshing, but I'm not very updated nowadays. @Daniel can talk better
about which chips are good for meshing.

Cheers.

> Thanks
>
> Bob
>
>>
>> Cheers
>>
>>
>> Daniel
>>
>>
>>> Any suggestions or pointers would be greatly appreciated.
>>>
>>> Thanks
>>>
>>> Bob
>>> _______________________________________________
>>> lime-users mailing list
>>> lime-users@lists.libremesh.org
>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>> _______________________________________________
>> lime-users mailing list
>> lime-users@lists.libremesh.org
>> https://lists.libremesh.org/mailman/listinfo/lime-users
>
> _______________________________________________
> lime-users mailing list
> lime-users@lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users

_______________________________________________
lime-users mailing list
lime-users@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users