Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1798 - mesh (802.11s) encrypted link wireless won't accept HT40 htmode unless AP also configured #8483

Closed
openwrt-bot opened this issue Aug 20, 2018 · 2 comments
Labels

Comments

@openwrt-bot
Copy link

Greybeard:

Issue occurs on multiple devices including TP-WR842v1/3, WR703 and WT3020.
18.06.0, 18.06.1 trunk

Configure wireless for mesh only (ie no AP) and HT40 mode. 'iw' command reports error in log when starting wireless and encrypted mesh link does not establish.

Works ok: encrypted mesh and ap with HT40 (wpa_supplicant has ht40=1)
cat /tmp/run/wpa_supplicant-mesh0.conf

country=AU
network={

    ssid="xxxxxx"
    key_mgmt=SAE
    mode=5
    mesh_fwding=1
    fixed_freq=1
    frequency=2462
    ht40=1
    max_oper_chwidth=0
    noscan=1
    sae_password="xxxxxxxx"
    beacon_int=100

}

Works ok: encrypted mesh (and no AP) with HT20 (wpa_supplicant has disable_ht40=1)
cat /tmp/run/wpa_supplicant-mesh0.conf

country=AU
network={

    ssid="xxxxxx"
    key_mgmt=SAE
    mode=5
    fixed_freq=1
    frequency=2462
    disable_ht40=1
    max_oper_chwidth=0
    sae_password="xxxxxxxx"
    beacon_int=100

}

Fails: encrypted mesh (and no AP) with HT40 (wpa_supplicant has no ht40 related entry)
cat /tmp/run/wpa_supplicant-mesh0.conf

country=AU
network={

    ssid="xxxxxx"
    key_mgmt=SAE
    mode=5
    fixed_freq=1
    frequency=2462
    max_oper_chwidth=0
    sae_password="xxxxxxxx"
    beacon_int=100

}

@openwrt-bot
Copy link
Author

Greybeard:

Neglected to highlight the lack of 'noscan' option being passed as well as the missing ht40 mode.

@openwrt-bot
Copy link
Author

mpratt14:

It is true that wpa-supplicant cannot control the radio mode, between ht20 and ht40.
You have to use /etc/config/wireless for that

If you cannot force ht40 without an AP, then the problem must be with the driver, not wpa-supplicant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant