dc8b77ce5f
Merging from uCentral-trunk. The switch in the IPQ807x/IPQ60xx devices will automatically learn the mac addresses behind a port. But it will not unlearn this entry when some mac switches from the ethernet port to the CPU port. This will for example happens when a device roams from on AP to another AP. At least when both are APs are bridging the wifi traffic directly or indirectly (mesh) to the same ethernet broadcast domain. As result, the roaming device can no longer receive any ethernet packets which the AP is expected to receive on the ethernet port. This state will be kept for a couple of minutes until the entry in the FDB is dropped automatically. But it is still possible for the wifi device to send data via the ethernet during this whole time. One solution is to just disable learning on all ports. The other option would be to enable the qca bridge-mgr which takes care of gathering the events from the bridge and forwards it to the qca-ssdk (to manipulate the state of the switch). The latter option was chosen to follow the approach which QCA is also using in their QSDK. Signed-off-by: ravi vaishnav <ravi.vaishnav@netexperience.com> |
||
|---|---|---|
| .github | ||
| docker | ||
| feeds | ||
| patches | ||
| patches-20.x | ||
| profiles | ||
| profiles-20.x | ||
| .gitignore | ||
| build.sh | ||
| config-20.x.yml | ||
| config.yml | ||
| dock-run.sh | ||
| LICENSE.md | ||
| Makefile | ||
| README.md | ||
| setup.py | ||
Setting up your build machine
Requires a recent linux installation. Older systems without python 3.7 will have trouble. See this link for details: https://openwrt.org/docs/guide-developer/quickstart-build-images
Install build packages: sudo apt install build-essential libncurses5-dev gawk git libssl-dev gettext zlib1g-dev swig unzip time rsync python3 python3-setuptools python3-yaml.
Plus specific for TIP: sudo apt-get install openvswitch-common
Doing a native build on Linux (OpenWrt 19.07 based)
First we need to clone and setup our tree. This will result in an openwrt/.
python3 setup.py --setup
Next we need to select the profile and base package selection. This setup will install the feeds, packages and generate the .config file. The available profiles are ap2220, ea8300, ecw5211, ecw5410.
cd openwrt
./scripts/gen_config.py ap2220 wlan-ap wifi
If you want to build an AX image you need to setup a different config. The available profiles are hawkeye, cypress, wallaby.
cd openwrt
./scripts/gen_config.py wallaby wifi-ax
Finally we can build the tree.
make -j X V=s
Builds for different profiles can co-exist in the same tree. Switching is done by simple calling gen_config.py again.
Doing a native build on Linux (OpenWrt 20.x based)
First we need to clone and setup our tree. This will result in an openwrt-20.x/.
python3 setup.py --setup --20x
Next we need to select the profile and base package selection. This setup will install the feeds, packages and generate the .config file. The available profiles are ap2220, ea8300, ecw5211, ecw5410. It is no longer required to add the wifi profile. Board profiles will now include their specific wifi flavour profile automatically.
cd openwrt
./scripts/gen_config.py ap2220 wlan-ap
Finally we can build the tree.
make -j X V=s
Builds for different profiles can co-exist in the same tree. Switching is done by simple calling gen_config.py again.
Doing a docker build
Start by installing docker.io on your host system and ensuring that you can run an unprivileged container. Once this is done edit the Dockerfile and choose the Ubuntu flavour. This might depend on your host installation. Then simple call (available targets are AP2220, EA8300, ECW5211, ECW5410)
TARGET=AP2200 make -j 8