OpenWrt/LEDE Project

Welcome to the OpenWrt Project bug reporting and issue tracking system

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

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

OpenedIDCategory  ascTask TypePrioritySeveritySummaryReported InStatus
16.03.20213686Base systemBug ReportVery LowCriticalBelkin F9K1115 v2 - boot loop with 21.02 snapshotopenwrt-21.02Unconfirmed Task Description

Boot loop, no communication with the router after upgrade to 21.02 snapshot (tested r15866).

Upgrade from Belkin web UI (factory image) is not working.

Probably migration to the new ath79 architecture is not correct:
- https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=563ece8a85dad24e8c3ce55af51938a4d37405f0 - https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=b403a6e1241c00f509b201ec2ac8ca5f29e1ffd1

13.04.20213738Base systemBug ReportVery LowLowFritz 1200 no network on luci-21.02-snapshot-r15866-17a...openwrt-21.02Unconfirmed Task Description

- Device: AVM FRITZ!Repeater 1200

- Software versions: luci-21.02-snapshot-r15866-17a627ec82-ipq40xx-generic-avm_fritzrepeater-1200-squashfs-sysupgrade

- Steps to reproduce: there is no LAN connection after upload this firmware to Fritz 1200, after back to luci-19.07-snapshot-r11328-81266d9001-ipq40xx-generic-avm_fritzrepeater-1200-squashfs-sysupgrade, everything works: Lan connection return.

 


19.04.20213745Base systemBug ReportVery LowLowWireless 'isolate' option not working in brcmfmac drive...openwrt-21.02Unconfirmed Task Description

Device: BCM4356 WiFi chip + brcmfmac
OpenWRT Version: 21.02 (commit 50f2f25d58 [4 days ago])

I experienced the problem using OpenWrt 21.02 on a device using the brcmfmac driver for the BCM4356 chip.

I’ve only been able to test this on an InvizBox 2 (not supported by OpenWRT) but I suspect it to also be a problem for other devices using brcmfmac.

Steps to reproduce:

On a device running OpenWRT 21.02 and with a WiFi chip using the brcmfmac driver:

Set wireless.<wifi-iface>.isolate=’1’ on the WiFi interface that uses the brcmfmac driver.

Devices connected to the WiFi interface should be isolated from each other, but are not.

Notes / Potential fixes:

I was able to fix this issue by building with a specific patch for brcmfmac from the latest Cypress Linux WiFi Driver Release (FMAC)(https://community.cypress.com/t5/Wi-Fi-Bluetooth-for-Linux/Cypress-Linux-WiFi-Driver-Release-FMAC-2021-01-14/m-p/268899). The particular patch that fixed the issue can be found in the .zip file linked in the latest Cypress driver release. cypress-fmac-v5.4.18-2021_0114.zip > cypress-patch-v5.4.18-2021_0114.tar.gz > cypress-patch > 0004-brcmfmac-support-AP-isolation.patch.

The patch has not been accepted into linux-wireless yet. But there are details about it here: https://patchwork.kernel.org/project/linux-wireless/patch/20200901063237.15549-2-wright.feng@cypress.com/.

Let me know if you need any more information or there’s anything I can do to help sort this out. Thanks.

20.04.20213746Base systemBug ReportVery LowLowx86_64 EFI image fails to boot when USB device is plugg...openwrt-21.02Unconfirmed Task Description

Snapshot OR 21.02.0-rc1-x86_64 will not boot EFI

System: AsRock J5005-ITX (EFI only boot), 4GB ram, Intel Dual 1000PT server adapter

 

Steps used to typically install snapshot:

Boot SystemRescueCD to prompt
issue dd if=openwrt-xxx of=/dev/sda
partitions are copied over, reboot
Error on Snapshot: “error: disk ‘hd0,gpt1’ not found

on RC1 file copies over as above but it does not boot in any fashion just returns to the bios screen.

It’s been a long time since I tested the EFI snapshots, but at one point they worked fine. Given that the EFI support was added to master, I decided to wait on 2021.02 for full implementation.

The original pull on github was https://github.com/openwrt/openwrt/pull/1968, but it has since been closed, and I saw there was some work on the EFI stack for dual booting. That image may in fact boot on a non-EFI system, but I do not have any way to test.

At this point I would say both snapshot and RC1 are broken for x86_64 EFI systems.

22.04.20213749Base systemBug ReportVery LowLowbusybox-ntp failing on specific ISP but ntpd works.openwrt-21.02Unconfirmed Task Description

- Device: glinet B1300 router
- Running 21.02

Attached are two pcap files you can open in wireshark.

This issue seems to only affect one Danish ISP, however I think it is worth reporting to see if it can be fixed.
The built in busybox-ntpd does not work (see packet in sysntpd.pcap)

However, if I install ntpdate instead then ntp is able to update (using the same ntp server).
You can see difference in the packets by comparing the two pcap files.

My best bet is that the ISP is blocking specific data in NTPv4 Packets that busybox-ntp is sending.

28.04.20213759Base systemBug ReportVery LowHighIdle ssh Connection exits with: client_loop: send disco...openwrt-21.02Unconfirmed Task Description

Summary

  • Device problem occurs on: x86-64 based router
  • Affected Software version: 21.02.0-rc1
    • This bug does NOT happen when running 19.07.7

Steps to reproduce

SSH from one computer to another machine that is on the internet

machine 1 < —- > openwrt 21.02.0-rc1 ←— internet —→ machine 2

Run this command on machine 1: watch ‘sleep 3000;date’

After some time has passed (wait about 30 minutes, maybe a little less):
1) the ssh tunnel will exit when you press enter in the terminal.
2) The error message will be: “client_loop: send disconnect: Broken pipe”

 


29.04.20213760Base systemBug ReportVery LowCriticalWifi to WAN traffic causes eth0 to crash with a NETDEV ...openwrt-21.02Unconfirmed Task Description

I have been testing OpenWRT 21.02-RC1 stock released firmware image on the Newifi-D2 target (MT7621 based).

Sporadically while using the router, i experience the WAN interface crashing with NETDEV WATCHDOG errors.

I am using the released image for OpenWrt 21.02-rc1 for the Newifi-D2 target
I have also experienced this fault with a custom router build based on MT7621 for a different target, the fault appears general to MT7621 not this target.

I have loaded 19.07.7 stock firmware on this same hardware and the fault does not occur in that firmware version. A colleague has replicated this fault in 21.02-RC1 with the same type of target (physically different unit), but in a different environment with no shared network resources.

Other than setting up the wifi ssid and password and enabling the 5ghz radio, the network settings are stock.

I have worked out a 90% reliable test case to reproduce the fault:

Have a client device connected to the router on WiFi 5ghz
And a local Iperf3 server running on the wan side of the wired interface.

On the server run:

iperf3 -s

Note the servers IP address

On the client run:

iperf3 -c <serverIP> -P 50

Notes:
Iperf3 server needs to be local on a 1gbps wired link. With an internet based Iperf3 server (or one with a slower connection) the error is much harder to trigger, it will happen but its much more random.
The number of connections does not need to be 50, however, the lower the number of connections the less reliable the error triggers.
The WiFi client should be getting about 300-400mbps throughput over the wifi link when its working correctly.

On most runs, the iperf3 performance will drop to 0mbps, logread on the router then reveals:

Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.065748] ------------[ cut here ]------------
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.070403] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:448 0x8047e780
Thu Apr 29 03:58:44 2021 kern.info kernel: [  578.077443] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed out
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.084412] Modules linked in: pppoe ppp_async iptable_nat xt_state xt_nat xt_conntrack xt_REDIRECT xt_MASQUERADE xt_FLOWOFFLOAD xt_CT pppox ppp_generic nf_nat nf_flow_table_hw nf_flow_table nf_conntrack_rtcache nf_conntrack mt76x2e mt76x2_common mt76x02_lib mt7603e mt76 mac80211 ipt_REJECT cfg80211 xt_time xt_tcpudp xt_multiport xt_mark xt_mac xt_limit xt_comment xt_TCPMSS xt_LOG slhc nf_reject_ipv4 nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables crc_ccitt compat ledtrig_usbport nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd gpio_button_hotplug usbcore nls_base usb_common
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.147503] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.111 #0
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.153490] Stack : 00000000 80840000 ffffffff 8007d6e0 00000000 00000000 00000000 00000000
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.161831]         00000000 00000000 00000000 00000000 00000000 00000001 8fc0fd50 8ba64c1c
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.170163]         8fc0fde8 00000000 00000000 00000000 00000038 805e1804 342e3520 3131312e
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.178486]         00000000 0000001c 00000000 0002402f 00000000 8fc0fd30 00000000 8047e780
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.186808]         00000009 00000001 00200000 00000122 00000003 80359e2c 00000004 80810004
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.195132]         ...
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.197567] Call Trace:
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.197583] [<8007d6e0>] 0x8007d6e0
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.203512] [<805e1804>] 0x805e1804
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.206990] [<8047e780>] 0x8047e780
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.210464] [<80359e2c>] 0x80359e2c
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.213941] [<8000b05c>] 0x8000b05c
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.217409] [<8000b064>] 0x8000b064
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.220879] [<805c6f9c>] 0x805c6f9c
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.224351] [<8007d8ac>] 0x8007d8ac
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.227829] [<8002bfe8>] 0x8002bfe8
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.231302] [<8047e780>] 0x8047e780
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.234775] [<8002c0c0>] 0x8002c0c0
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.238257] [<8047e780>] 0x8047e780
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.241731] [<800a9018>] 0x800a9018
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.245212] [<8047e484>] 0x8047e484
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.248688] [<800965d4>] 0x800965d4
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.252161] [<8009681c>] 0x8009681c
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.255640] [<805e7d1c>] 0x805e7d1c
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.259116] [<80030768>] 0x80030768
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.262588] [<802f8404>] 0x802f8404
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.266064] [<80006c28>] 0x80006c28
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.269533]
Thu Apr 29 03:58:44 2021 kern.warn kernel: [  578.271153] ---[ end trace eabfb050c5985bce ]---
Thu Apr 29 03:58:44 2021 kern.err kernel: [  578.275799] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out
Thu Apr 29 03:58:44 2021 kern.info kernel: [  578.282602] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
Thu Apr 29 03:58:44 2021 kern.info kernel: [  578.318310] mtk_soc_eth 1e100000.ethernet eth0: configuring for fixed/rgmii link mode
Thu Apr 29 03:58:44 2021 kern.info kernel: [  578.326251] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx

This only occurs on the first instance of the error, the error will repeatedly occur but the only evidence in the logs after the first error is:

Thu Apr 29 04:33:36 2021 kern.err kernel: [ 2670.043971] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out
Thu Apr 29 04:33:36 2021 kern.info kernel: [ 2670.050555] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
Thu Apr 29 04:33:36 2021 kern.info kernel: [ 2670.084619] mtk_soc_eth 1e100000.ethernet eth0: configuring for fixed/rgmii link mode
Thu Apr 29 04:33:36 2021 kern.info kernel: [ 2670.092556] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
29.04.20213769Base systemBug ReportVery LowHighDuplicate LAN MAC address on RB750Gr3openwrt-21.02Unconfirmed Task Description

Device: RB750Gr3
OpenWrt: 21.02.0-rc1 and 21.02-SNAPSHOT r16053-f066ee2ad5 (clean flash)

The kernel log has several lines of the following

br-lan: received packet on lan2 with own address as source address (addr:08:55:31:2e:c0:34, vlan:0)

/etc/config/network

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 packet_steering '1'
        option ula_prefix 'fd60:2450:7cfe::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'lan2 lan3 lan4 lan5'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config device 'lan_lan2_dev'
        option name 'lan2'
        option macaddr '08:55:31:2e:c0:34'

config device 'lan_lan3_dev'
        option name 'lan3'
        option macaddr '08:55:31:2e:c0:34'

config device 'lan_lan4_dev'
        option name 'lan4'
        option macaddr '08:55:31:2e:c0:34'

config device 'lan_lan5_dev'
        option name 'lan5'
        option macaddr '08:55:31:2e:c0:34'
                                          
