OpenWrt/LEDE Project

Welcome to the OpenWrt/LEDE Project bug reporting and issue tracking system

Problems to be reported here are for the OpenWrt/LEDE Project targets, sources, toolchain, core packages, build procedures, distribution and infrastructure. Guidelines for submitting a good bug report can be found at the OpenWrt/LEDE 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 lede-bugs@infradead.org.

OpenedIDCategoryTask Type  ascPrioritySeveritySummaryReported InStatus
13.07.201650Base systemBug ReportMediumLowNo image or non-verbose output created if image is too ...TrunkNew Task Description

The target/install target does not produce the *squashfs-factory.bin and *squashfs-sysupgrade.bin binaries if the images are too big to fit the selected flash size.
However, make doesn’t say a word to the user but simply does not produce the files. The user has to either check the mtime of the files if they were created earlier or use

make target/install V=s

to derive what’s wrong.
According to jow on IRC this is just an artifact of no way to bypass silent mode. That might be the common explanation but it is still a bug from my POV.

16.08.201694Base systemBug ReportVery LowMediumnetifd: PPPoE MTU problemTrunkNew Task Description

When you set the MTU of a ppp interface with proto=pppoe and ifname=nas0 via the mtu option,
the configured mtu will not be set on the ppp interface (what you want), but on the
underlying interface named by ifname (what you normally don’t want to change).

This leeds to log messages like this:


pppd[5641]: Interface nas0 has MTU of 1448 – should be at least 1500.


and MTUs other than what you really want.

example:


desired PPPoE MTU: 1448
actual nas0 MTU: 1448
actual PPPoE MTU: 1440

This issue seems to be related to the commit 7ac29b75319fd69a8a7c0aeea7804d381ec07d3d of netifd.

Regards,
Martin

17.08.201697Base systemBug ReportMediumLowdnsmasq doesn't receive updated dns servers when runnin...TrunkNew Task Description

Bind-mounting /tmp/resolv.conf.auto apparently doesn’t forward inotify events arriving from the kernel when resolv.conf.auto was changed (e.g. upstream DNS servers were received by a DHCP client or pppd). Restarting dnsmasq or running it without ujail solves the issue.

24.08.2016115Base systemBug ReportVery LowMediumWWAN-connections using 3g with HUAWEI ME909u-521 unstab...TrunkUnconfirmed Task Description

Actually, I am trying to stabilize wwan (3g actually; LTE later on) using pppd with my HUAWEI ME909u-521,
because either my MT7620-based router locks up during boot already; or after short period of real usage.
During night, when router is almost idle, just some watchdog date sent via wwan, no problem.

First trace of a possible problem was this msg in logread:
daemon.notice netifd: wwan (1676): Error setting WWAN mode!

Wich is expected, as in /lib/netifd/proto/3g.sh:

...

                      elif echo "$cardinfo" | grep -qi huawei; then
                              case "$service" in
                                      umts_only) CODE="14,2";;
                                      gprs_only) CODE="13,1";;
                                      *) CODE="2,2";;
                              esac
                              export MODE="AT^SYSCFG=${CODE},3FFFFFFF,2,4"    #####Will not work !!!!! Switching USB-Stick to 3g-preferred ?

...
...

                      [ -n "$MODE" ] && gcom -d "$device" -s /etc/gcom/setmode.gcom

Will not work, because the ME909u-521 rejects AT^SYSCFG . However, AT^SYSCFGEX will work, but having different syntax.
MODE=”AT^SYSCFG=${CODE},3FFFFFFF,2,4” will be effective for simpler modems.

/etc/gcom/setmode.gcom returns exit 1; but this error is not checked in 3g.sh

Not shure, whether this is the reason for my problems; however, reason of concern, as high speed modems
are more and more common.
Willing to participate in testing/debugging.

For details regarding my modem, consult
HUAWEI ME909u-521 LTE LGA Module AT Command Interface Specification
http://www.paoli.cz/out/media/HUAWEI_ME909u-521_LTE_LGA_Module_AT_Command_Interface_Specification-V100R001_02.pdf

02.09.2016133Base systemBug ReportVery LowLowNetgear r8000 cannot use 802.1x encryptionTrunkUnconfirmed Task Description

Github issue #305 reported by https://github.com/Halry

My android phone can’t connect to it.(tested on nexus 6p and samsung s7 edge)
Sun Aug 28 16:28:46 2016 daemon.debug hostapd: wlan2: STA 94:fe:22:11:22:33 IEEE 802.1X: Sending EAP Packet (identifier 247)
Sun Aug 28 16:28:46 2016 daemon.debug hostapd: wlan2: STA 94:fe:22:11:22:33 WPA: sending 1/4 msg of 4-Way Handshake
Sun Aug 28 16:28:46 2016 daemon.debug hostapd: wlan2: STA 94:fe:22:11:22:33 WPA: received EAPOL-Key frame (2/4 Pairwise)
Sun Aug 28 16:28:46 2016 daemon.debug hostapd: wlan2: STA 94:fe:22:11:22:33 WPA: sending 3/4 msg of 4-Way Handshake
Sun Aug 28 16:28:46 2016 daemon.info hostapd: wlan2: STA 94:fe:22:11:22:33 IEEE 802.11: disassociated
Sun Aug 28 16:28:46 2016 daemon.debug hostapd: wlan2: STA 94:fe:22:11:22:33 WPA: event 2 notification
Sun Aug 28 16:29:00 2016 daemon.info hostapd: wlan1: STA 94:fe:22:11:22:33 IEEE 802.11: associated
Sun Aug 28 16:29:00 2016 daemon.info hostapd: wlan1: STA 94:fe:22:11:22:33 IEEE 802.11: disassociated
Sun Aug 28 16:29:11 2016 daemon.info hostapd: wlan1: STA 94:fe:22:11:22:33 IEEE 802.11: associated
Sun Aug 28 16:29:11 2016 daemon.info hostapd: wlan1: STA 94:fe:22:11:22:33 IEEE 802.11: disassociated

However,Windows can connect to it.

Here are some my nexus 6p’s dmesg:
CFG80211-ERROR wl_cfg80211_disconnect:Reason 17

05.09.2016160Base systemBug ReportVery LowLowusb-serial (pl2303) failures on mt7621 dlink dir860l-b1TrunkUnconfirmed Task Description
git describe
reboot-1497-ga810e77

with diffconfig:

CONFIG_TARGET_ramips=y
CONFIG_TARGET_ramips_mt7621=y
CONFIG_TARGET_ramips_mt7621_DEVICE_dir-860l-b1=y
CONFIG_DEVEL=y
CONFIG_BUILD_LOG=y
CONFIG_PACKAGE_ip=y
CONFIG_PACKAGE_kmod-usb-core=y
CONFIG_PACKAGE_kmod-usb-ohci=y
CONFIG_PACKAGE_kmod-usb-ohci-pci=y
CONFIG_PACKAGE_kmod-usb-serial=y
CONFIG_PACKAGE_kmod-usb-serial-ftdi=y
CONFIG_PACKAGE_kmod-usb-serial-pl2303=y
CONFIG_PACKAGE_kmod-usb2=y
CONFIG_PACKAGE_kmod-usb2-pci=y
CONFIG_PACKAGE_kmod-usb3=y
CONFIG_PACKAGE_screen=y

screen starts, but doesn’t work. The usb-relevant dmesg’s are:

[    4.550000] usbcore: registered new interface driver usbfs
[    4.560000] usbcore: registered new interface driver hub
[    4.570000] usbcore: registered new device driver usb
[    4.580000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.620000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.670000] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 1
[    4.720000] hub 1-0:1.0: USB hub found
[    4.740000] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 2
[    4.760000] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.770000] hub 2-0:1.0: USB hub found
[    5.260000] usb 1-1: new full-speed USB device number 2 using xhci-mtk
[    5.410000] usb 1-1: no of_node; not parsing pinctrl DT
[   10.150000] usbcore: registered new interface driver usbserial
[   10.160000] usbcore: registered new interface driver usbserial_generic
[   10.180000] usbserial: USB Serial support registered for generic
[   10.220000] usbcore: registered new interface driver ftdi_sio
[   10.240000] usbserial: USB Serial support registered for FTDI USB Serial Device
[   10.260000] usbcore: registered new interface driver pl2303
[   10.270000] usbserial: USB Serial support registered for pl2303
[   10.290000] pl2303 ttyUSB0: no of_node; not parsing pinctrl DT
[   10.290000] usb 1-1: pl2303 converter now attached to ttyUSB0
[  871.510000] pl2303 ttyUSB0: pl2303_get_line_request - failed: -145
[  871.620000] pl2303 ttyUSB0: pl2303_set_line_request - failed: -145
[  871.840000] pl2303 ttyUSB0: pl2303_set_control_lines - failed: -145

Screen also throws an error (which gets blanked out, but is captured by the serial console):

# screen /dev/ttyUSB0 115200
/dev/null/utmp: Not a directory
07.09.2016162Base systemBug ReportVery LowLowTwo issues with libuclient-openssl in luci-sslTrunkUnconfirmed Task Description

