OpenWrt/LEDE Project

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

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

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

OpenedIDCategory  ascTask TypePrioritySeveritySummaryReported InStatus
10.03.20202893Base systemBug ReportVery LowHighEthernet port not receiving data on Ubiquiti LiteAP ac ...TrunkUnconfirmed Task Description

Hi,

The Ubiquiti LiteAP ac (LAP-120) does not receive incoming packets via eth0 with the latest snapshot (OpenWrt SNAPSHOT, r12498-2a18840cc7):

root@OpenWrt:/# ifconfig 
br-lan    Link encap:Ethernet  HWaddr B4:FB:E4:FA:FA:FA
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fdaa:a708:e003::1/60 Scope:Global
          inet6 addr: fe80::b6fb:e4ff:fefa:fafa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:4420 (4.3 KiB)

eth0      Link encap:Ethernet  HWaddr B4:FB:E4:FA:FA:FA  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:6622 (6.4 KiB)
          Interrupt:4

It works correctly with latest stable, 19.07.2.

Using tcpdump on the connected computer I see outgoing traffic from the device, but incoming traffic does not reach the device.

The device correctly detects link changes, but different link speeds make no difference:

[ 1536.519019] eth0: link down
[ 1536.522824] br-lan: port 1(eth0) entered disabled state
[ 1537.561807] eth0: link up (1000Mbps/Full duplex)
[ 1537.566554] br-lan: port 1(eth0) entered blocking state
[ 1537.571932] br-lan: port 1(eth0) entered forwarding state
[ 1541.719009] eth0: link down
[ 1541.722824] br-lan: port 1(eth0) entered disabled state
[ 1542.761703] eth0: link up (100Mbps/Half duplex)
[ 1542.766359] br-lan: port 1(eth0) entered blocking state
[ 1542.771738] br-lan: port 1(eth0) entered forwarding state
[ 1545.879008] eth0: link down
[ 1545.882820] br-lan: port 1(eth0) entered disabled state
[ 1546.921800] eth0: link up (10Mbps/Half duplex)
[ 1546.926365] br-lan: port 1(eth0) entered blocking state
[ 1546.931744] br-lan: port 1(eth0) entered forwarding state

Please find attached dmesg outputs for both snapshot (snap) and 19.07.2 (19072).

13.03.20202901Base systemBug ReportVery LowHighFlow offload not working properly in case of IPv6 (NAT6...openwrt-19.07Unconfirmed Task Description

Linksys WRT32X with NAT6 configuration.

On latest 19.07 branch r10959

With the flow_offload feature turned on, nat6 is not working properly.
The first (or several) TCP packets seemed to be fine but later packets were not properly transmitted. The connection was soon closed.

(In case of accessing ipv6.google.com, the browser would freeze. And the curl would freeze after receiving a portion of the HTML content.)

In the meantime, ICMPv6 worked normally.

After removing the FLOWOFFLOAD ip6tables record, everything is fine.
After inserting the `-m conntrack –cstate RELATED,ESTABLISHED -j ACCEPT` before the FLOWOFFLOAD everything is also fine.

IPv4 part looked normal even if flow_offload is on.

NAT6 worked on older versions like 18.04 branch with flow_offload enabled.

17.03.20202906Base systemBug ReportVery LowHighAdding v4 Static routes without selecting 'Advanced' Ta...openwrt-19.07Unconfirmed Task Description

Using Openwrt 19.07.2 release;
On TP-Link c2600 & N750(wdr4300 v1.4)

Observed behavior:

Adding a static v4 route i.e 172.16.253.0 via 172.16.253.254 in the Luci Static route page succesfully adds the route, and by default appears to select the local route table. However viewing the routes list in status or via ip r s on cli does not show the entry.

Work-Around:

Ensure that a different table is selected in the 'Advanced tab' then go back in and add it to the correct appropriate route table.



Expected behaviour:

Adding a static route add's it to the system route table irrespective of needing to switch into advanced tab and select a non-default route table first.


21.03.20202912Base systemBug ReportVery LowHighPhicomm K3 (bcm53xx) wifi channel can't be set to auto ...openwrt-19.07Unconfirmed Task Description

Device:Phicomm K3 (bcm53xx)
BUG:wifi channel can’t set to auto mode
Description:Wifi channel can’t set to auto mode in Network - Wireless.
When wireless channel sets to auto mode, wireless settings will change from AP to Cilent even I don’t do that.

22.03.20202918Base systemBuild FailureVery LowHighYesterday after the source code compiled out of the fir...TrunkUnconfirmed Task Description

but it is indeed that after synchronizing the source code, the compiled file has img and gzip, and the system cannot be successfully booted! Converting to vhdx with vmdk, cannot be successfully converted, and converted with img , The system does not start, using img to upgrade the system on the web is also unsuccessful! Hope to solve it, thanks for the ingredients!

23.03.20202922Base systemBug ReportVery LowHighNo COMFAST CF-E110NV2 8MB flash compatible versionTrunkUnconfirmed Task Description

CF-E110V2 is released with 8MB Flash (maybe it was before with 16 but apparently no longer, see forum discussions on CF-E110)
The current released package is only for 16MB flash

Can You generate and publicly release a 8MB flash compatible version too.

Hereafter the modified part of the dts file I’m using to compile my own FW (based on original OEM partition table).

flash@0 {
	compatible = "winbond,w25q64", "jedec,spi-nor";
	reg = <0>;
	spi-max-frequency = <25000000>;
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;
		partition@0 {
			label = "u-boot";
			reg = <0x000000 0x010000>;
			read-only;
		};
		art: partition@10000 {
			label = "art";
			reg = <0x010000 0x010000>;
			read-only;
		};
		partition@20000 {
			compatible = "denx,uimage";
			label = "firmware";
			reg = <0x020000 0x7d0000>;
		};
		partition@7f0000 {
			label = "nvram";
			reg = <0x7f0000 0x010000>;
			read-only;
		};
	};
};
 


25.03.20202928Base systemBug ReportVery LowHighTP-Link TL-WDR3600 v1 on kernel 5.4 boot-loops since ch...TrunkUnconfirmed Task Description

- Device problem occurs on

TP-Link TL-WDR3600 v1

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

Since reboot-12646-gdb70077668 “toolchain: Update GCC 8 to version 8.4.0” and kernel 5.4, WDR3600 boot-loops with the following message:

Starting kernel ...

[    0.000000] Linux version 5.4.24 (openwrt@hawg) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r12683-8c33debb52)) #0 Sat Mar 21 21:35:45 2020
[    0.000000] printk: bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001974c (MIPS 74Kc)
[    0.000000] MIPS: machine is TP-Link TL-WDR3600 v1
[    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 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32480
[    0.000000] Kernel command line: console=ttyS0,115200 rootfstype=squashfs,jffs2
[    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] 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: 122384K/131072K available (4681K kernel code, 187K rwdata, 1080K rodata, 1212K init, 196K bss, 8688K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 51
[    0.000000] random: get_random_bytes called from start_kernel+0x32c/0x51c with crng_init=0
[    0.000000] CPU clock: 560.000 MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6825930166 ns
[    0.000009] sched_clock: 32 bits at 280MHz, resolution 3ns, wraps every 7669584382ns
[    0.008305] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
[    0.084927] pid_max: default: 32768 minimum: 301
[    0.089999] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.097796] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.107070] Kernel panic - not syncing: Unexpected DSP exception
[    0.113470] Rebooting in 1 seconds..
26.03.20202931Base systemBug ReportVery LowHighloading package information never arrivedopenwrt-19.07Unconfirmed Task Description

using fresh install

from Luci interface goto menu
system/software
the loading package information never arrived

pushing the update list button
the loading package information never arrived

using the console
opk update, list... are working well


07.04.20202977Base systemBug ReportVery LowHighParameters sendopts seems to be bad formated in the cal...openwrt-19.07Unconfirmed Task Description

The options parameters sendopts define in /etc/config/network seems to be badly formated in the call of the command odhcp6c

In /etc/config/network:

 

option sendopts “11:00 15:456544 16:1234”

is parsed like this (show via ps|grep odhcp6c)
-x11 00 -x15 456544 -x16 1234

The syntax given by the help of odhcp6c is different:

-x <opt>:<val> Add option opt (with value val) in sent packets (cumulative)

		Examples of IPv6 address, string and base-16 encoded options:
		-x dns:2001:2001::1,2001:2001::2 - option 23
		-x 15:office - option 15 (userclass)
		-x 0x1f4:ABBA - option 500
		-x 202:'"file"' - option 202

It appears than the : is replace by a space in the call of the command.
Regarding the help of the command, it should be :
-x 11:00 -x 15:456544 -x 16:1234

Thanks
Regards

08.04.20202980Base systemBug ReportVery LowHighNo connection to Ethernet portTrunkUnconfirmed Task Description

Hi,
I can’t connect to my board with ethernet port, my chip is mt7688 and branch is master, I tested board with 19.07 branch, it seems all is OK.
Below are the logs with serial port :

root@OpenWrt:/# [  306.094979] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
[  306.101270] mtk_soc_eth 10100000.ethernet eth0: dma_cfg:00000057
[  306.107392] mtk_soc_eth 10100000.ethernet eth0: tx_ring=0, base=0707c000, max=1024, ctx=1, dtx=0, fdx=0, next=1
[  306.117655] mtk_soc_eth 10100000.ethernet eth0: rx_ring=0, base=0701c000, max=1024, calc=0, drx=1
[  316.094980] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
[  316.101273] mtk_soc_eth 10100000.ethernet eth0: dma_cfg:00000057
[  316.107393] mtk_soc_eth 10100000.ethernet eth0: tx_ring=0, base=0707c000, max=1024, ctx=1, dtx=0, fdx=0, next=1
[  316.117657] mtk_soc_eth 10100000.ethernet eth0: rx_ring=0, base=07070000, max=1024, calc=1023, drx=0
[  317.502718] rt3050-esw 10110000.esw: link changed 0x00
[  326.094981] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
[  326.101274] mtk_soc_eth 10100000.ethernet eth0: dma_cfg:00000057
[  326.107394] mtk_soc_eth 10100000.ethernet eth0: tx_ring=0, base=0707c000, max=1024, ctx=2, dtx=0, fdx=0, next=2
[  326.117659] mtk_soc_eth 10100000.ethernet eth0: rx_ring=0, base=0701c000, max=1024, calc=1023, drx=0
[  336.094979] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
[  336.101271] mtk_soc_eth 10100000.ethernet eth0: dma_cfg:00000057
[  336.107392] mtk_soc_eth 10100000.ethernet eth0: tx_ring=0, base=0707c000, max=1024, ctx=1, dtx=0, fdx=0, next=1
[  336.117656] mtk_soc_eth 10100000.ethernet eth0: rx_ring=0, base=07070000, max=1024, calc=1023, drx=0
[  346.094979] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
[  346.101272] mtk_soc_eth 10100000.ethernet eth0: dma_cfg:00000057
[  346.107392] mtk_soc_eth 10100000.ethernet eth0: tx_ring=0, base=0707c000, max=1024, ctx=1, dtx=0, fdx=0, next=1
[  346.117654] mtk_soc_eth 10100000.ethernet eth0: rx_ring=0, base=0701c000, max=1024, calc=1023, drx=0
[  356.094981] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
[  356.101273] mtk_soc_eth 10100000.ethernet eth0: dma_cfg:00000057
[  356.107393] mtk_soc_eth 10100000.ethernet eth0: tx_ring=0, base=0707c000, max=1024, ctx=1, dtx=0, fdx=0, next=1
[  356.117657] mtk_soc_eth 10100000.ethernet eth0: rx_ring=0, base=07070000, max=1024, calc=1023, drx=0
 


09.04.20202986Base systemBug ReportVery LowHighFunctionality broken by migration to DSA for Ubiquiti E...TrunkUnconfirmed Task Description

Supply the following if possible:
- Ubiquiti ER-X
- Trunk
- Build trunk of Openwrt and try to configure vlan enabled interfaces on an embedded switch.

Hi.

I have Ubiquiti ER-X which I have been using for quite a while and it was working just fine.
I was using it to route traffic from external internet connections to a ‘trunk’ port connected to a different OpenWrt device used as access point. So to clarify: I have one of the swich ports configured as ‘tagged’ (’tunk’) for multiple vlans.

Unfortunately commit 30644bc579e771e4b6dcc165ca966124e0259e1e that switched this device to use DSA for switch configuration have completely broken this setup.

And I’m not talking abut soft bricking - that was to be expected. Unfortunately DSA doesn’t provide functionality that was available in swconfig for years. Namely it seems to be impossible to configure switch ports to be ‘tagged’.

It looks like DSA is considered to be ‘the future’ but unfortunately it doesn’t see to be ready for prime time - it seems to be impossible to use DSA enabled devices in configurations that were perfectly possible before.

13.04.20203005Base systemBug ReportVery LowHighiptables ruleset order improvement optionTrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
TP-Link Archer C7 v5
- Software versions of OpenWrt/LEDE release, packages, etc.
19.07.2, just default packages
- Steps to reproduce
Current iptable ordering is badly pessimal (this repeats 3x, so 3 states get set for each connection, but thats for other news)
```
-A FORWARD -m comment –comment “!fw3: Custom forwarding rule chain” -j forwarding_rule
-A FORWARD -m conntrack –ctstate RELATED,ESTABLISHED -m comment –comment “!fw3” -j ACCEPT
-A FORWARD -m conntrack –ctstate INVALID -m comment –comment “!fw3” -j DROP
```
following does same job but does significantly less processing for typical case of in-state packets
```
-A FORWARD -m conntrack –ctstate RELATED,ESTABLISHED -m comment –comment “!fw3” -j ACCEPT
-A FORWARD -m conntrack –ctstate INVALID -m comment –comment “!fw3” -j DROP
-A FORWARD -m comment –comment “!fw3: Custom forwarding rule chain” -j forwarding_rule
```
Not willing to generalize, but my wifi and wire behind could not reach subscription 100Mbps in any way before the change, after change it is steady 100Mbps both ways.

21.04.20203031Base systemBug ReportVery LowHighBusybox force reinstalled when there are no opkg listsopenwrt-19.07Unconfirmed Task Description

Device problem occurs on: Turris Omnia, mvebu
Software version: OpenWrt 19.07.

Steps to reproduce:

I noticed this bug, when I forget to do before force-reinstalling busybox

opkg update

If there isn’t anything in folder /var/opkg-lists

root@turris:/# ls -la /var/opkg-lists
ls: /var/opkg-lists: No such file or directory

It is possible to remove busybox, which should not happen.

root@turris:/# opkg install busybox --force-reinstall
Removing package busybox from root...
Installing busybox (1.30.1-5.18) to root...
Collected errors:
 * opkg_download_pkg: Package busybox is not available from any configured src.
 * opkg_install_pkg: Failed to download busybox. Perhaps you need to run 'opkg update'?
 * opkg_install_cmd: Cannot install package busybox.

And then the device ends up being in a non-specific state when you can not do anything and you need to flash firmware it once again.

If you do

opkg update

before force-reinstalling busybox, it refuses to do it which is correct.

root@turris:~# opkg install busybox --force-reinstall
Refusing to remove essential package busybox.
        Removing an essential package may lead to an unusable system, but if
        you enjoy that kind of pain, you can force opkg to proceed against
        its will with the option: --force-removal-of-essential-packages