config interface 'wan'
        option ifname 'wan'
        option proto 'dhcp'
                                          
config device 'wan_wan_dev'
        option name 'wan'
        option macaddr '08:55:31:2e:c0:33'
                                          
config interface 'wan6'
        option ifname 'wan'
        option proto 'dhcpv6'


02.05.20213772Base systemBug ReportVery LowCriticalOpenWrt 21.02.0-rc1 reboots frequently after turning on...openwrt-21.02Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on TP-Link TL-WR1043ND v1
- Software versions of OpenWrt/LEDE release, packages, etc. OpenWrt 21.02.0-rc1 r16046-59980f7aaf / LuCI openwrt-21.02 branch git-21.106.55967-06dd6b5

- Steps to reproduce

 

Upgrade go OpenWrt 21.02.1-rc1 without saving previous configs (otherwise system will become unstable immediately after upgrade). Turn on Wireless in Network–>Wireless–>.... After this a device becomes unstable and completely unusable starting to reboot again and again.

02.05.20213775Base systemBug ReportVery LowVery LowR7800 & 21.02.0-rc1 : no client connected to Wifi 5GHzopenwrt-21.02Unconfirmed Task Description

Environment : - Netgear R7800 (Nighthawk X4S AC2600)
- OpenWrt 21.02.0-rc1 (sysupgraded from OpenWrt 19.07.7 with some basic configuration)

Problem encountered : After doing a sysupgrade from OpenWrt 19.07.7 to OpenWrt 21.02.0-rc1, everything looked fine at first sight, but I have noticed that none of the WiFi clients were connected to the 5GHz WiFi, they were all connected to the 2.4GHz WiFi, which leaded to a bandwidth diminution and my printer was not anymore accessible.
Now, I am back to OpenWrt 19.07.7 and the printer is working fine again.

Sorry I don’t have more details on that problem, I am creating that bug ticket to see if I am the only one concerned by that bug.
I don’t even know if the 5GHz WiFi was emitting for real or not.

05.05.20213782Base systemBug ReportVery LowCriticalTP-Link CPE510 v2 bootloop with 21.02.0-rc1openwrt-21.02Requires testing Task Description

Installing the 21.02.0-rc1 Sysupgrade image on the TP-Link CPE510 v2 or TP-Link CPE610 v1 results in the same bootloop as reported in https://bugs.openwrt.org/index.php?do=details&task_id=3750

Here is a log from my device with a line length of 80 chars

TP-LINK SafeLoader (Build time: Jun 14 2017 - 10:08:41)
CPU: 560MHz AHB: 225MHz DDR: 8MB
Performing LED check..  PASS
Press CTRL+B to enter SafeLoader: 1

Allocated memory for elf segment ok: addr: 0x80060000, size 0x16dc
Loading .text @ 0x80060000 (5852 bytes)

Starting kernel


OpenWrt kernel loader for AR7XXX/AR9XXX
Copyright (C) 2011 Gabor Juhos <juhosg@openwrt.org>
Looking for OpenWrt image... found at 0xbf043000
Decompressing kernel... done!
Starting kernel at 80060000...
[    0.000000] Linux version 5.4.111 (builder@buildhost) (gcc version 8.4.0 (Ope
[    0.000000] printk: bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001974c (MIPS 74Kc)
[    0.000000] MIPS: machine is TP-Link CPE510 v2
[    0.000000] SoC: Atheros AR9344 rev 2
[    0.000000] Initrd not found or empty - disabling initrd
[    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
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 16240
[    0.000000] Kernel command line: console=ttyS0,115200 rootfstype=squashfs,jf
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes, li
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes, lin
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 57336K/65536K available (5216K kernel code, 190K rwdata,
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 51
[    0.000000] random: get_random_bytes called from 0x80655984 with crng_init=0
[    0.000000] CPU clock: 560.000 MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_
[    0.000010] sched_clock: 32 bits at 280MHz, resolution 3ns, wraps every 7669
[    0.009095] Calibrating delay loop... 278.78 BogoMIPS (lpj=557568)
[    0.052225] pid_max: default: 32768 minimum: 301
[    0.057783] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, line
[    0.066284] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes,
[    0.080827] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, m
[    0.092208] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.100259] pinctrl core: initialized pinctrl subsystem
[    0.109580] NET: Registered protocol family 16
[    0.117299] GPIO line 18 (tp-link:ext:lna0) hogged as output/high
[    0.124466] GPIO line 19 (tp-link:ext:lna1) hogged as output/high
[    0.159972] workqueue: max_active 576 requested for napi_workq is out of ran
[    0.176037] clocksource: Switched to clocksource MIPS
[    0.183518] NET: Registered protocol family 2
[    0.189793] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096
[    0.199606] TCP established hash table entries: 1024 (order: 0, 4096 bytes, 
[    0.208534] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.216742] TCP: Hash tables configured (established 1024 bind 1024)
[    0.224301] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.231970] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.240490] NET: Registered protocol family 1
[    0.245632] PCI: CLS 0 bytes, default 32
[    0.255091] workingset: timestamp_bits=14 max_order=14 bucket_order=0
[    0.271344] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.278179] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORI
[    0.307686] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 
[    0.321044] pinctrl-single 1804002c.pinmux: 544 pins, size 68
[    0.329034] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.339440] printk: console [ttyS0] disabled
[    0.344535] 18020000.uart: ttyS0 at MMIO 0x18020000 (irq = 9, base_baud = 25
[    0.354585] printk: console [ttyS0] enabled
[    0.354585] printk: console [ttyS0] enabled
[    0.363495] printk: bootconsole [early0] disabled
[    0.363495] printk: bootconsole [early0] disabled
[    0.388005] spi-nor spi0.0: gd25q64 (8192 Kbytes)
[    0.392920] 6 fixed-partitions partitions found on MTD device spi0.0
[    0.399384] Creating 6 MTD partitions on "spi0.0":
[    0.404285] 0x000000000000-0x000000020000 : "u-boot"
[    0.410563] 0x000000020000-0x000000030000 : "partition-table"
[    0.417611] 0x000000030000-0x000000040000 : "info"
[    0.423688] 0x000000040000-0x0000007c0000 : "firmware"
[    0.430160] 0x0000007c0000-0x0000007f0000 : "config"
[    0.436538] 0x0000007f0000-0x000000800000 : "art"
[    0.445059] libphy: Fixed MDIO Bus: probed
[    0.768479] libphy: ag71xx_mdio: probed
[    0.773748] libphy: ar8xxx-mdio: probed
[    0.785848] switch0: Atheros AR8229 rev. 1 switch registered on mdio.0
[    1.145976] ag71xx 19000000.eth: connected to PHY at mdio.0:1f:04 [uid=004dd
[    1.156116] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode: mii
[    1.162648] i2c /dev entries driver
[    1.169430] NET: Registered protocol family 10
[    1.180091] random: fast init done
[    1.184945] Segment Routing with IPv6
[    1.188879] NET: Registered protocol family 17
[    1.193512] bridge: filtering via arp/ip/ip6tables is no longer available by
[    1.206679] 8021q: 802.1Q VLAN Support v1.8
[    1.212391] hctosys: unable to open rtc device (rtc0)
[    1.218812] /dev/root: Can't open blockdev
[    1.223069] VFS: Cannot open root device "(null)" or unknown-block(0,0): err
[    1.230673] Please append a correct "root=" boot option; here are the availa
[    1.239162] 1f00             128 mtdblock0 
[    1.239166]  (driver?)
[    1.245826] 1f01              64 mtdblock1 
[    1.245829]  (driver?)
[    1.252485] 1f02              64 mtdblock2 
[    1.252488]  (driver?)
[    1.259138] 1f03            7680 mtdblock3 
[    1.259140]  (driver?)
[    1.265792] 1f04             192 mtdblock4 
[    1.265795]  (driver?)
[    1.272452] 1f05              64 mtdblock5 
[    1.272455]  (driver?)
[    1.279103] Kernel panic - not syncing: VFS: Unable to mount root fs on unkn
[    1.287482] Rebooting in 1 seconds..


05.05.20213783Base systemBug ReportVery LowCriticalMT7621 WiFi driver crash openwrt-21.02Unconfirmed Task Description

Summary

The WiFi driver crashes on an MT7621 router running OpenWRT21.02rc1 (5 commits further to be exact 6f053e5b).
The router used is an InvizBox Go (WiFi only) i.e. MT7621 + MT7603E (not supported by OpenWRT just yet - I’m working on getting there). I don’t believe the issue is specific to that hardware though.

The crash seems to happen in AP/STA mode when an AP gets added to the configuration and the STA was connected (I’ll add more information if I come across more scenarios). I’m not able to reproduce consistently at the moment.
Once crashed the WiFi stack is not usable anymore until a reboot. Following a reboot, things are back to normal.

The crash stack is as follow:

[  726.587920] ------------[ cut here ]------------
[  726.597570] WARNING: CPU: 0 PID: 1767 at backports-5.10.16-1/net/mac80211/ieee80211_i.h:1468 sta_info_alloc+0x5c4/0x5fc [mac80211]
[  726.621113] Modules linked in: xt_connlimit pppoe ppp_async nf_conncount iptable_nat xt_state xt_nat xt_helper xt_conntrack xt_connmark xt_connbytes xt_REDIRECT xt_MASQUERADEr
[  726.621458]  algif_skcipher algif_rng algif_hash algif_aead af_alg sha256_generic libsha256 sha1_generic jitterentropy_rng drbg md5 hmac echainiv des_generic libdes cbc authec
[  726.859235] CPU: 0 PID: 1767 Comm: hostapd Not tainted 5.4.111 #0
[  726.871379] Stack : 8e375fb4 8007ce5c 80660000 80660d78 806c0000 80660d40 8065fe94 8e257a34
[  726.888032]         80800000 8dc34188 806aa6e3 805f993c 00000000 00000001 8e2579d8 72c69b9f
[  726.904659]         00000000 00000000 80830000 00000000 30232031 0000014b 2e352064 31312e34
[  726.921286]         00000000 00000024 00000000 000d1c63 80000000 806c0000 00000000 8e3075b8
[  726.937913]         00000009 8e146480 00000005 00000002 00000000 8034dfbc 00000000 80800000
[  726.954538]         ...
[  726.959397] Call Trace:
[  726.964284] [<8000b64c>] show_stack+0x30/0x100
[  726.973153] [<80542370>] dump_stack+0xa4/0xdc
[  726.981832] [<8002bee0>] __warn+0xc0/0x10c
[  726.989981] [<8002bf88>] warn_slowpath_fmt+0x5c/0xac
[  727.000018] [<8e3075b8>] sta_info_alloc+0x5c4/0x5fc [mac80211]
[  727.011712] [<8e3259b0>] ieee80211_nan_func_match+0x3d88/0x4410 [mac80211]
[  727.025846] ---[ end trace bc705bf94f0c5c24 ]---

Steps to reproduce

The following steps do not necessarily lead to the crash. I expect them to be what leads to it but am still unsure. The stack may show the way to a better reproduction scenario...

On an MT7621 router setup as AP/STA, add a second AP and possibly a third one.
Call /etc/init.d/network reload after each change

Current behaviour

Crash stack is visible in console/dmesg and the STA fails to reconnect (which also leads all APs to become not accessible - expected).

Expected behaviour

No crash

Notes This crash was also observed on builds before the rc1 tag. I don’t know the conditions leading to these crashes.

I had saved one older crash stack (truncated by console unfortunately) as a reference (early 21.02 branch when I started testing in preparation for release):

[ 1939.972549] ------------[ cut here ]------------
[ 1939.982051] WARNING: CPU: 2 PID: 2079 at backports-5.10.16-1/net/mac80211/ieee80211_i.h:1468 sta_info_alloc+0x5c4/0x]
[ 1940.005526] Modules linked in: xt_connlimit pppoe ppp_async nf_conncount iptable_nat xt_state xt_nat xt_helper xt_cor
[ 1940.005842]  algif_skcipher algif_rng algif_hash algif_aead af_alg sha256_generic libsha256 sha1_generic jitterentroc
[ 1940.243641] CPU: 2 PID: 2079 Comm: hostapd Not tainted 5.4.111 #0
[ 1940.255784] Stack : 8df75fb4 8007ce5c 80660000 80660d78 806c0000 80660d40 8065fe94 8dd01a34
[ 1940.272451]         80800000 8fe51fc8 806aa6e3 805f993c 00000002 00000001 8dd019d8 91468ee6
[ 1940.289110]         00000000 00000000 80830000 00000000 30232031 0000012f 2e352064 31312e34
[ 1940.305752]         00000000 00000060 00000000 0003b7b9 80000000 806c0000 00000000 8df075b8
[ 1940.322392]         00000009 8fed4480 00000005 00000002 00000000 8034dfbc 00000008 80800008
[ 1940.339021]         ...
[ 1940.343883] Call Trace:
[ 1940.348778] [<8000b64c>] show_stack+0x30/0x100
[ 1940.357652] [<80542370>] dump_stack+0xa4/0xdc
[ 1940.366336] [<8002bee0>] __warn+0xc0/0x10c
[ 1940.374487] [<8002bf88>] warn_slowpath_fmt+0x5c/0xac
[ 1940.384532] [<8df075b8>] sta_info_alloc+0x5c4/0x5fc [mac80211]
[ 1940.396280] [<8df259b0>] ieee80211_nan_func_match+0x3d88/0x4410 [mac80211]
[ 1940.410460] ---[ end trace dda71e821ee728c4 ]---
06.05.20213787Base systemBug ReportVery LowMedium21.02 RC1: BUG: Bad page state in process swapper/0openwrt-21.02Unconfirmed Task Description

Device used: RT-AC57U (mt7621 based device)
Version used: 21.02 RC1
Steps to reproduce: This ended up in my kernel log after a few days of uptime. I am unsure what exactly caused the issue.

I am currently beta testing the new 21.02 RC1 release on two different devices. Stability seems very good, but I did run into an issue with the aforementioned RT-AC57U. I found this stacktrace in the kernel log. I am unsure if this caused the network to go down, since I am not sure if I was using the network at that time. Does anyone have any idea what is causing this?

[410758.374134] BUG: Bad page state in process swapper/0  pfn:05edc
[410758.386105] page:809236f0 refcount:-1 mapcount:0 mapping:00000000 index:0x0
[410758.400121] flags: 0x0()
[410758.405331] raw: 00000000 00000000 00000122 00000000 00000000 00000000 ffffffff ffffffff
[410758.421588] raw: 00000000
[410758.426956] page dumped because: nonzero _refcount
[410758.436644] Modules linked in: xt_connlimit pppoe ppp_async nf_conncount iptable_nat xt_state xt_nat xt_helper xt_conntrack xt_connmark xt_connbytes xt_REDIRECT xt_MASQUERADE xt_FLOWOFFLOAD xt_CT wireguard pppox ppp_generic nf_nat_pptp nf_nat nf_flow_table_hw nf_flow_table nf_conntrack_rtcache nf_conntrack_pptp nf_conntrack_netlink nf_conntrack mt76x2e mt76x2_common mt76x02_lib mt7603e mt76 mac80211 libchacha20poly1305 libblake2s ipt_REJECT cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_recent xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_ecn xt_dscp xt_comment xt_TCPMSS xt_LOG xt_HL xt_DSCP xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc sch_cake poly1305_mips nf_reject_ipv4 nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 libcurve25519_generic libblake2s_generic iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat chacha_mips br_netfilter sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit
[410758.436829]  act_mirred ledtrig_usbport xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net 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 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb ip6_udp_tunnel udp_tunnel kpp leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd gpio_button_hotplug usbcore nls_base usb_common
[410758.712580] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.111 #0
[410758.724692] Stack : 00000000 80840000 00000003 8007d6e0 00000000 00000000 00000000 00000000
[410758.741481]         00000000 00000000 00000000 00000000 00000000 00000001 87c0db80 5fc2ce17
[410758.758268]         87c0dc18 00000000 00000000 00000000 00000038 805e1804 2e352064 31312e34
[410758.775053]         00000000 00004fd5 00000000 70617773 00000000 87c0db60 00000000 80840000
[410758.791840]         80604b20 806b0000 00000000 806d7f20 00000000 80359e2c 00000000 80810000
[410758.808627]         ...
[410758.813649] Call Trace:
[410758.813663] [<8007d6e0>] 0x8007d6e0
[410758.825779] [<805e1804>] 0x805e1804
[410758.832880] [<80359e2c>] 0x80359e2c
[410758.839978] [<8000b05c>] 0x8000b05c
[410758.847075] [<8000b064>] 0x8000b064
[410758.854173] [<805c6f9c>] 0x805c6f9c
[410758.861271] [<8014dabc>] 0x8014dabc
[410758.868420] [<80150ca4>] 0x80150ca4
[410758.875519] [<804a8b28>] 0x804a8b28
[410758.882662] [<806e0000>] 0x806e0000
[410758.889769] [<80151c80>] 0x80151c80
[410758.896866] [<80063508>] 0x80063508
[410758.903966] [<80150015>] 0x80150015
[410758.911063] [<804326ac>] 0x804326ac
[410758.918163] [<8001e448>] 0x8001e448
[410758.925262] [<80152bc4>] 0x80152bc4
[410758.932359] [<80433040>] 0x80433040
[410758.939456] [<800939cc>] 0x800939cc
[410758.946554] [<803dd720>] 0x803dd720
[410758.953652] [<800104dc>] 0x800104dc
[410758.960754] [<80433858>] 0x80433858
[410758.967852] [<80433acc>] 0x80433acc
[410758.974952] [<805e7d1c>] 0x805e7d1c
[410758.982053] [<80030768>] 0x80030768
[410758.989150] [<802f8404>] 0x802f8404
[410758.996249] [<80006c28>] 0x80006c28
[410759.003344] 
[410759.006466] Disabling lock debugging due to kernel taint
11.05.20213798Base systemBug ReportVery LowMediumflashing the install image leaves overlay filesystem in...openwrt-21.02Unconfirmed Task Description

I’m using the image builder for 21.02.0-rc1, specifically the one targeting bcm2709.

When I flash an install image, the resulting system image references an overlay filesystem (an ext4), the superblock of which is beyond the end of the install image itself. Therefore, flashing an install image may leave files from a previous overlay filesystem in place. This is counterintuitive, because I expected that flashing the install image would leave the OS in a well-defined state.

As a workaround, I’ve been appending 64KB of zeroes to the end of the install image, which seems to fix the problem.

Reproduction steps:

1. Build an image, flash it, boot it
2. Create files in the overlay filesystem
3. Remove card and reflash; files in the overlay filesystem remain

Thanks for your time!


13.05.20213808Base systemBug ReportVery LowHighASUS RT-AC57N wrong wan interfaceopenwrt-21.02Unconfirmed Task Description

After installation LEDE 21.02-rc1 on ASUS RT-AC57N wan interface was assigned to eth0, not eth0.2 as it was on 19.07, thus it cannot obtain an IP address from ISP.

I’ve tried to copy interface setup from 19.07, as:

config interface ‘wan’

      option ifname 'eth0.2'
      option proto 'dhcp'

config device ‘wan_eth0_2_dev’

      option name 'eth0.2'
      option macaddr '40:b0:76:9d:89:f0'

but it also has not helped.


13.05.20213809Base systemBug ReportVery LowHighv21.02.0-rc1 reports false missing "which" on fedora 34openwrt-21.02New Task Description

i use fedora 34, installed the required software and “which” is available on the command line

[oli@lucy openwrt]$ which which | grep which
which ()

eval ${which_declare} ) | /usr/bin/which --tty-only --read-alias --read-functions --show-tilde --show-dot "$@"

but when i run “./scripts/feeds update -a” i get:
hecking ‘perl’... ok.
Checking ‘python2-cleanup’... ok.
Checking ‘python’... ok.
Checking ‘python3’... ok.
Checking ‘git’... ok.
Checking ‘file’... ok.
Checking ‘rsync’... ok.
Checking ‘which’... failed.
Checking ‘ldconfig-stub’... ok.

Build dependency: Please install ‘which’

Prerequisite check failed. Use FORCE=1 to override.
gmake: *** [/home/oli/openwrt/include/toplevel.mk:180: staging_dir/host/.prereq-build] Fehler 1

[oli@lucy ~]$ rpm -qa | grep which
which-2.21-26.fc34.x86_64

corrected the meta infos of this ticket and copied it from https://bugs.openwrt.org/index.php?do=details&task_id=3805

19.05.20213817Base systemBug ReportVery LowMediumSSIDs on 5GHz radio dissapear a few days after bootopenwrt-21.02Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

BT homehub 5a (xrx200)

- Software versions of OpenWrt/LEDE release, packages, etc.

21.02-rc1

- Steps to reproduce

 

after upgrade from 19.07 all worked, then after a few days my 5GHz SSID was no longer visible, tried disable/enable the radio0, that didn’t help, radio1 on 2.4GHz still working, had to reboot to get 5GHz back

after another 5.75 days, same happened again.

most recent messages in dmesg

[508519.675343] device wlan0 left promiscuous mode
[508519.678732] br-lan: port 3(wlan0) entered disabled state
[508519.713414] ath10k_pci 0000:02:00.0: mac flush null vif, drop 0 queues 0xffff
[508520.786031] ath10k_pci 0000:02:00.0: 10.1 wmi init: vdevs: 16  peers: 127  tid: 256
[508520.802066] ath10k_pci 0000:02:00.0: wmi print 'P 128 V 8 T 410'
[508520.806810] ath10k_pci 0000:02:00.0: wmi print 'msdu-desc: 1424  sw-crypt: 0 ct-sta: 0'
[508520.815553] ath10k_pci 0000:02:00.0: wmi print 'alloc rem: 24984 iram: 38672'
[508520.884894] ath10k_pci 0000:02:00.0: pdev param 0 not supported by firmware
[508520.898436] ath10k_pci 0000:02:00.0: rts threshold -1
[508520.912045] br-lan: port 3(wlan0) entered blocking state
[508520.916090] br-lan: port 3(wlan0) entered disabled state
[508520.922193] device wlan0 entered promiscuous mode
22.05.20213821Base systemBug ReportVery LowCriticalRandom link down on RB 750Gr3openwrt-21.02Unconfirmed Task Description

HW: Mikrotik Routerboard 750Gr3
SW: linux version 5.4.119 (cezary@eko.one.pl) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r15819-0011c7ad12)) #0 SMP Fri May 14 21:36:47 2021

I am randomly loosing connection with the router for a few seconds. Here is the system log after the link is reestablished:

