OpenWrt/LEDE Project

Welcome to the OpenWrt Project bug reporting and issue tracking system

Problems to be reported here are for the current OpenWrt and legacy LEDE Project’s targets, sources, toolchain, core packages, build procedures, distribution and infrastructure. Guidelines for submitting a good bug report can be found at the OpenWrt Project website. Problems related to LuCI or OpenWrt packages need to be reported in their repositories:

Notifications of all submissions and task changes are sent to openwrt-bugs@infradead.org.

Opened  descIDCategoryTask TypePrioritySeveritySummaryReported InStatus
08.04.2017692Base systemBug ReportMediumMediumWLAN AP not working on RasPi (bcm2710 target)TrunkAssigned Task Description

When flashing the brcm2708 / bcm2710 target the WiFi interface gets stuck in “client mode” and the AP will not be able to be brought up.

Some screenshots and a load of discussion here:
https://forum.lede-project.org/t/ap-mode-radio0-in-raspi-3-always-acts-as-a-client-shows-as-wlan0-in-luci/2885

Two more days of tinkering, wifi-up’ing and -down’ing did not bring me further.
I flashed another Pi3 (to exclude a hardware defect) with the same result.

I tried latest snapshot and stable images.
I am happy to help debug – tell me what you need me to do.

Greetings,
–Thomas

02.04.2017672Base systemBug ReportVery LowLowNetgear WNR2000v3 - Looses always settings after power ...TrunkUnconfirmed Task Description

Device: Netgear WNR2000v3

Problem there since: 15.05.1. It was not there on 15.05 or previous releases.

Problem still there on 17.01 stable ( https://downloads.lede-project.org/releases/17.01.0/targets/ar71xx/generic/lede-17.01.0-r3205-59508e3-ar71xx-generic-wnr2000v3-squashfs-sysupgrade.bin )

The most simple way to make a example of this issue: Install 15.05.1 stable or 17.01 stable and open 192.168.1.1. It tells you that there is no password set. Go to settings, set a password. Open browser again. It asks you now for the password. Power off the device. Wait 2-3 seconds. Power it on. Password is now lost and device have again factory settings.

This makes lede on this device somehow useless. Would be great if someone could fix this problem.

Forum talk about this issue: https://forum.lede-project.org/t/netgear-wnr2000v3-not-saving-settings-after-reboot-with-rc2/1736/11

Bugreport about this issue on openwrt: https://dev.openwrt.org/ticket/22172

30.03.2017666Base systemBug ReportVery LowMedium"Wireless is disabled or not associated" when channel m...AllUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on Banana Pi R1
- Software versions: all

When I set the channel mode to “auto”, then the message appears “Wireless is disabled or not associated” and the WLAN does’nt work.
I set the channel manually, then WLAN works fine.

The problem is already known with OpenWrt:
https://dev.openwrt.org/changeset/32630


28.03.2017659Base systemBug ReportVery LowLowuboot-kirkwood (at least) fails to build if swig is ins...TrunkUnconfirmed Task Description

Building LEDE head (reboot-3906-g2a2dfb2be7) on a machine without python development headers but with swig in $PATH yields

  HOSTLD  tools/dumpimage
  HOSTCC  tools/mkimage.o
  HOSTLD  tools/mkimage
swig -python -o tools/libfdt_wrap.c lib/libfdt/libfdt.swig
LDFLAGS="" python ./lib/libfdt/setup.py \
        "-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer    -include ./include/libfdt_env.h -idirafterinclude -idirafter./arch/arm/include -I./lib/libfdt -I./tools -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE " lib/libfdt/fdt.c lib/libfdt/fdt_ro.c lib/libfdt/fdt_rw.c lib/libfdt/fdt_strerror.c lib/libfdt/fdt_wip.c lib/libfdt/fdt_region.c lib/libfdt/fdt_sw.c tools/libfdt_wrap.c
tools/libfdt_wrap.c:130:21: fatal error: Python.h: No such file or directory
 # include <Python.h>
                     ^
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
tools/Makefile:123: recipe for target 'tools/_libfdt.so' failed
make[5]: *** [tools/_libfdt.so] Error 1
Makefile:1229: recipe for target 'tools' failed
make[4]: *** [tools] Error 2
make[4]: Leaving directory '/tank/openwrt/scratch/builder-nwftest/build_dir/target-arm_xscale_musl_eabi/u-boot-pogo_v4/u-boot-2017.03'

As I don’t believe there are any in-tree consumers of the python libfdt bindings, adding the following patch file, which just removes the test for swig and therefore acts as if it is never present, should do the right thing:

$ cat package/boot/uboot-kirkwood/patches/201-no-python-fdt.patch 
--- u-boot-2017.03/tools/Makefile.orig	2017-03-28 03:11:34.081325904 +0000
+++ u-boot-2017.03/tools/Makefile	2017-03-28 03:13:09.225349051 +0000
@@ -112,10 +112,6 @@
 fit_info-objs   := $(dumpimage-mkimage-objs) fit_info.o
 fit_check_sign-objs   := $(dumpimage-mkimage-objs) fit_check_sign.o
 
-# Build a libfdt Python module if swig is available
-# Use 'sudo apt-get install swig libpython-dev' to enable this
-hostprogs-y += \
-	$(if $(shell which swig 2> /dev/null),_libfdt.so)
 _libfdt.so-sharedobjs += $(LIBFDT_OBJS)
 libfdt:
 
21.03.2017649Base systemBug ReportVery LowLowWDS not working on ath9k-htc TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: Any device with an wifi USB adapter with the chipset AR9271 (TPLink WN722N in my case).
- Software versions of LEDE release, packages, etc: Latest trunk LEDE versions.
- Steps to reproduce

 

Configure the USB AR9271 adapter as WDS AP, try to associate any other router as WDS Client (in my case the WDS Client is a TPLink WR741ND router, also compiled with latest trunk).
They both associate correctly, but there is no connection between them.

Here is a hostapd log on the WDS AP:

Mon Mar 20 14:05:00 2017 daemon.notice hostapd: wlan1: interface state ENABLED->DISABLED
Mon Mar 20 14:05:00 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 94:0c:6d:b0:f4:ac
Mon Mar 20 14:05:00 2017 daemon.notice hostapd: wlan1: AP-DISABLED
Mon Mar 20 14:05:00 2017 daemon.notice hostapd: wlan1: CTRL-EVENT-TERMINATING
Mon Mar 20 14:05:00 2017 daemon.notice hostapd: nl80211: deinit ifname=wlan1 disabled_11b_rates=0
Mon Mar 20 14:05:01 2017 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Mon Mar 20 14:05:02 2017 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Mon Mar 20 14:05:02 2017 daemon.err hostapd: Using interface wlan1 with hwaddr e8:de:27:a4:58:21 and ssid "EB1DJ"
Mon Mar 20 14:05:02 2017 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->ENABLED
Mon Mar 20 14:05:02 2017 daemon.notice hostapd: wlan1: AP-ENABLED
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: authentication OK (open system)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-AUTHENTICATE.indication(94:0c:6d:b0:f4:ac, OPEN_SYSTEM)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-DELETEKEYS.request(94:0c:6d:b0:f4:ac)
Mon Mar 20 14:05:03 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: authenticated
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: association OK (aid 1)
Mon Mar 20 14:05:03 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: associated (aid 1)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-ASSOCIATE.indication(94:0c:6d:b0:f4:ac)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-DELETEKEYS.request(94:0c:6d:b0:f4:ac)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: binding station to interface 'wlan1'
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: event 1 notification
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: start authentication
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.1X: unauthorizing port
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: sending 1/4 msg of 4-Way Handshake
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: EAPOL-Key timeout
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: sending 1/4 msg of 4-Way Handshake
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: received EAPOL-Key frame (2/4 Pairwise)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: sending 3/4 msg of 4-Way Handshake
Mon Mar 20 14:05:03 2017 daemon.err hostapd: nl80211: EAPOL TX: No message of desired type
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: ignore retransmitted EAPOL-Key 2/4 Pairwise - SNonce did not change
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: EAPOL-Key timeout
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: sending 3/4 msg of 4-Way Handshake
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: received EAPOL-Key frame (4/4 Pairwise)
Mon Mar 20 14:05:03 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 94:0c:6d:b0:f4:ac
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.1X: authorizing port
Mon Mar 20 14:05:03 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac RADIUS: starting accounting session 7797AE68AEE646F3
Mon Mar 20 14:05:03 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: pairwise key handshake completed (RSN)
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: authentication OK (open system)
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: event 0 notification
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-AUTHENTICATE.indication(94:0c:6d:b0:f4:ac, OPEN_SYSTEM)
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-DELETEKEYS.request(94:0c:6d:b0:f4:ac)
Tue Mar 21 09:58:59 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: authenticated
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: association OK (aid 1)
Tue Mar 21 09:58:59 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: associated (aid 1)

I think the error Mon Mar 20 14:05:03 2017 daemon.err hostapd: nl80211: EAPOL TX: No message of desired type has something to do with WDS not working?.

If there is any other info, tests etc you require feel free to ask.

17.03.2017634Base systemBug ReportMediumMediumFactory flashing fails because LEDE filename is too lon...AllNew Task Description

On a TP-Link TL-WR841N v11, flashing LEDE from the web interface of the stock firmware is not possible.

This is caused by a stupid check that refuses filename longer than 64 chars in the web interface. The check is implemented in javascript and returns a cryptic error message like “Please select a file to upload”, as if no file was selected.

The current naming scheme is quite long:

$ echo ‘lede-17.01.0-r3205-59508e3-ar71xx-generic-tl-wr841-v11-squashfs-factory-eu.bin’ | wc -c
79

Shortening the name like the following would decrease the length below 64 chars, and leave some space for a custom suffix (e.g. using EXTRA_IMAGE_NAME in the Imagebuilder):

$ echo ‘lede-17.01.0-ar71xx-tlwr841v11-squashfs-factory-eu.bin’ | wc -c
55

15.03.2017632Base systemBug ReportVery LowLowMP_CONFIG_INT settings not applied to meshpoint interfa...TrunkUnconfirmed Task Description

Supply the following if possible:
- Tested with OM5P-AC (on ath10k)
- Using LEDE reboot-3637-gc8f7031ba7 with wpad-mesh

The 5GHz device was configured using following entry in /etc/config/wireless

config wifi-iface 'mesh2'         
        option device 'radio1'  
        option ifname 'mesh-5'  
        option network 'lan'    
        option mode 'mesh'      
        option mesh_id 'mymesh' 
        option disabled '0'
        option mcast_rate '54000'
        option macaddr 'ae:86:74:00:00:01'
        option mesh_ttl 1
        option mesh_fwding 0
        option ieee80211w 1
        option encryption 'psk2+aes'
        option key 'reallysecretkey'

It is expected that mesh_ttl is 1 and mesh_fwding is 0. But the reality is quite different:

<pre>
root@lede:/# iw dev mesh-5 get mesh_param mesh_fwding
1
root@lede:/# iw dev mesh-5 get mesh_param mesh_ttl
31
</pre>

14.03.2017631Base systemBug ReportVery LowLowAR8327 switch link state change check not working on TL...TrunkUnconfirmed Task Description

Hello,

On my TP-LINK TL-WR1043ND v3 (ar71xx QCA9558) with today’s LEDE snapshot, the AR8327 switch isn’t sending port change interrupt events to the CPU.

The `ar8xxx_check_link_states` function in `target/linux/generic/files/drivers/net/phy/ar8216.c` is not being called at all, since not only the messages about port link status change aren’t printed to the dmesg, but the ARL table isn’t getting cleaned either. I don’t understand why this is happening...

This regression is not present in other routers with the same AR8327 switch chip (but rev. 2 instead of rev. 4), such as TP-LINK TL-WDR4300 v1 (ar71xx) and TP-LINK TL-WDR4900 v1 (mpc85xx).

(Latest LEDE stable release also does exibit the regression.)

Below you can see a session with LEDE; and a session with OpenWrt CC 15.05.1 release, which does not exibit the problem.

(The CC image is for the TL-WR1043ND v2, since v3 images weren’t built yet at that time; v2 and v3 are the same hardware, as it can be seen from the FCC docs, where TP-LINK requested an ID change from v2 to v3.)

Please let me know if there’s anything I can try to help debug this problem!

```
BusyBox v1.26.2 () built-in shell (ash)

   _________
  /        /\      _    ___ ___  ___
 /  LE    /  \    | |  | __|   \| __|
/    DE  /    \   | |__| _|| |) | _|

// LE \ ||_|_/|_| lede-project.org
\ \ DE /
\ LE \ / ———————————————————– \ DE \ / Reboot (SNAPSHOT, r1-2f09a1e)
\
\/ ———————————————————– === WARNING! =====================================
There is no root password defined on this device!
Use the “passwd” command to set up a new password
in order to prevent unauthorized SSH logins.
————————————————– root@LEDE:~# dmesg | grep 8327
[ 0.815273] switch0: Atheros AR8327 rev. 4 switch registered on ag71xx-mdio.0
root@LEDE:~# dmesg | grep 8216
[ 2.046658] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
root@LEDE:~# swconfig dev switch0 get arl_table
address resolution table
Port 0: MAC <router_lan_macaddr>
Port 4: MAC <my_laptop_macaddr>
Port 4: MAC <other_macaddr>
Port 6: MAC <router_wan_macaddr> root@LEDE:~# dmesg | grep 8216
[ 2.046658] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
root@LEDE:~# swconfig dev switch0 get arl_table
address resolution table
Port 0: MAC <router_lan_macaddr>
Port 3: MAC <my_laptop_macaddr>
Port 4: MAC <other_macaddr>
Port 6: MAC <router_wan_macaddr> root@LEDE:~#
``` ```
BusyBox v1.23.2 (2016-01-02 18:01:44 CET) built-in shell (ash)
_ | |.—–.—–.—–.| | | |.—-.| |_
| - || _ | -
| || | | || _|| _|
|_|| |_||||||| ||
|
| W I R E L E S S F R E E D O M


CHAOS CALMER (15.05.1, r48532)


  • 1 1/2 oz Gin Shake with a glassful
  • 1/4 oz Triple Sec of broken ice and pour
  • 3/4 oz Lime Juice unstrained into a goblet.
  • 1 1/2 oz Orange Juice
  • 1 tsp. Grenadine Syrup

—————————————————– root@OpenWrt:/# dmesg | grep 8327
[ 0.750000] switch0: Atheros AR8327 rev. 4 switch registered on ag71xx-mdio.0
root@OpenWrt:/# dmesg | grep 8216
[ 1.440000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
[ 24.680000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is up

root@OpenWrt:/# swconfig dev switch0 get arl_table
address resolution table
Port 0: MAC <router_lan_macaddr>
Port 4: MAC <my_laptop_macaddr>
Port 4: MAC <other_macaddr>
Port 6: MAC <router_wan_macaddr>

root@OpenWrt:/# dmesg | grep 8216
[ 1.440000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
[ 24.680000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is up
[ 1306.510000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is down
[ 1310.530000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 3 is up
root@OpenWrt:/# swconfig dev switch0 get arl_table
address resolution table
Port 0: MAC <router_lan_macaddr>
Port 3: MAC <my_laptop_macaddr>
Port 6: MAC <router_wan_macaddr>

root@OpenWrt:/# uname -a
Linux OpenWrt 3.18.23 #1 Sun Jan 31 18:39:35 CET 2016 mips GNU/Linux
root@OpenWrt:/#
```

Cheers,
Vittorio

13.03.2017623Base systemBug ReportVery LowLowar71xx: RB750UPr2: No serial consoleTrunkUnconfirmed Task Description

Hello,
The serial console isn’t working on MikroTik RB750UPr2 (NOR flash) (normal boot). Netboot is fine though. Notice no-uart in the kernel command line args.
Tested with recent snapshots (r3607-d49ddcd, r3617-f9da623)

Netboot

[    0.000000] Linux version 4.4.52 (buildbot@builds) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3607-d49ddcd) ) #0 Wed Mar 8 18:06:04 2017
[    0.000000] bootconsole [early0] enabled
...
[    0.000000] Kernel command line: no-uart no-nand parts=1 boot_part_size=16777216 gpio=8525375 HZ=325000000 mem=64M kmac=E4:8D:8C:99:18:31 board=750-hb hw_opt=0008400D boot=0 mlc=8 console=ttyS0,115200 rootfstype=squashfs noinitrd
...
[    0.125208] MIPS: machine is MikroTik RouterBOARD 750UP r2
...
[    2.957103] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    2.967151] console [ttyS0] disabled
[    2.991360] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 1562500) is a 16550A
[    3.001161] console [ttyS0] enabled
[    3.001161] console [ttyS0] enabled
[    3.008713] bootconsole [early0] disabled
[    3.008713] bootconsole [early0] disabled
[    3.023066] m25p80 spi0.0: found w25q128, expected m25p80
[    3.028744] m25p80 spi0.0: w25q128 (16384 Kbytes)
[    3.033619] Creating 6 MTD partitions on "spi0.0":
[    3.038569] 0x000000000000-0x00000000e000 : "routerboot"
[    3.046718] 0x00000000e000-0x00000000f000 : "hard_config"
[    3.054081] 0x00000000f000-0x000000010000 : "bios"
[    3.060744] 0x000000010000-0x00000001f000 : "routerboot2"
[    3.068174] 0x00000001f000-0x000000020000 : "soft_config"
[    3.075587] 0x000000020000-0x000001000000 : "firmware"