1: RC4 and 3DES are used when both have security issues. Actually the latter also is true of mbedtls/polarssl.

2: Only TLS 1.2 is supported. This makes multiple clients unable to connect.

BTW, I got this working after modifying the Makefile to luci-ssl to depend on libustream-openssl instead. No idea what the situation is but so far it works without a problem.

17.09.2016181Base systemBug ReportVery LowMediumChanging TX power doesn't nothing (MediaTek MT7628AN ve...TrunkUnconfirmed Task Description

Hello,

As I said, if I change the TX power from 0 dBm to 20 dBm doesn’t nothing. There isn’t any visible change in tx power. I tested other powers too (5, 8, 15,..).

It is a Xiaomi Nano (lite).

SoC Type: MediaTek MT7628AN ver:1 eco:2
MIPS: machine is MiWiFi Nano
Linux version 4.4.19 (-) (gcc version 5.4.0 (LEDE GCC 5.4.0 r1444) ) #0 Fri Aug 26 15:03:40 2016.

13.10.2016224Base systemBug ReportVery LowLowwrong source IP when logging to remote IPv6 syslog serv...TrunkAssigned Task Description

Hello,

I’m trying to send log to remote IPv6 syslog server (x:y:z:12::1), but packets received by syslog server are invalid. Instead of public IPv6 address, syslog udp packets are sent with ::1 source IP and therefore ignored by destination server. Logging over IPv4 works ok.

tcpdump log from destination syslog server:
23:34:16.988433 IP6 ::1.38044 > x:y:z:12::1.514: SYSLOG daemon.notice, length: 65

Configuration:

/etc/config/system:

 option log_ip 'x:y:z:12::1'

Device is in the same range as syslog server (x:y:z:12::119/64) and has native IPv6 connectivity. Other services (dropbear, ntp client, snmpd, luci) are running fine over IPv6.

Device is TP-Link WDR3600, running lede reboot-1818-gb81fc29.

14.10.2016227Base systemBug ReportMediumHighVLAN support mismatch between preinit and default netwo...TrunkResearching Task Description

PPPoE is broken on WRT1900ACS

Upgraded from Lede r578 to latest Lede r1814 and PPPOE doesn’t work anymore altough the pppd version and PPPoE version are the same:
- Linksys WRT1900ACS
- LEDE reboot r1814

pppd debug log:

Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Timeout waiting for PADO packets
Unable to complete PPPoE Discovery
Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]

While on the same hardware running LEDE r578, the PPPoE module works as expected:

Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Recv PPPOE Discovery V1T1 PADO session 0×0 length 40
dst c2:56:27:ca:d7:d4 src a0:f3:e4:34:d8:21
[service-name] [AC-name acc-aln1.hac] [AC-cookie 75 58 37 a5 ba 3c e4 a5 2a 61 bb 23 92 5c 1b dc]
Send PPPOE Discovery V1T1 PADR session 0×0 length 24
dst a0:f3:e4:34:d8:21 src c2:56:27:ca:d7:d4
[service-name] [AC-cookie 75 58 37 a5 ba 3c e4 a5 2a 61 bb 23 92 5c 1b dc]
Recv PPPOE Discovery V1T1 PADS session 0x30b length 4
dst c2:56:27:ca:d7:d4 src a0:f3:e4:34:d8:21
[service-name]
PADS: Service-Name: ‘’ PPP session is 779
Connected to a0:f3:e4:34:d8:21 via interface eth0
using channel 2
Using interface pppoe-wan
Connect: pppoe-wan ←→ eth0
sent [LCP ConfReq id=0×1 <mru 1492> <magic 0xc6952556>]
rcvd [LCP ConfReq id=0×66 <mru 1492> <auth chap MD5> <magic 0x4cc73648>]
sent [LCP ConfAck id=0×66 <mru 1492> <auth chap MD5> <magic 0x4cc73648>]
rcvd [LCP ConfAck id=0×1 <mru 1492> <magic 0xc6952556>]
sent [LCP EchoReq id=0×0 magic=0xc6952556]
rcvd [CHAP Challenge id=0×1 <7131a44524d1de8f1cd1061cac6d8c071d8bfe7351bc4ea7bd08f56684428475f229ba177a192696ebab32>, name = “acc-aln1.hac”]
sent [CHAP Response id=0×1 <4bb1a418b298790b128ad4d7ef3109ad>, name = “bthomehub@btbroadband.com”]
rcvd [LCP EchoRep id=0×0 magic=0x4cc73648]
rcvd [CHAP Success id=0×1 “CHAP authentication success”]
CHAP authentication succeeded: CHAP authentication success
CHAP authentication succeeded
peer from calling number A0:F3:E4:34:D8:21 authorized
sent [IPCP ConfReq id=0×1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
sent [IPV6CP ConfReq id=0×1 <addr fe80::c595:37d1:3987:1929>]
rcvd [IPV6CP ConfReq id=0x7b <addr fe80::0221:05ff:feb4:8824>]
sent [IPV6CP ConfAck id=0x7b <addr fe80::0221:05ff:feb4:8824>]
rcvd [IPCP ConfReq id=0×38 <addr 172.16.12.12>]
sent [IPCP ConfAck id=0×38 <addr 172.16.12.12>]
rcvd [IPCP ConfNak id=0×1 <addr 81.146.2.155> <ms-dns1 81.139.57.100> <ms-dns2 81.139.56.100>]
sent [IPCP ConfReq id=0×2 <addr 81.146.2.155> <ms-dns1 81.139.57.100> <ms-dns2 81.139.56.100>]
rcvd [IPV6CP ConfAck id=0×1 <addr fe80::c595:37d1:3987:1929>]
local LL address fe80::c595:37d1:3987:1929
remote LL address fe80::0221:05ff:feb4:8824
Script /lib/netifd/ppp-up started (pid 2646)
rcvd [IPCP ConfAck id=0×2 <addr 81.146.2.155> <ms-dns1 81.139.57.100> <ms-dns2 81.139.56.100>]
local IP address 81.146.2.155
remote IP address 172.16.12.12
primary DNS address 81.139.57.100
secondary DNS address 81.139.56.100
ppp.log
secondary DNS address 81.139.56.100
Script /lib/netifd/ppp-up started (pid 2653)
Script /lib/netifd/ppp-up finished (pid 2646), status = 0×9 Script /lib/netifd/ppp-up finished (pid 2653), status = 0×9

27.10.2016253Base systemBug ReportVery LowHighMulticast over wireless ceases to work properly after a...AllNew Task Description

I am having a problem on a UBNT UAP-LR where, if many clients stay connected the router for a long time, multicast packets will stop being reliably sent to the wireless clients. I can reproduce this with LEDE r1953, but it goes back at least as far as OpenWRT 15.05.1 with kernel 3.18. I can not, however, reproduce it on another network with the same WAP but with only one or two wireless clients.

This originally manifested as IPv6 ceasing to work since the (multicasted) RA packets were not reaching the wireless clients. I used tcpdump on the WAP and determined that the RAs were arriving through the wired interface and leaving through the wireless interface as they should, but tcpdump on the client indicates that a vast majority of the RAs are never received. (Please note that the IPv6 issue is not reproducible with the router running OpenWRT/LEDE and odhcpd, since odhcpd unicasts RAs sent as a response to an RS instead of multicasting them, while it is reproducible when the router is running radvd, for example as pfSense does.)

21.11.2016296Base systemBug ReportVery LowHighUbiquiti Bullet M 10/100 ethernet interface comes up as...TrunkUnconfirmed Task Description

For the last month or so, and persisting in r2248, when a Ubiquiti Bullet M is booted through typical Ubiquiti 10/100 passive PoE injector, the interface appears to come up in gigabit mode (see timestamp 18.990274 below), despite being only a 10/100 Mbps interface. Restarting /etc/init.d/network fixes it. I am running batman-adv over the ethernet interface, which may be involved. I will check if it happens when batman-adv is not used on the interface and report in a followup comment.

The dmesg look like this:

[    0.000000] Linux version 4.4.32 (openwrt@hawg) (gcc version 5.4.0 (LEDE GCC 5.4.0 r1439) ) #0 Mon Nov 21 07:14:51 2016
[    0.000000] MyLoader: sysp=00030800, boardp=088201a0, parts=fdeffeff
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019374 (MIPS 24Kc)
[    0.000000] SoC: Atheros AR7240 rev 2
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] No valid device tree found, continuing without
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] On node 0 totalpages: 8192
[    0.000000] free_area_init_node: node 0, pgdat 80412320, node_mem_map 81000000
[    0.000000]   Normal zone: 64 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 8192 pages, LIFO batch:0
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line:  board=UBNT-BM mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,7552k(firmware),256k(cfg)ro,64k(EEPROM)ro console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 27616K/32768K available (2990K kernel code, 174K rwdata, 756K rodata, 296K init, 198K bss, 5152K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:51
[    0.000000] Clocks: CPU:390.000MHz, DDR:390.000MHz, AHB:195.000MHz, Ref:40.000MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9801335621 ns
[    0.000013] sched_clock: 32 bits at 195MHz, resolution 5ns, wraps every 11012737021ns
[    0.007858] Calibrating delay loop... 259.27 BogoMIPS (lpj=1296384)
[    0.080537] pid_max: default: 32768 minimum: 301
[    0.085319] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091915] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.102739] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.113516] NET: Registered protocol family 16
[    0.120053] MIPS: machine is Ubiquiti Bullet M
[    0.126714] registering PCI controller with io_map_base unset
[    0.357171] PCI host bridge to bus 0000:00
[    0.361273] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
[    0.368174] pci_bus 0000:00: root bus resource [io  0x0000]
[    0.373719] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.380486] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.388422] pci 0000:00:00.0: [168c:002a] type 00 class 0x028000
[    0.388466] pci 0000:00:00.0: fixup device configuration
[    0.395018] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit]
[    0.395154] pci 0000:00:00.0: supports D1
[    0.395179] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    0.395521] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
[    0.395573] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1000ffff 64bit]
[    0.402864] pci 0000:00:00.0: using irq 40 for pin 1
[    0.408959] clocksource: Switched to clocksource MIPS
[    0.415845] NET: Registered protocol family 2
[    0.421435] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.428393] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.434796] TCP: Hash tables configured (established 1024 bind 1024)
[    0.441291] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.447126] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.453786] NET: Registered protocol family 1
[    0.458221] PCI: CLS 0 bytes, default 32
[    0.464223] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.470512] Crashlog allocated RAM at address 0x1f00000
[    0.495166] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.501050] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.514332] io scheduler noop registered
[    0.518252] io scheduler deadline registered (default)
[    0.523724] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[    0.530709] console [ttyS0] disabled
[    0.554342] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 12187500) is a 16550A
[    0.563020] console [ttyS0] enabled
[    0.570030] bootconsole [early0] disabled
[    0.582486] m25p80 spi0.0: found mx25l6405d, expected m25p80
[    0.588201] m25p80 spi0.0: mx25l6405d (8192 Kbytes)
[    0.593207] 5 cmdlinepart partitions found on MTD device spi0.0
[    0.599160] Creating 5 MTD partitions on "spi0.0":
[    0.603978] 0x000000000000-0x000000040000 : "u-boot"
[    0.611975] 0x000000040000-0x000000050000 : "u-boot-env"
[    0.619659] 0x000000050000-0x0000007b0000 : "firmware"
[    0.638850] 2 uimage-fw partitions found on MTD device firmware
[    0.644866] 0x000000050000-0x0000001a0000 : "kernel"
[    0.651748] 0x0000001a0000-0x0000007b0000 : "rootfs"
[    0.658927] mtd: device 4 (rootfs) set to be root filesystem
[    0.664753] 1 squashfs-split partitions found on MTD device rootfs
[    0.671002] 0x000000550000-0x0000007b0000 : "rootfs_data"
[    0.678725] 0x0000007b0000-0x0000007f0000 : "cfg"
[    0.685799] 0x0000007f0000-0x000000800000 : "EEPROM"
[    0.713743] libphy: ag71xx_mdio: probed
[    1.302694] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:04 [uid=004dd041, driver=Generic PHY]
[    1.312905] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    1.322158] NET: Registered protocol family 10
[    1.332118] NET: Registered protocol family 17
[    1.336691] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    1.349583] 8021q: 802.1Q VLAN Support v1.8
[    1.362372] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[    1.372025] Freeing unused kernel memory: 296K (80436000 - 80480000)
[    2.887723] init: Console is alive
[    2.891524] init: - watchdog -
[    4.278153] usbcore: registered new interface driver usbfs
[    4.283867] usbcore: registered new interface driver hub
[    4.289377] usbcore: registered new device driver usb
[    4.301662] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.310384] ehci-platform: EHCI generic platform driver
[    4.319460] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.327414] ohci-platform: OHCI generic platform driver
[    4.336259] init: - preinit -
[    5.148878] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    5.181862] random: procd: uninitialized urandom read (4 bytes read, 8 bits of entropy available)
[    7.440590] eth0: link up (100Mbps/Full duplex)
[    7.445184] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    8.484066] jffs2: notice: (361) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[    8.501955] mount_root: switching to jffs2 overlay
[    8.517794] urandom-seed: Seeding with /etc/urandom.seed
[    8.794632] eth0: link down
[    8.814035] procd: - early -
[    8.817063] procd: - watchdog -
[    9.492101] procd: - ubus -
[    9.545805] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.555498] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.564637] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.574254] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.583375] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.593373] random: ubusd: uninitialized urandom read (4 bytes read, 16 bits of entropy available)
[    9.602738] random: ubusd: uninitialized urandom read (4 bytes read, 16 bits of entropy available)
[    9.612394] procd: - init -
[   10.066368] Loading modules backported from Linux version wt-2016-10-03-1-g6fcb1a6
[   10.074041] Backport generated by backports.git backports-20160324-9-g0e38f5c
[   10.125220] batman_adv: B.A.T.M.A.N. advanced 2016.4 (compatibility version 15) loaded
[   10.213939] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
[   10.224958] ath: phy0: Ignoring endianness difference in EEPROM magic bytes.
[   10.233630] ath: EEPROM regdomain: 0x0
[   10.233647] ath: EEPROM indicates default country code should be used
[   10.233661] ath: doing EEPROM country->regdmn map search
[   10.233689] ath: country maps to regdmn code: 0x3a
[   10.233705] ath: Country alpha2 being used: US
[   10.233718] ath: Regpair used: 0x3a
[   10.248634] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   10.257391] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xb0000000, irq=40
[   11.870351] random: jshn: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
[   12.001559] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
[   18.855427] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   18.875510] IPv6: ADDRCONF(NETDEV_UP): br-pub: link is not ready
[   18.990274] eth0: link up (1000Mbps/Full duplex)
[   18.994964] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   19.330349] batman_adv: bat0: Adding interface: eth0
[   19.335365] batman_adv: bat0: The MTU of interface eth0 is too small (1500) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the
 performance. Setting the MTU to 1532 would solve the problem.