Sat May 22 16:32:05 2021 kern.info kernel: [24372.328509] mt7530 mdio-bus:1f lan2: Link is Down
Sat May 22 16:32:05 2021 kern.info kernel: [24372.333341] br-lan: port 1(lan2) entered disabled state
Sat May 22 16:32:05 2021 daemon.notice netifd: Network device 'lan2' link is down
Sat May 22 16:32:06 2021 daemon.notice netifd: bridge 'br-lan' link is down
Sat May 22 16:32:06 2021 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat May 22 16:32:09 2021 kern.info kernel: [24376.424716] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
Sat May 22 16:32:09 2021 kern.info kernel: [24376.432249] br-lan: port 1(lan2) entered blocking state
Sat May 22 16:32:09 2021 kern.info kernel: [24376.437506] br-lan: port 1(lan2) entered forwarding state
Sat May 22 16:32:09 2021 daemon.notice netifd: Network device 'lan2' link is up
Sat May 22 16:32:09 2021 daemon.notice netifd: bridge 'br-lan' link is up
Sat May 22 16:32:09 2021 daemon.notice netifd: Interface 'lan' has link connectivity
Sat May 22 16:32:10 2021 kern.info kernel: [24377.448578] mt7530 mdio-bus:1f lan2: Link is Down
Sat May 22 16:32:10 2021 kern.info kernel: [24377.453413] br-lan: port 1(lan2) entered disabled state
Sat May 22 16:32:10 2021 daemon.notice netifd: Network device 'lan2' link is down
Sat May 22 16:32:11 2021 daemon.notice netifd: bridge 'br-lan' link is down
Sat May 22 16:32:11 2021 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat May 22 16:32:13 2021 kern.info kernel: [24380.520779] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
Sat May 22 16:32:13 2021 kern.info kernel: [24380.528342] br-lan: port 1(lan2) entered blocking state
Sat May 22 16:32:13 2021 kern.info kernel: [24380.533562] br-lan: port 1(lan2) entered forwarding state
Sat May 22 16:32:13 2021 daemon.notice netifd: Network device 'lan2' link is up
Sat May 22 16:32:13 2021 daemon.notice netifd: bridge 'br-lan' link is up
Sat May 22 16:32:13 2021 daemon.notice netifd: Interface 'lan' has link connectivity
Sat May 22 16:32:14 2021 kern.info kernel: [24381.544635] mt7530 mdio-bus:1f lan2: Link is Down
Sat May 22 16:32:14 2021 kern.info kernel: [24381.549486] br-lan: port 1(lan2) entered disabled state
Sat May 22 16:32:14 2021 daemon.notice netifd: Network device 'lan2' link is down
Sat May 22 16:32:15 2021 daemon.notice netifd: bridge 'br-lan' link is down
Sat May 22 16:32:15 2021 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat May 22 16:32:17 2021 kern.info kernel: [24384.616828] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
Sat May 22 16:32:17 2021 kern.info kernel: [24384.624361] br-lan: port 1(lan2) entered blocking state
Sat May 22 16:32:17 2021 kern.info kernel: [24384.629611] br-lan: port 1(lan2) entered forwarding state
Sat May 22 16:32:17 2021 daemon.notice netifd: Network device 'lan2' link is up
Sat May 22 16:32:17 2021 daemon.notice netifd: bridge 'br-lan' link is up
Sat May 22 16:32:17 2021 daemon.notice netifd: Interface 'lan' has link connectivity
Sat May 22 16:32:18 2021 kern.info kernel: [24385.640683] mt7530 mdio-bus:1f lan2: Link is Down
Sat May 22 16:32:18 2021 kern.info kernel: [24385.645511] br-lan: port 1(lan2) entered disabled state
Sat May 22 16:32:18 2021 daemon.notice netifd: Network device 'lan2' link is down
Sat May 22 16:32:19 2021 daemon.notice netifd: bridge 'br-lan' link is down
Sat May 22 16:32:19 2021 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat May 22 16:32:21 2021 kern.info kernel: [24388.712887] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
Sat May 22 16:32:21 2021 kern.info kernel: [24388.720458] br-lan: port 1(lan2) entered blocking state
Sat May 22 16:32:21 2021 kern.info kernel: [24388.725684] br-lan: port 1(lan2) entered forwarding state
Sat May 22 16:32:21 2021 daemon.notice netifd: Network device 'lan2' link is up
Sat May 22 16:32:21 2021 daemon.notice netifd: bridge 'br-lan' link is up
Sat May 22 16:32:21 2021 daemon.notice netifd: Interface 'lan' has link connectivity
Sat May 22 16:32:22 2021 kern.info kernel: [24389.736743] mt7530 mdio-bus:1f lan2: Link is Down
Sat May 22 16:32:22 2021 kern.info kernel: [24389.741572] br-lan: port 1(lan2) entered disabled state
Sat May 22 16:32:22 2021 daemon.notice netifd: Network device 'lan2' link is down
Sat May 22 16:32:23 2021 daemon.notice netifd: bridge 'br-lan' link is down
Sat May 22 16:32:23 2021 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat May 22 16:32:25 2021 kern.info kernel: [24392.808941] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
Sat May 22 16:32:25 2021 kern.info kernel: [24392.816473] br-lan: port 1(lan2) entered blocking state
Sat May 22 16:32:25 2021 kern.info kernel: [24392.821720] br-lan: port 1(lan2) entered forwarding state
Sat May 22 16:32:25 2021 daemon.notice netifd: Network device 'lan2' link is up
Sat May 22 16:32:25 2021 daemon.notice netifd: bridge 'br-lan' link is up
Sat May 22 16:32:25 2021 daemon.notice netifd: Interface 'lan' has link connectivity
Sat May 22 16:32:26 2021 kern.info kernel: [24393.832799] mt7530 mdio-bus:1f lan2: Link is Down
Sat May 22 16:32:26 2021 kern.info kernel: [24393.837630] br-lan: port 1(lan2) entered disabled state
Sat May 22 16:32:26 2021 daemon.notice netifd: Network device 'lan2' link is down
Sat May 22 16:32:27 2021 daemon.notice netifd: bridge 'br-lan' link is down
Sat May 22 16:32:27 2021 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat May 22 16:32:30 2021 kern.info kernel: [24396.904992] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
Sat May 22 16:32:30 2021 kern.info kernel: [24396.912523] br-lan: port 1(lan2) entered blocking state
Sat May 22 16:32:30 2021 kern.info kernel: [24396.917771] br-lan: port 1(lan2) entered forwarding state
Sat May 22 16:32:30 2021 daemon.notice netifd: Network device 'lan2' link is up
Sat May 22 16:32:30 2021 daemon.notice netifd: bridge 'br-lan' link is up
Sat May 22 16:32:30 2021 daemon.notice netifd: Interface 'lan' has link connectivity
Sat May 22 16:32:31 2021 kern.info kernel: [24397.928855] mt7530 mdio-bus:1f lan2: Link is Down
Sat May 22 16:32:31 2021 kern.info kernel: [24397.933692] br-lan: port 1(lan2) entered disabled state
Sat May 22 16:32:31 2021 daemon.notice netifd: Network device 'lan2' link is down
Sat May 22 16:32:32 2021 daemon.notice netifd: bridge 'br-lan' link is down
Sat May 22 16:32:32 2021 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat May 22 16:32:34 2021 kern.info kernel: [24401.001066] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
Sat May 22 16:32:34 2021 kern.info kernel: [24401.008643] br-lan: port 1(lan2) entered blocking state
Sat May 22 16:32:34 2021 kern.info kernel: [24401.013868] br-lan: port 1(lan2) entered forwarding state
Sat May 22 16:32:34 2021 daemon.notice netifd: Network device 'lan2' link is up
Sat May 22 16:32:34 2021 daemon.notice netifd: bridge 'br-lan' link is up
Sat May 22 16:32:34 2021 daemon.notice netifd: Interface 'lan' has link connectivity
Sat May 22 16:32:35 2021 kern.info kernel: [24402.024917] mt7530 mdio-bus:1f lan2: Link is Down
Sat May 22 16:32:35 2021 kern.info kernel: [24402.029756] br-lan: port 1(lan2) entered disabled state
Sat May 22 16:32:35 2021 daemon.notice netifd: Network device 'lan2' link is down
Sat May 22 16:32:36 2021 daemon.notice netifd: bridge 'br-lan' link is down
Sat May 22 16:32:36 2021 daemon.notice netifd: Interface 'lan' has link connectivity loss
Sat May 22 16:32:41 2021 kern.info kernel: [24408.169236] mt7530 mdio-bus:1f lan2: Link is Up - 100Mbps/Full - flow control rx/tx
Sat May 22 16:32:41 2021 kern.info kernel: [24408.176955] br-lan: port 1(lan2) entered blocking state
Sat May 22 16:32:41 2021 kern.info kernel: [24408.182189] br-lan: port 1(lan2) entered forwarding state
Sat May 22 16:32:41 2021 daemon.notice netifd: Network device 'lan2' link is up
Sat May 22 16:32:41 2021 daemon.notice netifd: bridge 'br-lan' link is up
Sat May 22 16:32:41 2021 daemon.notice netifd: Interface 'lan' has link connectivity


24.05.20213823Base systemBug ReportVery LowCriticalethernet down after rebootopenwrt-21.02Unconfirmed Task Description

the problemi is with turris omnia and owrt 21.02-rc1 , fresh installation, no additional package
the turris is connected to
wan device
a second wan device (lan4)
a raspberry (lan3)
a switch (lan2)

all work with the 19.07.7
logread https://pastebin.com/XbzQL9aN ip address https://pastebin.com/9hcES8WQ

after upgrading to 21.02.0-rc1 at first reboot , i have in the serial console an error about “partx: /dev/mmcblk0 delete/adding” , i don’t know if it is normal or not
https://pastebin.com/g3CL8j1f

at first boot , here logread https://pastebin.com/V7Tsuvbd
i lost the device on the lan2 , it says “LOWERLAYERDOWN” and no led light on, but the user is connected https://pastebin.com/0033LAnL

if i reboot , here logread https://pastebin.com/8yxyvyL5 , i lost the other lan3 device , no light on https://pastebin.com/BmwRj5B3

no matter if i reboot the device or power it on/off
the front panel led litgh on according to the ip address state (UP/DOWN)

reverting to 19.07.7 , solve the problem

tried 3 time to flash 21.02 , same beahviour

 


26.05.20213828Base systemBug ReportVery LowLowNAT Reflection is not workingopenwrt-21.02Unconfirmed Task Description

Forwarding port 443 from WAN to an internal machine on LAN works from outside but not LAN. The https access from LAN to the WAN public IP is not working. It looked like the packet is dropped after NAT PREROUTING.

 


26.05.20213829Base systemBug ReportVery LowHighNo WiFi after upgrading from 19.07 to 21.02openwrt-21.02Unconfirmed Task Description

Device : Zyxel P2812 F1
Version : 21.02 snapshot r16824-91abeebd3b

Steps:
- Router with 19.07.4
- Upgrade to 21.02 (this is a custom build version because the version on the openwrt-download does not work (bug 2226))
- after reboot the WiFi device is not available
- run WiFi up resuls in message in logread:

Wed May 26 22:30:03 2021 daemon.notice netifd: radio0 (2491): Could not find PHY for device ‘radio0’ Wed May 26 22:30:03 2021 daemon.notice netifd: radio0 (2499): WARNING: Variable ‘data’ does not exist or is not an array/object


Attached is dmesg-log and config


26.05.20213830Base systemBug ReportVery LowMediumOpenVPN Client Using TCP Connection Has MTU or TCPMSS I...openwrt-21.02Unconfirmed Task Description

OpenVPN Client connects to a TCP based OpenVPN server connects fine. However, the connections to remote network servers connect but can’t transfer data. The mangle rule with clamp-mss-to-pmtu won’t receive any data. Setting tcpmss to something around 1000 will only receive the first 100 - 200 bytes and hang. It’s not working until reduced tcpmss to 59.

iptables -t nat -A postrouting_rule -o tun0 -j MASQUERADE
iptables -t mangle -A POSTROUTING -o tun0 -p tcp -m tcp –tcp-flags SYN,RST SYN -j TCPMSS –set-mss 59
#iptables -t mangle -A POSTROUTING -o tun0 -p tcp -m tcp –tcp-flags SYN,RST SYN -j TCPMSS –clamp-mss-to-pmtu

29.05.20213835Base systemBug ReportVery LowLow [MT7621] Hardware flow offloading doesn't work for PPP...openwrt-21.02Unconfirmed Task Description

Netgear R6220
OpenWrt 21.02-SNAPSHOT r16122-c213

Hardware flow offloading doesn’t work for PPPoE with VLAN (802.1q), so LAN to WAN is slow and CPU heavy. It does work on 19,07, though.

30.05.20213839Base systemBug ReportVery LowHighXiaomi 4A Gigabit link speed auto negotiationopenwrt-21.02Unconfirmed Task Description

- Device problem occurs on

Xiaomi Mi Router 4A Gigabit Edition

- Software versions of OpenWrt/LEDE release, packages, etc.

OpenWRT 21.02-rc2

- Description

The link speed auto-negotiation is broken. I’ve a 1Gbps switch and a 4-lines ethernet cable (pins 1 2 3 6). It should be possible to achieve a max speed of 100Mbps full duplex. When I connect the switch to the WAN port of the router, the link speed shows up as 1Gbps full duplex (in the router).

Ethernet connectivity remains non-functional unless I set a proper speed and duplex (ex.

ethtool -s wan speed 100 duplex full autoneg off

).

01.06.20213841Base systemBug ReportVery LowMediumHardware flow offloading sometimes causes network to sl...openwrt-21.02Unconfirmed Task Description

I flashed OpenWrt 21.02 RC2 to the following devices:
Ubiquiti EdgeRouter X
MikroTik RouterBOARD 760iGS

The following are enabled:
- Hardflow Flow Offloading
- Packet Steering
- luci-app-sqm: cake, piece-of-cake, 0 download/ 50000 upload
- Firewall and all other settings default (after installation)

I have a Huawei AX3 Pro in bridge mode, connected to one of the ethernet ports of either devices above.

Issue:
When scrolling down on any app like YouTube, Facebook, an RSS app from an Android phone, sometimes the contents don’t load or is taking more than 15 seconds to load. This is happening with 2 Android phones, also when using a 4G connection from my provider, this issue doesn’t happen. So this is not a problem with the mobile phones.

I have tried the following combinations which didn’t fix the issue:

Hardflow Flow Offload (on)
Packet Steering (off)
SQM (off)


Hardflow Flow Offload (on)
Packet Steering (on)
SQM (off)
— Hardflow Flow Offload (on)
Packet Steering (off)
SQM (on)

But turning off Hardflow Flow Offload seems to fix it. Unfortunately I have a 1 GB connection, so my downloads suffer if I turn this off.

When I flashed OpenWrt 19.07 to Ubiquiti EdgeRouter X with the same settings above, I didn’t encounter the issue. I have tried flashing again OpenWrt 21.02 RC2 from 19.07 the 2nd time, and using the same settings, and the issue back again.

03.06.20213846Base systemBug ReportVery LowLowppp-multilink in build system cannot replace ppp, but c...openwrt-21.02Unconfirmed Task Description

`PACKAGE_ppp-multilink` seems to provide the `ppp`-daemon with added multilink functionality. So it should be possible to select `ppp-multilink` instead of `ppp`. But in the configuration system the dependencies are not set that way.

If some package required `ppp`, it still cannot be unselected if `ppp-multilink` is selected (see attached screenshot), as it is with many other packages where there are alternatives for the same functionality. Furthermore, `PACKAGE_ppp-multilink=y` will produce a clash with `PACKAGE_ppp=y` when it comes to the install step, see Task #3845.

`ppp` has as `Selected by`-dependencies:

  Selected by [y]:
    - PACKAGE_modemmanager [=y]
    - PACKAGE_pppossh [=y] && (PACKAGE_dropbear [=y] || PACKAGE_openssh-client [=n])
  Selected by [m]:
    - PACKAGE_openfortivpn [=m]
    - PACKAGE_sstp-client [=m]
  Selected by [n]:
    - MODULE_DEFAULT_ppp [=n] && TARGET_PER_DEVICE_ROOTFS [=n] && m && MODULES [=y]
    - PACKAGE_rp-pppoe-sniff [=n] && BROKEN [=n]
    - PACKAGE_pptpd [=n]

where `PACKAGE_ppp-multilink` has none at all.

As `Selects`-dependency, they both have (in different order, but same items):

Selects: PACKAGE_kmod-ppp [=y] && PACKAGE_libc [=y] && PACKAGE_librt [=y] && PACKAGE_libpthread [=y]
04.06.20213853Base systemBug ReportVery LowHighath79: NETGEAR WNDR4300v2 Bricked on Power Cycle After ...openwrt-21.02Unconfirmed Task Description

On a NETGEAR WNDR4300v2 with stock firmware I flash OpenWrt. It works fine after flash (not power cycled *yet*). On the first power cycle the device is fails to start. I’m able to restore the factory firmware using nmrpflash.

Device: NETGEAR WNDR4300v2
Factory firmware: V1.0.0.58
OpenWrt firmware: openwrt-21.02.0-rc2-ath79-nand-netgear_wndr4300-v2-squashfs-factory.img

I checked the OpenWrt firmware checksum. I did a factory install. On first boot, OpenWrt works just fine. I’m able to adjust settings and Save & Apply them. If I power-cycle the device it fails to boot. The problem exists even if I don’t change any settings in OpenWrt. The Power led is amber continuously. The led for ports 1-4 flash once then remain off. After about 18 seconds the cycle repeats.

I’m able to restore the factory firmware by connecting to port 1. I set a static IP 192.168.1.100/255.255.255.0 Gateway:192.168.1.1. I ran the nmrpflash tool and power On the unit:

> sudo ./nmrpflash -i enp0s25 -f WNDR4300v2-V1.0.0.58.img
Waiting for physical connection.
Advertising NMRP server on enp0s25 ... |
Received configuration request from xx:yy:...
Sending configuration: 10.164.183.252/24.
Received upload request: filename 'firmware'.
Uploading WNDR4300v2-V1.0.0.58.img ... OK
Waiting for remote to respond.
Remote finished. Closing connection.
Reboot your device now.

Once completed the factory firmware is restored.


15.06.20213879Base systemBug ReportVery LowLowIncorrect switch config for TP-Link Archer C2 AC750openwrt-21.02Unconfirmed Task Description

Model TP-Link Archer C2 v1
Architecture MediaTek MT7620A ver:2 eco:5
Firmware Version OpenWrt 21.02.0-rc2 r16122-c2139eef27 / LuCI openwrt-21.02 branch git-21.148.49484-14511e5

The Archer C2 has a little unusual switch setup, in that the SoC itself only has an unused 100Mb switch and instead there is an extra RTL8367B chip. We can only assume TP-Link wanted to make this a 1Gb device, despite using a 100Mb SoC. (and indeed, the 1Gb ports is why I got this particular cheap device)

OpenWRT 19.07.7 handled this beautifully, as it simply did not show the switch0, neither in UCI nor in Luci, though the RTL8367B chip is labeled switch1 in stead of the more usual switch0

When clean upgrading (so removing and rebuilding all config) to 21.02.0-rc2 I noticed that the internal switch was now populated in UCI and displayed in Luci
The Archer C2 does work, switch1 is configured as expected, but the presence of switch0 seems to cause Luci to display an error “Switch switch0 has an unknown topology - the VLAN settings might not be accurate.” and further prevents Luci from updating switch1 settings.

So the presence of switch0 in UCI is confusing and unneeded, and also prevents Luci from working.

Manually removing the switch0 section from /etc/config/network makes it all work again.

/etc/config/network as generated on 19.07.7 (only the switch section)

config switch
        option name 'switch1'
        option reset '1'
        option enable_vlan '1'
        option max_length '3'

config switch_vlan
        option device 'switch1'
        option vlan '1'
        option ports '6t 1 2 3 4'

config switch_vlan
        option device 'switch1'
        option vlan '2'
        option ports '6t 0'

/etc/config/network as generated on 21.02.0-rc2 (only the switch section)

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '0'

config switch
        option name 'switch1'
        option reset '1'
        option enable_vlan '1'
        option enable_vlan4k '1'
        option max_length '3'

config switch_vlan
        option device 'switch1'
        option vlan '1'
        option ports '6t 1 2 3 4'

config switch_vlan
        option device 'switch1'
        option vlan '2'
        option ports '6t 0'

so to restate, after manually removing the extra switch0 from rc2, it all was normal again

17.06.20213882Base systemBug ReportVery LowLowLamobo R1 "Cannot attach to PHY" on all openwrt-21.02.0...openwrt-21.02Unconfirmed Task Description

On all RC of new 21.02.0,

no eth0 link

Model: Lamobo R1

root@OpenWrt:/# dmesg | egrep “mac|net|switch|dev|eth” [ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] Kernel command line: console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait
[ 0.000973] Console: colour dummy device 80×30 [ 0.058749] usbcore: registered new device driver usb
[ 0.058921] videodev: Linux video capture interface: v2.00
[ 0.837640] sun7i-dwmac 1c50000.ethernet: IRQ eth_wake_irq not found
[ 0.844029] sun7i-dwmac 1c50000.ethernet: IRQ eth_lpi not found
[ 0.850075] sun7i-dwmac 1c50000.ethernet: PTP uses main clock
[ 0.855848] sun7i-dwmac 1c50000.ethernet: no reset control found
[ 0.893805] mousedev: PS/2 mouse device common for all mice
[ 0.900580] i2c /dev entries driver
[ 0.939679] input: axp20x-pek as /devices/platform/soc/1c2ac00.i2c/i2c-0/0-0034/axp20x-pek/input/input0
[ 1.106169] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 1.119132] can: controller area network core (rev 20170425 abi 9)
[ 1.165248] sun7i-dwmac 1c50000.ethernet: IRQ eth_wake_irq not found
[ 1.171648] sun7i-dwmac 1c50000.ethernet: IRQ eth_lpi not found
[ 1.177695] sun7i-dwmac 1c50000.ethernet: PTP uses main clock
[ 1.183469] sun7i-dwmac 1c50000.ethernet: no reset control found
[ 1.222647] mmc0: host does not support reading read-only switch, assuming write-enable
[ 1.301829] sun7i-dwmac 1c50000.ethernet: Version ID not available
[ 1.308026] sun7i-dwmac 1c50000.ethernet: DWMAC1000
[ 1.313037] sun7i-dwmac 1c50000.ethernet: DMA HW capability register supported
[ 1.320255] sun7i-dwmac 1c50000.ethernet: Normal descriptors
[ 1.325923] sun7i-dwmac 1c50000.ethernet: Ring mode enabled
[ 1.331758] libphy: stmmac: probed
[ 1.387839] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[ 1.396129] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.477848] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[ 1.486130] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.605748] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04
[ 1.614037] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.646062] hctosys: unable to open rtc device (rtc0)
[ 1.651700] ALSA device list:
[ 1.664460] VFS: Mounted root (squashfs filesystem) readonly on device 179:2.
[ 1.811603] usb 2-1: new high-speed USB device number 2 using ehci-platform
[ 2.073388] usb 2-1: New USB device found, idVendor=0bda, idProduct=8178, bcdDevice= 2.00
[ 2.081671] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.303484] sun7i-dwmac 1c50000.ethernet eth0: no phy at addr -1
[ 3.309504] sun7i-dwmac 1c50000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 11.333343] mount_root: switching to f2fs overlay
[ 24.766062] sun7i-dwmac 1c50000.ethernet eth0: no phy at addr -1
[ 24.772199] sun7i-dwmac 1c50000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 24.788465] br-lan: port 1(eth0.1) entered blocking state
[ 24.794046] br-lan: port 1(eth0.1) entered disabled state
[ 24.799827] device eth0.1 entered promiscuous mode


20.06.20213891Base systemBug ReportVery LowMediumD-Link DIR-878 as AP, clients connected but no network ...openwrt-21.02Unconfirmed Task Description

I have D-Link DIR-878 A1 running OpenWRT 21.02.0-rc3 (also rc2 and rc1) with a simple “dumb AP” config (included at the bottom of this message). All ethernet ports and wireless are bridged together and DHCP and firewall disabled. Router with a DHCP server (72-hour leases) and radvd for IPv6 (ULA only) is connected to DIR-878’s WAN port.

Two Android 9 devices connected to the 802.11n 2.4 GHz AP will lose network connection (an x on the wifi icon) after a few hours (3-12 hours is typical, always less than 24 hours). One of the devices will fix itself after an hour or two. The other device will stick with the broken connection as long as it stays in the AP range or is manually reconnected. The AP won’t disassociate the devices so they must be correctly replying to the inactivity polls.

I haven’t been able to figure out anything in the OpenWRT log that could be interesting. There seems to be no way to determine from the log when a device has lost the network connection. For example, other devices connecting or disconnecting don’t seem to be a reason or at least it’s not very obvious.

When one of the devices loses network connection (while staying connected to the AP) the other devices continue to work normally with good performance. Both Android 9 devices may be without network connection at the same time but the connection loss doesn’t happen at the same moment on both devices (it may be hours apart).

When a device is in the problem state, trying to ping it from a computer connected via ethernet will obviously not work. “iw dev wlan0 station get THE_MAC_ADDRESS” on DIR-878 shows no change in “tx packets” or “rx packets” when pinging is attempted. I suspect that the device doesn’t see broadcasted ARP requests and thus cannot attempt to reply to them. So no unicast echo-request packets will be sent from the computer.