No packages removed.
Package busybox (1.30.1-5.18) installed in root is up to date.
26.04.20203048Base systemBug ReportVery LowHighKernel 5.4 no wan connection on Netgear R6850TrunkUnconfirmed Task Description

Affected Device - Netgear R6850

Software Versions:
1. Master commit 4c70bb4f906b875aee1da6636aa7d2023ef69064 or latest commit.
2. Luci
3. Luci-app-adblock, luci-app-upnp, luci-app-sqm, luci-app-wol, luci-app-openvpn

Issue:
1. Ever since kernel updated to 5.4, wan interface doesn’t get IPs.
2. Kernel logs doesn’t show error and even shows wan interface is up.
3. Sometimes it would get IP if I would restart /etc/init.d/network.
4. Currently reverted back to kernel 4.14 commit id: b51ea43f900191bc8ce7411dad39239fac6df4f8 and commit message: bcm53xx: refactor board.d code in 02_network

Step to reproduce:
1. Compile latest commit including following packages: luci-core, luci-app-adblock, luci-app-upnp, luci-app-sqm, etc.
1. Flash firmware and do not retain settings to latest commit.
2. Login to router via ssh. Then do cat /etc/config/network
3. Interface ‘wan’ ‘ipaddr’ is empty. ‘ifname’ is set to ‘wan’. ‘proto’ set to dhcp.
4. Set to static and input modem ip addresses manually. Then restart network. Unable to connect to modem gui.
5. Also try to set modem to bridge mode and the openwrt router to PPPoE - No IP.
6. Added ‘forcelink: 1’ then restarted network to no avail.
7. Restarting network might establish connection but when you restart network or router again, there will be no connection. Until you restart network until you get IP addresses.

PS: Can provide detailed logs if requested as I am back to kernel 4.14.172 commit. Since this router serves as gateway to our home internet with multiple clients.

08.05.20203072Base systemBug ReportVery LowHighSamknows WhiteBox8 misses 2.4 GHz pcie wireless NICTrunkUnconfirmed Task Description

device

software versions

tested & misses 2.4 GHz NIC

tested & has 2.4 GHz NIC

reproduce

  • build OpenWrt master branch with a given commits and flash it on the device (my build config is attached)
  • run “iw dev” or “iw list”
    • in problem state it lists one interface (the 5 GHz wireless NIC)
    • in good state it lists two interfaces (2.4 GHz and 5 GHz wireless NIC)

conclusion

I think it has either to do with ramips: mt7621: switch kernel version to 5.4 or with ramips: mt7621: update PCIe node in dtsi. Between the known good and earliest known bad commit are multiple commits working together. I fear to test them one by one.

09.05.20203079Base systemBug ReportVery LowHighTraceback when booting OpenWrt 19.07.2 on Netgear r7500...TrunkUnconfirmed Task Description

My Netgear r7500v2 running OpenWrt 19.07.2 always shows the following traceback when booting up.

[ 31.917130] ————[ cut here ]———— [ 31.917192] WARNING: CPU: 1 PID: 1938 at backports-4.19.98-1/net/wireless/util.c:1147 0xbf2e3d88 [cfg80211@bf2df000+0×37000]
[ 31.920831] invalid rate bw=0, mcs=15, nss=4
[ 31.932143] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT wireguard slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack 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 ip6_udp_tunnel udp_tunnel uas usb_storage f2fs ext4 mbcache jbd2 crc32c_generic crc32_generic leds_gpio xhci_plat_hcd
[ 31.985373] xhci_pci xhci_hcd dwc3 dwc3_of_simple ohci_platform ohci_hcd phy_qcom_dwc3 ahci ehci_platform sd_mod ahci_platform libahci_platform libahci libata scsi_mod ehci_hcd gpio_button_hotplug
[ 32.007657] CPU: 1 PID: 1938 Comm: hostapd Not tainted 4.14.171 #0
[ 32.025242] Hardware name: Generic DT based system
[ 32.031323] Function entered at [<c030f1c4>] from [<c030b390>]
[ 32.036095] Function entered at [<c030b390>] from [<c07c0664>]
[ 32.041911] Function entered at [<c07c0664>] from [<c031fa98>]
[ 32.047727] Function entered at [<c031fa98>] from [<c031faf8>]
[ 32.053544] Function entered at [<c031faf8>] from [<bf2e3d88>]
[ 32.059386] Function entered at [<bf2e3d88>] from [<bf2f17dc>]
[ 32.065179] Function entered at [<bf2f17dc>] from [<bf2fe5f4>]
[ 32.070992] Function entered at [<bf2fe5f4>] from [<bf2ff1e8>]
[ 32.076806] Function entered at [<bf2ff1e8>] from [<bf332ad0>]
[ 32.082632] Function entered at [<bf332ad0>] from [<bf332b60>]
[ 32.088438] Function entered at [<bf332b60>] from [<bf332bf8>]
[ 32.094255] Function entered at [<bf332bf8>] from [<bf2ed678>]
[ 32.100071] Function entered at [<bf2ed678>] from [<c06e190c>]
[ 32.105887] Function entered at [<c06e190c>] from [<c06e0128>]
[ 32.111702] Function entered at [<c06e0128>] from [<c06e0900>]
[ 32.117517] Function entered at [<c06e0900>] from [<c06df938>]
[ 32.123334] Function entered at [<c06df938>] from [<c06dfd54>]
[ 32.129150] Function entered at [<c06dfd54>] from [<c0689c18>]
[ 32.134967] Function entered at [<c0689c18>] from [<c068a480>]
[ 32.140782] Function entered at [<c068a480>] from [<c0307b60>]
[ 32.146678] —[ end trace 97f7e93c858c392e ]—

11.05.20203092Base systemBug ReportVery LowHighXiaomi Router 3G random rebootsopenwrt-19.07Unconfirmed Task Description

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

 

Hello,

I have a Xiaomi 3G router. Since the day I bought it I installed Openwrt and to tell you the truth, with version 18.06 I didn’t have any problem.

A few weeks ago I updated to the new version (19.07) using LuCI and it restarts me randomly.

I tried restoring the router, reinstalling the update and it keeps randomly rebooting. Right now I have it without any additional packages installed and it still keeps rebooting randomly.

I have noticed, that almost every time I see a reboot and look at the log file the first thing that appears is this, that is, the first line after the reboot is:

Mon May 11 22:16:59 2020 daemon.info dnsmasq[1148]: exiting on receipt of SIGTERM
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: started, version 2.80 cachesize 150
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: DNS service limited to local subnets
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile
Mon May 11 22:16:59 2020 daemon.info dnsmasq-dhcp[2722]: DHCP, IP range 192.168.2.100 -- 192.168.2.249, lease time 12h
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain test
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain onion
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain localhost
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain local
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain invalid
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain bind
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain lan
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: reading /tmp/resolv.conf.auto
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain test
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain onion
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain localhost
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain local
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain invalid
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain bind
Mon May 11 22:16:59 2020 daemon.info dnsmasq[2722]: using local addresses only for domain lan

Please, I need help since I can’t work if it constantly resets. If you need any more information, please do not hesitate to ask me.

16.08.201694Base systemBug ReportVery LowMediumnetifd: PPPoE MTU problemTrunkNew Task Description

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

This leeds to log messages like this:


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


and MTUs other than what you really want.

example:


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

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

Regards,
Martin

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

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

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

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

...

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

...
...

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

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

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

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

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

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

Hello,

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

It is a Xiaomi Nano (lite).

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

29.11.2016315Base systemFeature RequestVery LowMediumImprove sysupgrade (CLI) on dual-partition routersTrunkUnconfirmed Task Description

Some of the recent Linksys (maybe other) routers have two partitions: WRT1900, EA8500, etc.