[   19.359419] batman_adv: bat0: Interface activated: eth0
[   19.367077] 8021q: adding VLAN 0 to HW filter on device bat0
[   19.406417] device bat0 entered promiscuous mode
[   19.411309] br-pub: port 1(bat0) entered forwarding state
[   19.416772] br-pub: port 1(bat0) entered forwarding state
[   19.422579] IPv6: ADDRCONF(NETDEV_CHANGE): br-pub: link becomes ready
[   19.870508] batman_adv: bat0: bridge_loop_avoidance: Changing from: enabled to: disabled
[   20.359133] batman_adv: bat0: No IGMP Querier present - multicast optimizations disabled
[   20.367269] batman_adv: bat0: No MLD Querier present - multicast optimizations disabled
[   21.412169] br-pub: port 1(bat0) entered forwarding state
[   21.549966] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   21.563679] device wlan0 entered promiscuous mode
[   21.591315] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   21.597879] br-pub: port 2(wlan0) entered forwarding state
[   21.603541] br-pub: port 2(wlan0) entered forwarding state
[   21.784924] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
[   21.912131] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
[   22.268273] batman_adv: bat0: Adding interface: mesh0
[   22.273432] batman_adv: bat0: Interface activated: mesh0
[   23.599046] br-pub: port 2(wlan0) entered forwarding state
[   29.369162] batman_adv: bat0: IGMP Querier appeared
[   29.374093] batman_adv: bat0: MLD Querier appeared
[   34.068975] ------------[ cut here ]------------
[   34.073700] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:306 dev_watchdog+0x1dc/0x260()
[   34.082197] NETDEV WATCHDOG: eth0 (ag71xx): transmit queue 0 timed out
[   34.088754] Modules linked in: ath9k ath9k_common mac80211 ath9k_hw ath batman_adv libcrc32c cfg80211 compat ohci_platform ohci_hcd ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common crc16
 cryptomgr aead crypto_null crc32c_generic crypto_hash
[   34.112252] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.32 #0
[   34.118013] Stack : 803c8fc4 00000000 00000001 80420000 80413038 80412cc3 803aa67c 00000000
[   34.118013] 	  8048379c 8041135c 00000200 00100000 0000000a 800a71a8 803afce8 80410000
[   34.118013] 	  00000003 8041135c 803ae0f4 8040dc2c 0000000a 800a5124 00000006 00000000
[   34.118013] 	  00000000 801f3100 00000000 00000000 00000000 00000000 00000000 00000000
[   34.118013] 	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   34.118013] 	  ...
[   34.153969] Call Trace:
[   34.156440] [<80071af0>] show_stack+0x50/0x84
[   34.160843] [<80081870>] warn_slowpath_common+0xa0/0xd0
[   34.166096] [<800818cc>] warn_slowpath_fmt+0x2c/0x38
[   34.171111] [<80290970>] dev_watchdog+0x1dc/0x260
[   34.175854] [<800b0460>] call_timer_fn.isra.5+0x24/0x80
[   34.181125] [<800b06e4>] run_timer_softirq+0x1b4/0x1fc
[   34.186296] [<80083dec>] __do_softirq+0x250/0x298
[   34.191059] [<8006a5d0>] plat_irq_dispatch+0xd4/0x10c
[   34.196134] [<80060830>] ret_from_irq+0x0/0x4
[   34.200526] [<80060a80>] __r4k_wait+0x20/0x40
[   34.204906] [<800a2304>] cpu_startup_entry+0x9c/0xe8
[   34.209934] [<80436bd4>] start_kernel+0x470/0x490
[   34.214656] 
[   34.216159] ---[ end trace ef06a4b3ec78272a ]---
[   34.220810] eth0: tx timeout
[   37.565193] random: nonblocking pool is initialized
[   44.068999] eth0: tx timeout
[   54.069064] eth0: tx timeout
[   64.068993] eth0: tx timeout
[   74.069871] eth0: tx timeout
[   82.660973] batman_adv: bat0: MLD Querier disappeared - multicast optimizations disabled
[   84.070901] eth0: tx timeout
[   92.701961] batman_adv: bat0: MLD Querier appeared
[   94.071717] eth0: tx timeout
[  104.072355] eth0: tx timeout
[  114.072669] eth0: tx timeout
[...]

When I do an /etc/init.d/network restart, the interface recovers to normal function, and I get this in dmesg:

[ 1296.763793] br-pub: port 2(wlan0) entered disabled state
[ 1296.769232] br-pub: port 1(bat0) entered disabled state
[ 1296.808305] device bat0 left promiscuous mode
[ 1296.812986] br-pub: port 1(bat0) entered disabled state
[ 1296.862085] IPv6: ADDRCONF(NETDEV_UP): bat0: link is not ready
[ 1296.879239] device wlan0 left promiscuous mode
[ 1296.883945] br-pub: port 2(wlan0) entered disabled state
[ 1296.904196] batman_adv: bat0: Interface deactivated: mesh0
[ 1296.909752] batman_adv: bat0: Removing interface: mesh0
[ 1296.963462] batman_adv: bat0: Interface deactivated: eth0
[ 1296.993492] eth0: link down
[ 1296.998705] batman_adv: bat0: Removing interface: eth0
[ 1301.629484] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1301.649941] IPv6: ADDRCONF(NETDEV_UP): br-pub: link is not ready
[ 1301.985100] eth0: link up (100Mbps/Full duplex)
[ 1301.989698] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1302.191373] batman_adv: bat0: Adding interface: eth0
[ 1302.196453] batman_adv: bat0: The MTU of interface eth0 is too small (1500) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the
 performance. Setting the MTU to 1532 would solve the problem.
[ 1302.220488] batman_adv: bat0: Interface activated: eth0
[ 1302.228092] 8021q: adding VLAN 0 to HW filter on device bat0
[ 1302.275944] device bat0 entered promiscuous mode
[ 1302.280747] br-pub: port 1(bat0) entered forwarding state
[ 1302.286292] br-pub: port 1(bat0) entered forwarding state
[ 1302.292106] IPv6: ADDRCONF(NETDEV_CHANGE): br-pub: link becomes ready
[ 1302.590333] batman_adv: bat0: bridge_loop_avoidance: Changing from: enabled to: disabled
[ 1303.213417] batman_adv: bat0: No IGMP Querier present - multicast optimizations disabled
[ 1303.221556] batman_adv: bat0: No MLD Querier present - multicast optimizations disabled
[ 1304.283452] br-pub: port 1(bat0) entered forwarding state
[ 1304.672382] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1304.782643] device wlan0 entered promiscuous mode
[ 1304.827845] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1304.834479] br-pub: port 2(wlan0) entered forwarding state
[ 1304.840053] br-pub: port 2(wlan0) entered forwarding state
[ 1305.112607] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
[ 1305.190600] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
[ 1305.692918] batman_adv: bat0: Adding interface: mesh0
[ 1305.698080] batman_adv: bat0: Interface activated: mesh0
[ 1306.833410] br-pub: port 2(wlan0) entered forwarding state
[ 1312.303688] batman_adv: bat0: IGMP Querier appeared
[ 1312.308629] batman_adv: bat0: MLD Querier appeared

If I disconnect the other end of the ethernet cable so that there is no link peer, I do not see the problem (see below):

[    0.000000] Linux version 4.4.32 (openwrt@hawg) (gcc version 5.4.0 (LEDE GCC 5.4.0 r1439) ) #0 Mon Nov 21 07:14:51 2016
[    0.000000] MyLoader: sysp=00000000, boardp=00000000, parts=ffffffff
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019374 (MIPS 24Kc)
[    0.000000] SoC: Atheros AR7240 rev 2
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] No valid device tree found, continuing without
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] On node 0 totalpages: 8192
[    0.000000] free_area_init_node: node 0, pgdat 80412320, node_mem_map 81000000
[    0.000000]   Normal zone: 64 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 8192 pages, LIFO batch:0
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line:  board=UBNT-BM mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,7552k(firmware),256k(cfg)ro,64k(EEPROM)ro console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 27616K/32768K available (2990K kernel code, 174K rwdata, 756K rodata, 296K init, 198K bss, 5152K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:51
[    0.000000] Clocks: CPU:390.000MHz, DDR:390.000MHz, AHB:195.000MHz, Ref:40.000MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9801335621 ns
[    0.000013] sched_clock: 32 bits at 195MHz, resolution 5ns, wraps every 11012737021ns
[    0.007859] Calibrating delay loop... 259.27 BogoMIPS (lpj=1296384)
[    0.080537] pid_max: default: 32768 minimum: 301
[    0.085319] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091915] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.102743] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.113517] NET: Registered protocol family 16
[    0.120061] MIPS: machine is Ubiquiti Bullet M
[    0.126721] registering PCI controller with io_map_base unset
[    0.357179] PCI host bridge to bus 0000:00
[    0.361281] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
[    0.368182] pci_bus 0000:00: root bus resource [io  0x0000]
[    0.373728] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.380495] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.388431] pci 0000:00:00.0: [168c:002a] type 00 class 0x028000
[    0.388474] pci 0000:00:00.0: fixup device configuration
[    0.395026] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit]
[    0.395163] pci 0000:00:00.0: supports D1
[    0.395187] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    0.395530] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
[    0.395581] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1000ffff 64bit]
[    0.402872] pci 0000:00:00.0: using irq 40 for pin 1
[    0.408968] clocksource: Switched to clocksource MIPS
[    0.415854] NET: Registered protocol family 2
[    0.421444] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.428402] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.434805] TCP: Hash tables configured (established 1024 bind 1024)
[    0.441299] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.447134] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.453795] NET: Registered protocol family 1
[    0.458229] PCI: CLS 0 bytes, default 32
[    0.464231] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.470521] Crashlog allocated RAM at address 0x1f00000
[    0.495175] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.501058] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.514341] io scheduler noop registered
[    0.518261] io scheduler deadline registered (default)
[    0.523733] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[    0.530718] console [ttyS0] disabled
[    0.554351] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 12187500) is a 16550A
[    0.563030] console [ttyS0] enabled
[    0.570040] bootconsole [early0] disabled
[    0.582496] m25p80 spi0.0: found mx25l6405d, expected m25p80
[    0.588212] m25p80 spi0.0: mx25l6405d (8192 Kbytes)
[    0.593216] 5 cmdlinepart partitions found on MTD device spi0.0
[    0.599171] Creating 5 MTD partitions on "spi0.0":
[    0.603989] 0x000000000000-0x000000040000 : "u-boot"
[    0.611984] 0x000000040000-0x000000050000 : "u-boot-env"
[    0.619662] 0x000000050000-0x0000007b0000 : "firmware"
[    0.638852] 2 uimage-fw partitions found on MTD device firmware
[    0.644868] 0x000000050000-0x0000001a0000 : "kernel"
[    0.651750] 0x0000001a0000-0x0000007b0000 : "rootfs"
[    0.658926] mtd: device 4 (rootfs) set to be root filesystem
[    0.664753] 1 squashfs-split partitions found on MTD device rootfs
[    0.671004] 0x000000550000-0x0000007b0000 : "rootfs_data"
[    0.678725] 0x0000007b0000-0x0000007f0000 : "cfg"
[    0.685800] 0x0000007f0000-0x000000800000 : "EEPROM"
[    0.713752] libphy: ag71xx_mdio: probed
[    1.302703] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:04 [uid=004dd041, driver=Generic PHY]
[    1.312917] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    1.322177] NET: Registered protocol family 10
[    1.332146] NET: Registered protocol family 17
[    1.336720] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    1.349611] 8021q: 802.1Q VLAN Support v1.8
[    1.362390] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[    1.372040] Freeing unused kernel memory: 296K (80436000 - 80480000)
[    2.887726] init: Console is alive
[    2.891520] init: - watchdog -
[    4.278086] usbcore: registered new interface driver usbfs
[    4.283799] usbcore: registered new interface driver hub
[    4.289318] usbcore: registered new device driver usb
[    4.301475] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.310215] ehci-platform: EHCI generic platform driver
[    4.319363] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.327317] ohci-platform: OHCI generic platform driver
[    4.336163] init: - preinit -
[    5.148612] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    5.181619] random: procd: uninitialized urandom read (4 bytes read, 8 bits of entropy available)
[    8.484735] jffs2: notice: (361) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[    8.502585] mount_root: switching to jffs2 overlay
[    8.518273] urandom-seed: Seeding with /etc/urandom.seed
[    8.810840] procd: - early -
[    8.813863] procd: - watchdog -
[    9.487850] procd: - ubus -
[    9.541721] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.551409] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.560553] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.570163] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.579297] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.589333] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.598611] random: ubusd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[    9.608223] procd: - init -
[   10.064115] Loading modules backported from Linux version wt-2016-10-03-1-g6fcb1a6
[   10.071796] Backport generated by backports.git backports-20160324-9-g0e38f5c
[   10.122372] batman_adv: B.A.T.M.A.N. advanced 2016.4 (compatibility version 15) loaded
[   10.205329] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
[   10.216362] ath: phy0: Ignoring endianness difference in EEPROM magic bytes.
[   10.225034] ath: EEPROM regdomain: 0x0
[   10.225051] ath: EEPROM indicates default country code should be used
[   10.225065] ath: doing EEPROM country->regdmn map search
[   10.225093] ath: country maps to regdmn code: 0x3a
[   10.225109] ath: Country alpha2 being used: US
[   10.225122] ath: Regpair used: 0x3a
[   10.240049] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   10.248689] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xb0000000, irq=40
[   11.861887] random: jshn: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
[   11.993063] random: ubusd: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
[   18.833441] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   18.855566] IPv6: ADDRCONF(NETDEV_UP): br-pub: link is not ready
[   21.215610] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   21.255512] device wlan0 entered promiscuous mode
[   21.286637] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   21.293301] br-pub: port 1(wlan0) entered forwarding state
[   21.298864] br-pub: port 1(wlan0) entered forwarding state
[   21.335689] IPv6: ADDRCONF(NETDEV_CHANGE): br-pub: link becomes ready
[   21.541225] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
[   21.594616] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
[   22.284927] batman_adv: bat0: Adding interface: mesh0
[   22.290148] batman_adv: bat0: Interface activated: mesh0
[   22.297750] 8021q: adding VLAN 0 to HW filter on device bat0
[   22.362868] device bat0 entered promiscuous mode
[   22.367627] br-pub: port 2(bat0) entered forwarding state
[   22.373200] br-pub: port 2(bat0) entered forwarding state
[   22.718089] batman_adv: bat0: bridge_loop_avoidance: Changing from: enabled to: disabled
[   23.289035] br-pub: port 1(wlan0) entered forwarding state
[   23.309325] batman_adv: bat0: No IGMP Querier present - multicast optimizations disabled
[   23.317459] batman_adv: bat0: No MLD Querier present - multicast optimizations disabled
[   24.369054] br-pub: port 2(bat0) entered forwarding state
[   29.389161] batman_adv: bat0: IGMP Querier appeared
[   38.069058] random: nonblocking pool is initialized
[   44.920666] eth0: link up (100Mbps/Full duplex)
[   44.925732] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   45.001214] batman_adv: bat0: Adding interface: eth0
[   45.006233] batman_adv: bat0: The MTU of interface eth0 is too small (1500) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the
 performance. Setting the MTU to 1532 would solve the problem.
[   45.030291] batman_adv: bat0: Interface activated: eth0
[   50.459193] batman_adv: bat0: MLD Querier appeared
[   67.509156] batman_adv: bat0: MLD Querier disappeared - multicast optimizations disabled
[   77.549128] batman_adv: bat0: MLD Querier appeared

My LEDE diffconfig looks like this:

CONFIG_TARGET_ar71xx=y
CONFIG_TARGET_ar71xx_generic=y
CONFIG_TARGET_ar71xx_generic_DEVICE_ubnt-bullet-m=y
CONFIG_DEVEL=y
CONFIG_BUSYBOX_CUSTOM=y
CONFIG_ALFRED_NEEDS_lua=y
CONFIG_BUILD_LOG=y
CONFIG_BUSYBOX_CONFIG_MESG=y
CONFIG_BUSYBOX_CONFIG_PKILL=y
CONFIG_BUSYBOX_CONFIG_RDATE=y
# CONFIG_BUSYBOX_CONFIG_SHA256SUM is not set
CONFIG_KMOD_BATMAN_ADV_BATMAN_V=y
CONFIG_KMOD_BATMAN_ADV_BLA=y
CONFIG_KMOD_BATMAN_ADV_DAT=y
CONFIG_KMOD_BATMAN_ADV_DEBUGFS=y
CONFIG_KMOD_BATMAN_ADV_MCAST=y
CONFIG_LIBCURL_COOKIES=y
CONFIG_LIBCURL_FILE=y
CONFIG_LIBCURL_FTP=y
CONFIG_LIBCURL_HTTP=y
CONFIG_LIBCURL_NO_SMB="!"
CONFIG_LIBCURL_POLARSSL=y
CONFIG_LIBCURL_PROXY=y
CONFIG_OPENSSL_ENGINE_CRYPTO=y
CONFIG_OPENSSL_WITH_DEPRECATED=y
CONFIG_OPENSSL_WITH_EC=y
CONFIG_OPENSSL_WITH_NPN=y
CONFIG_OPENSSL_WITH_PSK=y
CONFIG_OPENSSL_WITH_SRP=y
CONFIG_PACKAGE_ALFRED_BATHOSTS=y
CONFIG_PACKAGE_ALFRED_VIS=y
CONFIG_PACKAGE_alfred=y
CONFIG_PACKAGE_batctl=y
CONFIG_PACKAGE_bridge=y
CONFIG_PACKAGE_curl=y
CONFIG_PACKAGE_diffutils=y
# CONFIG_PACKAGE_dnsmasq is not set
# CONFIG_PACKAGE_firewall is not set
CONFIG_PACKAGE_horst=y
CONFIG_PACKAGE_iftop=y
# CONFIG_PACKAGE_ip6tables is not set
CONFIG_PACKAGE_iperf3=y
# CONFIG_PACKAGE_iptables is not set
CONFIG_PACKAGE_kmod-batman-adv=y
CONFIG_PACKAGE_kmod-bridge=y
CONFIG_PACKAGE_kmod-crypto-aead=y
CONFIG_PACKAGE_kmod-crypto-crc32c=y
CONFIG_PACKAGE_kmod-crypto-hash=y
CONFIG_PACKAGE_kmod-crypto-manager=y
CONFIG_PACKAGE_kmod-crypto-null=y
CONFIG_PACKAGE_kmod-crypto-pcompress=y
# CONFIG_PACKAGE_kmod-ip6tables is not set
# CONFIG_PACKAGE_kmod-ipt-conntrack is not set
# CONFIG_PACKAGE_kmod-ipt-core is not set
# CONFIG_PACKAGE_kmod-ipt-nat is not set
# CONFIG_PACKAGE_kmod-lib-crc-ccitt is not set
CONFIG_PACKAGE_kmod-lib-crc16=y
CONFIG_PACKAGE_kmod-lib-crc32c=y
CONFIG_PACKAGE_kmod-llc=y
# CONFIG_PACKAGE_kmod-nf-conntrack is not set
# CONFIG_PACKAGE_kmod-nf-conntrack6 is not set
# CONFIG_PACKAGE_kmod-nf-ipt is not set
# CONFIG_PACKAGE_kmod-nf-ipt6 is not set
# CONFIG_PACKAGE_kmod-nf-nat is not set
# CONFIG_PACKAGE_kmod-ppp is not set
CONFIG_PACKAGE_kmod-stp=y
CONFIG_PACKAGE_libcurl=y
# CONFIG_PACKAGE_libip4tc is not set
# CONFIG_PACKAGE_libip6tc is not set
CONFIG_PACKAGE_liblua=y
CONFIG_PACKAGE_libncursesw=y
CONFIG_PACKAGE_libnetsnmp=y
CONFIG_PACKAGE_libopenssl=y
CONFIG_PACKAGE_libpcap=y
CONFIG_PACKAGE_libpcre=y
CONFIG_PACKAGE_libpolarssl=y
CONFIG_PACKAGE_libpopt=y
CONFIG_PACKAGE_libpthread=y
CONFIG_PACKAGE_librt=y
# CONFIG_PACKAGE_libxtables is not set
CONFIG_PACKAGE_lua=y
# CONFIG_PACKAGE_odhcp6c is not set
# CONFIG_PACKAGE_odhcpd is not set
# CONFIG_PACKAGE_ppp is not set
CONFIG_PACKAGE_procps-ng=y
CONFIG_PACKAGE_procps-ng-free=y
CONFIG_PACKAGE_procps-ng-kill=y
CONFIG_PACKAGE_procps-ng-pgrep=y
CONFIG_PACKAGE_procps-ng-pkill=y
CONFIG_PACKAGE_procps-ng-pmap=y
CONFIG_PACKAGE_procps-ng-ps=y
CONFIG_PACKAGE_procps-ng-pwdx=y
CONFIG_PACKAGE_procps-ng-skill=y
CONFIG_PACKAGE_procps-ng-slabtop=y
CONFIG_PACKAGE_procps-ng-snice=y
CONFIG_PACKAGE_procps-ng-tload=y
CONFIG_PACKAGE_procps-ng-top=y
CONFIG_PACKAGE_procps-ng-uptime=y
CONFIG_PACKAGE_procps-ng-vmstat=y
CONFIG_PACKAGE_procps-ng-w=y
CONFIG_PACKAGE_procps-ng-watch=y
CONFIG_PACKAGE_ptp-utils=y
CONFIG_PACKAGE_rsync=y
CONFIG_PACKAGE_snmpd=y
CONFIG_PACKAGE_tcpdump=y
CONFIG_PACKAGE_terminfo=y
CONFIG_PACKAGE_wget=y
CONFIG_PACKAGE_wireless-tools=y
CONFIG_PACKAGE_zlib=y
CONFIG_RSYNC_zlib=y

My uci show looks like this (system and wireless elided):

alfred.alfred=alfred
alfred.alfred.mode='master'
alfred.alfred.batmanif='bat0'
alfred.alfred.start_vis='1'
alfred.alfred.run_facters='1'
alfred.alfred.interface='br-pub'
alfred.alfred.disabled='0'
batman-adv.bat0=mesh
batman-adv.bat0.bridge_loop_avoidance='0'
dropbear.@dropbear[0]=dropbear
dropbear.@dropbear[0].PasswordAuth='on'
dropbear.@dropbear[0].RootPasswordAuth='on'
dropbear.@dropbear[0].Port='22'
network.loopback=interface
network.loopback.ifname='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.pub=interface
network.pub.type='bridge'
network.pub.proto='static'
network.pub.ip6assign='60'
network.pub.ifname='bat0'
network.pub.ipaddr='10.11.x.y'
network.pub.netmask='255.255.252.0'
network.pub.gateway='10.11.x.1'
network.pub.dns='10.11.x.1'
network.mesh=interface
network.mesh.mtu='1532'
network.mesh.proto='batadv'
network.mesh.mesh='bat0'
network.meshwire=interface
network.meshwire.proto='batadv'
network.meshwire.mesh='bat0'
network.meshwire.ifname='eth0'
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.

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 ]---

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
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.

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

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.

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
18.01.2017408Base systemBug ReportVery LowLowArcher C7 has incorrect default bssid addresses for wif...TrunkWaiting on reporter Task Description

Using LEDE Reboot SNAPSHOT r3022-7fb11c8.

This is at least for Archer C7 v2. The default bssids for the networks in my particular device are:

:::::*D for the 2,4 GHz radio and
:::::*C for the 5 GHz radio

In LEDE they result in

:::::*C for the 2,4 GHz radio and
:::::*B for the 5 GHz radio

The problem in LEDE is that the bssid set up for the 2,4 GHz is the one for 5 GHz and then the 5 GHz gets minus one. Don’t know if it could be because the ethernet lan gets also :::::*D and wlan1 can’t have the same mac address as eth1. In the original firmware this seems to be possible, both ethernet lan and 2,4 GHz radio have the same mac/bssid. Also, at least with the 2,4 GHz radio, when you set up another connection with the device as client, the bssid of the master one change *(+2)::::**:*C the second hex digit gets plus 2, the bssid that should get a second connection as ap, but in this case there is one ap one client connections. This one could be right and I have to test with another router to see if it happens because I didn’t notice this before.

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.


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.


31.01.2017446Base systemBug ReportVery LowLowusbport trigger: The default configuration for all fami...TrunkUnconfirmed Task Description

Recently LuCI has get ability to configure LED’s with the usbport trigger https://github.com/openwrt/luci/issues/971. There are issues when reading the old usbdev trigger. There is no need to stay with usbdev at all so if it’s possible it should be converted to use usbport.

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.
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’

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.

05.02.2017469Base systemBug ReportVery LowLowWifi firmware file is not available on ZyXEL P-2812HNU-...lede-17.01Unconfirmed Task Description

Kernel log:

[   11.336056] PCI: Enabling device 0000:00:0e.0 (0000 -> 0002)
[   11.340485] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'RT3062.eeprom'.
[   11.350276] rt2800pci 0000:00:0e.0: Direct firmware load for RT3062.eeprom failed with error -2
[   11.358782] rt2800pci 0000:00:0e.0: Falling back to user helper
[   11.479331] firmware RT3062.eeprom: firmware_loading_store: map pages failed
[   11.485217] ieee80211 phy0: rt2x00lib_request_eeprom_file: Error - Failed to request EEPROM.
[   11.493519] rt2800pci: probe of 0000:00:0e.0 failed with error -11

Firmware files:

root@lede:/lib/firmware# ls /lib/firmware/
lantiq-vrx200-a-to-b.bspatch                 rt2860.bin                                   xcpe_581816_580B11.LICENSE                   xcpe_581816_580B11_to_579906_574402.bspatch
lantiq-vrx200-a.bin                          rt3290.bin                                   xcpe_581816_580B11.bin

After adding a RT3062.eeprom the wifi port is available.

 


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.

07.02.2017476Base systemBug ReportVery LowHighfail to detect usb storage at boot time on apu2c4.lede-17.01Unconfirmed Task Description

version: 17.01.0-rc1, r3042-ec095b5 and latest master
device: pcengine apu2c4, toshiba 32GB usb3.0 storage
packages: kmod-usb-storage, kmod-usb-core, kmod-scsi-core

<success case>
After boot, inserting usb storage is detected successfully, like this

BusyBox v1.25.1 () built-in shell (ash)

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

// LE \ ||_|_/|_| lede-project.org
\ \ DE /
\ LE \ / ———————————————————– \ DE \ / Reboot (17.01.0-rc1, r3042-ec095b5)
\
\/ ———————————————————– root@lede:/# ls /dev/|grep sd (← Not inserted yet)
root@lede:/# [ 73.924056] usb 3-2: new SuperSpeed USB device number 2 using xhci_hcd (← Detected)
[ 73.948714] usb-storage 3-2:1.0: USB Mass Storage device detected
[ 73.955124] scsi host4: usb-storage 3-2:1.0
[ 74.954867] scsi 4:0:0:0: Direct-Access TOSHIBA TransMemory-Mx PMAP PQ: 0 ANSI: 6
[ 74.963873] sd 4:0:0:0: [sda] 60456960 512-byte logical blocks: (31.0 GB/28.8 GiB)
[ 74.971758] sd 4:0:0:0: [sda] Write Protect is off
[ 74.976597] sd 4:0:0:0: [sda] Mode Sense: 45 00 00 00
[ 74.981951] sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[ 75.107329] sda:
[ 75.110561] sd 4:0:0:0: [sda] Attached SCSI removable disk root@lede:/# ls /dev/|grep sd
sda (← device file found)
root@lede:/#
======================================================================================= <failure case>
After reboot keeping usb storage inserted, inserting usb storage is not detected, like this
=======================================================================================
BusyBox v1.25.1 () built-in shell (ash)
_
/ /\ _
_ _ _

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

// LE \ ||_|_/|_| lede-project.org
\ \ DE /
\ LE \ / ———————————————————– \ DE \ / Reboot (17.01.0-rc1, r3042-ec095b5)
\
__\/ ———————————————————–

root@lede:/# ls /dev/|grep sd
root@lede:/#

Do you know the clue fixing this issue?

Thanks in advance.

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.


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
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 ]—

 


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.

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.

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.

 


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.

15.02.2017517Base systemBug ReportVery LowVery LowPCEngines Alix Ethernet right hand led lit on boot for ...lede-17.01Unconfirmed Task Description

PCEngines Alix, Ethernet right hand led is on once booted, on all ports, with no cable connected.
LEDE Reboot 17.01.0-rc2
Image used: lede-17.01.0-rc2-r3131-42f3c1f-x86-geode-combined-squashfs.img

On booting the right hand LED is on for all ethernet ports with no cable connected. On connecting a cable the left hand light comes on as expected and the right hand stays on. Both leds then flash with traffic as expected.

Operation is not effected.

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'
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)


18.02.2017533Base systemBug ReportVery LowHighanon_mount 1 in fstab freezes boot in wrt3200acmlede-17.01Unconfirmed Task Description

I have run into strange trouble with my new WRT3200ACM:

anon_mount 1 option in /etc/config/fstab causes the boot process to hang.
Hang can be triggered manually with “/sbin/block mount” when that option is set.
Kernel log fills from entries “pxa3xx-nand f10d0000.flash: Wait time out!!!”

I am filing this bug report for 17.01, but the bug seems to be also in master.


For some reason enabling the anon_mount option in /etc/config/fstab prevents the boot process from completing. The boot progresses to some stage and router e.g. answers ping, but power led blinks and it does not allow login and does not provide dhcp etc. services.

I have had that option in all my routers (WNDR3700, WNDR3800, R7800) to make USB memory sticks to automount when inserted into the router’s USB port. So it is a quite normal setting.