Normal boot

[    0.000000] Linux version 4.4.52 (buildbot@buildslave) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3617-f9da623) ) #0 Fri Mar 10 00:23:50 2017
[    0.000000] bootconsole [early0] enabled
...
[    0.000000] Kernel command line: no-uart no-nand parts=1 boot_part_size=16777216 gpio=0 HZ=325000000 mem=64M kmac=E4:8D:8C:99:18:31 board=750-hb Board=750-hb ver=3.36 hw_opt=0008400D boot=1 mlc=10 console=ttyS0,115200 rootfstype=squashfs noinitrd
...
[    0.125275] MIPS: machine is MikroTik RouterBOARD 750UP r2
...
[    0.696259] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.706324] console [ttyS0] disabled
[    0.730536] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 1562500) is a 16550A
[    0.740339] console [ttyS0] enabled
[    0.747890] bootconsole [early0] disabled
[    0.762167] m25p80 spi0.0: found w25q128, expected m25p80
[    0.767840] m25p80 spi0.0: w25q128 (16384 Kbytes)
[    0.772706] Creating 6 MTD partitions on "spi0.0":
[    0.777667] 0x000000000000-0x00000000e000 : "routerboot"
[    0.785835] 0x00000000e000-0x00000000f000 : "hard_config"
[    0.793114] 0x00000000f000-0x000000010000 : "bios"
[    0.799850] 0x000000010000-0x00000001f000 : "routerboot2"
[    0.807243] 0x00000001f000-0x000000020000 : "soft_config"
[    0.814630] 0x000000020000-0x000001000000 : "firmware"
[    0.865054] 2 minor-fw partitions found on MTD device firmware
[    0.871104] 0x000000020000-0x0000001a0000 : "kernel"
[    0.877734] 0x0000001a0000-0x000001000000 : "rootfs"
[    0.884687] mtd: device 7 (rootfs) set to be root filesystem
[    0.890584] 1 squashfs-split partitions found on MTD device rootfs
[    0.897035] 0x000000390000-0x000001000000 : "rootfs_data"

BTW the serial console is working fine on RB750UP (NAND flash) (normal boot).

[    0.000000] Kernel command line: parts=1 boot_part_size=4194304 gpio=790343 HZ=200000000 mem=32M kmac=D4:CA:6D:91:86:F1 board=750i Board=750i ver=3.33 hw_opt=0000000D boot=1 mlc=10 console=ttyS0,115200 rootfstype=squashfs noinitrd
10.03.2017614Base systemBug ReportVery LowMedium/usr/lib/lua/luci/util.lua:623: Unable to establish ubu...TrunkUnconfirmed Task Description

when save&apply on system>mount luci always crash
error message:
/usr/lib/lua/luci/util.lua:623: Unable to establish ubus connection
stack traceback:

[C]: in function 'assert'
/usr/lib/lua/luci/util.lua:623: in function 'ubus'
/usr/lib/lua/luci/dispatcher.lua:347: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:141: in function </usr/lib/lua/luci/dispatcher.lua:140>
 


09.03.2017612Base systemBug ReportVery LowHighWAN to LAN leakage on MT7620 devicesTrunkUnconfirmed Task Description

I am currently testing two MT7620 devices - the ZBT WE826 and the Sanlinking D240. During the first seconds of the boot, I see that packets leak between the WAN and LAN ports. Typically, this results in clients receiving a DHCP reply from my upstream router, rendering the clients without connectivity when the switch is properly initialized. I have also tested with the default firmware and do not see this behavior. Also, if I stop the devices in the bootloader, then packets do not leak until I resume boot again.

In order to try to solve this bug, I have tried to port some (at least to me) missing steps from the bootloader switch code and to the mt7620 switch driver in LEDE. This did not have an effect, at least not on the packet leak. A work-around I have found is to update u-boot and remove the input delay, so that the device will boot immediately. However, this is quite cumbersome to install and not very reliable. I suspect my luck with this work-around is more due to the timing of the DHCP clients in Ubuntu and Windows 10.

Does anyone have any idea as to what could be wrong and where to start looking?

Thanks in advance for any help.

 


09.03.2017611Base systemBug ReportVery LowHighdnsmasq Ignore resolv file option forget at restartAllUnconfirmed Task Description

If you set up dnsmasq to ignore resolv file it will ignore it until reboot is performed. To make ignore it again the option must be uncheck and apply and then check and apply again.

I have /etc/resolv.conf as a symlink to /tmp/resolv.conf, when the router boots up the contents are the dns offered from dhcp over the wan interface. When the ignore resolv option is checked or unchecked the contens are overwrited to search lan and nameserver 127.0.0.1 but it doesn’t seems to affect as if you uncheck ignore resolv the router resolv names, and when you check again the option it can resolv names even the contents still are search lan and nameserver 127.0.0.1.

I haven’t seen yet any other change that can cause the reboot to make dnsmasq follow resolv file when the option is checked until you uncheck-apply and check-apply.

09.03.2017609Base systemBug ReportVery LowVery Lowprocd: implement runlevel 1TrunkNew Task Description

Sysupgrade currently kills processes with SIGKILL if they don’t shut down within 3 seconds after the SIGTERM signal. Some processes (e.g. domoticz) can take longer than 3 seconds to properly shut down. As this can potentially corrupt the sqlite database, it should be avoided.

While talking about this on IRC, it was suggested we should implement an “init 1” equivalent in procd. Adding this ticket as a reminder.

05.03.2017599Base systemBug ReportVery LowMediumHame MPR-A2 switch has unknown topologyTrunkUnconfirmed Task Description

Vlan don’t work.


04.03.2017592PackagesBug ReportVery LowLow6in4 not creating routes when multiples prefixes usedAllUnconfirmed Task Description

If you need to route several (non aggregatable) prefixes thru a 6in4 tunnel, I’ve not found documentation, but it seems that this will make it:

option ip6prefix ‘prefix::/64 prefix::/48’

(example for 2 prefixes)

Then doing ifstatus interface-ipv6, you can see that both prefixes have been considered under ipv6-prefix.

However, under route, only the first one has a default route for that “source-prefix”.

Creating a manual route, it works, so the bug is not creating automatically that route.

03.03.2017591OtherFeature RequestVery LowLowInclude branch info in subject from 'lede-commits'AllUnconfirmed Task Description

Please include the branch being committed to as part of the subject. As it currently stands emails are received:

[source] ubox: update to the latest version
[source] bcm53xx: include Broadcom PHY driver in the kernel

However there’s no clue in the subject that the ubox commit is for ‘master’ (and of interest to me) whilst the ‘bcm53xx’ is a commit to ‘17.01’ (and of much less interest to me)

It’s driving me (even more) insane :-)

01.03.2017580Base systemBug ReportVery LowLowNetgear R7800 does not receive multicast messages on LA...TrunkUnconfirmed Task Description

Netgear R7800 running lede-17.01.

Multicast packets are not received on LAN (wired) interfaces but work fine on WiFi interfaces. I think the problem is at device/driver level.

The problem was first noticed using Avahi, which did not see announcements on LAN interfaces. However it can be easily reproduced with a simple IP Multicast sender/receiver like https://github.com/GrahamCobb/Multicast-Client-Server-Example

To reproduce:

Run the “client” on the R7800 using:

client 232.0.1.1 4545 100

Run the “server” on another system using:

server 232.0.1.1 4545 100 1000

If the server is connected to the client using a WiFi interface, the messages are received. If it using a LAN, they are not.

The messages are received if the LAN interface is set in promiscuous mode (ifconfig ... promisc) or all multicast mode (ifconfig ... allmulti). They stop again immediately if the mode is turned off.

I believe this is the same problem as reported in https://forum.lede-project.org/t/ipv6-works-only-with-wan-in-promiscuous-mode/490/9 – in that thread it is mentioned that the AC2600 (which uses the same driver) has the same problem.

As the problem goes away in promiscuous or all multicast modes, I am guessing that the device is just not sending the multicast packets to the driver. This could be a hardware bug, a bug in the multicast filter setup code in dwmac1000_core.c or the devicetree incorrectly reporting device characteristics such as the number of multicast filter bins.

27.02.2017563Base systemBug ReportVery LowLowcake qdisc high cpu usage on tp-link 841nTrunkUnconfirmed Task Description

So, I had this crazy idea to just make cake the default qdisk after seeing the battlemesh presentation. Now we are seeing high spikes in CPU usage after some time - the peaks appear to be of periodic nature. I only have some nmeter plots (basically vmstat/sar with dots - it’s a busybox applet) - the high load immediatly vanishes after switching the qdiscs back to fq_codel.

I’ve seen this on 2 841n routers one only using ap+ibss mode the other having wan+lan+ap+ibss+tap interfaces with cake running. Both also run a bridge for the AP.

Is the high system cpu usage expacted behavoir? cake qdisc is just using defaults:

This script does the activation:

# cat /etc/hotplug.d/iface/00-cake-qdisc 
#!/bin/sh

case "$ACTION" in
                ifup)
                grep -q '^sch_cake' '/proc/modules' && {
                        command -V tc > /dev/null || return 
                        tc qdisc replace dev "$DEVICE" root cake
                }
        ;;
esac
# vim: set filetype=sh ai noet ts=4 sw=4 sts=4 :

The results (1 line = 1 second):

root@weimarnetz-188:~ :) nmeter '%40c wlan: %[nbr-vap] ibss: %[nwlan0]'

cake 

SSSSSSSSUii............................. wlan:  8856  756 ibss:  4026 9162
SSSSSSSSSSSSSSSSSSSSU................... wlan:   44k 1736 ibss:  8726  49k
SSSSSSSi................................ wlan:   58k 2130 ibss:  5974  62k
SSSUUUUi................................ wlan:   58k 1296 ibss:   15k  68k
SSSSSSSSi............................... wlan:   49k 2532 ibss:  5298  53k
SSSSSSSSSSiii........................... wlan:   45k 2082 ibss:  8282  49k
SSSSSSSSSSSSSSSSSSSSSSU................. wlan:   39k 1794 ibss:   14k  45k
SSSSSSSSSSSSSSUi........................ wlan:   34k 2112 ibss:   11k  29k
SSSSSSSSSSSSSSSSSSSSSUUi................ wlan:   47k 2172 ibss:  7614  60k
U....................................... wlan:   58k 2934 ibss:  7496  61k
SSUi.................................... wlan:   53k 1944 ibss:  9.8k  58k
SSSSSSSSSSSSSSSSSSU..................... wlan:   47k 1698 ibss:  6552  51k
SSSSSSSSSSSSSUi......................... wlan:   57k 2704 ibss:  9.9k  62k
UUUiii.................................. wlan:   57k 1512 ibss:  8956  63k
SSSSSSSSSSSSSSSSSSSSSSSSii.............. wlan:   77k 4010 ibss:   17k  85k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSUii wlan:  6400  318 ibss:   450 6784
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSi wlan:   47k 1296 ibss:   12k  55k
SUUii................................... wlan:   49k 2542 ibss:  5604  53k
SSSSSSSSUUi............................. wlan:   56k 2354 ibss:   10k  62k
SSSSSSSSSSSSSSSSSSSSSi.................. wlan:   58k 1926 ibss:   11k  64k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSi wlan:   59k 2464 ibss:   22k  67k
SSSSSSSSSSSSSSUi........................ wlan:   41k  972 ibss:   10k  50k
SUi..................................... wlan:   44k 2132 ibss:  6310  47k
SUUi.................................... wlan:   52k 1642 ibss:   11k  58k
SSSSSSSSSSSSSSSSSSSSSSUi................ wlan:   54k 3826 ibss:   11k  60k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSUi wlan:   44k 1482 ibss:  6580  48k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSi.......... wlan:   32k 2396 ibss:  9732  38k
SSSSSSSSSSSSSSSSUUi..................... wlan:   18k 1164 ibss:  6888  20k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSUi... wlan:   37k  864 ibss:   13k  46k
SSSSSSSSSSSi............................ wlan:   57k 2112 ibss:  4166  60k
SSi..................................... wlan:   56k 1746 ibss:   11k  62k
SSSSSSSSSSSSSSSSSSSSi................... wlan:   43k  28k ibss:   39k  48k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSUU....... wlan:   15k  18k ibss:   25k  21k
SSSSSSSSSSSSSSSSUiiii................... wlan:   42k 255k ibss:  261k  52k
SUiiii.................................. wlan:   39k 393k ibss:  398k  54k
SSSSSSSSSSSSSSSSSSSSSSSSiii............. wlan:   26k 244k ibss:  251k  33k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSii........ wlan:   44k  86k ibss:   93k  54k
SSSSSSSSSSSSSSSSSSSSSSSSSSSUUii......... wlan:   27k  33k ibss:   41k  33k
SSSSSUiii............................... wlan:   54k  36k ibss:   40k  60k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSii wlan:   30k  46k ibss:   52k  35k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSi wlan:   23k  13k ibss:   20k  26k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSUii.... wlan:   53k  31k ibss:   40k  66k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSU......... wlan:   31k  18k ibss:   29k  35k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSi wlan:   13k 1262 ibss:  8370  16k
SSSSSSSSSSSSUi.......................... wlan:   46k  35k ibss:   54k  63k
SU...................................... wlan:   53k  87k ibss:   93k  59k
SSSSSSSSSSUUi........................... wlan:   43k  23k ibss:   32k  50k
SSSUUUiii............................... wlan:   46k 164k ibss:  172k  54k
SSSSSSSSSUiii........................... wlan:   48k 245k ibss:  250k  59k
SSSSSSSSSSSSSSS......................... wlan:   38k 5959 ibss:   10k  44k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSi wlan:   38k 1838 ibss:  9944  41k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSi wlan:   25k 1344 ibss:  2774  25k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS wlan:   43k 2442 ibss:   10k  44k
SSSSSSSSSSSSSSSSSSSSUUii................ wlan:   59k 1968 ibss:   11k  73k
Si...................................... wlan:   60k 2354 ibss:   10k  67k
SU...................................... wlan:   57k 1680 ibss:   11k  63k
Siii.................................... wlan:   51k 3560 ibss:  8042  54k
SSSSSSSSSSSi............................ wlan:   50k 1080 ibss:   14k  58k
SSSSSSSSSSSSSUU......................... wlan:   53k 2548 ibss:   13k  59k
SSSSSSSSSSSSi........................... wlan:   46k 2309 ibss:  9093  52k
SSSSSSSSSSSSSSSSSSSSi................... wlan:   83k 3816 ibss:   14k  91k
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSi........ wlan:   25k 3210 ibss:  5668  26k
SSSSSSSSSSSSSSSSSSSSSSSUii.............. wlan:   53k 2478 ibss:   11k  59k
SSSSSSSSSSSSSSSSSSSSSSSSSUi............. wlan:   15k 1308 ibss:  8142  20k
SSUUii.................................. wlan:   799  607 ibss:   11k 5339
SUi..................................... wlan:  1449 1436 ibss:   11k 9399
SSSSSSSSSSSSSSSSSSSSSSSSSSSSU........... wlan:   240 2738 ibss:   10k 3224
SSSSSSSSSU.............................. wlan:   132   66 ibss:   10k 4804
UUi..................................... wlan:   320  347 ibss:   11k 6020


-----> fq_codel 

S....................................... wlan:     0    0 ibss:  8664 3682
SSSSSSSSSU.............................. wlan:     0    0 ibss:  9022 6566
SS...................................... wlan:   703 6076 ibss:   14k 3565
S....................................... wlan:  2971 1862 ibss:  8554 7219
SUi..................................... wlan:     0    0 ibss:  7810 3732
SSUUi................................... wlan:     0    0 ibss:  8440 2920
SSii.................................... wlan:  1449 1436 ibss:   10k 7771
Ui...................................... wlan:     0    0 ibss:  8068 3258
Ui...................................... wlan:     0    0 ibss:  7910 3614
SSUi.................................... wlan:   252  185 ibss:   12k 5022
SUi..................................... wlan:  4742 1368 ibss:  9.8k  10k
SU...................................... wlan:     0    0 ibss:   11k 4646
Ui...................................... wlan:     0    0 ibss:   15k 5802
SS...................................... wlan:     0    0 ibss:  6918 3742
SU...................................... wlan:   122 2576 ibss:  4978  404
SSUii................................... wlan:     0    0 ibss:  8856 5890
SU...................................... wlan:  1449 1436 ibss:  6598 4791
SU...................................... wlan:    41   54 ibss:  4234 2101
UUii.................................... wlan:     0    0 ibss:   12k 5438
SUi..................................... wlan:   280  239 ibss:  7599 1644
U....................................... wlan:     0    0 ibss:  5962 3606
U....................................... wlan:     0    0 ibss:   10k 5502
SU...................................... wlan:     0    0 ibss:   14k 7486
Ui...................................... wlan:     0    0 ibss:   14k 5030
SU...................................... wlan:     0    0 ibss:  7930 4702
Ui...................................... wlan:   799  606 ibss:   10k 5400
SSSSSSSSSSSSSU.......................... wlan:  1449 1436 ibss:  9936 5653
S....................................... wlan:     0    0 ibss:  5818 2964
SU...................................... wlan:     0    0 ibss:   11k 7547
SU...................................... wlan:   252  185 ibss:  6264 3875
Ui...................................... wlan:  4159  995 ibss:  8313 8409
U....................................... wlan:     0    0 ibss:  3912 1240
SU...................................... wlan:     0    0 ibss:  4600 3784
S....................................... wlan:   122 2604 ibss:  9706 3374
SUUUi................................... wlan:     0    0 ibss:   13k 6328
U....................................... wlan:     0    0 ibss:   10k 6940
ii...................................... wlan:  1504 1589 ibss:  8605 4736
SUUi.................................... wlan:   108    0 ibss:   13k 8516
SUi..................................... wlan:  5241  28k ibss:   32k 9431
SSUUi................................... wlan:  9.7k  24k ibss:   33k  14k
SUi..................................... wlan:   743  456 ibss:   14k 7591
U....................................... wlan:     0    0 ibss:  2212 2732
SSSSSSSSSSU............................. wlan:     0    0 ibss:  9750 6434
........................................ wlan:  4585  492 ibss:  4616 6971
SUi..................................... wlan:   326 1155 ibss:   11k 4874
Si...................................... wlan:     0    0 ibss:  2330  214
Si...................................... wlan:  4336 3047 ibss:   18k  11k
SUi..................................... wlan:   100    0 ibss:  9838 5264
S....................................... wlan:     0    0 ibss:   14k 6298
SSSU.................................... wlan:   644  511 ibss:  6719 4294
SUii.................................... wlan:     0    0 ibss:   13k 6274
S....................................... wlan:     0    0 ibss:  6822 1738
U....................................... wlan:     0    0 ibss:  4790 1730
Ui...................................... wlan:   124  110 ibss:  5518 3544
SU...................................... wlan:   229   42 ibss:  8218 4972
Si...................................... wlan:  1000  607 ibss:  4750 2432
........................................ wlan:  1650 1436 ibss:  8372 5635
UUi..................................... wlan:   201    0 ibss:  9418 5422
Ui...................................... wlan:     0    0 ibss:   14k 7438
SSUi.................................... wlan:  3268 1862 ibss:   14k 9690
SUU..................................... wlan:     0  108 ibss:  9030 4918
SSi..................................... wlan:    80  108 ibss:  9442 5162
Ui...................................... wlan:    41   54 ibss:  9768 4757
Sii..................................... wlan:    58  104 ibss:  5570 3562
UU...................................... wlan:     0    0 ibss:  7098 4134
SU...................................... wlan:     0    0 ibss:  8142 2818
S....................................... wlan:  2941 2271 ibss:  7081 6303
SUi..................................... wlan:   315    0 ibss:  8524 3738
Ui...................................... wlan:  1309  757 ibss:   10k 7143
SUU..................................... wlan:  1450  428 ibss:  7150 5470
SUi..................................... wlan:  3187 8952 ibss:   16k 7107
U....................................... wlan:  4559 2197 ibss:  7959 8811
Ui...................................... wlan:  5564 2171 ibss:  8323 9118
i....................................... wlan:   11k  41k ibss:   50k  18k
root@weimarnetz-188:~ 8( cat /tmp/sysinfo/model 
TP-Link TL-WR841N/ND v11
root@weimarnetz-188:~ :) cat /etc/os-release 
NAME="weimarnetz"
VERSION="SNAPSHOT, Reboot"
ID="weimarnetz"
ID_LIKE="lede openwrt"
PRETTY_NAME="weimarnetz Reboot SNAPSHOT"
VERSION_ID="snapshot"
HOME_URL="http://lede-project.org/"
BUG_URL="http://bugs.lede-project.org/"
SUPPORT_URL="http://forum.lede-project.org/"
BUILD_ID="v0.10.0-dirty+lede-r3598-eb09d79c16"
LEDE_BOARD="ar71xx/generic"
LEDE_ARCH="mips_24kc"
LEDE_TAINTS="no-all busybox"
LEDE_DEVICE_MANUFACTURER="LEDE"
LEDE_DEVICE_MANUFACTURER_URL="http://lede-project.org/"
LEDE_DEVICE_PRODUCT="weimarnetz"
LEDE_DEVICE_REVISION="v0"
LEDE_RELEASE="weimarnetz Reboot SNAPSHOT v0.10.0-dirty+lede-r3598-eb09d79c16"

(this is basically stock release just with a versioning patch and the symbols added:

CONFIG_KERNEL_KALLSYMS=y
CONFIG_BUSYBOX_CUSTOM=y
CONFIG_BUSYBOX_CONFIG_MKSWAP=n
CONFIG_BUSYBOX_CONFIG_SWAPONOFF=n
CONFIG_BUSYBOX_CONFIG_MKPASSWD=y
CONFIG_BUSYBOX_CONFIG_ARPING=y
CONFIG_BUSYBOX_CONFIG_NMETER=y
CONFIG_PACKAGE_MAC80211_MESH=n
CONFIG_TARGET_SQUASHFS_BLOCK_SIZE=256
CONFIG_STRIP_KERNEL_EXPORTS=y
27.02.2017559Base systemFeature RequestVery LowLowNo Ethernet statistics on ag71xxTrunkUnconfirmed Task Description

On WNDR3700v2:

  # ethtool -i eth1 | head -n 2
  driver: ag71xx
  version: 0.5.35
  # ethtool -S eth1
  no stats available

The only statistics available are the ones provided by `ifconfig`, but I’m not sure whether that is accurate — I’m not seeing any drops even under load.

Note that statistics are available on the switch (through `swconfig show`), it’s only the SoC’s interface that’s impacted.

(While I’m at it, the driver is incomplete in other ways — there’s no support for Pause frames or for scatter-gather, although a quick read of the datasheet indicates that it should be possible to implement these features. I’m not sure that’s important, though.)

24.02.2017552Base systemFeature RequestVery LowLowBackup & restore of additionally installed packagesAllUnconfirmed Task Description

There is a discussion and also two different scripts available here:
https://forum.lede-project.org/t/feature-request-for-backup-functionality/603

Is it possible to incorporate some kind of this functionality into the standard distribution to lower the bar for newbies?

Script one:
https://forum.openwrt.org/viewtopic.php?pid=194478#p194478

second:
https://github.com/richb-hanover/OpenWrtScripts/blob/master/config-openwrt.sh

16.02.2017522Base systemBug ReportVery LowLowsudden wifi-restarts when client connects / r3439 on TP...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
- Software versions of LEDE release, packages, etc.
- Steps to reproduce

 
Thu Feb 16 13:31:57 2017 daemon.info hostapd: wlan1-1: STA 00:1e:65:94:22:52 IEEE 802.11: authenticated
Thu Feb 16 13:31:57 2017 daemon.info hostapd: wlan1-1: STA 00:1e:65:94:22:52 IEEE 802.11: associated (aid 2)
Thu Feb 16 13:31:57 2017 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED 00:1e:65:94:22:52
Thu Feb 16 13:31:58 2017 authpriv.info dropbear[4509]: Child connection from fe80::21e:65ff:fe94:2252%br-mastergate:32784
Thu Feb 16 13:32:01 2017 authpriv.notice dropbear[4509]: Password auth succeeded for 'root' from fe80::21e:65ff:fe94:2252%br-mastergate:32784
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.773904] ath: EEPROM regdomain: 0x8348
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.773917] ath: EEPROM indicates we should expect a country code
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.773924] ath: doing EEPROM country->regdmn map search
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.773930] ath: country maps to regdmn code: 0x3a
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.773936] ath: Country alpha2 being used: US
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.773942] ath: Regpair used: 0x3a
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.773948] ath: regdomain 0x8348 dynamically updated by user
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.774020] ath: EEPROM regdomain: 0x8348
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.774025] ath: EEPROM indicates we should expect a country code
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.774031] ath: doing EEPROM country->regdmn map search
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.774038] ath: country maps to regdmn code: 0x3a
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.774043] ath: Country alpha2 being used: US
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.774048] ath: Regpair used: 0x3a
Thu Feb 16 13:32:03 2017 kern.debug kernel: [ 8201.774054] ath: regdomain 0x8348 dynamically updated by user
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852253] ath: EEPROM regdomain: 0x8348
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852266] ath: EEPROM indicates we should expect a country code
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852273] ath: doing EEPROM country->regdmn map search
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852279] ath: country maps to regdmn code: 0x3a
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852286] ath: Country alpha2 being used: US
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852291] ath: Regpair used: 0x3a
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852298] ath: regdomain 0x8348 dynamically updated by user
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852368] ath: EEPROM regdomain: 0x8348
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852373] ath: EEPROM indicates we should expect a country code
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852380] ath: doing EEPROM country->regdmn map search
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852386] ath: country maps to regdmn code: 0x3a
Thu Feb 16 13:32:04 2017 kern.debug kernel: [ 8202.852391] ath: Country alpha2 being used: US
[...]
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413158] ath: doing EEPROM country->regdmn map search
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413165] ath: country maps to regdmn code: 0x3a
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413171] ath: Country alpha2 being used: US
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413176] ath: Regpair used: 0x3a
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413183] ath: regdomain 0x8348 dynamically updated by user
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413254] ath: EEPROM regdomain: 0x8348
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413259] ath: EEPROM indicates we should expect a country code
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413265] ath: doing EEPROM country->regdmn map search
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413272] ath: country maps to regdmn code: 0x3a
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413277] ath: Country alpha2 being used: US
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413282] ath: Regpair used: 0x3a
Thu Feb 16 13:32:12 2017 kern.debug kernel: [ 8210.413288] ath: regdomain 0x8348 dynamically updated by user
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491093] ath: EEPROM regdomain: 0x8348
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491106] ath: EEPROM indicates we should expect a country code
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491113] ath: doing EEPROM country->regdmn map search
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491120] ath: country maps to regdmn code: 0x3a
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491126] ath: Country alpha2 being used: US
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491131] ath: Regpair used: 0x3a
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491138] ath: regdomain 0x8348 dynamically updated by user
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491210] ath: EEPROM regdomain: 0x8348
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491215] ath: EEPROM indicates we should expect a country code
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491221] ath: doing EEPROM country->regdmn map search
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491227] ath: country maps to regdmn code: 0x3a
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491232] ath: Country alpha2 being used: US
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491237] ath: Regpair used: 0x3a
Thu Feb 16 13:32:13 2017 kern.debug kernel: [ 8211.491243] ath: regdomain 0x8348 dynamically updated by user
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: wlan0-1: interface state ENABLED->DISABLED
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: wlan0-1: AP-DISABLED 
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: wlan0-1: CTRL-EVENT-TERMINATING 
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: nl80211: deinit ifname=wlan0-1 disabled_11b_rates=0
Thu Feb 16 13:32:16 2017 daemon.notice netifd: Network device 'wlan0-1' link is down
Thu Feb 16 13:32:16 2017 daemon.notice netifd: Network alias 'wlan0-1' link is down
Thu Feb 16 13:32:16 2017 daemon.notice netifd: Interface 'wlan' has link connectivity loss
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: wlan1-1: interface state ENABLED->DISABLED
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: wlan1-1: AP-STA-DISCONNECTED 00:1e:65:94:22:52
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: wlan1-1: AP-STA-DISCONNECTED c0:c9:76:09:0c:e0
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: wlan1-1: AP-DISABLED 
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: wlan1-1: CTRL-EVENT-TERMINATING 
Thu Feb 16 13:32:16 2017 daemon.notice hostapd: nl80211: deinit ifname=wlan1-1 disabled_11b_rates=0
Thu Feb 16 13:32:16 2017 daemon.notice netifd: Network device 'wlan1-1' link is down
Thu Feb 16 13:32:16 2017 daemon.notice netifd: Network alias 'wlan1-1' link is down
Thu Feb 16 13:32:16 2017 daemon.notice netifd: Interface 'wlanRADIO1' has link connectivity loss
Thu Feb 16 13:32:16 2017 daemon.info olsrd[5562]: Removing interface wlan1
Thu Feb 16 13:32:16 2017 daemon.err olsrd[5562]: OLSR: sendto IPv4 'Network unreachable' on interface wlan1
Thu Feb 16 13:32:16 2017 daemon.notice netifd: Network device 'wlan1' link is down
Thu Feb 16 13:32:16 2017 daemon.notice netifd: Interface 'wlanadhocRADIO1' has link connectivity loss
[...]

maybe this is a side-effect of may changed regdb, but it was till now never an issue:

root@F36-stube:~ :) iw reg get
global
country US: DFS-UNSET
	(2400 - 2494 @ 40), (N/A, 30), (N/A)
	(4910 - 5895 @ 40), (N/A, 30), (N/A)

phy#1
country US: DFS-UNSET
	(2400 - 2494 @ 40), (N/A, 30), (N/A)
	(4910 - 5895 @ 40), (N/A, 30), (N/A)

phy#0
country US: DFS-UNSET
	(2400 - 2494 @ 40), (N/A, 30), (N/A)
	(4910 - 5895 @ 40), (N/A, 30), (N/A)


16.02.2017521Base systemBug ReportVery LowLowkernel warning in mac802 11 / ibss_leave / r3472TrunkUnconfirmed Task Description

it is a “TP-LINK TL-WR1043ND”.

[46258.340310] ------------[ cut here ]------------
[46258.345255] WARNING: CPU: 0 PID: 10086 at compat-wireless-2017-01-31/net/mac80211/ibss.c:1082 ieee80211_get_vht_mask_from_cap+0x1a50/0x1b90 [mac80211]()
[46258.359026] Modules linked in: ath9k ath9k_common ath9k_hw ath nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack macvlan iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables compat em_nbyte sch_dsmark sch_pie sch_codel sch_gred em_cmp cls_basic act_ipt sch_red sch_prio em_meta act_police em_text sch_sfq sch_fq act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 zram lz4_decompress lz4_compress lzo_compress lzo_decompress zsmalloc usb_storage ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache usbcore nls_base usb_common crc16 crc32c_generic crypto_hash [last unloaded: crc_ccitt]
[46258.487331] CPU: 0 PID: 10086 Comm: kworker/u2:0 Not tainted 4.4.47 #0
[46258.494018] Workqueue: phy0 ieee80211_ibss_leave [mac80211]
[46258.499637] Stack : 80e34b40 80e34b40 00000001 800a7590 818ee5bc 80410d63 803aa280 00002766
[46258.499637]    803d4ab4 809dfab4 80410000 800a550c 00000001 800a7590 803af978 80410000
[46258.499637]    00000003 809dfab4 80410000 80095528 00000001 809dfaec 00000000 801f3b30
[46258.499637]    00000001 801f3b00 80f13acc 80e12300 80e12200 70687930 00000000 00000000
[46258.499637]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[46258.499637]    ...
[46258.535670] Call Trace:
[46258.538143] [<80071e10>] show_stack+0x50/0x84
[46258.542555] [<80081b9c>] warn_slowpath_common+0xa0/0xd0
[46258.547819] [<80081c54>] warn_slowpath_null+0x18/0x24
[46258.553014] [<80f1268c>] ieee80211_get_vht_mask_from_cap+0x1a50/0x1b90 [mac80211]
[46258.560637]
[46258.562148] ---[ end trace eb9418c3bbf97ef5 ]---


uci config is:

wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.country='US'
wireless.radio0.channel='11'
wireless.radio0.frag='off'
wireless.radio0.noscan='1'
wireless.radio0.path='platform/ath9k'
wireless.radio0.hwmode='11ng'
wireless.radio0.ht_capab='SHORT-GI-40' 'DSSS_CCK-40'
wireless.radio0.htmode='HT20'
wireless.radio0.beacon_int='250'
wireless.@wifi-iface[0]=wifi-iface
wireless.@wifi-iface[0].device='radio0'
wireless.@wifi-iface[0].network='wlan'
wireless.@wifi-iface[0].mode='adhoc'
wireless.@wifi-iface[0].bssid='02:ca:ff:ee:00:11'
wireless.@wifi-iface[0].ssid='bb'
wireless.@wifi-iface[0].mcast_rate='6000'
wireless.@wifi-iface[0].macaddr='64:70:02:5c:1b:3c'
14.02.2017514Base systemBug ReportVery LowLowAny files copied to flash gone after reboot17.01.0-rc2 ...TrunkUnconfirmed Task Description

PCEngines Alix with lede-17.01.0-rc2-r3131-42f3c1f-x86-geode-combined-squashfs.img

Boots fine.

Any software installed or files copied to flash disappear after reboot.

However LAN ethernet IP address is (usually)remembered but did get reset on one occasion.
But WiFi config of a USB dongle is always lost.

The board has a Lexar 16GB UDMA7 CF card. This config works fine with OpenWrt CC.

Reflashing, changing the flash card etc makes no difference.

13.02.2017506Base systemBug ReportVery LowMediumBT Home Hub 5: 5g WiFi jumps to channel 36 and stops wo...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on BT Home Hub 5
- Software versions of LEDE release, packages, r3425-f28eef4 and previous versions
- Steps to reproduce

It can be after a few hours, if WiFi 5g radio0 Qualcomm Atheros QCA9880 802.11nac (radio0) is configured to a Band B channel, it jumps to Channel 36 even though there is no apparent interference.
This appears to happen more frequently overnight during long periods of inactivity. Whilst the device is being used it does not happen.

After it does make the jump, if I stop and restart the device (using luci disable/enable) the device stops, but it fails to restart. Attempts to change the channel and re-enable the device also do not help.

It requires a reboot to restore service.

 


12.02.2017503KernelBuild FailureVery LowMediumBuild fails with CONFIG_KERNEL_GIT_CLONE_URI beig setAllAssigned Task Description

When specifying

CONFIG_KERNEL_GIT_CLONE_URI

a clean build fails, as the system assumes a already downloaded/cloned/packed linux-source is present in dl/ which on a freshly checked out openwrt/lede source isn’t the case yet, when

toolchain/kernel-headers

is about to be built.

The build error looks like:

make[3]: Entering directory `/build/lede.git/toolchain/kernel-headers'
zcat /build/lede.git/dl/linux-4.4.42.tar.gz | tar -C /build/lede.git/build_dir/toolchain-arm_cortex-a9+neon_gcc-6.3.0_glibc-2.24_eabi -xf -
gzip: /build/lede.git/dl/linux-4.4.42.tar.gz: No such file or directory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors

The issue apparently is located in

include/kernel-defaults.mk

, line 53ff::

  ifeq ($(strip $(CONFIG_KERNEL_GIT_CLONE_URI)),"")
    define Kernel/Prepare/Default
        zcat $(DL_DIR)/$(LINUX_SOURCE) | $(TAR) -C $(KERNEL_BUILD_DIR) $(TAR_OPTIONS)
        $(Kernel/Patch)
        $(if $(QUILT),touch $(LINUX_DIR)/.quilt_used)
    endef
  else
    define Kernel/Prepare/Default
        zcat $(DL_DIR)/$(LINUX_SOURCE) | $(TAR) -C $(KERNEL_BUILD_DIR) $(TAR_OPTIONS)
    endef
  endif

For the package

kernel-headers

it just tries to access the not-yet downloaded/cloned/packed linux kernel source archive.

12.02.2017500Base systemBug ReportVery LowLowfirewall3: missing targets with IPv6 NATopenwrt-18.06Unconfirmed Task Description

When the kmod-ipt-nat6 package is installed, running /etc/init.d/firewall reload or /etc/init.d/firewall restart produces warnings that targets are missing:

 * Populating IPv6 nat table
   * Zone 'lan'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_lan_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_lan_rule'
   * Zone 'wan'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_wan_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_wan_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'prerouting_rule'
Warning: fw3_ipt_rule_append(): Can't find target 'postrouting_rule'

I tested this on an Archer C7 v2 running LEDE 17.01.0rc2.

11.02.2017499Base systemBug ReportVery LowLowWiFi client mode leaves router inaccessible if upstream...TrunkUnconfirmed Task Description

This bug was originally reported to the OpenWrt team and there is a discussion of it in their mailing list. Luiz Angelo Daros de Luca suggested reporting here (and switching to LEDE, which I will do).

I have a TP-Link TL-MR3020 v1.9 with Chaos Calmer 15.05.01. I’m using it to provide a WiFi access point to my phone/tablet while I travel, and it’s acting as a WiFi client for the various hostels I visit.

If you configure it as a wifi client with a wwan interface using the LuCI scan/join wizard, and then you configure a wifi access point on the same radio, the router works as expected and when you connect to the router’s AP, you get Internet via the client connection.

However, if you move out of range of the network the router is a client of, or if it goes down, when you power off the OpenWrt router and power back on, the access point won’t come up.

The AP will only come up if the client network you configured is also working; so you have no way to connect to the router over wifi, and no way to reconfigure the router, if that client network is down or out of range.

This is a particular problem for a travel router because it will often move it out of range of the original upstream network, and you may only have a wifi-capable device with which to reconfigure it.

The Ethernet port on the router does remain active, so I can tell it does actually boot. It’s just the radio that doesn’t come up. I managed to get back in range of a network once, and the router worked as expected.

It doesn’t matter whether the AP or client connection are configured first or second on the radio interface, and, unticking “bring up on boot” for the wwan interface has no effect on the behaviour.

Steps to reproduce: Connect the router to a wifi network as a client using the Join wizard. Add a wifi master-mode access point on the same radio interface. Verify you can access the Internet by joining the router’s new master AP. Reboot the router with the original network it was a client of turned off. Notice the router’s AP you configured never comes up.

Expected behaviour: The master access point of the router should always come up, regardless of the availability of the client network.

The OpenWRT team will not fix it, but had some explanation as to why it is happening. IMO, it’s still a very frustrating bug and most users would expect the behaviour I did.

10.02.2017494Base systemBug ReportVery LowCriticalNETDEV WATCHDOG: ptm0 (): transmit queue 0 timed outAllNew Task Description

I have a VDSL line with Plusnet (UK) - the connection is pppoe - ptm0.101. With the supplied modem/router the line and connection is stable with no disconnects. With LEDE the connection is established and works well until it disconnects (sometimes as early as few minutes other times it stays connected up to an hour). After the disconnect there is no reconnection until a reboot. Restarting wan interface (ifdown wan/ifup wan) or dsl connection (/etc/init.d/dslcontrol stop/start) does not help.

Supply the following if possible:
- Device problem occurs on TP-w8970 and BTHomehub 5A (same crash on both lantiq based devices)
- Software versions of LEDE release, packages, etc. Tested on LEDE RC2, earlier LEDE snapshot from October 2016, Openwrt CC - same symptoms
- Steps to reproduce - VDSL connection on ptm0.101 via pppoe

Here is a trace of the crash (dmesg):

[ 1414.124413] —[ beginning trace ff034b465cdad16b ]— [ 1414.125631] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x1a8/0x2f0()
[ 1414.126471] NETDEV WATCHDOG: ptm0 (): transmit queue 0 timed out
[ 1414.132456] Modules linked in: ltq_ptm_vr9 option iptable_nat ath9k usb_wwan rt2800usb rt2800lib
pppoe nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 l2tp_ppp ipt_REJECT ipt_MASQUERADE ath9k_common
xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_policy xt_nat xt_multiport xt_mark xt_mac
xt_limit xt_length xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit
xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY usbserial rt2x00usb
rt2x00lib pppox ppp_async nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6
nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack ltq_deu_vr9 iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN
ip_tables crc_itu_t crc_ccitt cdc_acm ath9k_hw ath10k_pci ath10k_core ath mac80211 cfg80211 compat drv_dsl_cpe_api
drv_mei_cpe xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net
ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark
ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6
nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables pppoatm ppp_generic slhc
l2tp_ip6 l2tp_ip l2tp_eth sit l2tp_netlink l2tp_core udp_tunnel ip6_udp_tunnel ipcomp xfrm4_tunnel xfrm4_mode_tunnel
xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo br2684 atm
drv_ifxos echainiv sha256_generic sha1_generic jitterentropy_rng drbg md5 hmac des_generic cbc authenc usb_storage
dwc2 uhci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache aead crypto_null
[ 1414.287462] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.7 #1
[ 1414.293130] Stack : 804b0000 00000001 00000000 00000000 805172b8 80516f43 80489a24 00000000
[ 1414.293130] 80673844 00010000 80510000 805159bc 80515abc 80055664 00000003 80510000
[ 1414.293130] 80491b4c 00000000 8048ff50 80511c44 80515abc 800535b0 00000006 00000001
[ 1414.293130] 00000000 80512000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1414.293130] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1414.293130] ...
[ 1414.328618] Call Trace:
[ 1414.331095] [<800178a8>] show_stack+0×50/0×84 [ 1414.335454] [<8002af48>] warn_slowpath_common+0xa0/0xd0
[ 1414.340670] [<8002afa4>] warn_slowpath_fmt+0x2c/0×38 [ 1414.345636] [<802e637c>] dev_watchdog+0x1a8/0x2f0
[ 1414.350348] [<8005f7b0>] call_timer_fn.isra.5+0×24/0×80 [ 1414.355557] [<8005fa2c>] run_timer_softirq+0x1a4/0×208 [ 1414.360694] [<8002de80>] __do_softirq+0×298/0x2b0
[ 1414.365388] [<80002430>] ret_from_irq+0×0/0×4 [ 1414.369760] [<80013a8c>] r4k_wait_irqoff+0×18/0×20 [ 1414.374528] [<8004ff6c>] cpu_startup_entry+0xa4/0xf8
[ 1414.379508] [<80539bf8>] start_kernel+0×474/0×494 [ 1414.384180]
[ 1414.385631] —[ end trace ff034b465cdad16b ]—

 


09.02.2017488Base systemBug ReportVery LowMediumdynamic VLAN doesn't work on ath10kopenwrt-19.07Unconfirmed Task Description

Dynamic vlan config on ath10k seems not to work. Same config on ath9k works fine.

Config:

config wifi-device  radio0
        option type     mac80211
        option channel  36
        option hwmode   11a
        option path     'pci0000:01/0000:01:00.0'
        option htmode   VHT80
[...]

config wifi-iface
        option device   radio0
        option network  vlan1
        option mode     ap
[...]
        option dynamic_vlan     '1'
        option 'vlan_tagged_interface' 'eth1'
        option 'vlan_bridge' 'br-vlan'
        option 'vlan_naming' '0'

Log:

Thu Feb  9 15:54:37 2017 daemon.err hostapd: WPA initialization for VLAN 1 failed (-1)
Thu Feb  9 15:54:37 2017 daemon.err hostapd: WPA deinit of wlan0.1 failed
Thu Feb  9 15:54:37 2017 daemon.debug hostapd: wlan0: STA ac:22:0b:a1:c7:6b IEEE 802.11: could not add dynamic VLAN interface for vlan=1
07.02.2017479Base systemBug ReportVery LowLowSoftethervpn results in ReAlloc error after vpnbridge i...TrunkUnconfirmed Task Description

On a mostly vanilla Atmel at91sam9g20-ek with 32MB of RAM, we are seeing a couple of errors using the current package software version + patches.

Overall, it may be the cross compilation process, overlay or something else entirely.

1. If the vpnbridge is already started, a NAND-WAIT stacktrace results if the binary is executed to instantiate a second instance.

root@lede:/usr/libexec/softethervpn# /usr/bin/env LANG=en_US.UTF-8 vpncmd
[  241.880000] 
[  241.880000] =================================
[  241.880000] [ INFO: inconsistent lock state ]
[  241.880000] 4.4.36 #0 Not tainted
[  241.880000] ---------------------------------
[  241.880000] inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage.
[  241.880000] kswapd0/155 [HC0[0]:SC0[0]:HE1:SE1] takes:
[  241.880000]  (&f->sem){+.+.?.}, at: [<c012949c>] jffs2_do_clear_inode+0x28/0x114
[  241.880000] {RECLAIM_FS-ON-W} state was registered at:
[  241.880000]   [<c005047c>] lockdep_trace_alloc+0xf8/0x118
[  241.880000]   [<c00b5610>] kmem_cache_alloc+0x28/0x144
[  241.880000]   [<c01261d8>] jffs2_alloc_inode_cache+0x1c/0x28
[  241.880000]   [<c01293a4>] jffs2_do_read_inode+0x13c/0x20c
[  241.880000]   [<c012fe58>] jffs2_iget+0x74/0x324
[  241.880000]   [<c0130830>] jffs2_do_fill_super+0x190/0x274
[  241.880000]   [<c0130e98>] jffs2_fill_super+0xf4/0x144
[  241.880000]   [<c01d1528>] mount_mtd_aux+0x80/0x10c
[  241.880000]   [<c01d1630>] mount_mtd_nr+0x7c/0x94
[  241.880000]   [<c01d17f8>] mount_mtd+0x1b0/0x210
[  241.880000]   [<c01309d4>] jffs2_mount+0x1c/0x28
[  241.880000]   [<c00bbbe4>] mount_fs+0x1c/0xac
[  241.880000]   [<c00d6418>] vfs_kern_mount+0x5c/0x12c
[  241.880000]   [<c00d9e68>] do_mount+0xa04/0xbc8
[  241.880000]   [<c00da270>] SyS_mount+0x7c/0xa8
[  241.880000]   [<c0009660>] ret_fast_syscall+0x0/0x1c
[  241.880000] irq event stamp: 45867
[  241.880000] hardirqs last  enabled at (45867): [<c001508c>] _raw_spin_unlock_irq+0x2c/0x6c
[  241.880000] hardirqs last disabled at (45866): [<c0014e88>] _raw_spin_lock_irq+0x28/0x70
[  241.880000] softirqs last  enabled at (45450): [<c0024088>] __do_softirq+0x208/0x2a4
[  241.880000] softirqs last disabled at (45431): [<c0024488>] irq_exit+0xa4/0xec
[  241.880000] 
[  241.880000] other info that might help us debug this:
[  241.880000]  Possible unsafe locking scenario:
[  241.880000] 
[  241.880000]        CPU0
[  241.880000]        ----
[  241.880000]   lock(&f->sem);
[  241.880000]   <Interrupt>
[  241.880000]     lock(&f->sem);
[  241.880000] 
[  241.880000]  *** DEADLOCK ***
[  241.880000] 
[  241.880000] 2 locks held by kswapd0/155:
[  241.880000]  #0:  (shrinker_rwsem){++++..}, at: [<c0090034>] shrink_slab.part.1.constprop.7+0x30/0x230
[  241.880000]  #1:  (&type->s_umount_key#32){.+.+..}, at: [<c00bb3ec>] trylock_super+0x1c/0x60
[  241.880000] 
[  241.880000] stack backtrace:
[  241.880000] CPU: 0 PID: 155 Comm: kswapd0 Not tainted 4.4.36 #0
[  241.880000] Hardware name: Atmel AT91SAM9
[  241.880000] Backtrace: 
[  241.880000] [<c0019798>] (dump_backtrace) from [<c0019994>] (show_stack+0x18/0x1c)
[  241.880000]  r7:0000000a r6:c38af4c0 r5:c38af0c0 r4:c068f314
[  241.880000] [<c001997c>] (show_stack) from [<c016fdd8>] (dump_stack+0x20/0x28)
[  241.880000] [<c016fdb8>] (dump_stack) from [<c004d144>] (print_usage_bug.part.11+0x228/0x290)
[  241.880000] [<c004cf1c>] (print_usage_bug.part.11) from [<c004d5b0>] (mark_lock+0x404/0x63c)
[  241.880000]  r8:c004c558 r7:c38af0c0 r6:c38af4c0 r5:00000008 r4:0000000a
[  241.880000] [<c004d1ac>] (mark_lock) from [<c004e638>] (__lock_acquire+0x97c/0x198c)
[  241.880000]  r10:c38af0c0 r9:c0667044 r8:c38af4c0 r7:00000001 r6:00000002 r5:c3675704
[  241.880000]  r4:0000025d r3:00000004
[  241.880000] [<c004dcbc>] (__lock_acquire) from [<c004fdcc>] (lock_acquire+0x7c/0x9c)
[  241.880000]  r10:00000042 r9:c334c4c4 r8:c38af0c0 r7:c0ccdd8c r6:00000001 r5:60000013
[  241.880000]  r4:00000000
[  241.880000] [<c004fd50>] (lock_acquire) from [<c0011580>] (mutex_lock_nested+0x50/0x39c)
[  241.880000]  r6:c334d000 r5:c334d000 r4:c36756d0
[  241.880000] [<c0011530>] (mutex_lock_nested) from [<c012949c>] (jffs2_do_clear_inode+0x28/0x114)
[  241.880000]  r10:00000042 r9:c334c4c4 r8:c334c000 r7:00000058 r6:c334d000 r5:c334d000
[  241.880000]  r4:c36756d0
[  241.880000] [<c0129474>] (jffs2_do_clear_inode) from [<c012fde0>] (jffs2_evict_inode+0x34/0x38)
[  241.880000]  r7:00000058 r6:c044ba88 r5:c334d000 r4:c3675730
[  241.880000] [<c012fdac>] (jffs2_evict_inode) from [<c00d1a7c>] (evict+0xac/0x164)
[  241.880000]  r5:c367580c r4:c3675730
[  241.880000] [<c00d19d0>] (evict) from [<c00d1b6c>] (dispose_list+0x38/0x44)
[  241.880000]  r7:00000058 r6:00000063 r5:00000006 r4:c392dd58
[  241.880000] [<c00d1b34>] (dispose_list) from [<c00d2e1c>] (prune_icache_sb+0x4c/0x5c)
[  241.880000]  r5:00000006 r4:c392dd58
[  241.880000] [<c00d2dd0>] (prune_icache_sb) from [<c00bb570>] (super_cache_scan+0x140/0x184)
[  241.880000]  r5:00000000 r4:c392ddd8
[  241.880000] [<c00bb430>] (super_cache_scan) from [<c00901b0>] (shrink_slab.part.1.constprop.7+0x1ac/0x230)
[  241.880000]  r10:00000601 r9:00000000 r8:00000000 r7:00000400 r6:00000062 r5:c334c4c4
[  241.880000]  r4:000000a5
[  241.880000] [<c0090004>] (shrink_slab.part.1.constprop.7) from [<c0092318>] (shrink_zone+0x5f0/0x640)
[  241.880000]  r10:00000004 r9:00000117 r8:c04da918 r7:00000000 r6:00000000 r5:c392ded4
[  241.880000]  r4:c04da6fc
[  241.880000] [<c0091d28>] (shrink_zone) from [<c0092c8c>] (kswapd+0x4ac/0x668)
[  241.880000]  r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c04da6fc
[  241.880000]  r4:c04da6fc
[  241.880000] [<c00927e0>] (kswapd) from [<c003d1b4>] (kthread+0xe4/0xfc)
[  241.880000]  r10:00000000 r9:00000000 r8:00000000 r7:c00927e0 r6:c04da6fc r5:00000000
[  241.880000]  r4:c3950780
[  241.880000] [<c003d0d0>] (kthread) from [<c00096ec>] (ret_from_fork+0x14/0x28)
[  241.880000]  r7:00000000 r6:00000000 r5:c003d0d0 r4:c3950780

2. If the vpnbridge is instantiated only once, and the vpn client is to be executed, a realloc error occurs:

 /usr/bin/env LANG=en_US.UTF-8 ./vpnclient 
Fatal Error: InternalReAlloc: error: realloc() failed.


Aborted

This is on 4.4.36 LEDE trunk with a FS that looks like:

Filesystem                Size      Used Available Use% Mounted on
/dev/root                 7.4M      7.4M         0 100% /rom
tmpfs                    25.3M      2.7M     22.6M  11% /tmp
tmpfs                    25.3M     44.0K     25.2M   0% /tmp/root
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mtdblock2           50.0M      2.2M     47.8M   4% /overlay
overlayfs:/overlay       50.0M      2.2M     47.8M   4% /

Any assistance would be helpful.


06.02.2017472Base systemBug ReportVery LowMedium6to4 support with 1:1 natTrunkWaiting on reporter Task Description

One-to-one NAT means you have LAN address on interface and its mapped 1:1 to external ip addresses.
You can have incoming connections.

In such configuration “ipaddr” must be specified in 6to4 protocol section.
But due to bug this addr is submitted as local address for tunnel creation.
It does not work.

I fixed this with the following patch to /lib/netifd/proto/6to4.sh

48,53c48,53
< [ -z “$ipaddr” ] && {
< if ! network_get_ipaddr ipaddr “$wanif”; then
< proto_notify_error “$cfg” “NO_WAN_ADDRESS” < return
< fi
< }

if ! network_get_ipaddr ipladdr “$wanif”; then
> proto_notify_error “$cfg” “NO_WAN_ADDRESS”
return
> fi
>
> [ -z “$ipaddr” ] && ipaddr=$ipladdr
76c76
< json_add_string local “$ipaddr”

json_add_string local “$ipladdr”

I suggest you integrate this patch or do something similar yourself.

04.02.2017463Base systemBug ReportVery LowLowup/down on a usbnet interfaces fails to reassign ULA ad...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: anything running usbnet
- Software versions of LEDE release, packages, etc: head
- Steps to reproduce:

Install the usbnet package, enable a usb0 device in /etc/config/network

(in my case this is a c.h.i.p, but most hackerboards except the pi do usbnet)

config interface ‘usb0’

      option ifname 'usb0'            
      option proto 'static'                 
      option ipaddr '172.26.97.200'
      option netmask '255.255.255.255'
      option ip6assign '64'           
      option ip6class 'local' 

So long as the chip beats the router to booting, this gives it an ipv4 and ipv6 ULA out of the pool.

Reboot the device on the other side. The kernel deregisters and registers the usbnet driver, and netifd assigns the ipv4 address again.

However the ip6 subnet that was assigned from the ula does not come back. Haven’t tried it with a public address.

ifup/ifdown does not work and the ifstatus usb0 does not show any ipv6 addresses assigned.

04.02.2017461Base systemBug ReportVery LowMediumMass Cascade of DHCP ULA Prefix Assignments with DHCP-P...AllUnconfirmed Task Description

Here is one that gets a bit ugly. Lets say we chain a bunch of LEDE based routers together. Lets also enable a nice numbering system in IP4 and IP6. Lets enable DHCP-PD through the network, because our ISP was generous with a /56. The IP4 is only static and is easy to control, see table below. Its tedious, but easy. The problem is in parallel the IP6 addresses compound in the ULA region. Each router DHCP-PD the ULA above it, and gets its own ULA from Global settings in Network UCI. There seems no easy way to control this mass cascade of ULA, and get good fail over.

Ideal Requirements:
(1) If router above is unavailable, then next tier router uses ULA (network global UCI) to begin assigning addresses to clients and subnets.
(2) If router above is available, then next tier router expires its self-generated ULA and subnets, and gets ULA from delegation above to then re-delegate to subnets.
(*) Bonus: make some parts optional

IP4 WAN Name Serves Subnet
(NAT) Router-1 172.16.0.1/24
172.16.0.2 Router-2A 172.17.0.1/24
172.17.0.2 Router-3A 172.24.0.1/24
172.17.0.3 Router-3B 172.25.0.1/24
172.16.0.3 Router-2B 172.18.0.1/24

IP6 Roots Name Serves Subnet Delegates Subnet
2001:db8/56 Router-1 2001:db8::1/64 2001:db8:0:10/60
fd00:ac10/48 fd00:ac10::1/64 2001:db8:0:20/60

                                                fd00:ac10:0:10/60
                                                fd00:ac10:0:20/60

2001:db8:0:10/60 Router-2A 2001:db8:0:10::1/64 2001:db8:0:14/62
fd00:ac10:0:10/60 fd00:ac10:0:10::1/64 2001:db8:0:18/62
fd00:ac11/48 fd00:ac11::1/64 fd00:ac10:0:14/62

                                                fd00:ac10:0:18/62
                                                fd00:ac11:0:14/62
                                                fd00:ac11:0:18/62

* please, i don’t want to type more. see how the ULA prefixes just keep multiplying.
** ‘172.16’ = ‘ac10’

01.02.2017449Base systemBug ReportVery LowLowrelayd can cause dropped packets if client has /proc/sy...TrunkUnconfirmed Task Description

DEVICE: N/A (can be reproduced on any system running relayd)
LEDE version: N/A (can be reproduced on a VM running debian with relayd installed)

Steps to reproduce:

* Run relayd on a system (aka router)with two interfaces.
* Run a stock Ubuntu-16.04 system (aka client) connected to the managed interface.
* Run another system (aka server) on the other interface of relayd system.
* Have server ping client and watch connectivity drop out periodically.
* Have client ping server and watch connectivity drop out periodically.

Our fix for the problem need two changes:

* Add arptables rules to system to handle kernel level arp requests properly via mangling the source address in the arp requests
* Modify relayd to send the correct src addr in the arp requests that it generates.

Our changes to relayd are here:

* https://github.com/troth/relayd/commit/c8d895ee71be59262f01c3fdf50f307ebf1593e7

From commit message for my fix:

    Add option to set arp src addr for managed interfaces.
    
    Relayd will send arp requests out a managed interface like this:
    
        Who has 192.168.1.40, tell 192.168.2.1
    
    In most cases, this works, but some clients will not send a reply (on
    linux, client will not reply if /proc/sys/net/ipv4/conf/*/rp_filter is
    set to 1, which happens to be the default on ubuntu-16.04).
    
    Add '-s' option to tell relayd to use the specified addr as the arp src
    addr for managed interfaces. The arp requests would then look like:
    
        Who has 192.168.1.40, tell 192.168.1.100
    
    for which the client properly sends a reply.
    
    The symptoms of the problem manifest as dropped packets due to the
    kernel marking the arp entry for the client as FAILED due to lack of
    responses to the arp requests. Eventually (10-30 seconds later), the arp
    table is updated and connectivity is restored.
28.01.2017441Base systemBug ReportVery LowLowKernel crash: eth0 (ag71xx): transmit queue 0 timed outTrunkUnconfirmed Task Description

Device: TL-WR1043ND v1
LEDE: snapshot r3189-12db207

During a simultaneous bidirectional iperf load test, after about 20 minutes, the kernel crashes. I reproduced this several times:

Server 1 ←–> 1043ND ←–> Laptop via wireless N

LEDE is using a default setup. Only changes:
* Setting wireless encryption to psk with password
* Setting a DNAT rule for server 1 to be able reach the iperf server on the Laptop

This bug was actually discovered while testing fixes for  FS#13  - Ath9k AP stays up for connected clients but doesn’t show in scan on new ones

Serial console ouput:

[ 1294.022551] ------------[ cut here ]------------
[ 1294.027247] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:306 dev_watchdog+0x1dc/0x260()
[ 1294.035754] NETDEV WATCHDOG: eth0 (ag71xx): transmit queue 0 timed out
[ 1294.042319] Modules linked in: ath9k ath9k_common pppoe ppp_async ath9k_hw ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nn
[ 1294.106287] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.45 #0
[ 1294.112066] Stack : 803e4844 00000000 00000001 80440000 8042f1dc 8042ee63 803c5e64 00000000
          804a378c 8042d4fc 00000200 00100000 0000000a 800a7618 803cb554 80430000
          00000003 8042d4fc 803c9960 81809e34 0000000a 800a5594 00000006 00000000
          00000000 801f5400 00000000 00000000 00000000 00000000 00000000 00000000
          00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          ...
[ 1294.148122] Call Trace:
[ 1294.150617] [<800a7618>] vprintk_default+0x24/0x30
[ 1294.155474] [<800a5594>] printk+0x2c/0x38
[ 1294.159515] [<801f5400>] wait_for_xmitr+0x84/0xcc
[ 1294.164289] [<80081c3c>] warn_slowpath_common+0xa0/0xd0
[ 1294.169564] [<801a72dc>] dump_stack+0x14/0x28
[ 1294.173975] [<80071eb0>] show_stack+0x50/0x84
[ 1294.178376] [<80081c3c>] warn_slowpath_common+0xa0/0xd0
[ 1294.183661] [<8028ef3c>] dev_watchdog+0x1dc/0x260
[ 1294.188408] [<80081c98>] warn_slowpath_fmt+0x2c/0x38
[ 1294.193450] [<8028ef3c>] dev_watchdog+0x1dc/0x260
[ 1294.198191] [<8028ed60>] dev_watchdog+0x0/0x260
[ 1294.202782] [<800b08d0>] call_timer_fn.isra.5+0x24/0x80
[ 1294.208051] [<800b0b54>] run_timer_softirq+0x1b4/0x1fc
[ 1294.213248] [<800a89f0>] handle_irq_event_percpu+0x154/0x188
[ 1294.218960] [<800841b8>] __do_softirq+0x250/0x298
[ 1294.223721] [<800abdac>] handle_percpu_irq+0x50/0x80
[ 1294.228746] [<8006a9e0>] plat_irq_dispatch+0xd4/0x10c
[ 1294.233848] [<80060bf4>] handle_int+0x134/0x140
[ 1294.238400] 
[ 1294.239904] ---[ end trace 17bad011a41ccba7 ]---
[ 1294.244567] eth0: tx timeout
[ 1299.022570] eth0: tx timeout
[ 1304.022581] eth0: tx timeout
[ 1309.022588] eth0: tx timeout

The eth0: tx timeout line is repeated every 5 seconds.


24.01.2017427Base systemBug ReportVery LowMediumSwitch broken with WRT3200ACM (removes wifi adapters an...TrunkUnconfirmed Task Description

- Device problem occurs on:

WRT3200ACM

- Software versions of LEDE release, packages, etc.:

master tree (and v17.01), bisected to f24ffb901e0408917748773b883841eca52eea05.

- Steps to reproduce

* Flash a recent LEDE snapshot on the WRT3200ACM (and factory reset),
* enable wifi (2 or 5 Gz) → Wifi works
* disable wifi → errors in the dmesg about not being able to set a feature (can’t remember the exact error)
* re-enable wifi → errors in the dmesg saying that the adapter does not exist. This gets shouted in the dmesg every 5 seconds

A reboot doesn’t fix the issue. I need to downgrade the firmware prior to f24ffb901e0408917748773b883841eca52eea05 and factory reset to get the wifi adapters back.

For the Vlan bridge, symptoms are easier to detect:
* create a new adapter bridged on eth0.100 eth1.100
* no traffic goes through it. An snapshot before f24ffb901 used to work
(the setup is the Free french provider which has a vlan between the modem and the TV adapter over VLAN 100. So the LEDE box should act like a pass-through here only)

I bisected to the commit mentioned above (which, to me seems suspicious given that the driver is for mvsw61xx and the switch in the WRT3200ACM is MV88E6352, so a different generation). I don’t have enough knowledge of the chip to understand why this fails, but I don’t feel confident enough to simply send a PR with the revert.

Reverting f24ffb901e on top of master makes the Wifi and VLAN back to normal.


18.01.2017406Base systemFeature RequestVery LowLowodhcpd: enable IPv6 unicast relayTrunkUnconfirmed Task Description

We want to use Prefix Delegation in a large layer3 mesh network. Currently odhcpd only supports DHCPv6-Relay by forwarding the incoming request to the master interface with multicast all-routers-destination address.

In a mesh network we do not have master/uplink interfaces. But we have the IP of the DHCP server which is X hops away and the routing protocol knows which way to send the packet.

Is it possible to add dhcp relay via unicast? An additional config parameter for the IP of the DHCP server is then also needed.

18.01.2017403PackagesFeature RequestVery LowLowodhcpd: expand the capability of DHCPv6 HOSTID assignem...TrunkUnconfirmed Task Description

It would be nice to assign the HOSTID range or bit width as an option. odhcpd just assigns ::0100~::0FFF without any options. It would be nice to be able to use all 64 bits. With this, also it would be nice to add a random seed and seed time as options. This way the DUID hash-to-HOSTID could be rotated. In this way, SLAAC privacy addresses could be replicated with STATEFUL DHCP control and well known hostnames. This would support high-accountability networks like Universities and other large organizations.

It would be a counter to Google’s lack of “interest” in supporting DHCPv6. This would provide DHCPv6 privacy addresses.
Android Bug: https://code.google.com/p/android/issues/detail?id=32621

18.01.2017401PackagesFeature RequestVery LowLowodhcpd: lease trigger script receives no argumentsTrunkUnconfirmed Task Description

when odhcpd calls the “lease trigger” script it does not pass any arguments to the script. The reason for the trigger and the host involved in the trigger are not shared. There is no discretion for RENEW, REBIND, CONFIRM, or RELEASE. Scripts which wish to load DNS with limited data, need to store their own copy of DHCP lease file and do differences. Otherwise a raw translate and dump of a large DHCP network could cause a lot of congestion as DHCP clients come on line. Reseting a network can cause an “in rush” flow like air conditioning loads on a power grid during a summer power outage.
This is exacerbated if the DNS is served on a separate device over the network, such as nsd and nsd-control (bind or unbound also). It would be good to at least pass the command and parameters common to a odhcpd lease file line.

18.01.2017400PackagesBug ReportVery LowLowodhcpd: lease file persistence per RFC2131 S-2.1 and S-...TrunkUnconfirmed Task Description

RFC2131 DHCPv4 expects that the DHCP leases and other configuration results are in persistent storage. For small embedded routers during a machine reboot, it has been accepted that read-write memory is RAM (not flash) and persistence may not be entirely upheld. That being said, odhcpd has no means to maintain the lease information even through an application only restart (example ifup event). The lease file odhcpd writes is not used to seed odhcpd, if it is restarted. (1) an interface reconnect that causes odhcpd to restart destroys the lease record, even if the network resumes as previously configured. (2) even if odhcpd lease file is directed to persistent storage (USB drive) it is not used to resume leases.

17.01.2017398PackagesFeature RequestVery LowLowodhcpd: add UCI option to insert DHCP fill for missing ...TrunkUnconfirmed Task Description

This is a request for a common DHCP function found in other software. It would be nice for an odhcpd general option to enable it to fill in unnamed leases. DHCPv4 use the MAC as in unknown-010203040506 and DHCPv6 use the last 64 bits of the DUID as in unknown-0102030405060708. This can be used to figure out which device has failed to send its host name. This is a common problem with DHCPv6. This is a common problem for smart TV or cameras. Consider logs from a device other than the DHCP serving router. Consider where IT may not want to static assign 100’s of host names for display devices over a large work site or campus. Security logs and DHCP logs on a distributed network can then be reconciled a-synchronously, off line, or only when an investigation is required.

17.01.2017395Base systemBug ReportMediumLowmac80211.sh: detect_mac80211 should check available cha...TrunkNew Task Description

This problem was reported by few Netgear R8000 users and I managed to reproduce it. It’s related to the following code:

		vht_cap=$(iw phy "$dev" info | grep -c 'VHT Capabilities')
		cap_5ghz=$(iw phy "$dev" info | grep -c "Band 2")
		[ "$vht_cap" -gt 0 -a "$cap_5ghz" -gt 0 ] && {
			mode_band="a";
			channel="36"
			htmode="VHT80"
		}

Default htmode

The first problem is that even if hardware supports VHT80 it may be not available for every/any current channel. If channel 36 doesn’t support VHT80, for better user experience, it shouldn’t be set in /etc/config/wireless by default. Example:

root@lede:/# iw phy phy2 info
Wiphy phy2
        max # scan SSIDs: 10
        max scan IEs length: 2048 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports roaming.
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * P2P-client
                 * P2P-GO
                 * P2P-device
        Band 2:
                Capabilities: 0x1062
                        HT20/HT40
                        Static SM Power Save
                        RX HT20 SGI
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 16 usec (0x07)
                HT TX/RX MCS rate indexes supported: 0-23
                VHT Capabilities (0x0c025820):
                        Max MPDU length: 3895
                        Supported Channel Width: neither 160 nor 80+80
                        short GI (80 MHz)
                        SU Beamformer
                        SU Beamformee
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT RX highest supported: 0 Mbps
                VHT TX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 0 Mbps
                Frequencies:
                        * 5170 MHz [34] (disabled)
                        * 5180 MHz [36] (20.0 dBm)
                        * 5190 MHz [38] (disabled)
                        * 5200 MHz [40] (20.0 dBm)
                        * 5210 MHz [42] (disabled)
                        * 5220 MHz [44] (20.0 dBm)
                        * 5230 MHz [46] (disabled)
                        * 5240 MHz [48] (20.0 dBm)
                        * 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
                        * 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
                        * 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
                        * 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
                        * 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
                        * 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
                        * 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
                        * 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
                        * 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
                        * 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
                        * 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
                        * 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
                        * 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
                        * 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
                        * 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
                        * 5720 MHz [144] (disabled)
                        * 5745 MHz [149] (disabled)
                        * 5765 MHz [153] (disabled)
                        * 5785 MHz [157] (disabled)
                        * 5805 MHz [161] (disabled)
                        * 5825 MHz [165] (disabled)
        valid interface combinations:
                 * #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
                   total <= 3, #channels <= 1
                 * #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
                   total <= 4, #channels <= 1
                 * #{ AP } <= 4,
                   total <= 4, #channels <= 1, STA/AP BI must match
root@lede:/# iw phy phy2 channels
Band 2:
        * 5170 MHz [34] (disabled)
        * 5180 MHz [36] 
          Maximum TX power: 20.0 dBm
          Channel widths: 20MHz HT40+
        * 5190 MHz [38] (disabled)
        * 5200 MHz [40] 
          Maximum TX power: 20.0 dBm
          Channel widths: 20MHz HT40-
        * 5210 MHz [42] (disabled)
        * 5220 MHz [44] 
          Maximum TX power: 20.0 dBm
          Channel widths: 20MHz HT40+
        * 5230 MHz [46] (disabled)
        * 5240 MHz [48] 
          Maximum TX power: 20.0 dBm
          Channel widths: 20MHz HT40-
        * 5260 MHz [52] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40+
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5280 MHz [56] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40-
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5300 MHz [60] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40+
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5320 MHz [64] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40-
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5500 MHz [100] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40+
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5520 MHz [104] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40-
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5540 MHz [108] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40+
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5560 MHz [112] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40-
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5580 MHz [116] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40+
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5600 MHz [120] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40-
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5620 MHz [124] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40+
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5640 MHz [128] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40-
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5660 MHz [132] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40+
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5680 MHz [136] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz HT40-
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5700 MHz [140] 
          Maximum TX power: 20.0 dBm
          No IR
          Radar detection
          Channel widths: 20MHz
          DFS state: usable (for 163 sec)
          DFS CAC time: 0 ms
        * 5720 MHz [144] (disabled)
        * 5745 MHz [149] (disabled)
        * 5765 MHz [153] (disabled)
        * 5785 MHz [157] (disabled)
        * 5805 MHz [161] (disabled)
        * 5825 MHz [165] (disabled)

as you can see, VHT80 isn’t support on any currently available channel due to regulatory limits.

Default channel

Picking channel 36 blindly is a bad idea as it may not be available. In case of phy0/radio0 on Netgear R8000 only available channels are 149+ due to hardware/board design (see ARM: BCM5301X: Set 5 GHz wireless frequency limits on Netgear R8000).

root@lede:/# iw phy phy0 info
Wiphy phy0
        max # scan SSIDs: 10
        max scan IEs length: 2048 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports roaming.
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * P2P-client
                 * P2P-GO
                 * P2P-device
        Band 2:
                Capabilities: 0x1062
                        HT20/HT40
                        Static SM Power Save
                        RX HT20 SGI
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 16 usec (0x07)
                HT TX/RX MCS rate indexes supported: 0-23
                VHT Capabilities (0x0c025820):
                        Max MPDU length: 3895
                        Supported Channel Width: neither 160 nor 80+80
                        short GI (80 MHz)
                        SU Beamformer
                        SU Beamformee
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT RX highest supported: 0 Mbps
                VHT TX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 0 Mbps
                Frequencies:
                        * 5170 MHz [34] (disabled)
                        * 5180 MHz [36] (disabled)
                        * 5190 MHz [38] (disabled)
                        * 5200 MHz [40] (disabled)
                        * 5210 MHz [42] (disabled)
                        * 5220 MHz [44] (disabled)
                        * 5230 MHz [46] (disabled)
                        * 5240 MHz [48] (disabled)
                        * 5260 MHz [52] (disabled)
                        * 5280 MHz [56] (disabled)
                        * 5300 MHz [60] (disabled)
                        * 5320 MHz [64] (disabled)
                        * 5500 MHz [100] (disabled)
                        * 5520 MHz [104] (disabled)
                        * 5540 MHz [108] (disabled)
                        * 5560 MHz [112] (disabled)
                        * 5580 MHz [116] (disabled)
                        * 5600 MHz [120] (disabled)
                        * 5620 MHz [124] (disabled)
                        * 5640 MHz [128] (disabled)
                        * 5660 MHz [132] (disabled)
                        * 5680 MHz [136] (disabled)
                        * 5700 MHz [140] (disabled)
                        * 5720 MHz [144] (disabled)
                        * 5745 MHz [149] (20.0 dBm)
                        * 5765 MHz [153] (20.0 dBm)
                        * 5785 MHz [157] (20.0 dBm)
                        * 5805 MHz [161] (20.0 dBm)
                        * 5825 MHz [165] (20.0 dBm)
        valid interface combinations:
                 * #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
                   total <= 3, #channels <= 1
                 * #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
                   total <= 4, #channels <= 1
                 * #{ AP } <= 4,
                   total <= 4, #channels <= 1, STA/AP BI must match
root@lede:/# iw phy phy0 channels
Band 2:
        * 5170 MHz [34] (disabled)
        * 5180 MHz [36] (disabled)
        * 5190 MHz [38] (disabled)
        * 5200 MHz [40] (disabled)
        * 5210 MHz [42] (disabled)
        * 5220 MHz [44] (disabled)
        * 5230 MHz [46] (disabled)
        * 5240 MHz [48] (disabled)
        * 5260 MHz [52] (disabled)
        * 5280 MHz [56] (disabled)
        * 5300 MHz [60] (disabled)
        * 5320 MHz [64] (disabled)
        * 5500 MHz [100] (disabled)
        * 5520 MHz [104] (disabled)
        * 5540 MHz [108] (disabled)
        * 5560 MHz [112] (disabled)
        * 5580 MHz [116] (disabled)
        * 5600 MHz [120] (disabled)
        * 5620 MHz [124] (disabled)
        * 5640 MHz [128] (disabled)
        * 5660 MHz [132] (disabled)
        * 5680 MHz [136] (disabled)
        * 5700 MHz [140] (disabled)
        * 5720 MHz [144] (disabled)
        * 5745 MHz [149] 
          Maximum TX power: 20.0 dBm
          Channel widths: 20MHz HT40+ VHT80
        * 5765 MHz [153] 
          Maximum TX power: 20.0 dBm
          Channel widths: 20MHz HT40- VHT80
        * 5785 MHz [157] 
          Maximum TX power: 20.0 dBm
          Channel widths: 20MHz HT40+ VHT80
        * 5805 MHz [161] 
          Maximum TX power: 20.0 dBm
          Channel widths: 20MHz HT40- VHT80
        * 5825 MHz [165] 
          Maximum TX power: 20.0 dBm
          Channel widths: 20MHz
17.01.2017394Base systemBug ReportVery LowLowPPPoE/802.1Q issues on Linksys WRT1900ACSTrunkUnconfirmed Task Description

Device: Linksys WRT1900ACS
LEDE commit: b9a408c2b49ccfa0e906bda00ef77f4002e401fd

diffconfig:
CONFIG_TARGET_mvebu=y
CONFIG_TARGET_mvebu_DEVICE_linksys-wrt1900acs=y
CONFIG_TARGET_BOARD=”mvebu” CONFIG_LIBSODIUM_MINIMAL=y
CONFIG_PACKAGE_dnscrypt-proxy=y
CONFIG_PACKAGE_dnscrypt-proxy-resolvers=y
CONFIG_PACKAGE_libsodium=y

I have an ISP that requires PPPoE on vlan 201 with 802.1Q tags (CenturyLink fiber). On OpenWRT 15.05.1 and on earlier versions of LEDE (not sure about an exact revision, but maybe October/November timeframe) I could simply define my wan interface in /etc/config/network like this and it just worked:

```
config interface ‘wan’

  option ifname 'eth0.201'
  option proto 'pppoe'
  option username 'user@provider'
  option password 'password'

```

I can’t find any way to make this work on recent versions of LEDE. I’ve tried new builds at least every few weeks, but none have worked for the past few months. I’ve tried configuring the switch_vlan section by adding a ‘t’ after the appropriate switch port to enable tagging, I’ve tried defining a new interface and then using that as the wan ifname, and I’ve tried the command line `ip link` and `ppp` invocations that work on every other linux system I’ve tried, but I can’t find anything that works on recent versions of LEDE.

On other linux systems I can do roughly the following and it works:

```
ip link add link eth0 name eth0.201 type vlan id 201
ip link set eth0.201 up
pppd call centurylink
```

where /etc/ppp/peers/centurylink and /etc/ppp/chap-secrets looks like this:
```
> cat /etc/ppp/peers/centurylink
plugin rp-pppoe.so

eth0.201
name “user@provider” usepeerdns
persist
defaultroute
hide-password
noauth

cat /etc/ppp/chap-secrets
#USERNAME PROVIDER PASSWORD IPADDRESS
user@provider * password
```

I’ve tried using tcpdump to capture what’s happening and on other systems (Ubuntu 16.10, Debian Jessie, pfsense) I see an 802.1Q tag, but I don’t see that on LEDE. That might be expected though because it seems totally possible that the switch itself is doing the 802.1Q stuff and tcpdump doesn’t see the actual packets sent over the wire. I have no idea if that’s the case, though. I guess I could also try this on OpenWRT as well, but I haven’t taken the time to do that yet.

The only other difference I’ve seen is that by default LEDE doesn’t send a Host-Uniq tag, but even if I set the host_uniq uci config it doesn’t fix things. Regardless of what I do I see logs that look like this:

```
Tue Jan 17 01:55:26 2017 daemon.notice netifd: Interface ‘wan’ is now down
Tue Jan 17 01:55:26 2017 daemon.notice netifd: Interface ‘wan’ is disabled
Tue Jan 17 01:55:26 2017 daemon.notice netifd: Interface ‘wan’ has link connectivity loss
Tue Jan 17 01:55:26 2017 kern.info kernel: [23415.581135] mvneta f1034000.ethernet eth0: configuring for fixed link mode
Tue Jan 17 01:55:26 2017 kern.info kernel: [23415.588150] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Tue Jan 17 01:55:26 2017 kern.info kernel: [23415.594095] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Tue Jan 17 01:55:26 2017 daemon.notice netifd: Interface ‘wan’ is enabled
Tue Jan 17 01:55:26 2017 daemon.notice netifd: Network device ‘eth0’ link is up
Tue Jan 17 01:55:26 2017 daemon.notice netifd: VLAN ‘eth0.201’ link is up
Tue Jan 17 01:55:26 2017 daemon.notice netifd: Interface ‘wan’ has link connectivity
Tue Jan 17 01:55:26 2017 daemon.notice netifd: Interface ‘wan’ is setting up now
Tue Jan 17 01:55:26 2017 kern.info kernel: [23415.602431] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Jan 17 01:55:26 2017 daemon.info pppd[2263]: Plugin rp-pppoe.so loaded.
Tue Jan 17 01:55:26 2017 daemon.info pppd[2263]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Tue Jan 17 01:55:26 2017 daemon.notice pppd[2263]: pppd 2.4.7 started by root, uid 0
...
Tue Jan 17 01:55:41 2017 daemon.warn pppd[2263]: Timeout waiting for PADO packets
Tue Jan 17 01:55:41 2017 daemon.err pppd[2263]: Unable to complete PPPoE Discovery
Tue Jan 17 01:55:41 2017 daemon.info pppd[2263]: Exit.
```

A sample /etc/config/network looks like this:
```
config interface ‘loopback’

      option ifname 'lo'
      option proto 'static'
      option ipaddr '127.0.0.1'
      option netmask '255.0.0.0'

config globals ‘globals’

      option ula_prefix 'fd25:2a59:2a7b::/48'

config interface ‘lan’

      option type 'bridge'
      option ifname 'eth1'
      option proto 'static'
      option ipaddr '192.168.2.1'
      option netmask '255.255.255.0'
      option ip6assign '60'

config interface ‘wan’

  option ifname 'eth0.201'
  option proto 'pppoe'
  option username 'user@provider'
  option password 'password'

config switch

      option name 'switch0'
      option reset '1'
      option enable_vlan '1'

config switch_vlan

      option device 'switch0'
      option vlan '1'
      option ports '0 1 2 3 6'

config switch_vlan

      option device 'switch0'
      option vlan '2'
      option ports '4 5'

config interface ‘guest’

      option _orig_ifname 'wlan1'
      option _orig_bridge 'false'
      option proto 'static'
      option ipaddr '192.168.3.1'
      option netmask '255.255.255.0'

```

Interestingly, OpenWRT has exactly the same version of ppp and rp-pppoe (2.4.7 and 3.8p, respectively) so it seems like there’s something else in play and my guess is it’s related to vlan tagging, but I don’t seem to have the same issue as FS#227 which mentions both PPPoE and vlan config, but it is quite difficult to follow the discussion there so maybe I’m missing something.

15.01.2017389Base systemBug ReportVery LowLowodhcpd relay mode is blocked by firewall by defaultTrunkUnconfirmed Task Description

odhcpd currently won’t work when put in relay mode if followed the manual naively. Turns out this is because firewall blocks incoming traffic to DHCPv6 server (port 547) from external DHCPv6 servers (port 547) from WAN zone by default. It may be a good idea to allow this out of the box, though I’m unsure if there are any security complications from this – I’m a newcomer to IPv6. Replies come with the source global IPv6 address of DHCPv6 server to the global IPv6 address of the router, so it’s difficult to make a more constrained rule without hardcoding them or at least the prefix.

Example rule which fixes relay mode:

config rule
	option enabled '1'
	option target 'ACCEPT'
	option src 'wan'
	option proto 'udp'
	option dest_port '547'
	option name 'Allow DHCPv6 Relay'
	option family 'ipv6'
	option src_port '547'

LEDE revision: 3e7b894ac08b56343e6e449a38fdb2be7b02a127

13.01.2017386Base systemBug ReportVery LowLowConfig option "list channels" doesn't workTrunkUnconfirmed Task Description

Hi,

the option “list channels” is not working.

Patch which implements the function: https://patchwork.ozlabs.org/patch/536533/

LEDE version: SNAPSHOT r2790-08d73bf

Device: Archer C5

config wifi-device 'radio0'
	option type 'mac80211'
	option hwmode '11a'
	option path 'pci0000:01/0000:01:00.0'
	option country 'DE'
	option htmode 'VHT80'
	option txpower '12'
	option channel 'auto'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'yyy'
	option encryption 'psk2+ccmp'
	option key 'xxx'
	option disabled '1'

config wifi-device 'radio1'
	option type 'mac80211'
	option hwmode '11g'
	option path 'platform/qca955x_wmac'
	option channel 'auto'
	option country 'DE'
	option txpower '20'
	option htmode 'HT40'
	list channels 13
        list channels 12

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option encryption 'psk2+ccmp'
	option key 'xxx'
	option ssid 'yyy'


Ends with a 2.4GHz wlan which is not
visible and iwinfo shows the following information:

Mode: Master Channel: unknown (2.407 GHz)

root@lede:~# iwinfo wlan1 freqlist
  2.412 GHz (Channel 1)
  2.417 GHz (Channel 2)
  2.422 GHz (Channel 3)
  2.427 GHz (Channel 4)
  2.432 GHz (Channel 5)
  2.437 GHz (Channel 6)
  2.442 GHz (Channel 7)
  2.447 GHz (Channel 8)
  2.452 GHz (Channel 9)
  2.457 GHz (Channel 10)
  2.462 GHz (Channel 11)
  2.467 GHz (Channel 12)
  2.472 GHz (Channel 13)

A part of the syslog with a bunch of error messages is attached.

Fell free to ask, if something is missing.

13.01.2017385Base systemBug ReportVery LowLowrampis / JFFS2-problem / Xiaomi Miwifi mini / r2919 / w...TrunkUnconfirmed Task Description

after flashing r2919 i can see strange message with dmesg:

root@lede:~  dmesg | grep -i jffs
[    0.000000] Kernel command line: console=ttyS0,115200 rootfstype=squashfs,jffs2
[    0.638380] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    9.908794] jffs2: Node at 0x00000044 with length 0x00001044 would run over the end of the erase block
[    9.918337] jffs2: Perhaps the file system was created with the wrong erase size?
[    9.926009] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000048: 0x1044 instead
[    9.935697] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000004c: 0x586d instead
[    9.945403] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000050: 0x0002 instead
[    9.955094] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000054: 0x0002 instead
[    9.964797] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000058: 0x81a4 instead
[    9.974488] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000060: 0xd8a2 instead
[    9.984190] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000064: 0x9ad1 instead
[    9.993881] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000068: 0x9ad2 instead
[   10.003587] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000006c: 0x9ad2 instead
[   10.013278] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000074: 0x1000 instead
[   10.022959] jffs2: Further such events for this erase block will not be printed
[   11.479386] jffs2: notice: (377) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[   11.496420] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[   11.525523] jffs2: Node at 0x00000044 with length 0x00001044 would run over the end of the erase block
[   11.535100] jffs2: Perhaps the file system was created with the wrong erase size?
[   11.542896] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000048: 0x1044 instead
[   11.552600] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000004c: 0x586d instead
[   11.562304] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000050: 0x0002 instead
[   11.571994] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000054: 0x0002 instead
[   11.581696] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000058: 0x81a4 instead
[   11.591387] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000060: 0xd8a2 instead
[   11.601089] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000064: 0x9ad1 instead
[   11.610780] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000068: 0x9ad2 instead
[   11.620481] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000006c: 0x9ad2 instead
[   11.630173] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000074: 0x1000 instead
[   11.639854] jffs2: Further such events for this erase block will not be printed
[   13.095966] jffs2: notice: (374) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[   14.064922] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[   14.086950] mount_root: switching to jffs2 overlay
root@lede:~  

beside that, it seems that the device is working:

root@lede:~  df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 3.5M      3.5M         0 100% /rom
tmpfs                    61.5M      1.1M     60.4M   2% /tmp
/dev/mtdblock6           10.8M    796.0K     10.0M   7% /overlay
overlayfs:/overlay       10.8M    796.0K     10.0M   7% /
tmpfs                   512.0K         0    512.0K   0% /dev
tmpfs                     2.0M         0      2.0M   0% /coredumps
08.01.2017375ToolchainBuild FailureVery LowMediumBulidbots should have multilib support installed to pre...TrunkUnconfirmed Task Description

I’ve run into this earlier myself and now we are seeing at least one package failing because of it.
https://github.com/openwrt/packages/pull/2823

People seem to have run into this issue before since it’s listed as a requirement for Ubuntu 64-bit as an example.
https://wiki.openwrt.org/doc/howto/buildroot.exigence#examples_of_package_installations

12.12.2016331Base systemBug ReportVery LowLowmac80211 / warning / ieee80211_ibss_leave / r2449TrunkUnconfirmed Task Description

spotted on TP-Link 4900 v1 with LEDE r2449 (selfcompiled):

[ 2860.974569] ------------[ cut here ]------------
[ 2860.979191] WARNING: at compat-wireless-2016-10-08/net/mac80211/ibss.c:1082
[ 2860.986142] Modules linked in: ath9k ath9k_common iptable_nat ath9k_hw ath snd_usb_audio nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_id xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda snd_usbmidi_lib nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack macvlan iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables compat em_nbyte sch_dsmark sch_pie sch_codel sch_gred sch_htb em_cmp cls_basic act_ipt sch_red sch_prio em_meta act_police em_text sch_tbf sch_sfq sch_fq act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ipip tunnel4 ip_tunnel tun snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd soundcore nls_utf8 zram lz4_decompress lz4_compress lzo_compress lzo_decompress zsmalloc usb_storage gpio_keys leds_gpio ehci_fsl ehci_platform ehci_hcd scsi_mod fsl_mph_dr_of mbcache button_hotplug input_core usbcore nls_base usb_common crc16 crc32c_generic crypto_hash [last unloaded: sd_mod]
[ 2861.124825] CPU: 0 PID: 8624 Comm: kworker/u2:0 Not tainted 4.4.36 #0
[ 2861.131337] Workqueue: phy1 ieee80211_ibss_leave [mac80211]
[ 2861.136903] task: c783b840 ti: c68a4000 task.ti: c68a4000
[ 2861.142292] NIP: c99ab128 LR: c99ab354 CTR: 00000000
[ 2861.147247] REGS: c68a5b10 TRAP: 0700   Not tainted  (4.4.36)
[ 2861.152982] MSR: 00029000 <CE,EE,ME>  CR: 28072422  XER: 20000000
[ 2861.159082]
[ 2861.159082] GPR00: c99ab004 c68a5bc0 c783b840 00000000 c68a5bf4 00000000 00000001 00000000
[ 2861.159082] GPR08: c724b114 00000001 c99f97f6 00000000 000000ff 00000000 c003c474 c790bfe0
[ 2861.159082] GPR16: c6f0f070 00000fff 00000fff c70b2138 c6ae5800 c6e30b40 00000000 00000087
[ 2861.159082] GPR24: 00000000 c68a5c68 c724b114 00000000 c6e30b40 c6e7a3d8 c6f25420 c6f0f070
[ 2861.188805] NIP [c99ab128] ieee80211_get_vht_mask_from_cap+0x1964/0x1c64 [mac80211]
[ 2861.196468] LR [c99ab354] ieee80211_get_vht_mask_from_cap+0x1b90/0x1c64 [mac80211]
[ 2861.204025] Call Trace:
[ 2861.206481] [c68a5bc0] [c99ab004] ieee80211_get_vht_mask_from_cap+0x1840/0x1c64 [mac80211] (unreliable)
[ 2861.215884] [c68a5c60] [c99ab414] ieee80211_get_vht_mask_from_cap+0x1c50/0x1c64 [mac80211]
[ 2861.224156] [c68a5d30] [c99ab9d0] ieee80211_ibss_rx_queued_mgmt+0x264/0x370 [mac80211]
[ 2861.232081] [c68a5e20] [c99acc44] ieee80211_ibss_leave+0x768/0x1770 [mac80211]
[ 2861.239307] [c68a5e80] [c00379f8] process_one_work+0x208/0x380
[ 2861.245135] [c68a5ea0] [c0037de0] worker_thread+0x270/0x48c
[ 2861.250704] [c68a5ef0] [c003c53c] kthread+0xc8/0xcc
[ 2861.255580] [c68a5f40] [c000cb3c] ret_from_kernel_thread+0x5c/0x64
[ 2861.261752] --- interrupt: 0 at   (null)
[ 2861.261752]     LR =   (null)
[ 2861.268618] Instruction dump:
[ 2861.271578] 38810034 387e0510 7f984800 419e024c 4bf410ed 2f830000 40be0030 3d40c9a0
[ 2861.279336] 394a97f6 3b600001 892a0003 69290001 <0f090000> 2f890000 41be01d0 39200001
[ 2861.287267] ---[ end trace a37b58c3292c2cbf ]---

09.12.2016329Base systemBug ReportVery LowLowAR9341 needs analog switch resetTrunkUnconfirmed Task Description

This is a bug report for the AR9341 SOC on LEDE trunk reboot-2445-gee5a6c1.

I have builded a custom firmware for a unsupported device based on the Atheros DB120 reference board.

The analog port of the ethernet switch needs to be resetted before it can operate.

Part of bootlog without analog reset:

[    2.179262] ag71xx-mdio.1: unknown phy id 'ffff:ffff'

Br-lan is not intialized due no analog switch reset.

Part of bootlog with analog reset:

[    2.059037] ag71xx-mdio.1: Found an AR934X built-in switch

And br-lan is initialized and networking is working fine.

A reset is performed by the function ath79_register_eth (defined in dev-eth.c):

ath79_device_reset_set(AR934X_RESET_ETH_SWITCH);
ath79_device_reset_clear(AR934X_RESET_ETH_SWITCH);

However, no analog reset is performed, for example:

ath79_device_reset_set(AR934X_RESET_ETH_SWITCH);
ath79_device_reset_clear(AR934X_RESET_ETH_SWITCH);

ath79_device_reset_set(AR934X_RESET_ETH_SWITCH_ANALOG);
ath79_device_reset_clear(AR934X_RESET_ETH_SWITCH_ANALOG);

Omitting the analog reset does not break the DB120 builds because the analog reset is already performed by ar934x_nfc_hw_reset in dev-nfc.c.

An easy fix is to do a analog reset in the device’s mach file. However, for the sake of consistency and autism, the reset should be performed by ath79_register_eth in dev_eth.c and not by ar934x_nfc_hw_reset in dev_nfc.c. My AR9341 device doesn’t even use a NAND flash.

03.12.2016320Base systemFeature RequestVery LowLowrelayd feature requestTrunkUnconfirmed Task Description

I found a couple of bugs with relayd based bridge configuration and I would like to suggest a feature request. Will fill one entry per issue:

On today’s trunk

3- in a configuration where the network attached to the wireless radio is configured via DHCP, the listening interface is not set up automatically. DD-WRT and Gargoyle do this automatically ( they overwrite the config/network file with the gateway parameter and reload relayd.

 


Showing tasks 1301 - 1350 of 1367 Page 27 of 28<<First - 24 - 25 - 26 - 27 - 28 -

Available keyboard shortcuts

Tasklist

Task Details

Task Editing