everloop2

@znrR see: https://github.com/freifunk-berlin/firmware/issues/769#issuecomment-603955561 if everything runs "normal" and box has nothing to do CPU load is around 0-5% for single core boxes running vanilla OpenWrt: https://openwrt.org/toh/astoria/arv752dpw22#hardware_highlights -> EasyBox803 -> 333MHz...

1. set WAN default to DHCP -> would be easy way with less impact on generated images to upstream ones: disadvantage i've seen so far: xDSL drivers are loaded and...

> @everloop2 can you post the relevant section of the uci-config? think this is good place: https://github.com/freifunk-berlin/firmware-packages/blob/master/defaults/freifunk-berlin-network-defaults/uci-defaults/freifunk-berlin-network-defaults ``` # setup wan as bridge, set wan to dhcp (prevents xDSL wan...

OpenWrt SNAPSHOT, r12706-1fb3c003d6 (25.03.2020) -> CPU load seems okay ``` Mem: 22204K used, 36240K free, 104K shrd, 2120K buff, 6560K cached CPU: 0% usr 1% sys 0% nic 98% idle...

Openwrt 19.07.02 (29.02.2020), r10947-65030d81f3 -> CPU load seems okay -> tested wifi uplink ``` Mem: 23720K used, 35832K free, 364K shrd, 2364K buff, 7844K cached CPU: 0% usr 0% sys...

setting: ``` config rssid 'rssid_wlan0' option dev 'wlan0' -> all rssi LED are OFF (only LAN and power ON) ``` to: ``` config rssid 'rssid_wlan0' option dev 'wlan0-mesh-2' or option...

> To make it short: having a non-existing interface specified in "config rssid" will cause high CPU-load and as per #509 not working LEDs. Right? Exactly. strange is -> vanilla...

numbers: appreciate it. Its far more easy to compare.

https://openwrt.org/toh/tp-link/cpe210 its CPE210 v2, one LAN Port

> So this LAN-port is Freifunk-DHCP - net by default yes, works like expected > uplink should only be found via mesh yes, FreifunkWizard -> choosed: not sharing internet connection...