I first compiled a mvebu wrt3200acm firmware image from master with kernel 4.9, and that failed to boot. I thought that the new kernel 4.9 might be the reason. So I installed 17.01.0-rc2 official image and it booted ok. I installed packages, configured, rebooted and everything was ok as long as I did not change that anon_mount to 1 in fstab. After changing that, the next boot again gets stuck. (Editing the option in failsafe enables the router to boot normally.)

Boot completes ok with the output of “block detect” entered into fstab:

  config 'global'
          option  anon_swap       '0'
          option  anon_mount      '0'
          option  auto_swap       '1'
          option  auto_mount      '1'
          option  delay_root      '5'
          option  check_fs        '0'

Boot does not complete with anon_mount 1 in /etc/config/fstab:

  config 'global'
          option  anon_swap       '0'
          option  anon_mount      '1'
          option  auto_swap       '1'
          option  auto_mount      '1'
          option  delay_root      '5'
          option  check_fs        '0'

I have no good guess about the reason. My initial guess was some connection to ubi1:syscfg being mounted as /tmp/syscfg as that is different than in my other devices, but it is hard to see how that could be the reason. (That mounting is done in /lib/preinit/81_linksys_syscfg )

After some investigation it looks like the reason is actually “/sbin/block mount”.

At the boot the init script /etc/init.d/fstab actually runs “/sbin/block mount”.
Running that command manually from console (with anon_mount 1) makes the console to hang. From another console window I can see that system & kernel log fills from entries like these:

  kern.err kernel: [ 3032.483307] pxa3xx-nand f10d0000.flash: Wait time out!!!
  kern.err kernel: [ 3032.683301] pxa3xx-nand f10d0000.flash: Wait time out!!!
  kern.err kernel: [ 3032.883296] pxa3xx-nand f10d0000.flash: Wait time out!!!
  kern.err kernel: [ 3033.083293] pxa3xx-nand f10d0000.flash: Wait time out!!!
  kern.err kernel: [ 3033.283291] pxa3xx-nand f10d0000.flash: Wait time out!!!
  kern.err kernel: [ 3033.483287] pxa3xx-nand f10d0000.flash: Wait time out!!!
  kern.err kernel: [ 3033.683283] pxa3xx-nand f10d0000.flash: Wait time out!!!

And the “block” process can’t even be killed with “kill -9” or “kill -15”.
I rebooted the router from power switch to get it killed.

With anon_mount 0 in fstab the same command works ok and produces:

 root@LEDE:~# /sbin/block mount
 block: /dev/ubiblock0_0 is already mounted on /rom
 block: /dev/ubi0_1 is already mounted on /overlay
19.02.2017534Base systemBug ReportVery LowHighUSB xHCI deadlock on bootlede-17.01Assigned Task Description

Supply the following if possible:
- Device problem occurs on
VirtualBox x86_64 Version 5.0.32 r112930
- Software versions of LEDE release, packages, etc.
17.01.00rc2
- Steps to reproduce
Create the disk image
Switch from EHCI (the default in a new VM) to xHCI.
Boot the machine
The machine will deadlock soon after initializing the USB ports


21.02.2017545Base systemBug ReportVery LowLowUSB does not work ARV4518PWR01Alede-17.01Unconfirmed Task Description

Hello, I tried to install 17.01.0-rc2, r3131 on Arcadyan ARV4518PWR01A but USB is not working.

 


26.02.2017557Base systemBug ReportVery LowMediumNexx wt3020 wifi rx sensitivity low with LEDE 17.01lede-17.01Unconfirmed Task Description

The rx sensitivity reported by a Nexx wt3020 is ~ 20dB lower than a comparable tp-link device located sided by side with the Nexx wt3020.
There have been reports of a similar problem with OpenWRT versions.

There is a ticket open with openwrt with a similar reported issue https://dev.openwrt.org/ticket/20369 as well as on the openwrt forum https://forum.openwrt.org/viewtopic.php?id=69042

lede trunk (and openwrt trunk) as of 24/2/17 also display similar poor rx sensitivity.

 


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
28.02.2017568Base systemBug ReportVery LowVery LowFirst boot messages are not logged to filelede-17.01Unconfirmed Task Description

I’m saving logs to a file on an external partition that is mounted at boot. After rebooting with an empty log file, an inconsistency can be noticed between the output of logread and the content of the log file. The first message printed by logread is, as expected,

Mon Feb 27 20:33:15 2017 kern.info kernel: [    0.000000] Booting Linux on physical CPU 0x0

while the first message in the log file reads

Mon Feb 27 20:33:16 2017 user.notice : Added device handler type: tunnel

The first boot messages are missing from the log file. From this point on, logread and the log file are identical.
Of course this is a minor issue, but still one would expect logs to be 100% complete, regardless whether they are stored in memory or to file.

root@lede:~# cat /etc/config/system 
config system
        option hostname 'lede'
	option zonename 'Europe/Rome'
	option timezone 'CET-1CEST,M3.5.0,M10.5.0/3'
        option ttylogin '0'
        option urandom_seed '0'
        option log_remote '0'
        option log_type 'file'
        option log_file '/mnt/sda1/var/log/messages'
        option log_buffer_size '64'
        option log_size '1024'
        option conloglevel '8'
        option cronloglevel '0'
...

Start order of init scripts log and fstab has been changed to start logging as early as possible.

root@lede:~# ls -1 /etc/rc.d/S*
/etc/rc.d/S00sysfixtime
/etc/rc.d/S10boot
/etc/rc.d/S10fstab
/etc/rc.d/S10system
/etc/rc.d/S11log
/etc/rc.d/S11sysctl
...

Device: WRT1200AC
Software version: Reboot (17.01.0, r3205-59508e3)

01.03.2017576Base systemBug ReportVery LowMediumath10k fails to load reporting a 'firmware crash' on QC...lede-17.01Unconfirmed Task Description

Problem occurs on a ZYXEL NBG6716. (802.11ac should be a QCA9880)
running 17.01.1 i.e. lede-17.01.0-r3205-59508e3-ar71xx-nand-nbg6716-squashfs-sysupgrade.bin
Crash occurs every time ath10k attempts to load

log with driver included in release

[   14.783881] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[   15.000294] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[   15.011181] ath10k_pci 0000:01:00.0: Falling back to user helper
[   15.090655] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[   15.299839] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   15.309251] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   15.322304] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00016 api 5 features no-p2p,raw-mode,mfp crc32 0c5668f8
[   15.333090] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[   15.343695] ath10k_pci 0000:01:00.0: Falling back to user helper
[   15.423744] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[   15.442629] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   16.551704] ath10k_pci 0000:01:00.0: firmware crashed! (uuid 68334050-5a5e-48bf-bccc-87f25cba960e)
[   16.560832] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   16.570194] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   16.583244] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00016 api 5 features no-p2p,raw-mode,mfp crc32 0c5668f8
[   16.593975] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   16.601395] ath10k_pci 0000:01:00.0: htt-ver 0.0 wmi-op 5 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
[   16.613031] ath10k_pci 0000:01:00.0: firmware register dump:
[   16.618783] ath10k_pci 0000:01:00.0: [00]: 0x4100016C 0x000015B3 0x009BA6A2 0x00955B31
[   16.626822] ath10k_pci 0000:01:00.0: [04]: 0x009BA6A2 0x00060130 0x0000001D 0x00000000
[   16.634857] ath10k_pci 0000:01:00.0: [08]: 0xFFFFFFFF 0x00401F6A 0x0000096C 0xFFFFFFFF
[   16.642883] ath10k_pci 0000:01:00.0: [12]: 0x00000009 0x00000000 0x009BAB4C 0x009BABA7
[   16.650916] ath10k_pci 0000:01:00.0: [16]: 0x00958080 0x0094E9B1 0x00000000 0x00000000
[   16.658951] ath10k_pci 0000:01:00.0: [20]: 0x409BA6A2 0x0040AA24 0x0040AAD4 0x00000001
[   16.666985] ath10k_pci 0000:01:00.0: [24]: 0x809BB189 0x0040AA84 0x0040EE0C 0xC09BA6A2
[   16.675020] ath10k_pci 0000:01:00.0: [28]: 0x809BB612 0x0040AAB4 0x000000E2 0x00000001
[   16.683047] ath10k_pci 0000:01:00.0: [32]: 0x80984880 0x0040ABA4 0x0040EE3C 0x0000003F
[   16.691089] ath10k_pci 0000:01:00.0: [36]: 0x8098FBA5 0x0040ABE4 0x0040E270 0x004062DC
[   16.699131] ath10k_pci 0000:01:00.0: [40]: 0x8098A79E 0x0040AC34 0x0040AC94 0x004062DC
[   16.707166] ath10k_pci 0000:01:00.0: [44]: 0x80988785 0x0040AC94 0x00410670 0x00400000
[   16.715200] ath10k_pci 0000:01:00.0: [48]: 0x8098AE78 0x0040AD44 0x00410670 0x00000001
[   16.723227] ath10k_pci 0000:01:00.0: [52]: 0x809B66F0 0x0040AD84 0x00410670 0x00411254
[   16.731269] ath10k_pci 0000:01:00.0: [56]: 0x809B2868 0x0040ADA4 0x00400000 0x00416EB4
[   21.543818] ath10k_pci 0000:01:00.0: wmi unified ready event not received
[   21.646943] ath10k_pci 0000:01:00.0: could not init core (-145)
[   21.653075] ath10k_pci 0000:01:00.0: could not probe fw (-145)
[   21.664514] ath10k_pci 0000:01:00.0: cannot restart a device that hasn't been started