Would be great if when running sysupgrade on those routers it did NOT kill all active processes and kept the router working while writing an image to the inactive partition.

Would also be great if there was an option to prevent automatic reboot after writing an image.

Ultimate goal is to have an upgrade process where current working state is uninterrupted and only when you reboot – you boot into new image.

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

- Device problem occurs on:

WRT3200ACM

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

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

- Steps to reproduce

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

json_add_string local “$ipladdr”

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

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

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

Config:

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

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

Log:

Thu Feb  9 15:54:37 2017 daemon.err hostapd: WPA initialization for VLAN 1 failed (-1)
Thu Feb  9 15:54:37 2017 daemon.err hostapd: WPA deinit of wlan0.1 failed
Thu Feb  9 15:54:37 2017 daemon.debug hostapd: wlan0: STA ac:22:0b:a1:c7:6b IEEE 802.11: could not add dynamic VLAN interface for vlan=1
13.02.2017506Base systemBug ReportVery LowMediumBT Home Hub 5: 5g WiFi jumps to channel 36 and stops wo...TrunkUnconfirmed Task Description

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

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

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

It requires a reboot to restore service.

 


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

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

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

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

 


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

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

log with driver included in release

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

log with alernative ath10k-ct from packages

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


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

Vlan don’t work.


10.03.2017614Base systemBug ReportVery LowMedium/usr/lib/lua/luci/util.lua:623: Unable to establish ubu...TrunkUnconfirmed Task Description

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

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


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

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

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

The current naming scheme is quite long:

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

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

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

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

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

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

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


08.04.2017689Base systemBug ReportVery LowMedium WiFi disconnects on Dir300 b7lede-17.01Unconfirmed Task Description

This: https://github.com/nodemcu/nodemcu-firmware/issues/639 and this: https://forum.openwrt.org/viewtopic.php?id=43188

Device: Dlink Dir-300 b7 with latest LEDE 17.01

Solution: Adding an option ‘option disassoc_low_ack 0’ to /etc/config/wireless in the config wifi-iface section.

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

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

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

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

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

Greetings,
–Thomas

23.04.2017731Base systemBug ReportVery LowMediumOffline build not possible after "make download"lede-17.01Unconfirmed Task Description

I tried to do an offline build of almost the default configuration for x86_64 of 17.01.1. So I did “make download” (with that configuration) on a machine connected to the internet and then tried to build from there offline, but “make” tried to download files, that “make download” did not and failed.

The first few files were the following, then I gave up:

ncurses-6.0.tar.gz
lzo-2.09.tar.gz
usign-2015-07-04-ef641914.tar.xz
mbedtls-2.4.2-gpl.tgz
ustream-ssl-2016-07-02-ec80adaa.tar.xz
openssl-1.0.2k.tar.gz

28.04.2017740Base systemBug ReportVery LowMediumWRT54 Router Power LED continually flasheslede-17.01Unconfirmed Task Description
  • LEDE 17.01.1
  • WRT54G v3 and WRT54GS
  • after installing, power LED continually flashes
  • no noticeable difference in LED between failsafe/actual moment of soft reboot//when router is up
  • I had to failsafe the WRT54G multiple times due to other initial config errors (attempting to bridge wlan0 to LAN, which was possible in another OS), I could only identify failsafe by Pinging it then SSHing quickly
  • The method I described to identify failsafe is not mentioned in documentation
03.05.2017752Base systemBug ReportVery LowMediummtk7688 radio in client mode throwing kernel stack trac...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

AsiaRF AWM688, based on the mtk7688 SoC, similar to the LinkIt 7688

- Software versions of LEDE release, packages, etc.

current HEAD (21c2e93e67bc44c1b72dbbe2dc9f9451d44f81a0)

- Steps to reproduce

Put your wifi interface into station mode, with something like this:

uci set wireless.@wifi-iface[0].mode=sta
uci set wireless.@wifi-iface[0].network=wan
uci set wireless.@wifi-iface[0].ssid="<yournetworkssid>"
uci set wireless.@wifi-iface[0].encryption=<yournetworkencryption>
uci set wireless.@wifi-iface[0].key=<yournetworkkey>
uci set network.wan.ifname=''
uci commit wireless
uci commit network
/etc/init.d/network restart

The stack traces look like this:

[  381.712245] ------------[ cut here ]------------
[  381.721603] WARNING: CPU: 0 PID: 0 at compat-wireless-2017-01-31/net/mac80211/tx.c:4230 ieee80211_csa_is_complete+0x4d4/0x668 [mac80211]()
[  381.746243] Modules linked in: pppoe ppp_async snd_usb_audio pppox ppp_generic pl2303 nf_conntrack_ipv6 mmc_spi iptable_nat ipt_REJECT ipt_MASQUERADE ftdi_sio cp210x ch341 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG usbserial usbmon ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda spidev snd_usbmidi_lib slhc pwm_mediatek of_mmc_spi nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc7 crc_itu_t crc_ccitt snd_soc_simple_card snd_soc_ralink_i2s snd_soc_wm8960 i2c_mt7621 snd_soc_core ralink_gdma virt_dma mt76x2e mt7603e i2c_dev mt76 mac80211 cfg80211 compat ledtrig_oneshot ledtrig_heartbeat ledtrig_gpio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables snd_pcm_dmaengine snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd input_core soundcore vfat fat nls_utf8 nls_iso8859_1 nls_cp437 regmap_spi regmap_mmio regmap_i2c i2c_core regmap_core lzo_decompress lzo_compress mmc_block usb_storage mtk_sd mmc_core leds_gpio ohci_platform ohci_hcd ledtrig_transient ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[  381.997790] CPU: 0 PID: 0 Comm: swapper Tainted: G        W       4.4.61 #0
[  382.011576] Stack : 8035bff4 00000000 00000001 803a0000 803a10dc 803a0d63 8033d94c 00000000
          803f3438 8380de90 00000000 82d2b630 00000001 8004ae6c 80342e54 803a0000
          00000003 8380de90 80341258 8380dd74 00000001 80048dd8 83012b40 00000000
          8039fe50 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          ...
[  382.082022] Call Trace:
[  382.086872] [<8001486c>] show_stack+0x50/0x84
[  382.095501] [<8002544c>] warn_slowpath_common+0xa0/0xd0
[  382.105857] [<80025504>] warn_slowpath_null+0x18/0x24
[  382.115987] [<832aa34c>] ieee80211_csa_is_complete+0x4d4/0x668 [mac80211]
[  382.129537] 
[  382.132479] ---[ end trace cedc8f2cca6a57da ]---
[  448.821439] ------------[ cut here ]------------
[  448.830796] WARNING: CPU: 0 PID: 0 at compat-wireless-2017-01-31/net/mac80211/tx.c:4230 ieee80211_csa_is_complete+0x4d4/0x668 [mac80211]()
[  448.855431] Modules linked in: pppoe ppp_async snd_usb_audio pppox ppp_generic pl2303 nf_conntrack_ipv6 mmc_spi iptable_nat ipt_REJECT ipt_MASQUERADE ftdi_sio cp210x ch341 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG usbserial usbmon ums_usbat ums_sddr55 ums_sddr09 ums_karma ms_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda spidev snd_usbmidi_lib slhc pwm_mediatek of_mmc_spi nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc7 crc_itu_t crc_ccitt snd_soc_simple_card snd_soc_ralink_i2s snd_soc_wm8960 i2c_mt7621 snd_soc_core ralink_gdma virt_dma mt76x2e mt7603e i2c_dev mt76 mac80211 cfg80211 compat ledtrig_oneshot ledtrig_heartbeat ledtrig_gpio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables snd_pcm_dmaengine snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd input_core soundcore vfat fat nls_utf8 nls_iso8859_1 nls_cp437 regmap_spi regmap_mmio regmap_i2c i2c_core regmap_core lzo_decompress lzo_compress mmc_block usb_storage mtk_sd mmc_core leds_gpio ohci_platform ohci_hcd ledtrig_transient ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[  449.106963] CPU: 0 PID: 0 Comm: swapper Tainted: G        W       4.4.61 #0
[  449.120752] Stack : 8035bff4 00000000 00000001 803a0000 803a10dc 803a0d63 8033d94c 00000000
          803f3438 8380de90 00000000 82d2b630 00000001 8004ae6c 80342e54 803a0000
          00000003 8380de90 80341258 8380dd74 00000001 80048dd8 831a7852 00000000
          8039fe50 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          ...
[  449.191202] Call Trace:
[  449.196044] [<8001486c>] show_stack+0x50/0x84
[  449.204680] [<8002544c>] warn_slowpath_common+0xa0/0xd0
[  449.215034] [<80025504>] warn_slowpath_null+0x18/0x24
[  449.225170] [<832aa34c>] ieee80211_csa_is_complete+0x4d4/0x668 [mac80211]
[  449.238722] 
[  449.241679] ---[ end trace cedc8f2cca6a57db ]---

The line number is a bit off, but it looks like maybe ieee80211_csa_is_complete is complaining because vif→type == station mode isn’t handled. I don’t know what “csa” means here.

15.05.2017786Base systemFeature RequestVery LowMediumPlease, add support to ecdsa key typelede-17.01Researching Task Description

At the moment dropbear tool is compiled without the ecdsa key type support.
ECDSA (https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm) is considere better than RSA as it requires fewer key bits to gain same security.

16.05.2017788Base systemBug ReportVery LowMediumMQMaker WiTi 5ghz interface does not workAllUnconfirmed Task Description

Supply the following if possible:
- MQMaker WiTi
- All released LEDE versions
- enable the 5ghz interface. LEDE reports that it’s up and running but it isn’t.

I tried 3 builds.

LEDE trunk - fail
LEDE 17.01.0 - fail
OpenWRT trunk - works.

Something broke in the mt76 driver between OpenWRT trunk and LEDE final.

AFAIK it’s after the bug fix to packet injection.

 


09.06.2017833Base systemBug ReportVery LowMediumpppoe memory problemlede-17.01Unconfirmed Task Description

I have observed a problem with pppoe connection. PPP runs well, but if the connection is interrupted by synchronization etc. then the free memory is less.

If I pull the plug and wait, then the system rapidly loses free memory and then crashes by approximately 25 MB of free RAM.

echo 3> /proc/sys/vm/drop_caches does not help in this case.

Tested on Linksys WRT1200AC, kernel 4.4.69 and 4.4.70
LEDE 17.01

Is there a way to investigate the problem more closely?

Many Thanks

Edy

18.06.2017855Base systemBug ReportVery LowMediumWrong MAC address (00:00:00:00:00:01) on Arcadyan AR751...lede-17.01Unconfirmed Task Description
root@LEDE:~# ifconfig | grep HW
br-lan    Link encap:Ethernet  HWaddr 00:00:00:00:00:01  
eth0      Link encap:Ethernet  HWaddr 00:00:00:00:00:01  
eth0.1    Link encap:Ethernet  HWaddr 00:00:00:00:00:01  
eth0.2    Link encap:Ethernet  HWaddr 00:00:00:00:00:01  
wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:02

I know MAC addresses can be overriden in config, but is it possible to automatically detect the original addresses?

20.06.2017858Base systemBug ReportVery LowMediumInstalling bind / named will cause resolving names fail...TrunkUnconfirmed Task Description

Device TP-LINK MR-3220 v2.1 and 2.3 and 2.4 tested, LEDE 17.01.1 version.

After installing bind-server, setting “option port ‘0’” for dnsmasq (to disable DNS configuration) and using provided named.conf file (below), resolution of domain names to IP addresses breaks down.

I was able to track down the problem. There is race condition in bringing interfaces up, starting nptd service and named service, resulting in:
* named service beeing unable to open sockets and/or
* ntpd service beeing unable to connect to ntp pool and set router time correctly and/or
* incorrect time setting causes dnssec of named to reject proper answers for dns resolving.

With no named installed, the dnsmasq itself often starts too early, but this is masked by it beeing reinitialized on lan interface up event.

This is a known openwrt problem, the workaround is described here: https://dev.openwrt.org/ticket/19427 and involves creating a “netwait” service. I have tested this workaround and confirmed it works, however it is not nice.

Here my named.conf:

This is the primary configuration file for the BIND DNS server named. acl locals {
localhost;
10.10.10/24;
}; options {
directory “/tmp”; forwarders {
8.8.8.8;
8.8.4.4;
}; recursion yes;
allow-query { locals; }; dnssec-validation auto;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { none; };
listen-on { 127.0.0.1; 10.10.10.10; };
};
prime the server with knowledge of the root servers
zone “.” {

type hint;
file "/etc/bind/db.root";

};

be authoritative for the localhost forward and reverse zones, and for
broadcast zones as per RFC 1912

zone “localhost” {

type master;
file "/etc/bind/db.local";

};

zone “127.in-addr.arpa” {

type master;
file "/etc/bind/db.127";

};

zone “0.in-addr.arpa” {

type master;
file "/etc/bind/db.0";

};

zone “255.in-addr.arpa” {

type master;
file "/etc/bind/db.255";

};

 


28.06.2017873Base systemBug ReportVery LowMediumproblems of mt7628 wifi driver on miwifi nanoAllUnconfirmed Task Description

I started using lede on my miwifi nano since the release of version 17.01.1. All function works well except its wireless function.

What makes it a problem is its stability. After a random period of time(ranging from a quarter of an hour to half of a day), it suddenly disconnected. If you try to reconnect, my device shows something like “setting the network address”(varing from devices to devices). After reboot, I found something like “deauthenticated due to inactivity (timer DEAUTH/REMOVE)”. Unfortunately, I haven’t found a way to reproduce the problem till now.

I thought there might be bugs on its wireless driver because on another firmware(http://downloads.pandorabox.com.cn/pandorabox/Xiaomi-Mini-R1CL/firmware/PandoraBox-ralink-mt7628-xiaomi-r1cl-squashfs-sysupgrade-r1752-20151201.bin) which is a variant of Openwrt, it works well.

There are many other problems like the inability to set channel to auto and the txpower option is of no use. But for my daily use, they may not so important compared to the connectivity problem.

Sorry for my bad English and thank you for fixing it.

11.08.2017954Base systemBug ReportVery LowMediumIGMP queries redirected to CPU port when snooping enabl...AllUnconfirmed Task Description

The Netgear R7800 has a QCA8337N switch chip, and the CPU has two interfaces (eth0/port 0 and eth1/port 6) connected to the switch. The default in LEDE is that WAN is on port0/eth0, and LAN is on port6/eth1.

When using multicast, it is often desirable to enable IGMP snooping on the switch to avoid flooding the multicast stream to all ports. A multicast server will normally send IGMP general queries to the all hosts address 224.0.0.1 at a regular interval (every few minutes) to check if there are still clients that wants to receive the multicast.

However, when IGMP snooping is enabled on this device, these queries are all redirected to port 0 on the switch, which is a problem if the multicast server is within the LAN. In this scenario, the server sends queries, but these queries are not being broadcast to the clients within the LAN, instead they end up at port 0 (eth0) where they are not needed. The server will then receive no responses to the queries, and subsequently times out and stops the stream multicast.

I think I found a viable fix for this, which is to set bit 3 (IGMP_COPY_EN) of the GLOBAL_FW_CTRL0 register in the switch chip to 1. This causes the IGMP queries to be broadcast on all switch ports (provided they are members of the same VLAN), instead of being redirected only to port 0. In my testing, I have found no adverse effects from this change.

I have attached a patch for this change, to make testing easy:

Assuming that the LAN interface is br-lan, run tcpdump on the router and inject IGMP general queries from a computer in the LAN, for example using Ostinato. With IGMP snooping off, the query is seen on br-lan:

root@R7800:/# tcpdump -i br-lan igmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br-lan, link-type EN10MB (Ethernet), capture size 262144 bytes
11:47:06.832511 IP 192.168.20.1 > all-systems.mcast.net: igmp query v2

If IGMP snooping is turned on (globally or for the port where the query is received), then the query no longer appears at br-lan,
but instead only on eth0. Applying the attached patch fixes this.

21.08.2017972Base systemBug ReportVery LowMediumUbiquiti EdgeRouter X (ER-X) port connection interrupti...lede-17.01Unconfirmed Task Description

- Device: Ubiquiti EdgeRouter X (ER-X)
- LEDE version: 17.01.2

We have several devices running, with 17.01.1 all is rock solid.
After upgrading to 17.01.2 we have problems with port connection interruption and sometimes kernel crashes.

Other people have similar experiences → https://forum.lede-project.org/t/er-x-lan-port-connection-interruption/5709

Port connection interruption log:

Mon Aug 21 07:28:57 2017 kern.info kernel: [69826.410000] mtk_soc_eth 1e100000.ethernet eth0: port 3 link down
Mon Aug 21 07:28:59 2017 kern.info kernel: [69828.710000] mtk_soc_eth 1e100000.ethernet eth0: port 3 link up
Mon Aug 21 07:29:05 2017 kern.info kernel: [69833.950000] mtk_soc_eth 1e100000.ethernet eth0: port 3 link down
Mon Aug 21 07:29:34 2017 kern.info kernel: [69863.260000] mtk_soc_eth 1e100000.ethernet eth0: port 3 link up
Mon Aug 21 07:29:53 2017 kern.info kernel: [69882.840000] mtk_soc_eth 1e100000.ethernet eth0: port 3 link down
Mon Aug 21 07:30:01 2017 kern.info kernel: [69890.820000] mtk_soc_eth 1e100000.ethernet eth0: port 3 link up
Mon Aug 21 07:30:02 2017 kern.info kernel: [69891.570000] mtk_soc_eth 1e100000.ethernet eth0: port 3 link down
Mon Aug 21 07:30:19 2017 kern.info kernel: [69908.040000] mtk_soc_eth 1e100000.ethernet eth0: port 3 link up

Kernel crash log:

Sun Aug 20 15:39:45 2017 kern.err kernel: [12873.930000] INFO: rcu_sched detected stalls on CPUs/tasks:
Sun Aug 20 15:39:45 2017 kern.err kernel: [12873.940000] 	3-...: (0 ticks this GP) idle=88c/0/0 softirq=786546/786546 fqs=0 
Sun Aug 20 15:39:45 2017 kern.err kernel: [12873.950000] 	(detected by 1, t=6004 jiffies, g=23478, c=23477, q=130)
Sun Aug 20 15:39:45 2017 kern.info kernel: [12873.960000] Task dump for CPU 3:
Sun Aug 20 15:39:45 2017 kern.info kernel: [12873.970000] swapper/3       R running      0     0      1 0x00100000
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12873.980000] Stack : 00000000 8fc53c80 00000bb8 ffffffff 00000a4f 00000000 804762a4 80420000
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12873.980000] 	  8042475c 00000001 00000001 80424680 80424724 80420000 80420000 8000c0e0
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12873.980000] 	  1100fc03 00000003 8fc74000 8fc75ec0 80420000 8000c410 1100fc03 00000003
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12873.980000] 	  804762a4 80420000 804762a4 8005dc70 80420000 8001acc0 1100fc03 00000000
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12873.980000] 	  00000004 804244a0 000000a0 8001acc8 f99b5fff 5dfcf51e fccb7bd5 ff7fca95
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12873.980000] 	  ...
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12874.050000] Call Trace:[<8000c0e0>] 0x8000c0e0
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12874.060000] [<8000c410>] 0x8000c410
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12874.070000] [<8005dc70>] 0x8005dc70
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12874.080000] [<8001acc0>] 0x8001acc0
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12874.080000] [<8001acc8>] 0x8001acc8
Sun Aug 20 15:39:45 2017 kern.warn kernel: [12874.090000] 
Sun Aug 20 15:39:45 2017 kern.err kernel: [12874.090000] rcu_sched kthread starved for 6018 jiffies! g23478 c23477 f0x0 s3 ->state=0x1
Sun Aug 20 15:40:47 2017 kern.err kernel: [12936.490000] INFO: rcu_sched detected stalls on CPUs/tasks:
Sun Aug 20 15:40:47 2017 kern.err kernel: [12936.500000] 	3-...: (0 ticks this GP) idle=a0c/0/0 softirq=786546/786546 fqs=0 
Sun Aug 20 15:40:47 2017 kern.err kernel: [12936.510000] 	(detected by 1, t=6004 jiffies, g=23490, c=23489, q=159)
Sun Aug 20 15:40:47 2017 kern.info kernel: [12936.520000] Task dump for CPU 3:
Sun Aug 20 15:40:47 2017 kern.info kernel: [12936.530000] swapper/3       R running      0     0      1 0x00100000
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.540000] Stack : 00000000 8fc53c80 00000bc6 ffffffff 00000a59 00000000 804762a4 80420000
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.540000] 	  8042475c 00000001 00000001 80424680 80424724 80420000 80420000 8000c0e0
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.540000] 	  1100fc03 00000003 8fc74000 8fc75ec0 80420000 8000c410 1100fc03 00000003
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.540000] 	  804762a4 80420000 804762a4 8005dc70 80420000 8001acc0 1100fc03 00000000
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.540000] 	  00000004 804244a0 000000a0 8001acc8 f99b5fff 5dfcf51e fccb7bd5 ff7fca95
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.540000] 	  ...
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.610000] Call Trace:[<8000c0e0>] 0x8000c0e0
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.620000] [<8000c410>] 0x8000c410
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.630000] [<8005dc70>] 0x8005dc70
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.640000] [<8001acc0>] 0x8001acc0
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.640000] [<8001acc8>] 0x8001acc8
Sun Aug 20 15:40:47 2017 kern.warn kernel: [12936.650000] 
Sun Aug 20 15:40:47 2017 kern.err kernel: [12936.650000] rcu_sched kthread starved for 6018 jiffies! g23490 c23489 f0x0 s3 ->state=0x1
Sun Aug 20 15:41:52 2017 kern.err kernel: [13000.910000] INFO: rcu_sched detected stalls on CPUs/tasks:
Sun Aug 20 15:41:52 2017 kern.err kernel: [13000.920000] 	3-...: (0 ticks this GP) idle=b20/0/0 softirq=786546/786546 fqs=0 
Sun Aug 20 15:41:52 2017 kern.err kernel: [13000.930000] 	(detected by 1, t=6004 jiffies, g=23496, c=23495, q=184)
Sun Aug 20 15:41:52 2017 kern.info kernel: [13000.940000] Task dump for CPU 3:
Sun Aug 20 15:41:52 2017 kern.info kernel: [13000.950000] swapper/3       R running      0     0      1 0x00100000
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13000.960000] Stack : 00000000 0e77bc1c 00000bd5 ffffffff 00000a65 00401b75 804762a4 80420000
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13000.960000] 	  8042475c 00000001 00000001 80424680 80424724 80420000 000010d9 80013554
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13000.960000] 	  1100fc03 00000003 8fc74000 8fc75ec0 80420000 8005dc78 1100fc03 00000003
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13000.960000] 	  00000000 80420000 804762a4 8005dc70 80420000 8001acc0 1100fc03 00000000
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13000.960000] 	  00000004 804244a0 000000a0 8001acc8 f99b5fff 5dfcf51e fccb7bd5 ff7fca95
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13000.960000] 	  ...
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13001.030000] Call Trace:[<80013554>] 0x80013554
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13001.040000] [<8005dc78>] 0x8005dc78
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13001.050000] [<8005dc70>] 0x8005dc70
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13001.060000] [<8001acc0>] 0x8001acc0
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13001.060000] [<8001acc8>] 0x8001acc8
Sun Aug 20 15:41:52 2017 kern.warn kernel: [13001.070000] 
Sun Aug 20 15:41:52 2017 kern.err kernel: [13001.070000] rcu_sched kthread starved for 6018 jiffies! g23496 c23495 f0x0 s3 ->state=0x1
Sun Aug 20 15:43:01 2017 kern.err kernel: [13069.970000] INFO: rcu_sched detected stalls on CPUs/tasks:
Sun Aug 20 15:43:01 2017 kern.err kernel: [13069.980000] 	3-...: (0 ticks this GP) idle=c38/0/0 softirq=786546/786546 fqs=0 
Sun Aug 20 15:43:01 2017 kern.err kernel: [13069.990000] 	(detected by 1, t=6004 jiffies, g=23508, c=23507, q=179)
Sun Aug 20 15:43:01 2017 kern.info kernel: [13070.000000] Task dump for CPU 3:
Sun Aug 20 15:43:01 2017 kern.info kernel: [13070.010000] swapper/3       R running      0     0      1 0x00100000
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.020000] Stack : 00000000 8fc53c80 00000be3 ffffffff 00000a77 00000000 804762a4 80420000
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.020000] 	  8042475c 00000001 00000001 80424680 80424724 80420000 80420000 8000c0e0
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.020000] 	  1100fc03 00000003 8fc74000 8fc75ec0 80420000 8000c410 1100fc03 00000003
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.020000] 	  804762a4 80420000 804762a4 8005dc70 80420000 8001acc0 1100fc03 00000000
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.020000] 	  00000004 804244a0 000000a0 8001acc8 f99b5fff 5dfcf51e fccb7bd5 ff7fca95
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.020000] 	  ...
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.090000] Call Trace:[<8000c0e0>] 0x8000c0e0
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.100000] [<8000c410>] 0x8000c410
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.110000] [<8005dc70>] 0x8005dc70
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.120000] [<8001acc0>] 0x8001acc0
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.120000] [<8001acc8>] 0x8001acc8
Sun Aug 20 15:43:01 2017 kern.warn kernel: [13070.130000] 
Sun Aug 20 15:43:01 2017 kern.err kernel: [13070.130000] rcu_sched kthread starved for 6018 jiffies! g23508 c23507 f0x0 s3 ->state=0x1
Mon Aug 21 01:52:45 2017 kern.err kernel: [49654.240000] INFO: rcu_sched detected stalls on CPUs/tasks:
Mon Aug 21 01:52:45 2017 kern.err kernel: [49654.250000] 	3-...: (0 ticks this GP) idle=8be/0/0 softirq=3072493/3072493 fqs=0 
Mon Aug 21 01:52:45 2017 kern.err kernel: [49654.260000] 	(detected by 1, t=6004 jiffies, g=90843, c=90842, q=104)
Mon Aug 21 01:52:45 2017 kern.info kernel: [49654.270000] Task dump for CPU 3:
Mon Aug 21 01:52:45 2017 kern.info kernel: [49654.280000] swapper/3       R running      0     0      1 0x00100000
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.290000] Stack : 00000000 00000001 00000005 00000000 00000000 00000001 804762a4 80420000
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.290000] 	  8042475c 00000001 00000001 80424680 80424724 80420000 00000000 80013554
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.290000] 	  1100fc03 00000003 8fc74000 8fc75ec0 80420000 8005dc78 1100fc03 00000003
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.290000] 	  00000000 80420000 804762a4 8005dc70 80420000 8001acc0 1100fc03 00000000
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.290000] 	  00000004 804244a0 000000a0 8001acc8 f99b5fff 5dfcf51e fccb7bd5 ff7fca95
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.290000] 	  ...
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.360000] Call Trace:[<80013554>] 0x80013554
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.370000] [<8005dc78>] 0x8005dc78
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.380000] [<8005dc70>] 0x8005dc70
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.390000] [<8001acc0>] 0x8001acc0
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.390000] [<8001acc8>] 0x8001acc8
Mon Aug 21 01:52:45 2017 kern.warn kernel: [49654.400000] 
Mon Aug 21 01:52:45 2017 kern.err kernel: [49654.400000] rcu_sched kthread starved for 6018 jiffies! g90843 c90842 f0x0 s3 ->state=0x1
Mon Aug 21 01:53:51 2017 kern.err kernel: [49720.510000] INFO: rcu_sched detected stalls on CPUs/tasks:
Mon Aug 21 01:53:51 2017 kern.err kernel: [49720.520000] 	3-...: (0 ticks this GP) idle=a3e/0/0 softirq=3072493/3072493 fqs=0 
Mon Aug 21 01:53:51 2017 kern.err kernel: [49720.530000] 	(detected by 1, t=6004 jiffies, g=90851, c=90850, q=139)
Mon Aug 21 01:53:51 2017 kern.info kernel: [49720.540000] Task dump for CPU 3:
Mon Aug 21 01:53:51 2017 kern.info kernel: [49720.550000] swapper/3       R running      0     0      1 0x00100000
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.560000] Stack : 00000000 00000001 00000005 00000000 00000000 00000001 804762a4 80420000
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.560000] 	  8042475c 00000001 00000001 80424680 80424724 80420000 00000000 80013554
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.560000] 	  1100fc03 00000003 8fc74000 8fc75ec0 80420000 8005dc78 1100fc03 00000003
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.560000] 	  00000000 80420000 804762a4 8005dc70 80420000 8001acc0 1100fc03 00000000
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.560000] 	  00000004 804244a0 000000a0 8001acc8 f99b5fff 5dfcf51e fccb7bd5 ff7fca95
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.560000] 	  ...
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.630000] Call Trace:[<80013554>] 0x80013554
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.640000] [<8005dc78>] 0x8005dc78
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.650000] [<8005dc70>] 0x8005dc70
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.660000] [<8001acc0>] 0x8001acc0
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.660000] [<8001acc8>] 0x8001acc8
Mon Aug 21 01:53:51 2017 kern.warn kernel: [49720.670000] 
Mon Aug 21 01:53:51 2017 kern.err kernel: [49720.670000] rcu_sched kthread starved for 6018 jiffies! g90851 c90850 f0x0 s3 ->state=0x1


02.09.2017996Base systemBug ReportVery LowMediumAt boot /etc/hotplug scripts are not triggered by kerne...AllUnconfirmed Task Description

At boot /etc/hotplug.d scripts are not triggered by kernel events.
If we have a HDD/usb printer atached to an usb port, at boot, those scripts are not executed. However when we add/remove it later, after boot those scripts are executed properly.

Same problem as here:

https://dev.openwrt.org/ticket/18116

I am using this hotplug script:

https://www.all4os.com/router/add-multiple-usb-printers-to-openwrt-firmware-router-via-p910nd-using-hotplug.html

27.09.20171020Base systemBug ReportVery LowMediumMikrotik RB493G AR8316 switch0/ETH0 cannot be managed AllUnconfirmed Task Description

Exists on OpenWRT 14 and 15, LEDE 17 and Trunk

The behaviour is identical to issues reported on RB951G and RB2011 models.

See historical details:
https://github.com/openwrt/openwrt/issues/352 https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/030216.html

I have been able to work around the issue by cross-connecting the PoE/WAN port to switch0 LAN4 and turning off eth0 CPU. This allows me to use all remaining ports. It’s a horrible kludge, I’m only mentioning it as a temporary workaround.

07.10.20171046Base systemBug ReportVery LowMediumLED lights functionality brokes WiFi connection, switch...lede-17.01Unconfirmed Task Description

On the Linksys 3200ACM with clean LEDE 17.01.3
it’s not possible to turn off WIFI LEDS.

Any write operation to /sys/class/leds/rango:white:wlan_2g/trigger
or cat /sys/class/leds/rango:white:wlan_5g/trigger will cause the WiFi
to stop operating (accordingly 2G or 5G depending which trigger we want to change).
Steps to reproduce:

echo none > /sys/class/leds/rango:white:wlan_2g/trigger

What is strange that after boot the WiFi leds are operating (flashing according to tx/rx),
but current trigger reported by sysfs is anyway none:

cat /sys/class/leds/rango:white:wlan_5g/trigger 
[none] nand-disk usbport mmc0 timer default-on netdev phy0rx phy0tx phy0assoc phy0radio phy1rx phy1tx phy1assoc phy1radio

The writes to the brightness value are ignored.

Also there are no controls for the wired ethernet switch leds.
All controls that are reported by sysfs:

ls /sys/class/leds/
mmc0::                      pca963x:0:68:14             pca963x:rango:amber:wan     pca963x:rango:white:wan     rango:white:wlan_5g
pca963x:0:68:10             pca963x:0:68:15             pca963x:rango:amber:wps     pca963x:rango:white:wps
pca963x:0:68:11             pca963x:0:68:2              pca963x:rango:white:usb2    rango:white:power
pca963x:0:68:12             pca963x:0:68:3              pca963x:rango:white:usb3_1  rango:white:sata
pca963x:0:68:13             pca963x:0:68:4              pca963x:rango:white:usb3_2  rango:white:wlan_2g
28.10.20171121Base systemBug ReportVery LowMediummake image doesn't return failure if build failslede-17.01Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
N/A

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

- Steps to reproduce
Set up the imagebuilder and build an image with:

make -C $BUILDER_DIR/ image PROFILE="$PROFILE" PACKAGES="$PACKAGES" FILES="$PWD/$FILES_DIR" CUSTOMIZE_IMAGE_SCRIPT=$PWD/$ROUTER_MODEL.custom

Where $PACKAGES is a list big enough to make the image too big so that you get:

[mktplinkfw] *** error: images are too big by 1614 bytes

Observe that the exit status from the above make is still 0. That make should reflect that the build failed with a non-zero exit status.

31.10.20171133Base systemBug ReportVery LowMediumCan't set channels 12 and 13 on Raspberry Pi 3 in AP co...AllUnconfirmed Task Description

It is not possible to set up channel 12/13 on Raspberry Pi 3 in Wifi AP configuration. I get error “brcmfmac: brcmf_cfg80211_start_ap: Set Channel failed: chspec=4109, -20”.
Tested on 17.01.1 and latest snapshot (r5217-098afa1).
PS Raspbian works properly on 13 channel as AP.

Logs:

root@LEDE:~# uci show wireless
wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.hwmode='11g'
wireless.radio0.path='platform/soc/3f300000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1'
wireless.radio0.htmode='HT20'
wireless.radio0.disabled='0'
wireless.radio0.country='PL'
wireless.radio0.channel='11'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='lan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.ssid='Dantooine'
wireless.default_radio0.encryption='psk2'
wireless.default_radio0.key='secret'

root@LEDE:~# wifi
[  828.291269] device wlan0 left promiscuous mode
[  828.301579] br-lan: port 2(wlan0) entered disabled state
[  830.594037] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  830.608333] br-lan: port 2(wlan0) entered blocking state
[  830.619697] br-lan: port 2(wlan0) entered disabled state
[  830.631336] device wlan0 entered promiscuous mode
[  830.911507] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  830.924197] br-lan: port 2(wlan0) entered blocking state
[  830.935606] br-lan: port 2(wlan0) entered forwarding state

root@LEDE:~# uci set wireless.radio0.channel=13
root@LEDE:~# uci commit wireless
root@LEDE:~# wifi
[  913.551274] device wlan0 left promiscuous mode
[  913.561751] br-lan: port 2(wlan0) entered disabled state
[  915.854693] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  915.869110] br-lan: port 2(wlan0) entered blocking state
[  915.880481] br-lan: port 2(wlan0) entered disabled state
[  915.892046] device wlan0 entered promiscuous mode
[  916.080443] brcmfmac: brcmf_cfg80211_start_ap: Set Channel failed: chspec=4109, -20
[  916.131249] device wlan0 left promiscuous mode
[  916.142014] br-lan: port 2(wlan0) entered disabled state
[  927.997654] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  928.012458] br-lan: port 2(wlan0) entered blocking state
[  928.024440] br-lan: port 2(wlan0) entered disabled state
[  928.036703] device wlan0 entered promiscuous mode
[  928.222287] brcmfmac: brcmf_cfg80211_start_ap: Set Channel failed: chspec=4109, -20
[  928.301237] device wlan0 left promiscuous mode
[  928.312608] br-lan: port 2(wlan0) entered disabled state

root@LEDE:~# uci set wireless.radio0.channel=11
root@LEDE:~# uci commit wireless
root@LEDE:~# wifi
[  990.032785] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  990.048153] br-lan: port 2(wlan0) entered blocking state
[  990.060246] br-lan: port 2(wlan0) entered disabled state
[  990.072619] device wlan0 entered promiscuous mode
[  990.351670] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  990.365070] br-lan: port 2(wlan0) entered blocking state
[  990.377132] br-lan: port 2(wlan0) entered forwarding state
[ 1000.491313] device wlan0 left promiscuous mode
[ 1000.502769] br-lan: port 2(wlan0) entered disabled state
[ 1002.676007] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1002.691453] br-lan: port 2(wlan0) entered blocking state
[ 1002.703651] br-lan: port 2(wlan0) entered disabled state
[ 1002.716135] device wlan0 entered promiscuous mode
[ 1003.093512] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1003.107183] br-lan: port 2(wlan0) entered blocking state
[ 1003.119522] br-lan: port 2(wlan0) entered forwarding state

root@LEDE:~# iw list
Wiphy phy0
	max # scan SSIDs: 10
	max scan IEs length: 2048 bytes
	max # sched scan SSIDs: 16
	max # match sets: 16
	max # scan plans: 1
	max scan plan interval: 508
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports T-DLS.
	Available Antennas: TX 0 RX 0
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * P2P-client
		 * P2P-GO
		 * P2P-device
	Band 1:
		Capabilities: 0x1020
			HT20
			Static SM Power Save
			RX HT20 SGI
			No RX STBC
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 16 usec (0x07)
		HT TX/RX MCS rate indexes supported: 0-7
		Frequencies:
			* 2412 MHz [1] (20.0 dBm)
			* 2417 MHz [2] (20.0 dBm)
			* 2422 MHz [3] (20.0 dBm)
			* 2427 MHz [4] (20.0 dBm)
			* 2432 MHz [5] (20.0 dBm)
			* 2437 MHz [6] (20.0 dBm)
			* 2442 MHz [7] (20.0 dBm)
			* 2447 MHz [8] (20.0 dBm)
			* 2452 MHz [9] (20.0 dBm)
			* 2457 MHz [10] (20.0 dBm)
			* 2462 MHz [11] (20.0 dBm)
			* 2467 MHz [12] (20.0 dBm)
			* 2472 MHz [13] (20.0 dBm)****
			* 2484 MHz [14] (disabled)
	valid interface combinations:
		 * #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
		   total <= 3, #channels <= 1
		 * #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
		   total <= 4, #channels <= 1
Showing tasks 151 - 200 of 1140 Page 4 of 23<<First - 2 - 3 - 4 - 5 - 6 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing