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:
[ 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
if ((dev->priv_flags & IFF_BRIDGE_PORT) &&
(ntype == NL80211_IFTYPE_ADHOC ||
ntype == NL80211_IFTYPE_STATION ||
ntype == NL80211_IFTYPE_P2P_CLIENT))
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?
Any suggestions or pointers would be greatly appreciated.
lime-users mailing list