log with alernative ath10k-ct from packages

Sun Feb 26 20:09:36 2017 kern.info kernel: [   15.991374] ath10k driver, optimized for CT firmware, probing pci.
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   15.998923] PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
Sun Feb 26 20:09:36 2017 kern.info kernel: [   16.004876] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
Sun Feb 26 20:09:36 2017 kern.info kernel: [   16.115573] EXT4-fs (sda1): mounted filesystem without journal. Opts: 
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.220291] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.231178] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.309980] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.322702] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/fwcfg-pci-0000:01:00.0.txt failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.333430] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.483479] firmware ath10k!fwcfg-pci-0000:01:00.0.txt: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.502812] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-5.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.513707] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.656794] firmware ath10k!QCA988X!hw2.0!firmware-5.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.666061] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-5.bin': -11
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.676241] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-4.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.687110] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.839245] firmware ath10k!QCA988X!hw2.0!firmware-4.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.848512] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-4.bin': -11
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.858690] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-3.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.869560] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   17.020761] firmware ath10k!QCA988X!hw2.0!firmware-3.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.err kernel: [   17.030028] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-3.bin': -11
Sun Feb 26 20:09:36 2017 kern.info kernel: [   17.152659] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Sun Feb 26 20:09:36 2017 kern.info kernel: [   17.162062] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Sun Feb 26 20:09:36 2017 kern.info kernel: [   17.174406] ath10k_pci 0000:01:00.0: firmware ver 10.1.467-ct-_fW-019-647197c api 2 features wmi-10.x,has-wmi-mgmt-tx,txstatus-noack,wmi-10.x-CT,ratemask-CT crc32 ce5082a8
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   17.190041] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   17.200645] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   17.280425] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.info kernel: [   17.293109] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   18.216205] ath10k_pci 0000:01:00.0: 10.1 wmi init: vdevs: 16  peers: 127  tid: 256
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.224910] ath10k_pci 0000:01:00.0: firmware crashed! (uuid 44fc9f0a-8adb-4077-ae4e-82113c83f387)
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.234031] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.243382] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.255705] ath10k_pci 0000:01:00.0: firmware ver 10.1.467-ct-_fW-019-647197c api 2 features wmi-10.x,has-wmi-mgmt-tx,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT crc32 ce5082a8
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.278224] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.285650] ath10k_pci 0000:01:00.0: htt-ver 0.0 wmi-op 2 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.297288] ath10k_pci 0000:01:00.0: firmware register dump:
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.303030] ath10k_pci 0000:01:00.0: [00]: 0x4100016C 0x000015B3 0x009B1635 0x00955B31
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.311074] ath10k_pci 0000:01:00.0: [04]: 0x009B1635 0x00060130 0x0000001D 0x009BAB8B
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.319114] ath10k_pci 0000:01:00.0: [08]: 0xFFFFFFFF 0x00401F6A 0x0000096C 0xFFFFFFFF
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.327147] ath10k_pci 0000:01:00.0: [12]: 0x00000009 0x00000000 0x009B1AD1 0x009B1B29
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.335182] ath10k_pci 0000:01:00.0: [16]: 0x00958080 0x0094085D 0x00000000 0x00000000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.343210] ath10k_pci 0000:01:00.0: [20]: 0x409B1635 0x0040AA44 0x0040AAF4 0x00000001
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.351251] ath10k_pci 0000:01:00.0: [24]: 0x809B21C2 0x0040AAA4 0x00401F7E 0xC09B1635
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.359290] ath10k_pci 0000:01:00.0: [28]: 0x809B2676 0x0040AAD4 0x00401CC0 0x000000E2
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.367329] ath10k_pci 0000:01:00.0: [32]: 0x8098494F 0x0040ABC4 0x0040E07C 0x0000003F
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.375362] ath10k_pci 0000:01:00.0: [36]: 0x8098ED6F 0x0040AC04 0x0040D4B0 0x004062DC
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.383391] ath10k_pci 0000:01:00.0: [40]: 0x809892DD 0x0040AC54 0x0040ACB4 0x00400000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.391431] ath10k_pci 0000:01:00.0: [44]: 0x809887C9 0x0040ACA4 0x0040F7B8 0x00400000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.399463] ath10k_pci 0000:01:00.0: [48]: 0x809897B4 0x0040AD44 0x0040F7B8 0x00000001
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.407500] ath10k_pci 0000:01:00.0: [52]: 0x809AD74A 0x0040AD84 0x0040F7B8 0x0000A000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.415535] ath10k_pci 0000:01:00.0: [56]: 0x809AA392 0x0040ADA4 0x00400000 0x00414F44
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   18.425582] ath10k_pci 0000:01:00.0: debug log header, dbuf: 0x412598  dropped: 0
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   18.434191] ath10k_pci 0000:01:00.0: [0] next: 0x4125b0 buf: 0x4103fc sz: 1500 len: 56 count: 2 free: 0
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.444731] ath10k_pci 0000:01:00.0: ath10k_pci ATH10K_DBG_BUFFER:
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.451001] ath10k: [0000]: 38700000 0500FC17 70201031 08000000 80000000 B8F74000 01000600 39700000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.460186] ath10k: [0008]: 0100FC17 B3150000 B3150000 34A94000 6C010041 09000000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.467775] ath10k_pci 0000:01:00.0: ATH10K_END
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   18.473385] ath10k_pci 0000:01:00.0: [1] next: 0x412598 buf: 0x4109ec sz: 1500 len: 0 count: 0 free: 0
Sun Feb 26 20:09:36 2017 kern.err kernel: [   23.223848] ath10k_pci 0000:01:00.0: wmi unified ready event not received
Sun Feb 26 20:09:36 2017 kern.err kernel: [   23.325855] ath10k_pci 0000:01:00.0: could not init core (-145)
Sun Feb 26 20:09:36 2017 kern.err kernel: [   23.331970] ath10k_pci 0000:01:00.0: could not probe fw (-145)
Sun Feb 26 20:09:36 2017 kern.info kernel: [   23.338980] i2c /dev entries driver
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   23.344460] ath10k_pci 0000:01:00.0: cannot restart a device that hasn't been started


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.

03.03.2017588Base systemBug ReportMediumLowopenvpn-mbedtls crash on mpc85xx with signal 4 (SIGILL)lede-17.01Waiting on reporter Task Description

device: tp-link wdr4900
affected version: lede 17.01 / openvpn-mbedtls - 2.4.0-3

openvpn config:

dev tun-monitoring
remote somehost 1194

ca /etc/openvpn/monitoring-vpn/ca.crt
cert /etc/openvpn/monitoring-vpn/xyz.crt
key /etc/openvpn/monitoring-vpn/xyz.key
tls-auth /etc/openvpn/monitoring-vpn/ta.key 1
remote-cert-tls server

keepalive 10 120
cipher AES-256-CBC
comp-lzo yes

persist-key
persist-tun


03.03.2017590Base systemBug ReportVery LowLowImageBuilder ar71xx BIN_DIR issuelede-17.01Unconfirmed Task Description

Software versions of LEDE release: lede 17 branch

Steps to reproduce:

- compile ar71xx with image builder support from lede 17 branch
- use the imagebuilder like: make image BIN_DIR=/var/www/downoads

we started testing lede-17.01 for OpenWISP.org and we noticed a
strange issue with the image-generator.

We supply a command like:

make image PROFILE=”Default” BIN_DIR=”$BIN_DIR”

but the image building fails because something goes to look for binaries
in ./bin/targets/ar71xx/generic instead of
“$BIN_DIR/targets/ar71xx/generic”.

If we create manually the dir with:

mkdir ./bin/targets/ar71xx/generic

The image building procedure completes successfully.

Is this desired behaviour or not?

We had to insert a workaround in our automated LEDE compilation process.

05.03.2017598Base systemBug ReportMediumLow842nd doesnt flash successful with factory image using ...lede-17.01New Task Description

Device: 842nd v3.1
LEDE: 17.01

Go into recovery tftp mode by pressing first the WPS/Reset button and now connect the power.
The device enters tftp recovery to download via tftp from 192.168.0.66 file (wr842nv3_tp_recovery.bin)

The device *seems* to accept the flash (sorry, no serial to confirm).
On boot, the device doesn’t show leds nor it accepts any packets on ipv6 on any port (ping ff02::1) or ping to 192.168.1.1.

I guess this happens, because the oem flasher doesn’t flash all blocks of the factory image.

To recover from this state:
- flash via tftp recovery
- enter LEDE rescue/recovery
- ssh root@192.168.1.1
- use sysupgrade image

Task:
- confirm this happens also with trunk
- use serial to get more debug

Showing tasks 1 - 50 of 1140 Page 1 of 231 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing