- fix issue #15: minor config mistake in the new nss setup vlan readme guide
- fix formatting of primary subsection displaying too large.
Signed-off-by: Sean Khan <datapronix@protonmail.com>
* 802.11 k/v/r now fully works in sae-mixed mode. So we can now switch
from psk2 (WPA2) to WPA2/WPA3 mixed mode.
* Clean up uncessary configs
* Remove WDS example as it's not applicable in this example
Signed-off-by: Sean Khan <datapronix@protonmail.com>
- Added detailed build instructions for new users,
including the use of `scripts/env` for reproducible builds.
- Updated comments to provide context for each config setting and package.
- Clarified steps for selecting target devices and running make commands.
- Included notes on SSL preferences, performance optimizations, and optional packages.
- Removed redundant or unnecessary package entries for improved readability.
Signed-off-by: Sean Khan <datapronix@protonmail.com>
Although qca-nss-ecm isn't explicitly depended on by other
nss packages, it is still required for proper offloading.
There are also a few init and hotplug scripts needed
to mitigate issues (like disabling rx-gro-list)
Signed-off-by: Sean Khan <datapronix@protonmail.com>
For NSS setups, you CANNOT enable option for vlan filtering.
This is done internally by NSS (via `kmod-qca-nss-drv-vlan-mgr`).
Check if you have it enabled by running the following command:
`uci show network | grep vlan_filtering`
If it's enabled, you might see:
`network.@device[0].vlan_filtering='1'`
Disable it by running the following commands:
```sh
uci del network.@device[0].vlan_filtering
uci commit network
service network restart
```
Or reboot the device
You also cannot use tagging in the typical way, as the NSS does not support it.
That means your config must not anything like:
```
list ports 'lan1:u*'
list ports 'lan2:t'
list ports 'lan3:t'
```
To set up VLANs you must:
1.) Set them up on specific ports
2.) Bridge them into interfaces (they can be left unmanaged)
3.) Create firewall rules
Check `nss-setup/example/04-vlans` for more examples
Signed-off-by: Sean Khan <datapronix@protonmail.com>
1.) Clarify what radio_5g_high, and radio_5g_low mean
2.) Make txpower configurable
3.) Don't hardcode radio names in the generated config, but allow
specifiying them as variables.
4.) Set `cell_density` to 0 (don't enforce rates, let driver choose)
5.) Remove `pmk_r1_push` as `ft_psk_generate_local` already deals with
generating key locally
6.) Reduce `mesh_max_peer_links` and lower ttl
Signed-off-by: Sean Khan <datapronix@protonmail.com>
* Refactor and clean up script and add more helpful docs.
* If a device's MAC doesn't match or isn't specified the following will
be configured:
1.) lan network will use DHCP ("lan_proto=dhcp") to retrieve an IP
2.) device name will be "mx4300-xxxx", where "xxxx" represents the
last 4 characters of the device MAC address found on the bottom of
sticker.
* When in bridge mode, devices can be setup to use static or dhcp for their lan interface.
This is specified with option "lan_proto=dhcp" under each devices's
config, or if no suffix is specified, it is assumed the IP needs to be
optained.
* Add fallback mgmt IP address 10.1.1.1 that can be used in case mesh
fails to come up and hardwire connection is required. Make sure to set
a static IP for your computer in the 10.1.1.x subnet in order to
connect.
Signed-off-by: Sean Khan <datapronix@protonmail.com>
Included starter config seed NSS offloading for MX4300. Although it can
be used by any compatible ipq807x NSS setup.
There is also an example 'uci-defaults' script that you can use to build
a single image for multiple nodes.
Although the script includes options to set low/high band for mesh backhaul.
Only the high-band works for offloading.
Signed-off-by: Sean Khan <datapronix@protonmail.com>