If I manually add an ARP entry for the Android 9 device on the computer and try to ping again, then both tx and rx counters grow. tx growth matches the number of echo-requests sent. rx grows about twice the rate of tx. However, no echo-replies will be seen.

Trying to connect from the Android 9 devices to a computer on my LAN using a web browser and IPv4 address shows no IPv4 or ARP packets on the target computer or on the OpenWRT device.

A third device, Android 8.1, has a milder problem. It disconnects and reconnects immediately a few times a day. Sometimes it happens just a few minutes apart, sometimes several hours. It might be an unrelated problem or it might be the same problem as above except that the device notices the problem very quickly and reconnects immediately. In practice this is most visible when using a Chromecast as the controls to the Chromecast get lost for a minute when the Android 8.1 device reconnects. This behavior occurs also on 5 GHz (VHT80). (I haven’t tried the Android 9 devices on 5 GHz.)

There are a few other devices connected to the AP but I haven’t noticed problems or heard users complaining so I suspect that those don’t have this kind of issues.

All three problem devices work without any issues on 2.4 GHz if the AP is set to 802.11g using “uci set wireless.radio0.htmode=NOHT”. The three devices used to work fine with a different 2.4 GHz 802.11n AP but that AP broke.

Things that don’t help:

  • Omitting disassoc_low_ack, ieee80211w, wpa_disable_eapol_key_retries, tdls_prohibit, or dtim_period.
  • uci set wireless.default_radio0.dtim_period=1
  • uci set ‘network.@device[0].multicast_to_unicast=0’

My “dumb AP” configuration information follows.

#
# Disabled services:
#
/etc/init.d/dnsmasq disable
/etc/init.d/firewall disable
/etc/init.d/odhcpd disable
/etc/init.d/uhttpd disable

#
# /etc/config/system
#
config system
        option ttylogin '0'
        option log_size '64'
        option urandom_seed '0'
        option compat_version '1.1'
        option hostname 'wlan-dlink'
        option timezone 'EET-2EEST,M3.5.0/3,M10.5.0/4'
        option log_buffer_size '256'

config timeserver 'ntp'
        option enabled '1'
        option enable_server '0'
        option server 'fdxx:xxxx:xxxx::x'

config led 'led_wan'
        option name 'wan'
        option sysfs 'green:net'
        option trigger 'netdev'
        option mode 'link tx rx'
        option dev 'wan'

#
# /etc/config/network
#
config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option packet_steering '1'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'
        list ports 'wan'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option netmask '255.255.255.0'
        option ipaddr '192.168.0.xxx'
        option ip6addr 'fdxx:xxxx:xxxx::xxx/64'

config route
        option interface 'lan'
        option target '192.168.0.0'
        option netmask '255.255.224.0'
        option gateway '192.168.0.x'

config route6
        option interface 'lan'
        option target 'fdxx:xxxx:xxxx::/48'
        option gateway 'fdxx:xxxx:xxxx::x'

#
# /etc/config/wireless
#
config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11g'
        option path '1e140000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
        option country 'FI'
        option txpower '20'
        option channel '11'
        option htmode 'HT20'
        option log_level '0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'my_ssid'
        option encryption 'psk2'
        option key 'password123'
        option disassoc_low_ack '0'
        option ieee80211w '1'
        option wpa_disable_eapol_key_retries '1'
        option tdls_prohibit '1'
        option dtim_period '3'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'
        option htmode 'VHT80'
        option country 'FI'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'my_ssid_5GHz'
        option encryption 'psk2'
        option key 'password123'
        option disassoc_low_ack '0'
        option ieee80211w '1'
        option wpa_disable_eapol_key_retries '1'
        option tdls_prohibit '1'
        option dtim_period '3'
20.06.20213892Base systemBug ReportVery LowVery LowCannot set bss_load_update_period or chan_util_avg_peri...openwrt-21.02Unconfirmed Task Description

In the file /lib/netifd/hostapd.sh the function hostapd_common_add_bss_config() seems to lack

config_add_int bss_load_update_period chan_util_avg_period

and thus setting them via uci doesn’t work. Adding that one line fixes it.

20.06.20213893Base systemBug ReportVery LowCriticalConnecting to a WiFi network causes interoperabilityopenwrt-21.02Unconfirmed Task Description

I’m using a WRT3200ACM, one partition is OpenWRT 19.07.7 and works perfectly. The other has been flashed to 21.*(all three candidates and a snapshot tried) and when I connect to my wifi router thru the Network»Wireless»Scan Luci page the whole router becomes unresponsive(Luci and SSH). I manually cleared the configuration by using the button in the back. Then I can SSH and reboot to the first partition (I find that switching it three times doesn’t always work). I’m not sure the logs that’ll you’ll need but send the code and I’ll return the results ASAP.

PS I’ve also tried disabling 802.11w with the same results.

23.06.20213897Base systemBug ReportVery LowLowodhcp is not assigning lease times as specified in stat...openwrt-21.02Unconfirmed Task Description
  • TP-Link Archer C2600
  • OpenWRT 21.02-RC3

From boot, ipv6 leases are mostly assigned with leases of 1 hour. Occasionally leases of 14 days (as specified in Static Leases), and occasionally leases of 30 minutes and occasionally no leases (or leases expire and are not renewed).

What debugging / logging steps can I take to better pin down this issue?

I suspect that this is related to, or causes, occasional long stalls when opening new web pages, reported at the OpenWRT forum

In an initial effort to debug, I stopped odhcp and then started it on the command line with -l 7. The only logging that looked like a possible error are occasional sequences similar to this:

odhcpd[8869]: Received 123 Bytes from fe80::215:5dff:fe01:aa0f%lan@br-lan
odhcpd[8869]: Got a DHCPv6-request on lan
odhcpd[8869]: DHCPV6 REBIND IA_NA from 00020000ab113cca95908581f184 on lan: ok 2401:xxxx:xxxx:7bf7::ffff:253/128 fda6:3ce8:c11::ffff:253/128
odhcpd[8869]: Sending a DHCPv6-reply on lan
odhcpd[8869]: Sent 172 bytes to fe80::215:5dff:fe01:aa0f%lan@br-lan
BusyBox v1.33.1 (2021-06-13 22:02:19 UTC) multi-call binary.

Usage: basename FILE [SUFFIX]

Strip directory path and .SUFFIX from FILE
odhcpd[8869]: Netlink newneigh 2401:xxxx:xxxx:7bf7::aaaa:aaaa on lan
23.06.20213899Base systemBug ReportVery LowLowlibncurses - add option to create a 3rd package with pr...openwrt-21.02Unconfirmed Task Description

Currently the ncurses package is split into libncurses and libncurses-dev.
There is no option to get the binaries, or progs as the ncurses package calls them for the target:

tic, infocmp, captoinfo, tset, reset, clear, tput, toe, tabs

May I please suggest adding another ifdef called Package/libncurses-bin or Package/libncurses-progs to the Makefile that builds and packages just the binaries from the ncurses package?

The use case for tput, reset and clear seem wide ranging.
My use case for this is adding terminfo for my terminal instead of spawning a different one just for openwrt devices:

infocmp xterm-kitty | ssh owrtdevice tic -x -o \~/.terminfo /dev/stdin

This currently fails ion x86_64 with:

$ infocmp -a xterm-kitty | ssh apu tic -x -o \~/.terminfo /dev/stdin
Error relocating /usr/bin/tic: _nc_set_writedir: symbol not found
Error relocating /usr/bin/tic: _nc_tic_expand: symbol not found
Error relocating /usr/bin/tic: _nc_check_termtype2: symbol not found
Error relocating /usr/bin/tic: _nc_write_entry: symbol not found
Error relocating /usr/bin/tic: _nc_syntax: symbol not found
Error relocating /usr/bin/tic: _nc_read_entry_source: symbol not found
Error relocating /usr/bin/tic: _nc_resolve_uses2: symbol not found
Error relocating /usr/bin/tic: _nc_write_object: symbol not found
Error relocating /usr/bin/tic: _nc_strict_bsd: symbol not found
Error relocating /usr/bin/tic: _nc_infotocap: symbol not found
Error relocating /usr/bin/tic: _nc_disable_period: symbol not found
Error relocating /usr/bin/tic: _nc_capcmp: symbol not found
Error relocating /usr/bin/tic: _nc_tic_written: symbol not found
Failed to compile terminfo using tic 
25.06.20213904Base systemBug ReportVery LowMediumAdding another SSID to a radio prvents the interface f...openwrt-21.02Unconfirmed Task Description

Adding a second SSID from Luci results in a configuration error which prevents the radio interface from starting.

resulted configuration:
config wifi-device ‘radio1’

option type 'mac80211'
option hwmode '11g'
option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
option country 'US'
option htmode 'HT40'
option channel 'auto'
option cell_density '0'

config wifi-iface ‘default_radio1’

option device 'radio1'
option network 'lan'
option mode 'ap'
option macaddr '60:38:e0:be:e2:69'
option ssid 'somename'
option encryption 'psk2'
option key 'somepassword'

config wifi-iface ‘another_radio1’

option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid 'anothername'
option encryption 'psk2'
option key 'anotherpassword'

Log:
Fri Jun 25 10:24:07 2021 daemon.notice netifd: Network device ‘wlan1’ link is down
Fri Jun 25 10:24:07 2021 daemon.notice netifd: radio1 (14904): sh: acs_survey: out of range
Fri Jun 25 10:24:07 2021 daemon.notice netifd: radio1 (14904): sh: acs_survey: out of range
Fri Jun 25 10:24:07 2021 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy wlan1) –> new PHY
Fri Jun 25 10:24:07 2021 daemon.err hostapd: Duplicate BSSID aa:bb:cc:dd:ee:ff on interface ‘wlan1-1’ and ‘wlan1’.
Fri Jun 25 10:24:07 2021 daemon.err hostapd: 1 errors found in configuration file ‘/var/run/hostapd-phy1.conf’ Fri Jun 25 10:24:07 2021 daemon.err hostapd: Failed to set up interface with /var/run/hostapd-phy1.conf
Fri Jun 25 10:24:07 2021 daemon.notice netifd: radio1 (14904): Command failed: Invalid argument
Fri Jun 25 10:24:07 2021 daemon.notice netifd: radio1 (14904): Device setup failed: HOSTAPD_START_FAILED

“workaround”:
If I add a different (fake) macaddr to the 2nd SSID, it works.

04.07.20213913Base systemBug ReportVery LowMediumOn WAC124, the frrequency database is no read correctlyopenwrt-21.02Unconfirmed Task Description

Apologies for not reporting this sooner - it has been true for the last
several months of beta’s and for rc3.

When choosing a frequency for 5ghz for the Netgear WAC124:
[1] an incomplete list is given (nothing above channel 144)
[2] changing the width (20/40/80) does not affect choices
[3] NO choice will work except ch 36. Any other choice will be
accepted but the radio will be disabled - in GUI and in reality.
[4] Ch 36 does work fine

This has been true whether access the device from Mac/Linux or Windows,
Firefox or Chrome, so suspect base package issue (as opposed to GUI), but
not sure.

In case this helps any:
Netgear GUI allows any non-DFS channel (as appropriate for bw) up to 165
dd-wrt gui allows all (dfs/non-dfs) (as appropriate for bw) up to 165

Note that the WAC124 is limited to 100mw (great for AP, as often < $55).

I’ve 3 of them, so can test as desired.
I’ve saved the partitions (eg: factory) in case that is useful for anyone.


05.07.20213915Base systemBug ReportVery LowLowExpiration time for leases populated incorrectly in dhc...openwrt-21.02Unconfirmed Task Description
 
I’m running 21.02 on a FriendlyArm R4S. Noticed that all dhcp leases in Luci show as expired. Checking dhcp.leases, it shows:
43200 dc:xx:xx:xx:xx:xx 192.168.1.52 octopi *

According to dnsmasq, the first column should be the timestamp of when the lease is expiring (so either ‘now + leasetime’ or ‘uptime + leasetime’). In this case, it is just ‘0 + leasetime’.

