WiFi interface specific options

The following options must be edited in lime-node or lime-<MAC>

Configure a single radio

Ensure that the chosen radio name exists, i.e. running the wifi status command, likely radio0 or radio1.

config wifi radio0
  ...

All the non-specified options will be taken from config lime-wifi-band and the general config lime wifi sections

Examples

Wifi client mode

If you want to use Wifi client mode just to connect to an AP offering internet, you need two pieces of configuration: the wifi specific configuration and the network specific one.

If your router has an ethernet WAN port, you will need also the third piece of configuration for disable the interface created by default by lime-hwd-openwrt-wan.

Set radio99 as client of access point for internet access

config wifi radio99
    list modes 'client'
    option channel 'auto'
    option client_ssid 'SomeWiFiNetwork'
    option client_key 'SomeWPApskPassword'
    option client_encryption 'psk2'
    option distance 1000

config net wirelessclientWAN
    option linux_name 'wlan0-sta'
    list protocols 'wan'

config net lm_hwd_openwrt_wan
    option autogenerated 'false'

Options for wireless.radio99:

• client_encryption 'psk2' - psk for WPA or psk2 for WPA2
• distance 1000 - Maximum distance to AP, affects performances

Options for network.wirelessclientWAN:

• linux_name 'wlan0-sta' - Verify the name, the client interface name could be named differently, like wlan1-sta
• protocols 'wan' - Use wan to get Internet connectivity via DHCP.
  Use static to manually assign an ipv4/ipv6 addresses, refers to Static protocol.

Use only for mesh

config wifi radio99
    list modes 'ieee80211s'

Change SSID

config wifi radio99
    option ap_ssid 'Special'

Change the channel

config wifi radio99
    option channel '1'

Disable lime-config

config wifi radio99
    option modes 'manual'

If you use manual protocol you must not specify other protocol, or your configuration will be broken!

Decrease power output

This is rarely a good idea, do it just if you are very sure of what you are doing. Be aware that decreasing the power output can create a "hidden node problem", see https://en.wikipedia.org/wiki/Hidden_node_problem

config wifi radio99
    option txpower '14'

For knowing the current txpower, use the iwinfo command.

Adhoc mode

config wifi radio99
    list modes 'adhoc'
    option channel '1'
    option adhoc_ssid 'LiMe'
    option adhoc_bssid 'ca:fe:00:c0:ff:ee'
    option adhoc_mcast_rate '24000'

adhoc_ssid - Parametrizable with %M, %H

Wifi backbone AP

If you want to use Wifi client and AP instead of mesh for building the backbone of your LibreMesh network (and you are using Batman-adv + Babeld) you will need specific wifi and net configuration both on the client and on the access point

Set radio99 as backbone access point apbb stands for backbone AP, for other LibreMesh routers connection rather than for users connection part of the LibreMesh network structure using Batman-adv and Babeld, both the following "wifi" and "net" sections are required on the AP

config wifi radio99
    list modes 'apbb'
    option apbb_ssid 'backbone/%H'
#   option apbb_key 'somePassword'
#   option apbb_encryption 'psk2'

config net wirelessAPbackbone
    option linux_name 'wlan0-apbb'
    list protocols 'apbb'
    list protocols 'babeld:17'
    list protocols 'batadv:%N1'

list modes 'ap', list modes 'apname' - Include this if you additionally want an AP for clients on the same radio.
list modes 'ieee80211s' - Include this if you additionally want also do IEEE802.11s mesh on the same radio, check the maximum number of "interface combinations" with "iw phy phy0 info" command.
option apbb_ssid 'backbone/%H' - Clients should not connect to this AP, SSID name should point it out.

option linux_name 'wlan0-apbb' - Verify the name, the backbone AP interface name could be named differently, like wlan1-apbb.
list protocols 'apbb' - Backbone AP proto, needed for setting up the interface

Wifi backbone client

Set radio0 as backbone client of a backbone access point (not for users connection, specific AP configuration reported above) using Batman-adv and Babeld, both the following "wifi" and "net" sections are required on the client

config wifi radio99
    list modes 'client'
    option channel '11'
    option client_ssid 'backbone/LiMe-ddeeff'           
#   option client_key 'somePassword'
#   option client_encryption 'psk2'
    option distance 1000

config net wirelessclientbackbone
    option linux_name 'wlan0-sta'
    list protocols 'client'                             
    list protocols 'babeld:17'
    list protocols 'batadv:%N1'

option client_ssid 'backbone/LiMe-ddeeff' - Specify the name of the specifically configured backbone AP interface you want to connect to

option linux_name 'wlan0-sta' - Verify the name, the client interface name could be named differently, like wlan1-sta.
list protocols 'client' - Needed for setting up the new interface