meshd-nl80211 5GHz not working about authsae

[chunyeow]

Can you confirm whether the interface allows adhoc mode on the 5GHz or not?

• 5180 MHz [36] (17.0 dBm) (passive scanning, no IBSS)

Use "iw phyX info" to check.

[chunyeow]

If it is Ralink chipset, try to load the driver with "nohwcrypt=1".

…

On Wed, Apr 26, 2017 at 3:37 PM, Sebastian Rager ***@***.***> wrote: In the linux variant there ist a static function for frequency selection (channel_to_freq), which does not support the channels in the 5GHz range. I patched this method with the variant in the freebsd implementation (which DOES support 5GHz channels), the mesh is starting up but I get the following nlerror: joining mesh samplemesh on freq 5180, mode 3 nlerror, cmd 68, seq 1493191664: Invalid argument I don't find any error in the code, and the nlerror doesn't tell me much. In unencrypted mesh, the 5GHz channels work just fine with HT40+ enabled. Used Chipset: RT5370 and RT5572, hwencrypt disabled, Kernel 4.9 Any ideas? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#60>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABBewhuI_yOUPOlgGyDP3EoCNdlBs9Ofks5rzvQogaJpZM4NIehU> .

[interpretor]

I am already using the nohwcrypt=1 flag, it is working in the 2.4GHz Band.
The config that works:

authsae:
{
 sae:
  {
    debug = 480;
    password = "thisisreallysecret";
    group = [19, 26, 21, 25, 20];
    blacklist = 5;
    thresh = 5;
    lifetime = 3600;
  };
 meshd:
  {
    meshid = "samplemesh";
    interface = "mesh0";
    band = "11g";
    channel = 6;
    htmode = "HT20";
    mcast-rate = 12;
  };
};

The config that does NOT work:

authsae:
{
 sae:
  {
    debug = 480;
    password = "thisisreallysecret";
    group = [19, 26, 21, 25, 20];
    blacklist = 5;
    thresh = 5;
    lifetime = 3600;
  };
 meshd:
  {
    meshid = "samplemesh";
    interface = "mesh0";
    band = "11a";
    channel = 36;
    htmode = "HT20";
    mcast-rate = 12;
  };
};

With the second configuration the peers will not connect and it gives the error that I posted above:

joining mesh samplemesh on freq 5180, mode 3
nlerror, cmd 68, seq 1493191664: Invalid argument

[chunyeow]

RT5370 is bgn
RT5572 is abgn

So only RT5572 has 5GHz support. Confirm that this is not the issue?

[interpretor]

I use the 5GHz mesh only on the RT5572 chipsets, so no, this can't be the issue.

[interpretor]

Thank you very much for the hint, I just forgot to set the correct region in iw.
Looks like everything is working now.
Just wondering why the unencrypted mesh will set up with wrong region settings...