Not sure if this is an issue with dnsmasq or openwrt itself. Happy to add more info if needed!


08.07.20213921Base systemBug ReportVery LowHighWAVLINK WL-WN577A2 (Maginon WLR-755AC) still crashes un...openwrt-21.02Unconfirmed Task Description

Device problem occurs on: WAVLINK WL-WN577A2 / Maginon WL-755 / Winstars WS-WN577A2 / Winstars WS-WN566A2 (MT7628AN)

Software versions of OpenWrt/LEDE release, packages, etc.:
all released till now! (testet lately with 20.01-rc3-snapshot again)

Problem:

The WLR755AC-Device regulary crashes under high load (LAN → WLAN) when using OpenWRT (latest 20.01-rc3 snapshot).
Using the stock firmware the issue does not occur.

With normal or low load the device works relieable and stable.

But when put under high load like playing a fullhd video, copying a lot of data and iperf simultaneously over WLAN the device will crash after a while.
The surface of the case will get palpable warm.

As there are only (too) very few venting holes on the downside of the device I assumed this could be the cause for the crash. It is not I proofed:

I opened the case (two screws on the bottom and four plastic clamps, two on very long side, sits very tight but can be removed without breaking the brackets if you work carful) and tried again with the case open:

Too put load on the device I copied a 3GB directory with mp3 files and startet iperf:

Device crashed after a few minutes, wlan does not come up again. Had to hard-reset (powercycle).

Active cooling:

Put a big office-fan right in front of the opened device:

Same result, device crashed after a few minutes but wlan came back by itself this time.

So the issue is NOT related to overheating but to some bug relatet to OpenWRT.

# iperf -c 192.168.200.14 -i 5 -t300
[  3] 215.0-220.0 sec  34.2 MBytes  57.5 Mbits/sec
[  3] 220.0-225.0 sec  34.2 MBytes  57.5 Mbits/sec
[  3] 225.0-230.0 sec  28.0 MBytes  46.9 Mbits/sec
[  3] 230.0-235.0 sec  1.12 MBytes  1.88 Mbits/sec
[  3] 235.0-240.0 sec  0.00 Bytes  0.00 bits/sec
[  3] 240.0-245.0 sec  0.00 Bytes  0.00 bits/sec
[  3] 245.0-250.0 sec  0.00 Bytes  0.00 bits/sec
10.07.20213923Base systemBug ReportVery LowLowEdgerouter4 port numbers out of synck in system logopenwrt-21.02Unconfirmed Task Description

Model Ubiquiti EdgeRouter 4
Architecture UBNT_E300 (CN7030p1.2-1000-AAP)
Firmware Version OpenWrt 21.02-SNAPSHOT r16232-febf6db0d0 / LuCI openwrt-21.02 branch git-21.188.55099-e52e1de

The forum post:
External Link

It seems that port numbers in system log is out of synck with hardware port numbers, for example this log text:

switch0: port 1(lan0)

This bug makes log errors like

Port 1 receive error code 7, packet dropped

very hard to find if the actual port is false flagged.

kern.notice kernel: [ 4979.972921] lan0: Link down
kern.info kernel: [ 4979.975979] switch0: port 1(lan0) entered disabled state
daemon.notice netifd: Network device 'lan0' link is down
kern.notice kernel: [ 5011.719291] lan0: 1000 Mbps Full duplex, port 1, queue 1
kern.info kernel: [ 5011.724648] switch0: port 1(lan0) entered blocking state
kern.info kernel: [ 5011.729976] switch0: port 1(lan0) entered forwarding state
daemon.notice netifd: Network device 'lan0' link is up
kern.notice kernel: [ 5035.272920] lan0: Link down
kern.info kernel: [ 5035.275978] switch0: port 1(lan0) entered disabled state
daemon.notice netifd: Network device 'lan0' link is down
kern.info kernel: [ 3594.470962] switch0: port 4(lan3) entered disabled state
daemon.notice netifd: Network device 'lan3' link is down
kern.notice kernel: [ 3615.941460] lan1: 1000 Mbps Full duplex, port 2, queue 2
kern.info kernel: [ 3615.946870] switch0: port 2(lan1) entered blocking state
kern.info kernel: [ 3615.952201] switch0: port 2(lan1) entered forwarding state
daemon.notice netifd: Network device 'lan1' link is up
11.07.20213927Base systemBug ReportVery LowCriticalOpenWrt 21.02.0-rc3 bricks Netgear WNDR3700 v4openwrt-21.02Unconfirmed Task Description

I saw the announcement on the website about the next stable release so like an idiot I went to upgrade the firmware. Router never came back, left it on overnight to see if it would eventually come up. I was upgrading from 19.07.7.

Breaking open the case I see a UART header and some pads for a JTAG but I’m not the guy to debug what broke. I just wanted to give someone else a heads up so they don’t lose their router, too.

The debricking guide is some random notes for people who jump into the hardware, not really organized in any understandable way.

https://openwrt.org/docs/guide-user/troubleshooting/generic.debrick

I like the line “The usual recovery methods have failed, forceing the user to to go to JTAG.” Like, where are the usual recovery methods listed? Not in the debricking guide, they aren’t.

Sorry, it’s just frustrating for a somewhat literate user like me (coming from LEDE, 20-ish years in IT/networking/sysadmin crap) that the debricking guide is useless for me. No “here’s the steps the OS takes to initialize” and “here’s where a safemode kicks in where you can set some TFTP or here’s where you pop into the serial connection via PuTTY” or like a general list of steps in order that you can attempt before working up to “ok solder a JTAG connector, here’s a DIGIKey part number to get you started.”

Tried Failsafe, Factory Reset, and Recovery all with no dice.

13.07.20213932Base systemBug ReportVery LowCritical[21.02] Autonegotiation speed fails with my provider's ...openwrt-21.02Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: xiaomi mir3g
- 21.02 rc3
- My provider uses pppoe, cable is 4-wire 100baseT and my router is 1000baseT xiaomi mir3g

 

openwrt 21.02 fails to establish pppoe link because of failing to autonegotiate (Speed: Unknown!, Link detected: no, etc):

# ethtool wan
Settings for wan:
	Supported ports: [ TP MII ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: Unknown!
	Duplex: Unknown! (255)
	Port: MII
	PHYAD: 1
	Transceiver: external
	Auto-negotiation: on
	Supports Wake-on: d
	Wake-on: d
	Link detected: no

When I set autonegotiation to off and forced to 100baseT/Full, pppoe worked like a charm.

/usr/sbin/ethtool -s wan speed 100 duplex full autoneg off
# ethtool wan
Settings for wan:
	Supported ports: [ TP MII ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  100baseT/Full 
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: No
	Advertised FEC modes: Not reported
	Speed: 100Mb/s
	Duplex: Full
	Port: MII
	PHYAD: 1
	Transceiver: external
	Auto-negotiation: off
	Supports Wake-on: d
	Wake-on: d
	Link detected: yes
14.07.20213934Base systemBug ReportVery LowHighWireless Wan loosing packets when pppoe-wan is upopenwrt-21.02Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: Home Hub 5, Linksys EA8300, Linksys WRT32x
- Software versions of OpenWrt 21.02-rc3
- Steps to reproduce:

Configure pppoe-wan and wwan to your ISPs

Bring up wwan
# ping -I wwan0 8.8.8.8
all good.

Now bring up wan (pppoe-wan)
# ifup wan

ping -I wwan0 8.8.8.8 looses packets in initial pings as follows:

# ping -c10 -Iwwan0 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=4 ttl=113 time=201.142 ms
64 bytes from 8.8.8.8: seq=5 ttl=113 time=41.131 ms
64 bytes from 8.8.8.8: seq=6 ttl=113 time=50.998 ms
64 bytes from 8.8.8.8: seq=7 ttl=113 time=40.956 ms
64 bytes from 8.8.8.8: seq=8 ttl=113 time=50.932 ms
64 bytes from 8.8.8.8: seq=9 ttl=113 time=40.753 ms

— 8.8.8.8 ping statistics — 10 packets transmitted, 6 packets received, 40% packet loss
round-trip min/avg/max = 40.753/70.985/201.142 ms

As a consequence wwan gets disabled by mwan3 because the test pings always fail.

If I take down wan (ifdown wan), then ping through wwan0 works normally.

The same configuration was working fine in 19.07 therefore something was changed in 21.02 that causes this issue with the wireless wan network. I am not sure however if this is related to “Wireless Wan”, but I do not have a second wan of ethernet type that I can test this issue with.

Excerpt from /etc/config/network relative to the interfaces:

config interface ‘wan’

  option device 'wan'
  option proto 'pppoe'
  option username 'vodafonedsl'
  option password 'vodafonedsl'
  option metric '1'
  option ipv6 '0'
  option delegate '0'

config interface ‘wwan’

  option proto 'ncm'
  option device '/dev/cdc-wdm0'
  option pdptype 'IP'
  option apn 'web.omnitel.it'
  option service 'preferlte'
  option ipv6 '0'
  option metric '5'
 

The only solution right now is to return to 19.07 that works flawlessly with the same configuration.
Tested with 3 different router (as specified above), all giving the same result.

19.07.20213937Base systemBug ReportVery LowMediumMR32 BCM53xx boot erroropenwrt-21.02Unconfirmed Task Description

I have an MR32 I’m trying to flash. Following the instructions on https://openwrt.org/toh/meraki/mr32 I uploaded the initramfs successfully to part.safe. When rebooting the console has the following errors then boots back into the Meraki firmware:

[ 4.690000] Mapping 10362880 bytes for /dev/mtdblock/part.safe
[ 4.730000] find_itb_subimage: error finding kernel@1: FDT_ERR_NOTFOUND
[ 4.740000] find_itb_subimage: error finding ramdisk@1: FDT_ERR_NOTFOUND
[ 4.750000] find_itb_subimage: error finding fdt@2: FDT_ERR_NOTFOUND
[ 4.750000] kexec_raw: kexec_load: Cannot assign requested address
[ 6.490000] Mapping 10235904 bytes for /dev/mtdblock/part.old
[ 6.530000] Meraki-build is 23-191963

I built the initramfs from the current git master (7/18/2021). I also had someone on #openwrt-dev build it and I tried theirs and received the same errors.


19.07.20213938Base systemBug ReportVery LowCriticalAkitio MyCloud Mini hangs during boot of akitio_mycloud...openwrt-21.02Unconfirmed Task Description

Supply the following if possible:

 

The akitio_mycloud-initramfs-uImage from 21.02.0-rc3 hangs when booting on Akitio MyCloud Mini. This was also reported as an issue in the forums with 19.07 release.

Stage-1 Bootloader 五 10月 28 10:36:29 CST 2011
Attempting to set PLLA to 750MHz ...
  plla_ctrl0 : 0x0000000A
  plla_ctrl1 : 0x000F0000
  plla_ctrl2 : 0x001D01A0
  plla_ctrl3 : 0x00000017
PLLA Set

Setup memory, testing, Image 0
  Hdr len: 0x0001AC3C
  Hdr CRC: 0xB931AD17
 OK


U-Boot 1.1.2 (Oct 28 2011 - 10:44:29)

U-Boot code: 60D00000 -> 60D1AC3C  BSS: -> 60D1F2F4
RAM Configuration:
        Bank #0: 60000000 256 MB
SRAM Configuration:
        64KB at 0x50000000
NAND:256 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Setting Linux mem= boot arg value
Reading upgrade flag from NAND address 0x01ec0000 : 0
Hit any key to stop autoboot:  0 
$ tftp 64000000 uImage.mycloud
Wait GMAC to reset
Wait for PHY reset
PHY is Realtek RTL8211D
Wait for link to come up................Link up
Wait for auto-negotiation to complete
Link is 1000M
TFTP from server 192.168.50.59; our IP address is 192.168.50.100
Filename 'uImage.mycloud'.
Load address: 0x64000000
Loading: 
ARP Resend request
T invalid RARP header
################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################
done
Bytes transferred = 7120489 (6ca669 hex)
$ bootm 64000000
## Booting image at 64000000 ...
   Image Name:   ARM OpenWrt Linux-5.4.124
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    7120425 Bytes =  6.8 MB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.4.124 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16172-2aba3e9784)) #0 SMP Sun Jun 13 22:02:19 2021
[    0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Akitio MyCloud
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 64 MiB at 0x64000000
[    0.000000] percpu: Embedded 15 pages/cpu s29772 r8192 d23476 u61440
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32480
[    0.000000] Kernel command line: earlyprintk console=ttyS0,115200
[    0.000000] Bootloader command line (ignored): root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=256M poweroutage=yes
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 47188K/131072K available (6144K kernel code, 171K rwdata, 784K rodata, 9216K init, 214K bss, 18348K reserved, 65536K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=16 to nr_cpu_ids=2.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] FPGA IRQ chip 0 "interrupt-controller" @ (ptrval), 32 irqs, parent IRQ: 16
[    0.000000] random: get_random_bytes called from 0xc0800b88 with crng_init=0
[    0.000020] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 21474835200ns
[    0.000074] clocksource: oxnas_rps_clocksource_timer: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 19112603332 ns
[    0.000089] timer_oxnas_rps: Registered clocksource rate 390625Hz
[    0.000112] timer_oxnas_rps: Registered clock event rate 6250000Hz prescaler 0 period 62500
[    0.000276] GIC: PPI13 is secure or misconfigured
[    0.000330] GIC: PPI13 is secure or misconfigured
[    0.000450] Calibrating delay loop... 298.59 BogoMIPS (lpj=1492992)
[    0.070307] pid_max: default: 32768 minimum: 301
[    0.070661] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.070689] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.072107] CPU: Testing write buffer coherency: ok
[    0.074155] Setting up static identity map for 0x60100000 - 0x6010005c
[    0.074457] rcu: Hierarchical SRCU implementation.
[    0.075202] smp: Bringing up secondary CPUs ...
[    0.076308] GIC: PPI13 is secure or misconfigured
[    0.140692] smp: Brought up 1 node, 2 CPUs
[    0.140728] SMP: Total of 2 processors activated (598.42 BogoMIPS).
[    0.146245] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.146286] futex hash table entries: 512 (order: 2, 16384 bytes, linear)
[    0.153093] pinctrl core: initialized pinctrl subsystem
[    0.154055] NET: Registered protocol family 16
[    0.158021] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.160611] cpuidle: using governor menu
[    0.160719] No ATAGs?
[    0.181959] pps_core: LinuxPPS API ver. 1 registered
[    0.181982] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.182041] PTP clock support registered
[    0.182300] workqueue: max_active 576 requested for napi_workq is out of range, clamping between 1 and 512
[    0.183626] clocksource: Switched to clocksource oxnas_rps_clocksource_timer
[    0.185013] thermal_sys: Registered thermal governor 'step_wise'
[    0.185392] NET: Registered protocol family 2
[    0.185592] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.187010] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[    0.187092] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.187130] TCP bind hash table entries: 1024 (order: 1, 8192 bytes, linear)
[    0.187169] TCP: Hash tables configured (established 1024 bind 1024)
[    0.187343] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.187412] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.187837] NET: Registered protocol family 1
[    0.187896] PCI: CLS 0 bytes, default 32
[    0.487014] workingset: timestamp_bits=14 max_order=15 bucket_order=1
[    0.498406] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.499348] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.502737] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.506877] printk: console [ttyS0] disabled
[    0.507051] 44200000.serial: ttyS0 at MMIO 0x44200000 (irq = 55, base_baud = 390625) is a 16550A
[    0.967037] printk: console [ttyS0] enabled
[    0.989649] brd: module loaded
[    1.004014] loop: module loaded
[    1.073950] Could not find a valid ONFI parameter page, trying bit-wise majority to recover it
[    1.082611] ONFI parameter recovery failed, aborting
[    1.087621] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
[    1.093977] nand: Hynix NAND 256MiB 3,3V 8-bit
[    1.098403] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.105996] Scanning device for bad blocks
[    1.161538] Bad eraseblock 618 at 0x000004d40000
[    1.183211] Bad eraseblock 824 at 0x000006700000
[    1.190617] Bad eraseblock 858 at 0x000006b40000
[    1.251353] Bad eraseblock 1536 at 0x00000c000000
[    1.271260] Bad eraseblock 1720 at 0x00000d700000
[    1.295429] Bad eraseblock 1955 at 0x00000f460000
[    1.307783] 2 fixed-partitions partitions found on MTD device 41000000.nand-controller
[    1.315706] Creating 2 MTD partitions on "41000000.nand-controller":
[    1.322055] 0x000000000000-0x0000026c0000 : "boot"
[    1.328936] 0x0000026c0000-0x000010000000 : "ubi"
[    1.337172] libphy: Fixed MDIO Bus: probed
[    1.342082] oxnas-dwmac 40400000.ethernet: IRQ eth_lpi not found
[    1.348318] oxnas-dwmac 40400000.ethernet: PTP uses main clock
[    1.354201] oxnas-dwmac 40400000.ethernet: no reset control found
[    1.424023] oxnas-dwmac 40400000.ethernet: User ID: 0x12, Synopsys ID: 0x35
[    1.430981] oxnas-dwmac 40400000.ethernet:   DWMAC1000
[    1.436070] oxnas-dwmac 40400000.ethernet: DMA HW capability register supported
[    1.443345] oxnas-dwmac 40400000.ethernet: RX Checksum Offload Engine supported
[    1.450659] oxnas-dwmac 40400000.ethernet: COE Type 2
[    1.455723] oxnas-dwmac 40400000.ethernet: TX Checksum insertion supported
[    1.462563] oxnas-dwmac 40400000.ethernet: Wake-Up On Lan supported
[    1.468899] oxnas-dwmac 40400000.ethernet: Enhanced/Alternate descriptors
[    1.475706] oxnas-dwmac 40400000.ethernet: Enabled extended descriptors
[    1.482291] oxnas-dwmac 40400000.ethernet: Ring mode enabled
[    1.487953] oxnas-dwmac 40400000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    1.495815] oxnas-dwmac 40400000.ethernet: device MAC address 3e:c3:3f:d1:0c:ca
[    1.536033] libphy: stmmac: probed
[    1.539445] RTL8211DN Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211DN Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[    1.552128] RTL8211DN Gigabit Ethernet stmmac-0:03: attached PHY driver [RTL8211DN Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:03, irq=POLL)
[    1.567016] ledtrig-cpu: registered to indicate activity on CPUs
[    1.573120] hidraw: raw HID events driver (C) Jiri Kosina
[    1.580288] NET: Registered protocol family 10
[    1.586462] Segment Routing with IPv6
[    1.590225] NET: Registered protocol family 17
[    1.594862] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.607805] 8021q: 802.1Q VLAN Support v1.8

Device hangs at this point.

20.07.20213942Base systemBug ReportVery LowHighI report a bug [21.02-rc3 ]openwrt-21.02Unconfirmed Task Description

I report a bug. After testing, openwrt 21.02-rc3 version: the interface protocol “PPPoE” severely limits the network speed, or “the network speed is seriously not up to the speed provided by the service provider“.

The test results are as follows:

My device is tp link Archer C7

I use 300m broadband network for testing, download the same link resources, the new version 21.02-rc3 speed is only 26m, using the old version 19.07. X test, download speed can reach 40m, and very stable.


20.07.20213944Base systemBug ReportVery LowLowOctegon can't read timezoneopenwrt-21.02Unconfirmed Task Description

EdgeRouter-4 21.02-snapshot-r16232-febf6db0d0 (and other Octegon devices as seen it the forum thread).

I can’t get the EdgeRouter-4 to read the /etc/tz file. The file exist and I can read it from PuTTy. The /etc/tz changes to the correct time zone every time I in LuCi system settings change time zone.
I have also tried installing the Europe time zone package in hope for good luck but without any luck.

No matter what I do the system time in LuCi overview, date command and system log always show UTC time!? But the time in LuCi system time settings read the correct local time.

Fault tread from the OpenWRT forum

root@[sanitized]:~# uci show system; readlink -f /etc/TZ
system.@system[0]=system
system.@system[0].ttylogin='0'
system.@system[0].urandom_seed='0'
system.@system[0].hostname='[sanitized]'
system.@system[0].description='[sanitized]'
system.@system[0].log_file='/Logs/system.log'
system.@system[0].log_size='640'
system.@system[0].log_proto='udp'
system.@system[0].conloglevel='8'
system.@system[0].cronloglevel='5'
system.@system[0].zonename='Europe/Stockholm'
system.@system[0].timezone='CET-1CEST,M3.5.0,M10.5.0/3'
system.ntp=timeserver
system.ntp.server='0.openwrt.pool.ntp.org' '1.openwrt.pool.ntp.org' '2.openwrt.pool.ntp.org' '3.openwrt.pool.ntp.org'
/tmp/TZ
root@[sanitized]:~#
root@[sanitized]:~# cat /etc/TZ
CET-1CEST,M3.5.0,M10.5.0/3
root@[sanitized]:~#
root@[sanitized]:~# cat /tmp/TZ
CET-1CEST,M3.5.0,M10.5.0/3
root@[sanitized]:~#

There have been some fault finding already pointing to a fault in the code?
External Link

26.07.20213951Base systemBug ReportVery LowCriticalAP inaccessible after https://github.com/openwrt/openwr...openwrt-21.02Unconfirmed Task Description

Supply the following if possible:
- mir3g and mi4a gigabit edition mt7621 devices.. a dlink dir 882 remained accessible but all other ports seem down..
- openwrt https://github.com/openwrt/openwrt/commit/089efd61e9a6cdc0ea39c184d37bc8ebbe03175c - flash latest master or latest 21.02 makes device unreachable had to hard flash stock again and flash older openwrt

 


28.07.20213953Base systemBug ReportVery LowMediumWireguard slow performance - mpc85xx (Tp-Link WDR-4900)...openwrt-21.02Unconfirmed Task Description

With openwrt-21.02-rc3 the wireguard vpn speed is quite slow ~ 50 Mbps, compared to 19.07.7 where I get 100 Mbps.
My hardware is Tp-Link WDR-4900 - mpc85xx.

30.07.20213957Base systemBug ReportVery LowCriticalWAN port broken on WNDR3800openwrt-21.02Unconfirmed Task Description

Supply the following if possible:
- Netgear WNDR3800-1CHNAS
- OpenWrt 21.02-SNAPSHOT r16247-60fad8f82b
- Steps to reproduce:

  • Flash from stock to OpenWRT 19.07.x ATH79
  • Flash from 19.07.x to OpenWRT 21.02-SNAPSHOT
  • Reset to factory in GUI
  • WAN never comes up, it never leaves “UP BROADCAST MULTICAST” according to ifconfig.
  • WAN port is always flapping, nothing is logged on kernel/system logs.

The hardware was checked before flashing, in OEM firmware WAN is working.

As shown below one of the ports has a blank uid value (full zeros).

(Attached is a full copy of kernel log.

[ 1.192635] ag71xx 19000000.eth: connected to PHY at fixed-0:00 [uid=00000000, driver=Generic PHY]
[ 1.202218] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode: rgmii
[ 1.524463] ag71xx 1a000000.eth: connected to PHY at rtl8366s:04 [uid=001cc960, driver=Generic PHY]
[ 1.534115] eth1: Atheros AG71xx at 0xba000000, irq 5, mode: rgmii

03.08.20213965Base systemBug ReportVery LowLowMAC addresses should be kept as in 19.07openwrt-21.02Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: WRT1200AC
- Software versions of OpenWrt/LEDE release, packages, etc.: 21.02
- Steps to reproduce: Clean install

After upgrading from 19.07 to 21.02 I found out issues with IP addresses given by my ISP. I found out that the MAC address of the WAN port has changed instead of LAN (before LAN started with 26 and WAN 24 but after upgrading it was the opposite - LAN started with 24 and WAN with 26). It is a very confusing behavior and addressing and IMO it should stay as it was in previous versions.

 


Showing tasks 1 - 50 of 1430 Page 1 of 291 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing