Encrypted mesh knocks AP offline about network-profiles HOT 18 CLOSED

I remeber that some fixes for that were merged afterwards on openwrt 18.06. I'll try to offer a testing version of libremesh based on 18.06 and you could try again

from network-profiles.

Which network-profile are you using?
I'm asking because with the default network-profile the wpad-mini package is installed, but you will need to replace it with the more complete wpad-mesh that allows for ieee802.11s encryption (it would be interesting to know how much the image size increases and to consider if to include it by default) as documented here.

from network-profiles.

I've tried rebuilding the firmware with wpad-mesh and confirmed it is installed on the nodes. However I still have the same issues trying to establish an encrypted mesh.

I have even tried removing the AP mode and just having it as a mesh only but this does not work either.

from network-profiles.

@tomjones1977 Which hardware are you targetting and which OpenWrt release or commit are you basing your build on?

from network-profiles.

I'm using chef to build the images:

Distributions: LibreMesh
Release: 17.06
Model: Ubiquiti Rocket M XW
Target: ar71xx
Subtarget: generic

I'm using the Ubiquiti Rocket M5 XW, and Ubiquiti NanoStation M5 XW.

from network-profiles.

Please try the master branch of lime-sdk https://github.com/libremesh/lime-sdk/tree/master and use OpenWrt snapshot in chef, ie.

diff --git a/options.conf b/options.conf
index f4583c2..6fbaca1 100644
--- a/options.conf
+++ b/options.conf
@@ -1,9 +1,9 @@
 # check if SDK or IB is outdated before further actions
 snapshots=1
 # name of used release - just for storing IB and SDK
-release=18.06.1
+release=snapshots
 # where do download the SDK and ImageBuilder (IB) from
-base_url=https://downloads.openwrt.org/releases/$release/targets/
+base_url=https://downloads.openwrt.org/snapshots/targets/
 # git repository for network profiles
 communities_git=https://github.com/libremesh/network-profiles.git
 # local folder with network profiles aka community settings

from network-profiles.

I was using chef online but I'll pull the SDK down and give it a try.

from network-profiles.

I might be missing something obvious here but I can't see how to get cooker to use the snapshot instead of the 18.06 release?

./cooker -c ar71xx/generic --profile=ubnt-rocket-m-xw --flavor=lime_default

from network-profiles.

Can't you just use the stable 17.06 LibreMesh release based on LEDE for testing purposes?
For compiling the stable release just use the master branch of lime-sdk :)
Then you can include wpad-mesh with the --extra-pkg= option.
I don't know if that option can also be used for deselecting wpad-mini... @p4u

from network-profiles.

Can't you just use the stable 17.06 LibreMesh release based on LEDE for testing purposes?
For compiling the stable release just use the master branch of lime-sdk :)
Then you can include wpad-mesh with the --extra-pkg= option.
I don't know if that option can also be used for deselecting wpad-mini... @p4u

I was only trying to get the later version as one of the previous comments mentioned 18.06 has some fixes related to the encrypted mesh option. If I can get it working with a stable version I'd be a lot happier!

from network-profiles.

So for anyone who gets here via google:

18.06.1 on the Chef development version online (as of 23/11/18) works correctly with wpad-mesh. However it does have interface issues in terms of formatting but the networking seems to work okay.

from network-profiles.

As we're speaking about this on 18.06 and I've just had the same issue, can anyone confirm or deny that hostapd and authsae [which I've always used pre-18.06] are not needed on 18.06? They're both causing errors on my builds done on the develop branch. However my 18.06 nodes are not meshing. Thanks in advance.

EDIT: They do actually mesh, but I'd still like to make sure they are not needed.

from network-profiles.

authsae is deprecated in favour of SAE support in hostapd/wpa_supplicant. just install wpad-mesh-openssl and encrypted mesh, including mesh+AP should work.

from network-profiles.

from network-profiles.

No. wpad is the pre-mesh 'full' variant of wpa_suppilcant+hostapd which includes WPA-EAP and 802.1x features. Please use wpad-mesh instead, which includes everything in wpad plus support for 802.11s interfaces and SAE crypto, but needs an external crypto library because not all primitives needed for SAE have been implemented internally in hostapd/wpa_supplicant. Up to 18.06, wpad-mesh depends on openssl. Shortly after the 18.06 release of OpenWrt, support for using either openssl or wolfssl was added and more package variants (wpad-mesh-wolfssl, wpad-mesh-openssl, ...) introduced.

from network-profiles.

from network-profiles.

Exactly. wpad is basically just a single executable cotaining both, hostapd and wpa_supplicant. wpad-mesh additionally contains the functionality of authsea.

from network-profiles.

Thank you so much. This is the list of packages I've committed on our PACKAGES file:

lime-full
luci-ssl
wpad-mesh
ath10k-firmware-qca988x
kmod-ath10k
-wpad-mini

from network-profiles.