OpenWrt/LEDE Project

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

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

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

OpenedIDCategoryTask TypePrioritySeveritySummaryReported InStatus  desc
28.06.2017873Base systemBug ReportVery LowMediumproblems of mt7628 wifi driver on miwifi nanoAllRequires testing 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.

16.07.20181657Base systemBug ReportVery LowLowCannot add/remove VLAN's in AR71xx mikrotik buildopenwrt-18.06Requires testing Task Description

Add/remove of VLANs in the LUCI interface {Network>switch} does not create new VLANs as per previous versions.

“Changes pending” match “existing config”

network.cfg0a1ec7
network.cfg0a1ec7.ports=0t 5
network.cfg0a1ec7.vid=2

network.cfg091ec7
network.cfg091ec7.ports=0t 1 2 3 4
network.cfg091ec7.vid=1

network.cfg071ec7
network.cfg071ec7.ports=0t 1 2 3 4
network.cfg071ec7.vid=1

21.11.2016295KernelBug ReportVery LowHighath10k_pci 0001:01:00.0: SWBA overrun on vdevTrunkWaiting on reporter Task Description

Supply the following if possible:

- TP-LINK c2600 v1.1
- LEDE Reboot r2244
- after some hours, the network device produce the below stacktrace.

[61789.980553] ————[ cut here ]———— [61789.980600] WARNING: CPU: 0 PID: 3 at net/core/dev.c:4837 net_rx_action+0×154/0x2e4()
[61789.984240] Modules linked in: pppoe ppp_async iptable_nat pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_id xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack_netlink nf_conntrack iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt br_netfilter em_cmp sch_teql em_nbyte sch_htb sch_pie sch_gred sch_dsmark cls_basic act_ipt sch_prio em_text
[61790.061568] sch_codel sch_tbf sch_sfq em_meta act_police sch_fq sch_red act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ath10k_pci ath10k_core ath mac80211 cfg80211 compat ledtrig_usbport xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_tunnel tunnel6 tun snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd input_core soundcore
[61790.130320] usb_storage uhci_hcd f2fs ext4 jbd2 mbcache crc32c_generic crypto_hash leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom dwc3_of_simple ohci_platform ohci_hcd phy_qcom_dwc3 ahci ehci_platform ehci_hcd sd_mod ahci_platform libahci_platform libahci libata scsi_mod gpio_button_hotplug usbcore nls_base usb_common
[61790.158798] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.4.30 #0
[61790.159062] Hardware name: Qualcomm (Flattened Device Tree)
[61790.165160] [<c02207f4>] (unwind_backtrace) from [<c021d2e4>] (show_stack+0×14/0×20)
[61790.170534] [<c021d2e4>] (show_stack) from [<c03b82a4>] (dump_stack+0x8c/0xa0)
[61790.178521] [<c03b82a4>] (dump_stack) from [<c0228aec>] (warn_slowpath_common+0xa4/0xd0)
[61790.185550] [<c0228aec>] (warn_slowpath_common) from [<c0228bcc>] (warn_slowpath_null+0x1c/0×24)
[61790.193798] [<c0228bcc>] (warn_slowpath_null) from [<c050bcd0>] (net_rx_action+0×154/0x2e4)
[61790.202568] [<c050bcd0>] (net_rx_action) from [<c022bc90>] (do_softirq+0xdc/0×230)
[61790.210636] [<c022bc90>] (
do_softirq) from [<c022be18>] (run_ksoftirqd+0×34/0×64)
[61790.218626] [<c022be18>] (run_ksoftirqd) from [<c0246784>] (smpboot_thread_fn+0×190/0x1b8)
[61790.226006] [<c0246784>] (smpboot_thread_fn) from [<c02438e4>] (kthread+0xf8/0×100)
[61790.234335] [<c02438e4>] (kthread) from [<c0209cb8>] (ret_from_fork+0×14/0x3c)
[61790.241951] —[ end trace bbf62e8dea16c714 ]— [61790.250226] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon

18.04.20181502KernelBug ReportVery LowHighMT7621 - MTU > 1500 not supported (was previously) TrunkWaiting on reporter Task Description

Edgerouter X / Edgerouter X SFP running Trunk

root@OpenWrt:~# ifconfig eth0 mtu 1600
ifconfig: SIOCSIFMTU: Invalid argument

[ 109.619242] eth0: Invalid MTU 1600 requested, hw max 1500

This was supported previously on Reboot r4651-a6f6f8d

 


11.05.20181542Base systemBug ReportVery LowHighDHCP (dnsmasq) server doesn't properly reply on request...TrunkWaiting on reporter Task Description

There’s some breakage on the EdgeRouter Lite regarding DHCP/dnsmasq on LAN.
Neither r6861 (local build) or r6868 (official snapshot) works.

Setting static ip on clients works so it’s not a link issue.

17.06.20181592PackagesBug ReportVery LowHighmap.sh failing to do MTU:1460bytes lede-17.01Waiting on reporter Task Description

- Device problem occurs on
Buffalo BHR-4GRV

- Software versions of OpenWrt/LEDE release, packages, etc.
Reboot (17.01.4, r3560-79f57e422d)

- Steps to reproduce
Somewhat relevant to the bug report on map.sh from a few days ago, I also discovered the following :

While the MTU of the IPv4-over-IPv6 tunnel created by that script may be set to 1460bytes in /etc/config/network, the actual tunnel will only achieve 1452bytes when tested with ping at DF=1.

FYI, the MAP-E service I am using (called “v6plus” provided by JPNE, AS2516) runs on the 1500byte-MTU for IPv6 and is known to support 1460bytes.
You may also see this on the page of YAMAHA, for their brand-new firmware released for RTX1210 router. (http://www.rtpro.yamaha.co.jp/RT/docs/v6plus/index.html - in Japanese)

BTW, the MTU of such tunnels being limited to some value that is 8bytes less than what is theoretically possible on Linux-based systems is something I’ve seen before and it has something to do with encapsulation limit option (which can be disabled).
If this were on Debian/Ubuntu I would do something like this - or else I get the 1452bytes with extra 8bytes subtracted from 1460bytes for MTU.

pre-up ip tunnel add ${IFACE} mode ipip6 remote <REMOTE> local <LOCAL> encaplimit none

Now, I tried to see how I could do the same on OpenWrt - and since I did not know how scripts brought up tunnels precisely, I began by seeing if any other implementations for OpenWrt using IPv4-over-IPv6 tunnel behaved any differently. I discovered that the dslite.sh in the package ds-lite installed on BHR-4GRV actually does the 1460bytes-MTU when tested with my server on AS9370 (Sakura Internet, with the MTU at 1500bytes for the L3, behaving as a simulated CGN of DS-Lite). I then tried to see if those two scripts did anything different with respect to creating tunnels. Unfortunately, I was not able to spot any notable differences (or maybe I should have gone further with the investigation).

I know this is most likely a simple fix, and maybe the most I need to get from this bug report is the info on what to look into rather than actually filing a bug report. Any helpful info is appreciated since I do intend to work on this by myself.

Thanks

17.07.20181665Base systemBug ReportVery LowHighNetgear r6100 (ar71xx) does not recognize 5Ghz wlan int...openwrt-18.06Waiting on reporter Task Description

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

 

Problem occurs on Netgear R6100

Software version 18.06 rc2 (also on rc1)

Steps to reproduce:
1) upgrade to 18.06 rc2
2) log in and check for existence of wlan0 & wlan1 (showing both 2.4 & 5 Ghz wifi interfaces are present). OR in LuCI, check that there is radio0 and radio1

Attaching dmesg and logread from boot of 18.06 rc2

28.12.2016362Base systemBug ReportVery LowMediumWR1043ND v4 Slow WAN -> LAN Whilst Synced @100MbpsTrunkWaiting on reporter Task Description

Recently, builds for this device have started to be made, but there’s a very peculiar issue I’ve found. Any client that is synced to 100 Mbps (and not 1 Gbps, in my case due to incapacity of the cable used) gets their speed seemingly throttled to 20-30 Mbps. My connection is a 100 Mbps connection, and I get full 95 Mbps (Hardware NAT disabled) on the stock firmware, and I also get this speed on LEDE only if I use a 1 Gbps link.

Speedtest on the stock firmware with the 100 Mbps link: http://www.speedtest.net/result/5904234776.png Speedtest on the latest LEDE with the 100 Mbps link: http://www.speedtest.net/result/5915271748.png 1 Gbps links get full speed, as expected.

If I perform a transfer from LAN to LAN, I get full speed on the 100 Mbps link. The resulting speed graph is not a hard-cap, but seemingly some kind of throttle/flow control being applied. I cannot change any settings with ethtool as it throws ‘not supported’ errors.

Only happens WAN > LAN connections.
Nothing of interest in the logs, unless I can somehow get a more verbose log of the connection status.

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.

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

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

openvpn config:

dev tun-monitoring
remote somehost 1194

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

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

persist-key
persist-tun


14.05.2017784ToolchainBug ReportVery LowLowar71xx: imagebuilder fails when BIN_DIR or EXTRA_IMAGE_...lede-17.01Waiting on reporter Task Description

Supply the following if possible:

- Device problem occurs on

HORNETUBx2

HORNETUB

- Software versions of LEDE release, packages, etc.

lede-imagebuilder-17.01.1-ar71xx-generic.Linux-x86_64

- Steps to reproduce

make image PROFILE=HORNETUBx2 BIN_DIR=/tmp/bld/

... dies with :

“Warning: /home/kjh/toolroot.d/lede-imagebuilder-17.01.1-ar71xx-generic.Linux-x86_64/bin/targets/ar71xx/generic/lede-17.01.1-ar71xx-generic-hornet-ub-x2-squashfs-sysupgrade.bin is too big (> 16318464 bytes)”

... but it seems to work OK without BIN_DIR :

make image PROFILE=HORNETUBx2

EXTRA_IMAGE_NAME also seems to cause this problem


24.06.2017866Base systemBug ReportVery LowLowThe DownloadMethod/hg in include/download.mk seems to b...AllWaiting on reporter Task Description

This is a build issue for packages which are using the Mercurial (hg) source code control system. The DownloadMethod/hg tries to re-stamp the files, but the method to do so seems insufficient.

My current fix is this one (without any claim of correctness or completeness), it allows me to make the builds as before the timestamping change was implemented.

— a/include/download.mk
+++ b/include/download.mk
@@ -198,7 +198,7 @@ define DownloadMethod/hg

              rm -rf $(SUBDIR) && \
              [ \! -d $(SUBDIR) ] && \
              hg clone -r $(VERSION) $(URL) $(SUBDIR) && \

- export TAR_TIMESTAMP=`cd $(SUBDIR) && hg log –template ‘@{date}’ -l 1` && \
+ export TAR_TIMESTAMP=`cd $(SUBDIR) && hg log –template ‘@{date}’ -l 1 | cut -d’.’ -f1` && \

This is with Mercurial 3.7.3 (default Mercurial in Ubuntu 16.04.2)


17.07.2017911OtherBug ReportVery LowLowProblem with login into private git reposAllWaiting on reporter Task Description

I am not able to use packages from my private git repos which needs login. The system during the build process don’t ask me for login as before.

Here is the verbose log output:

make[3]: Leaving directory `/home/flowtester/caes/platform/package/base-files'
make[3]: Entering directory `/home/flowtester/caes/platform/package-bumblebee/packages/libdevereader'
mkdir -p /home/flowtester/caes/platform/dl
SHELL= flock /home/flowtester/caes/platform/tmp/.libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860.tar.gz.flock -c '          echo "Checking out files from the git repository..."; mkdir -p /home/flowtester/caes/platform/tmp/dl && cd /home/flowtester/caes/platform/tmp/dl && rm -rf libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 && [ \! -d libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 ] && git clone  https://redmine.develict.com/git/devereader libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 && (cd libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 && git checkout daa94e0fad44a000892570665e6c792fd9cad860 && git submodule update --init --recursive) && echo "Packing checkout..." && export TAR_TIMESTAMP=`cd libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 && git log -1 --format='\''@%ct'\''` && rm -rf libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860/.git &&  tar --numeric-owner --owner=0 --group=0 --sort=name ${TAR_TIMESTAMP:+--mtime="$TAR_TIMESTAMP"} -c libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 |     gzip -nc > /home/flowtester/caes/platform/tmp/dl/libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860.tar.gz && mv /home/flowtester/caes/platform/tmp/dl/libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860.tar.gz /home/flowtester/caes/platform/dl/ && rm -rf libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860;     '
Checking out files from the git repository...
Cloning into 'libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860'...
fatal: Authentication failed for 'https://redmine.develict.com/git/devereader/'
make[3]: *** [/home/flowtester/caes/platform/dl/libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860.tar.gz] Error 128
make[3]: Leaving directory `/home/flowtester/caes/platform/package-bumblebee/packages/libdevereader'
make[2]: *** [package/feeds/bumblebee/libdevereader/compile] Error 2
make[2]: Leaving directory `/home/flowtester/caes/platform'
make[1]: *** [/home/flowtester/caes/platform/staging_dir/target-mipsel_24kc_musl/stamp/.package_compile] Error 2
make[1]: Leaving directory `/home/flowtester/caes/platform'
make: *** [world] Error 2

If I try it manually from cli everythings works but not during the prepare process ....


25.07.2017932KernelBug ReportVery LowLowTP-Link WR841N: mixed VLANs on the same portTrunkWaiting on reporter Task Description

Hi,
i have several TP-Link WR841N v9/v10/v11 running LEDE trunk. Configuring tagged and untagged VLANs on the same port fails.

cat /etc/config/network
config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 1 2 3 4'
        option vid '1'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '0t 1t 2t 3t 4t'
        option vid '2'

swconfig dev switch0 show
    Global attributes:
            enable_vlan: 1
    Port 0:
            pvid: 1
            link: port:0 link:up speed:1000baseT full-duplex txflow rxflow
    Port 1:
            pvid: 1
            link: port:1 link:down
    Port 2:
            pvid: 1
            link: port:2 link:down
    Port 3:
            pvid: 1
            link: port:3 link:down
    Port 4:
            pvid: 1
            link: port:4 link:up speed:100baseT full-duplex auto
    VLAN 1:
            vid: 1
            ports: 0t 1t 2t 3t 4t
    VLAN 2:
            vid: 2
            ports: 0t 1t 2t 3t 4t
17.06.20181591Base systemBug ReportVery LowLowprocd: May hangs during reboot because of netdevice ref...lede-17.01Waiting on reporter Task Description

- Device problem occurs on: Basically all I’ve tested (ar71xx, ipq806x, ipq40xx, ...)
- Software versions of OpenWrt/LEDE: LEDE 17.01x
- Steps to reproduce: Install the attached package, boot the system, try to reboot it

It was observed that OpenWrt sometimes prints

 unregister_netdevice: waiting for br-lan to become free. Usage count = 1

and then hangs indefinitely when trying to reboot. Doing a hard reset seems to the the only way to resolve this problem.

I didn’t have such problems with a systemd based Debian Stretch system and the same trigger kernel module

04.07.20181632Base systemBug ReportVery LowLowZBT APE522ii Wlanaccess over radio0 breaks deviceAllWaiting on reporter Task Description

Version LEDE 17.01.3 stable

Device boots successfully
Default config for both radios: Client
Changing both radios to AP and rebooting
Connecting via radio1 (2.4GHz) renders device unaccessible
Disabling radio1 and connecting via radio0 no problem

Versions LEDE 17.01.4 and Openwrt 18.06.0

Device not accessible via Ethernet nor Wlan


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

PPPoE is broken on WRT1900ACS

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

pppd debug log:

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

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

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

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.

22.06.201626FlysprayFeature RequestVery LowLowComment formatting syntax should be documentedTrunkResearching Task Description

Currently the formatting options are not documented anywhere, and I failed to find any documentation with google. There are a few buttons to use, but they seem to be rather limited (e.g. nothing for quotations).

17.04.2017713Base systemBug ReportVery LowLownetifd: substantially more IFUP events are being create...TrunkResearching Task Description

I have noticed that some services reloaded with a procd “interface.*” raw trigger are reloading on a much more frequent cadence (few minutes or so). LEDE 17.01 does not do this. LEDE Trunk does. I can not find an obvious cause in procd. Though procd should not stop-start for reload without a command line change or explicit file under watch. Perhaps netifd commit a03216660797173fbe67866f75564e3fec9c1e8d is generating unusual numbers of IFUP.

procd_add_raw_trigger “interface.*” 2000 /etc/init.d/[script] reload

29.09.20171024PackagesFeature RequestVery LowLowThere is no "LEDE interface" for the Linux interface cr...AllResearching Task Description

Let’s say I want to enable dropbear only in the tun0 interface created by OpenVPN. The dropbear configuration has an “Interface” field where I can make it listen, for example, only on the “wan” or “lan” interfaces. But the tun0 interface has not been created by anything in /etc/config/network and LEDE doesn’t really know about it, so I can’t specify it the dropbear configuration.

Even adding the tun0 interface to a “vpn” network in /etc/config/network using “proto none” fails to do the trick.

24.07.2017927Base systemBug ReportVery LowCriticalSQUASHFS error: xz decompression failedlede-17.01Assigned Task Description

Ubiquiti AirGateway and Bullet M2
LEDE 17.01.2
Lighttpd
PHP7

Runs very well on boot up. Then after some interval ranging from minutes to days, the following typical error occurs, repeated numerous times with differing blocks:
Mon Jul 24 07:09:39 2017 kern.err kernel: [43650.730023] SQUASHFS error: xz decompression failed, data probably corrupt
Mon Jul 24 07:09:39 2017 kern.err kernel: [43650.735459] SQUASHFS error: squashfs_read_data failed to read block 0x1e5d9a

Following this the unit becomes unresponsive, very slow or reboots its self.
Tried on two different devices and get the same result.

Images produced with Imagebuilder with ipv6, usb, ppp, luci removed to give space on flash.

The exact same config on OpenWrt CC (but with php5) gives no problems.

root@BlueWave:~# free

           total       used       free     shared    buffers     cached

Mem: 28176 19956 8220 132 1460 4296
-/+ buffers/cache: 14200 13976
Swap: 0 0 0

root@BlueWave:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 4.8M 4.8M 0 100% /rom
tmpfs 13.8M 132.0K 13.6M 1% /tmp
/dev/mtdblock5 1.4M 508.0K 964.0K 35% /overlay
overlayfs:/overlay 1.4M 508.0K 964.0K 35% /
tmpfs 512.0K 0 512.0K 0% /dev


19.02.2017534Base systemBug ReportVery LowHighUSB xHCI deadlock on bootlede-17.01Assigned Task Description

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


20.08.2016105Base systemBug ReportMediumMediumlantiq: high latency on adsl lines using pppo[ae]TrunkAssigned Task Description

based on the thread
[LEDE-DEV] [OpenWrt-Devel] latency on PPPoA ADSL Annex A on using Lantiq

http://lists.infradead.org/pipermail/lede-dev/2016-August/002138.html

When using ssh onto the box via adsl, there is a high latency.
The last 3.18 version of lede works. Known good:

  • 161179f40bd7899516518f3844fea28c6dd86efc r47130

Known broken versions:

  • 2795592d913ba8ba57ba537d40714407ea463426 r47131
  • 2a0e1b7f8d59f795abb29d20007822f0da232c43 r47958

mkresin also has a patch for lantiq+4.0, which also has a high latency.
blogic mentioned linux commit 7424ce65065852bdf7a040bf2490da4a8fc4b464 [atm] switch vcc_sendmsg() to copy_from_iter() could be the issue.

Also an interesting side-effect. setup a uhttpd on the device and serve a file to the internet is very slow (using 4mb file random data). it only uploads 5kb/s

12.02.2017503KernelBuild FailureVery LowMediumBuild fails with CONFIG_KERNEL_GIT_CLONE_URI beig setAllAssigned Task Description

When specifying

CONFIG_KERNEL_GIT_CLONE_URI

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

toolchain/kernel-headers

is about to be built.

The build error looks like:

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

The issue apparently is located in

include/kernel-defaults.mk

, line 53ff::

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

For the package

kernel-headers

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

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

22.06.2017863KernelBug ReportMediumMediumath9k failure with AP+11s VIFs ("unsupported hw bitrate...lede-17.01Assigned Task Description

A Gluon user reported the following issue, observed on a TL-WR841N v9 (QCA953x). LEDE version is 17.01.2.

Gluon uses AP+11s VIFs, with multicast_rate set to 12000.

The WLAN became unusable (no connection possible, WLAN LED permantently on) after a few hours of operation. Both VIFs were affected. The system recovered on its own after an hour in this state. Unfortunately, I have no information if beacons were still running in the broken state.

After the recovery, the large number of messages like the following were found in the kernel log:

[40085.953696] ath: phy0: unsupported hw bitrate detected 0x73 using 1 Mbit
[40200.844082] ath: phy0: unsupported hw bitrate detected 0x48 using 1 Mbit
[40281.298039] ------------[ cut here ]------------
[40281.303081] WARNING: CPU: 0 PID: 0 at compat-wireless-2017-01-31/net/mac80211/rx.c:4214 ieee80211_rx_napi+0x130/0x8b0 [mac80211]()
[40281.315230] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 100 (0x64)
[40281.325023] Modules linked in: iptable_nat ath9k nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE ebtable_nat ebtable_filter ebtable_broute ath9k_common xt_time xt_tcpudp xt_state xt_quota xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_LOG xt_CT nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack mac80211 iptable_mangle iptable_filter ip_tables ebtables ebt_vlan ebt_stp ebt_snat ebt_redirect ebt_pkttype ebt_mark_m ebt_mark ebt_limit ebt_ip6 ebt_ip ebt_dnat ebt_arpreply ebt_arp ebt_among ebt_802_3 br_netfilter ath9k_hw ath em_nbyte em_cmp sch_pie em_meta sch_gred sch_teql act_ipt sch_prio em_text sch_codel sch_red sch_fq sch_sfq sch_dsmark act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_htb sch_hfsc batman_adv libcrc32c cfg80211 compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables dummy veth tun act_police cls_basic sch_tbf sch_ingress gpio_button_hotplug crc16 crc32c_generic crypto_hash
[40281.433128] CPU: 0 PID: 0 Comm: swapper Tainted: G        W       4.4.71 #0
[40281.440330] Stack : 803e32a4 00000000 00000001 80440000 8042d1dc 8042ce63 803c48ac 00000000
[40281.440330]    804a378c 00000004 00000000 8180e918 00000000 800a7664 803c9fa8 80430000
[40281.440330]    00000003 00000004 803c83b4 81809d5c 00000000 800a55e0 00000002 00000000
[40281.440330]    8042bf70 801f5300 00000000 00000000 00000000 00000000 00000000 00000000
[40281.440330]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[40281.440330]    ...
[40281.477351] Call Trace:
[40281.479951] [<800a7664>] vprintk_default+0x24/0x30
[40281.484917] [<800a55e0>] printk+0x2c/0x38
[40281.489077] [<801f5300>] serial8250_get_mctrl+0x30/0x54
[40281.494512] [<80081c60>] warn_slowpath_common+0xa0/0xd0
[40281.499949] [<801a772c>] dump_stack+0x14/0x28
[40281.504473] [<80071ea8>] show_stack+0x50/0x84
[40281.509003] [<80081c60>] warn_slowpath_common+0xa0/0xd0
[40281.514543] [<80e25cf0>] ieee80211_rx_napi+0x130/0x8b0 [mac80211]
[40281.520918] [<80081cbc>] warn_slowpath_fmt+0x2c/0x38
[40281.526158] [<80e25cf0>] ieee80211_rx_napi+0x130/0x8b0 [mac80211]
[40281.532495] [<802623ec>] __build_skb+0x48/0xc8
[40281.537148] [<802625d0>] __netdev_alloc_skb+0xd0/0x148
[40281.542477] [<80060bf4>] handle_int+0x134/0x140
[40281.547181] [<80de8388>] ath9k_cmn_rx_skb_postprocess+0x50/0x168 [ath9k_common]
[40281.554852] [<80e88374>] ath_rx_tasklet+0xee8/0xf4c [ath9k]
[40281.560635] [<8006503c>] __bzero+0xa0/0x164
[40281.565012] [<80e88340>] ath_rx_tasklet+0xeb4/0xf4c [ath9k]
[40281.570828] [<80e851b8>] ath9k_tasklet+0x200/0x28c [ath9k]
[40281.576512] [<80084820>] tasklet_action+0x80/0xc8
[40281.581390] [<800841dc>] __do_softirq+0x250/0x298
[40281.586284] [<800a82bc>] generic_handle_irq+0x24/0x3c
[40281.591540] [<8006a9e0>] plat_irq_dispatch+0xd4/0x10c
[40281.596760] [<80060bf4>] handle_int+0x134/0x140
[40281.601447]
[40281.602992] ---[ end trace f41ea26ed5101c02 ]---

Both the numbers in the “unsupported hw bitrate detected” messages and the status→rate_idx values in the WARNINGs are seemingly random.

04.09.2016153KernelBug ReportVery LowLowKERNEL_DYNAMIC_FTRACE=y on mips => panic TrunkAssigned Task Description

Github issue #129 reported by: https://github.com/stsydow

If KERNEL_DYNAMIC_FTRACE is enabled on a MIPS system it will panic in late boot. (tested on ar71xx and malta)
The error message is not very helpful, maybe some one has an idea how to track it down:

[    5.579744] procd: - init -
Please press Enter to activate this console.
[    5.854903] CPU 0 Unable to handle kernel paging request at virtual address 00c03849, epc == 8026a400, ra == 8026a3e4
[    5.855392] Oops[#1]:
[    5.855602] CPU: 0 PID: 1611 Comm: kmodloader Not tainted 4.4.13 #20
[    5.855862] task: 8d86a0a0 ti: 8fa22000 task.ti: 8fa22000
[    5.856060] $ 0   : 00000000 8026a3e4 80130620 00000000
[    5.856380] $ 4   : 8dc48ab0 00000001 0000000e 81b97540
[    5.856607] $ 8   : 0024f000 00003edc 00000000 00000001
[    5.856795] $12   : 8d8410c0 00000025 00000000 6261745f
[    5.856984] $16   : 8dc48a80 81980000 00c03821 801305f4
[    5.857174] $20   : 8dc48ad9 80130620 0000001d 024000c0
[    5.857362] $24   : 00000000 8015655c                  
[    5.857569] $28   : 8fa22000 8fa23bd0 80194d48 8026a3e4
[    5.857766] Hi    : 00000018
[    5.857863] Lo    : 00000007
[    5.858008] epc   : 8026a400 proc_register+0x74/0x130
[    5.858167] ra    : 8026a3e4 proc_register+0x58/0x130
[    5.858317] Status: 1000b703 KERNEL EXL IE 
[    5.858529] Cause : 00800008 (ExcCode 02)
[    5.858655] BadVA : 00c03849
[    5.858764] PrId  : 00019300 (MIPS 24Kc)
[    5.858895] Modules linked in: ip6_tables(+) x_tables mii
[    5.859219] Process kmodloader (pid: 1611, threadinfo=8fa22000, task=8d86a0a0, tls=77528e48)
[    5.859477] Stack : 8da50000 8026a1a4 8f898000 81b94a40 81945a40 8014d8c4 00000001 8dc48a80
      8da4e540 00000000 8f9d6370 8da50000 8da50000 8026a724 00000000 80650000
      8da4e400 00000000 8f9d6370 80650000 8da4e400 8da4d134 00000000 8d86a0e8
      801305f4 00000000 00000000 5ce6d83d 81b94a40 61745f78 73656c62 6d616e5f
      8d007365 0000af3b 81b94a40 81b94a40 8dad46b0 00000000 8fa23d30 80650000
      ...
[    5.861631] Call Trace:
[    5.861728] [<8026a400>] proc_register+0x74/0x130
[    5.861954] [<8026a724>] proc_create_data+0xac/0xd8
[    5.862188] [<8da4d134>] xt_proto_init+0xa4/0x1d0 [x_tables]
[    5.862414] [<8042e640>] ops_init.constprop.9+0x10c/0x150
[    5.862593] [<8042e71c>] register_pernet_operations.isra.4+0x98/0xec
[    5.862796] [<8042e7a4>] register_pernet_subsys+0x34/0x58
[    5.862986] [<8f9d7030>] init_module+0x28/0xcc [ip6_tables]
[    5.863174] [<801006b4>] do_one_initcall+0x1f8/0x224
[    5.863341] [<801c5c8c>] do_init_module+0x84/0x1f8
[    5.863504] [<80197ca0>] load_module+0x1888/0x1d58
[    5.863680] [<80198290>] SyS_init_module+0x120/0x164
[    5.863846] [<80113908>] syscall_common+0x30/0x54
[    5.864046] 
[    5.864130] 
Code: 12400014  26040030  92060058 <92420028> 00c2182b  14600008  00000000  0046102b  14400009 
[    5.864794] ---[ end trace 6cd948b6ebb870af ]---

To test, try this config: config.zip

(default config for malta-mips + KERNEL_DYNAMIC_FTRACE)
and run

qemu-system-mipsel -kernel bin/targets/malta/le/lede-malta-le-vmlinux-initramfs.elf -nographic -m 256

Full boot log: crash-dyn-trace.log.txt

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

Hello,

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

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

Configuration:

/etc/config/system:

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

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

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

18.06.2017853Base systemBug ReportVery LowLowChange dnsmasq domain and local options to listsTrunkAssigned Task Description

On LEDE 17.01 ‘domain’ and ‘local’ options in dnsmasq configuration doesn’t correctly support lists values as per dnsmasq capabilities.

Steps to reproduce

#/etc/config/dhcp
[...]
config dnsmasq
        list domain 'example1.com,192.168.0.0/24'
        list domain 'example2.com,192.168.1.0/24'
        list local '/example1.com/'
        list local '/example2.com/'
[...]

$ uci commit dhcp
$ /etc/init.d/dnsmasq restart

Actual results

#/var/etc/dnsmasq.conf.cfg02411c
[...]
domain=example1.com,192.168.0.0/24 example2.com,192.168.1.0/24
local=/example1.com/ /example2.com/
[...]

Expected results

#/var/etc/dnsmasq.conf.cfg02411c
[...]
domain=example1.com,192.168.0.0/24
domain=example2.com,192.168.1.0/24
local=/example1.com/
local=/example2.com/
[...]

Workaround

Replace append_parm with config_list_foreach here resolve the issue.
I’m attaching a patch for the 17.01 dnsmasq init script but it will break old uci configuration that use ‘option’ instead of ‘list’.
Do you have any suggestion on how to migrate old configuration and set those parameters as lists in uci web interface?

25.11.20171190Base systemBug ReportVery LowLowNETGEAR WNDR3800 USB LED trigger not work properly!TrunkAssigned Task Description

When I plug USB device in USB port, USB is working。I can copy data to usb device. The USB LED show green。But when the data is copying to usb device, the usb led do not blink, just is always green. I select usb trigger and select usbport hub1 and port1. It does not blink too. It means trigger dont work.

model: NETGEAR WNDR3800
Firmware Version LEDE Reboot SNAPSHOT r5420-332438b / LuCI Master (git-17.328.04231-802d5b6)
Kernel Version 4.9.63

By the way, my device work properly in 15.05.1 and 14.07. When I flash LEGE, it have been found this problem.

02.01.20181252Base systemBug ReportVery LowLowNo IP Assigned to Interface with QMI on Quectel EC-25ATrunkAssigned Task Description

I’m attempting to use QMI on a GL.Inet MiFi equipped with a Quectel EC-25A cellular modem.

When I configure the interface using qmi I am able to connect to the cellular network at the radio layer, however my wwan0 interface is not assigned an IP address. Here’s my configuration from /etc/config/network:

  config interface 'modem'
          option proto 'qmi'
          option ifname 'wwan0'
          option device '/dev/cdc-wdm0'
          option country 'country11'
          option apn 'inet.bell.ca'

And some commands showing the device behaviour. You’ll note that raw_ip needs to be set to Y. I’ve integrated this [patch](https://github.com/bmork/LEDE/commit/10aed12fa587e818e4dc5d0db54545623fbe9b5f) to have qmi.sh set the raw_ip mode when required.

  root@OpenWrt:~# cat /sys/class/net/wwan0/qmi/raw_ip
  Y
  root@OpenWrt:~# ifup modem
  root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-data-status
  "connected"
  root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-current-settings
  {
      "pdp-type": "ipv4",
      "ip-family": "ipv4",
      "mtu": 1500,
      "ipv4": {
          "ip": "100.105.180.51",
          "dns1": "206.47.201.246",
          "dns2": "207.231.231.254",
          "gateway": "100.105.180.52",
          "subnet": "255.255.255.248"
      },
      "ipv6": {
          
      },
      "domain-names": {
          
      }
  }
  root@OpenWrt:~# ifconfig wwan0
  wwan0     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
            inet6 addr: fe80::d789:480e:bfc8:2dac/64 Scope:Link
            UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
            RX packets:28 errors:0 dropped:0 overruns:0 frame:0
            TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000 
            RX bytes:5129 (5.0 KiB)  TX bytes:768 (768.0 B)

If I manually use the uqmi command to connect to the cellular network I can then drive the wwan0 interface using dhcp successfully. Here’s my /etc/config/network.

  config interface 'modem'
          option proto 'dhcp'
          option ifname 'wwan0'

And the resulting successful network connection:

  root@OpenWrt:~# ifup modem
  root@OpenWrt:~# ifconfig wwan0
  wwan0     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
            inet addr:100.105.180.51  P-t-P:100.105.180.51  Mask:255.255.255.248
            inet6 addr: fe80::d789:480e:bfc8:2dac/64 Scope:Link
            UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
            RX packets:80 errors:0 dropped:0 overruns:0 frame:0
            TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000 
            RX bytes:24102 (23.5 KiB)  TX bytes:16842 (16.4 KiB)
  root@OpenWrt:~# ping -c 1 google.ca
  PING google.ca (172.217.1.163): 56 data bytes
  64 bytes from 172.217.1.163: seq=0 ttl=51 time=29.792 ms
  1. – google.ca ping statistics —

1 packets transmitted, 1 packets received, 0% packet loss

  round-trip min/avg/max = 29.792/29.792/29.792 ms

I believe that for some reason the dhcp client isn’t being run on the wwan0 interface by qmi.sh once it’s online but I’m not able to determine how this is supposed to work. I’m eager to address this issue and submit the resulting patches. Please let me know if you can help.

  root@OpenWrt:~# ping -c 1 8.8.8.8
  PING 8.8.8.8 (8.8.8.8): 56 data bytes
  64 bytes from 8.8.8.8: seq=0 ttl=54 time=31.805 ms
  1. – 8.8.8.8 ping statistics —

1 packets transmitted, 1 packets received, 0% packet loss

  round-trip min/avg/max = 31.805/31.805/31.805 ms
01.06.20181571Base systemBug ReportMediumLownetifd does not honor rules when using network.lan.enab...AllAssigned Task Description

Device: ar71xx TP-LINK TL-WR841N/ND v9
Revision: c8fdd0e9c843dd483f6677dc41f7df17313aa3cd

netifd: does not apply network rules after disabling the interface via uci set network.lan.enabled=0 and reenabling it via uci set network.l .enabled=1

Steps to reproduce:

uci set network.guestable=rule
uci set network.guestable.in=lan
uci set network.guestable.lookup='1001'
uci set network.guestable.priority='100'
uci set network.unreach=rule
uci set network.unreach.in=lan
uci set network.unreach.action='unreachable'
uci set network.unreach.priority='110'
uci set network.lan.enabled=1
ubus call network reload
sleep 5
ip ru sho

uci set network.lan.enabled=0
ubus call network reload
sleep 5
uci set network.lan.enabled=1
ubus call network reload
sleep 5
ip ru sho
echo "The rules are missing now"


09.07.20181645Base systemFeature RequestVery LowLowNAT reflection/loopback fails with multiple zoneslede-17.01Assigned Task Description

I have multiple internal VLANs, and multiple firewall zones (e.g. a guest network, a DMZ LAN) with separate IP ranges and locked-down routing in between. I’ve found that if I forward a port to a web server in my DMZ zone the ‘NAT Loopback’ option has no effect on hosts outside of that zone (e.g. in my LAN or GuestLAN zones).

LEDE:

# curl https://mywebsite.com curl: (7) Failed to connect to mywebsite.com port 443: Connection refused

On DMZ:

$ curl https://mywebsite.com <html>
<head>
<title>
...

The port forward works fine on hosts outside my network.

I’ve looked into adding custom rules to fix this, since a Linux sysadmin with a little bit of iptables experience, but I’m not having much luck figuring out the LEDE firewall.

Using LEDE Reboot (17.01.4, r3560-79f57e422d) on x86 (QOTOM J1900 embedded PC).

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

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

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

Here is a trace of the crash (dmesg):

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

 


05.10.2016205Base systemBug ReportVery LowHighCannot install LEDE on Ubiquiti PicoStation M2TrunkNew Task Description

This is the same as issue 20982 on dev.openwrt.org

Using the nightly build of LEDE and installing on a Ubiquiti PicoStation M2 (Ar7xxx, XM hardware rev, AirOS 5.6.3), got the following error:

sent DATA <block=6657, 412 bytes>
received ERROR <code=2, msg=Firmware check failed>
Error code 2: Firmware check failed
Sent 3407872 bytes in 6.6 seconds

The only work-around I have found works consistently is to:

Flash from recovery (tftp) the AirOS 5.6 image,
Downgrade to AirOS 5.5, then
Flash LEDE (or OpenWRT).

This same error seems to occur on the Bullet M2 (same hardware) and the NanoStation LOCO M2.

The severity is high - it can be worked around, but it prevents installation without significant work-arounds. I view this as a high-priority bug, because the Ubiquiti hardware is popular and the problem has been fixed in AirOS and DD-WRT.

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

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

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

10.03.2017615KernelBug ReportMediumHighWDS AP: kernel panic under high traffic loadTrunkNew Task Description

I built a WDS bridge with two TL-WR841 v8, running LEDE r3670-154b3a6 from the buildbot snapshots.

When sending a high amount of traffic through the bridge (bidirectional iperf from one computer to another through the bridge), the WDS AP crashes repeatedly (roughly every hour, sometimes it takes a bit longer).

This is possibly related to other WDS issues  FS#447  and FS#608.

AP wireless config:

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'LEDE'
	option encryption 'psk-mixed'
	option key 'XXX'
	option wds '1'

STA wireless config:

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'sta'
	option ssid 'LEDE'
	option encryption 'psk2'
	option key 'XXX'
	option wds '1'

The network configuration is unchanged on both devices (except changing the LAN IP).

Some kernel crashes I obtained with /sys/kernel/debug/crashlog after a crash:


[ 2581.160504] Trap instruction in kernel code[#1]:
[ 2581.165297] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.52 #0
[ 2581.171239] task: 8042ef58 ti: 80428000 task.ti: 80428000
[ 2581.176814] $ 0   : 00000000 804a0000 00000000 fffffffe
[ 2581.182253] $ 4   : 00afc0cc 009f844e 0000007f a0e7c980
[ 2581.187691] $ 8   : 009f849c 00000052 0000004a 01000000
[ 2581.193129] $12   : 80000000 8000004e 00000000 00000002
[ 2581.198559] $16   : 81b27000 80df7000 81a15000 81942f00
[ 2581.203989] $20   : 00000000 00000000 8042a4e0 80d18400
[ 2581.209428] $24   : 00000000 8007d2d4
[ 2581.214866] $28   : 80428000 81809a58 8042a4e0 80272104
[ 2581.220305] Hi    : 00000019
[ 2581.223280] Lo    : 00000000
[ 2581.226272] epc   : 80272128 __dev_queue_xmit+0x2d8/0x4c4
[ 2581.231852] ra    : 80272104 __dev_queue_xmit+0x2b4/0x4c4
[ 2581.237428] Status: 1100f403 KERNEL EXL IE
[ 2581.241785] Cause : 00800034 (ExcCode 0d)
[ 2581.245924] PrId  : 0001974c (MIPS 74Kc)
[ 2581.249972] Modules linked in: ath9k ath9k_common pppoe ppp_async ath9k_hw 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_CT slhc
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 crc_ccitt compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter
ip6_tables x_tables gpio_button_hotplug
[ 2581.309535] Process swapper (pid: 0, threadinfo=80428000, task=8042ef58, tls=00000000)
[ 2581.317710] Stack : 80ecf420 8187992c 81809b2c 81879900 81b27068 00000001 80430000 fffffff4
[ 2581.317710]    80ece09c 80ed7000 0000004a 80ed7000 80d18400 80ed7000 00000000 8035b5a4
[ 2581.317710]    00000000 80df7000 00000000 80905e00 80f81000 80430000 80df7000 80271cd0
[ 2581.317710]    80428000 00440002 00000020 0000000e 00000003 80df7000 8042a4e0 00000000
[ 2581.317710]    80d18400 80271718 80430000 803fc6cc 8190af00 80ece090 80430000 80df7000
[ 2581.317710]    ...
[ 2581.354706] Call Trace:
[ 2581.357239] [] __dev_queue_xmit+0x2d8/0x4c4
[ 2581.362495] [] vlan_dev_hard_start_xmit+0x98/0x128
[ 2581.368341] [] dev_hard_start_xmit+0x2a8/0x354
[ 2581.373834] [] __dev_queue_xmit+0x3c0/0x4c4
[ 2581.379068] [] br_dev_queue_push_xmit+0x16c/0x1a0
[ 2581.384828] [] br_forward_finish+0x3c/0xb0
[ 2581.389963] [] __br_forward+0xa8/0x114
[ 2581.394741] [] br_handle_frame_finish+0x4f4/0x550
[ 2581.400500] [] br_handle_frame+0x380/0x418
[ 2581.405662] [] __netif_receive_skb_core+0x42c/0x898
[ 2581.411768] [] ieee80211_attach_ack_skb+0x103c/0x19e8 [mac80211]
[ 2581.418913]
[ 2581.420454]
[ 2581.420454] Code: 02002025  10000014  00008825  00431024  ae020074  1000000f  00008825  8e020000
[ 2581.430831] ---[ end trace 8251bd1741f30e24 ]---
[ 2581.437731] Kernel panic - not syncing: Fatal exception in interrupt

Another one which is a bit different:

[  420.687915] Reserved instruction in kernel code[#1]:
[  420.693066] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.52 #0
[  420.699008] task: 8042ef58 ti: 80428000 task.ti: 80428000
[  420.704583] $ 0   : 00000000 804a0000 00000002 00000002
[  420.710022] $ 4   : 81809e34 00000003 00000000 a0fb5980
[  420.715460] $ 8   : 0179f4bc 000005f2 000005ea 01000000
[  420.720898] $12   : 80000000 800005ee 00000000 772a02c0
[  420.726328] $16   : 81809e34 00000000 80f82420 8179eed2
[  420.731758] $20   : 80d54b40 00000000 80f82000 81809ddc
[  420.737197] $24   : 00000000 8007d2d4                  
[  420.742635] $28   : 80428000 81809d28 00000000 80da2a4c
[  420.748066] Hi    : 00000008
[  420.751041] Lo    : 00000023
[  420.754198] epc   : 80da2a4c ieee80211_sta_uapsd_trigger+0xff4/0x2d7c [mac80211]
[  420.761875] ra    : 80da2a4c ieee80211_sta_uapsd_trigger+0xff4/0x2d7c [mac80211]
[  420.769508] Status: 1100f403	KERNEL EXL IE 
[  420.773864] Cause : 80800028 (ExcCode 0a)
[  420.778004] PrId  : 0001974c (MIPS 74Kc)
[  420.782050] Modules linked in: ath9k ath9k_common pppoe ppp_async ath9k_hw 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_CT slhc 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 crc_ccitt compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables gpio_button_hotplug
[  420.841606] Process swapper (pid: 0, threadinfo=80428000, task=8042ef58, tls=00000000)
[  420.849779] Stack : 8086da00 8034a074 00000141 81809e14 00000042 81a18c20 00000003 81a18800
[  420.849779] 	  804c0000 00000000 0000002f 00000080 803c9c94 80dd6e74 80de0000 80dd6e40
[  420.849779] 	  80df9780 80440000 80f81420 8034a304 00000032 81b90010 00000001 00000008
[  420.849779] 	  80fc1380 81809e34 80fa9cc0 000008c9 8086f460 00000008 8086f460 00000000
[  420.849779] 	  00000001 80da5abc 815d1746 80df9780 00000000 8034bc5c 00000003 81a18800
[  420.849779] 	  ...
[  420.886779] Call Trace:
[  420.889373] [<80da2a4c>] ieee80211_sta_uapsd_trigger+0xff4/0x2d7c [mac80211]
[  420.896693] 
[  420.898234] 
[  420.898234] Code: 00402825  0c3687a9  02002025 <1000fe1b> 8ee20000  0c36817d  02402025  0441ff8b  24420012 
[  420.908615] ---[ end trace 2fd42b1e71175ff5 ]---
[  420.915438] Kernel panic - not syncing: Fatal exception in interrupt
16.08.201694Base systemBug ReportVery LowMediumnetifd: PPPoE MTU problemTrunkNew Task Description

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

This leeds to log messages like this:


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


and MTUs other than what you really want.

example:


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

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

Regards,
Martin

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

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

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

02.11.2016262Base systemBug ReportVery LowLowipq806x: wlan LEDs not working on TP-Link Archer C2600AllNew Task Description

The LEDs on the Archer C2600 don’t work properly. The WLAN lights don’t work at all (I believe that they are controlled PCIE chips and not GPIO) and the LAN and WAN lights are always on regardless of a cable being connected.

JW


12.12.2016333KernelBug ReportMediumLowath10k_pci: crash after ~10d uptimeTrunkNew Task Description

After ~10 days of uptime, ath10k crashed and I could no longer associate.

Device: D-Link DAP-2695 rev A1
Running: LEDE r2370

Wireless config:

config wifi-device  radio0
        option type     mac80211
        option channel  100
        option country  BE
        option txpower  20
        option hwmode   11a
        option path     'pci0000:00/0000:00:00.0'
        option htmode   VHT80
        option disabled 0

config wifi-iface
        option device 'radio0'
        option ifname 'wlan0'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '1'
        option network 'lan'
        option mode 'ap'
        option ssid 'xxxxxxxx'
        option key 'XXXXXXXX'

config wifi-iface
        option device 'radio0'
        option ifname 'wlan2'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '0'
        option network 'guest'
        option mode 'ap'
        option ssid 'Guests'
        option key 'YYYYYYYY'
        #option disassoc_low_ack '0'

config wifi-device  radio1
        option type     mac80211
        option channel  1
        option country  BE
        option txpower  20
        option hwmode   11g
        option path     'platform/qca955x_wmac'
        option htmode   HT40
        #option noscan   1

config wifi-iface
        option device 'radio1'
        option ifname 'wlan1'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '1'
        option mode 'ap'
        option network 'lan'
        option ssid 'xxxxxxxx'
        option key 'XXXXXXXX'

config wifi-iface
        option device 'radio1'
        option ifname 'wlan3'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '0'
        option network 'guest'
        option mode 'ap'
        option ssid 'Guests'
        option key 'YYYYYYYY'
        #option disassoc_low_ack '0'

Kernel log:

[   54.439387] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[   54.652312] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:00:00.0.bin failed with error -2
[   54.663197] ath10k_pci 0000:00:00.0: Falling back to user helper
[   54.742675] firmware ath10k!pre-cal-pci-0000:00:00.0.bin: firmware_loading_store: map pages failed
[   54.752039] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/cal-pci-0000:00:00.0.bin failed with error -2
[   54.762568] ath10k_pci 0000:00:00.0: Falling back to user helper
[   61.648688] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   61.658088] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   61.671139] ath10k_pci 0000:00:00.0: firmware ver 10.2.4.70.54 api 5 features no-p2p,raw-mode,mfp crc32 9d340dd9
[   61.681571] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[   61.692178] ath10k_pci 0000:00:00.0: Falling back to user helper
[   61.771624] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[   61.786987] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   62.893736] ath10k_pci 0000:00:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
[   63.001904] ath: EEPROM regdomain: 0x0
[   63.001920] ath: EEPROM indicates default country code should be used
[   63.001928] ath: doing EEPROM country->regdmn map search
[   63.001945] ath: country maps to regdmn code: 0x3a
[   63.001955] ath: Country alpha2 being used: US
[   63.001963] ath: Regpair used: 0x3a
[   63.284566] ath: EEPROM regdomain: 0x0
[   63.284583] ath: EEPROM indicates default country code should be used
[   63.284591] ath: doing EEPROM country->regdmn map search
[   63.284608] ath: country maps to regdmn code: 0x3a
[   63.284617] ath: Country alpha2 being used: US
[   63.284625] ath: Regpair used: 0x3a
[   72.829974] ath: EEPROM regdomain: 0x8038
[   72.834045] ath: EEPROM indicates we should expect a country code
[   72.840265] ath: doing EEPROM country->regdmn map search
[   72.845651] ath: country maps to regdmn code: 0x37
[   72.850522] ath: Country alpha2 being used: BE
[   72.855022] ath: Regpair used: 0x37
[   72.858554] ath: regdomain 0x8038 dynamically updated by user
[   72.864452] ath: EEPROM regdomain: 0x8038
[   72.868513] ath: EEPROM indicates we should expect a country code
[   72.874707] ath: doing EEPROM country->regdmn map search
[   72.880092] ath: country maps to regdmn code: 0x37
[   72.884943] ath: Country alpha2 being used: BE
[   72.889458] ath: Regpair used: 0x37
[   72.892996] ath: regdomain 0x8038 dynamically updated by user
[920549.560152] ath10k_pci 0000:00:00.0: failed to delete peer c0:ee:fb:4a:18:b7 for vdev 0: -145
[920549.568951] ath10k_pci 0000:00:00.0: found sta peer c0:ee:fb:4a:18:b7 (ptr 8d43f600 id 95) entry on vdev 0 after it was supposedly removed
[920549.581722] ------------[ cut here ]------------
[920549.586618] WARNING: CPU: 0 PID: 1431 at compat-wireless-2016-10-08/net/mac80211/sta_info.c:964 sta_set_sinfo+0x92c/0x9e0 [mac80211]()
[920549.598968] Modules linked in: ath9k ath9k_common crc_ccitt ath9k_hw act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ath10k_pci ath10k_core ath mac80211 cfg80211 compat gpio_button_hotplug
[920549.620582] CPU: 0 PID: 1431 Comm: hostapd Not tainted 4.4.35 #0
[920549.626772] Stack : 803c2d64 00000000 00000001 80420000 8fe26580 8040acc3 803a4424 00000597
[920549.626772]           8047379c 8ff8d000 00000000 77415e94 00000000 800a7198 803a9a90 80400000
[920549.626772]           00000003 8ff8d000 803a7e9c 8e5f3b2c 00000000 800a5114 80400000 00000000
[920549.626772]           00000001 801f3100 00000000 00000000 00000000 00000000 00000000 00000000
[920549.626772]           00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[920549.626772]           ...
[920549.663219] Call Trace:
[920549.665810] [<80071ae0>] show_stack+0x50/0x84
[920549.670323] [<80081860>] warn_slowpath_common+0xa0/0xd0
[920549.675724] [<80081918>] warn_slowpath_null+0x18/0x24
[920549.680994] [<8f5870a4>] sta_set_sinfo+0x92c/0x9e0 [mac80211]
[920549.686990] [<8f587188>] __sta_info_destroy+0x30/0x48 [mac80211]
[920549.693222] [<8f587238>] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
[920549.700118] [<8f54c144>] cfg80211_check_station_change+0xed8/0x1390 [cfg80211]
[920549.707564] 
[920549.709166] ---[ end trace e15a227055dd36c2 ]---
[920866.693883] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer b0:df:3a:12:79:80: -145
[920866.703088] wlan0: failed to remove key (0, b0:df:3a:12:79:80) from hardware (-145)
[920866.719519] ath10k_pci 0000:00:00.0: cipher 0 is not supported
[920866.725602] ath10k_pci 0000:00:00.0: failed to remove peer wep key 0: -122
[920866.732670] ath10k_pci 0000:00:00.0: failed to clear all peer wep keys for vdev 0: -122
[920866.740901] ath10k_pci 0000:00:00.0: failed to disassociate station: b0:df:3a:12:79:80 vdev 0: -122
[920866.750169] ------------[ cut here ]------------
[920866.755066] WARNING: CPU: 0 PID: 1431 at compat-wireless-2016-10-08/net/mac80211/sta_info.c:956 sta_set_sinfo+0x8d8/0x9e0 [mac80211]()
[920866.767421] Modules linked in: ath9k ath9k_common crc_ccitt ath9k_hw act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ath10k_pci ath10k_core ath mac80211 cfg80211 compat gpio_button_hotplug
[920866.789044] CPU: 0 PID: 1431 Comm: hostapd Tainted: G        W       4.4.35 #0
[920866.796465] Stack : 803c2d64 00000000 00000001 80420000 8fe26580 8040acc3 803a4424 00000597
[920866.796465]           8047379c 8ff8d000 00000000 77415e94 00000000 800a7198 803a9a90 80400000
[920866.796465]           00000003 8ff8d000 803a7e9c 8e5f3b2c 00000000 800a5114 00000000 00000000
[920866.796465]           80409dd0 801f3100 00000000 00000000 00000000 00000000 00000000 00000000
[920866.796465]           00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[920866.796465]           ...
[920866.832912] Call Trace:
[920866.835502] [<80071ae0>] show_stack+0x50/0x84
[920866.840016] [<80081860>] warn_slowpath_common+0xa0/0xd0
[920866.845417] [<80081918>] warn_slowpath_null+0x18/0x24
[920866.850691] [<8f587050>] sta_set_sinfo+0x8d8/0x9e0 [mac80211]
[920866.856685] [<8f587188>] __sta_info_destroy+0x30/0x48 [mac80211]
[920866.862914] [<8f587238>] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
[920866.869817] [<8f54c144>] cfg80211_check_station_change+0xed8/0x1390 [cfg80211]
[920866.877266] 
[920866.878867] ---[ end trace e15a227055dd36c3 ]---
[920869.873901] ath10k_pci 0000:00:00.0: failed to delete peer b0:df:3a:12:79:80 for vdev 0: -11
[920869.882572] ath10k_pci 0000:00:00.0: found sta peer b0:df:3a:12:79:80 (ptr 8f3f3000 id 243) entry on vdev 0 after it was supposedly removed
[920872.893898] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
[920875.893871] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
[920878.913873] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
[920881.913852] ath10k_pci 0000:00:00.0: failed to set protection mode 0 on vdev 0: -11
[920884.913828] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
[920887.923826] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 1: -11
[920890.923830] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 1: -11
[920893.933787] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 1: -11
[920896.933770] ath10k_pci 0000:00:00.0: failed to set protection mode 0 on vdev 1: -11
[920899.933771] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 1: -11

Kernel log after running “wifi” in the crashed state:

[921144.042842] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[921144.051948] wlan0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-11)
[921147.052846] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[921147.061984] wlan0: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-11)
[921150.082845] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[921150.092017] wlan2: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-11)
[921153.092796] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[921153.101928] wlan2: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-11)
[932082.286927] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
[932390.335807] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
[932607.674665] ath10k_pci 0000:00:00.0: failed to down vdev_id 1: -11
[932610.674753] ath10k_pci 0000:00:00.0: failed to stop WMI vdev 1: -11
[932610.682338] ath10k_pci 0000:00:00.0: failed to stop vdev 1: -11
[932613.684666] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[932613.694955] wlan2: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-11)
[932616.694882] ath10k_pci 0000:00:00.0: failed to submit AP/IBSS self-peer removal on vdev 1: -11
[932619.694635] ath10k_pci 0000:00:00.0: failed to delete WMI vdev 1: -11
[932622.694758] ath10k_pci 0000:00:00.0: failed to remove AP self-peer on vdev 1: -145
[932622.704039] ath10k_pci 0000:00:00.0: found vif peer 9e:d6:43:29:cc:18 entry on vdev 1 after it was supposedly removed
[932622.715667] ath10k_pci 0000:00:00.0: removing stale peer 9e:d6:43:29:cc:18 from vdev_id 1
[932622.724455] br-guest: port 3(wlan2) entered disabled state
[932622.796620] device wlan2 left promiscuous mode
[932622.802446] br-guest: port 3(wlan2) entered disabled state
[932622.856835] br-guest: port 2(wlan3) entered disabled state
[932622.885493] device wlan3 left promiscuous mode
[932622.891306] br-guest: port 2(wlan3) entered disabled state
[932622.935955] device wlan0 left promiscuous mode
[932622.940833] br-lan: port 2(wlan0) entered disabled state
[932622.976382] device wlan1 left promiscuous mode
[932622.981149] br-lan: port 3(wlan1) entered disabled state
[932626.004584] ath10k_pci 0000:00:00.0: failed to down vdev_id 0: -11
[932629.004572] ath10k_pci 0000:00:00.0: failed to stop WMI vdev 0: -11
[932629.011031] ath10k_pci 0000:00:00.0: failed to stop vdev 0: -11
[932634.014537] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[932637.034556] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[932637.043707] wlan0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-11)
[932640.044532] ath10k_pci 0000:00:00.0: failed to submit AP/IBSS self-peer removal on vdev 0: -11
[932643.044507] ath10k_pci 0000:00:00.0: failed to delete WMI vdev 0: -11
[932646.044501] ath10k_pci 0000:00:00.0: failed to remove AP self-peer on vdev 0: -145
[932646.052277] ath10k_pci 0000:00:00.0: found vif peer 9c:d6:43:29:cc:18 entry on vdev 0 after it was supposedly removed
[932646.063205] ath10k_pci 0000:00:00.0: removing stale peer 9c:d6:43:29:cc:18 from vdev_id 0
[932652.064468] ath10k_pci 0000:00:00.0: could not suspend target (-11)
[932653.410146] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[932654.710106] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[932654.716877] device wlan1 entered promiscuous mode
[932654.755523] device wlan0 entered promiscuous mode
[932655.397455] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[932655.404141] br-lan: port 3(wlan0) entered forwarding state
[932655.409904] br-lan: port 3(wlan0) entered forwarding state
[932655.426138] device wlan2 entered promiscuous mode
[932655.445231] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
[932655.451454] br-guest: port 2(wlan2) entered forwarding state
[932655.457370] br-guest: port 2(wlan2) entered forwarding state
[932655.714483] br-guest: port 2(wlan2) entered disabled state
[932655.842761] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[932655.849460] br-guest: port 2(wlan2) entered forwarding state
[932655.855380] br-guest: port 2(wlan2) entered forwarding state
[932656.428869] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[932656.435563] br-lan: port 2(wlan1) entered forwarding state
[932656.441274] br-lan: port 2(wlan1) entered forwarding state
[932656.466101] device wlan3 entered promiscuous mode
[932656.477745] IPv6: ADDRCONF(NETDEV_UP): wlan3: link is not ready
[932656.483865] br-guest: port 3(wlan3) entered forwarding state
[932656.489791] br-guest: port 3(wlan3) entered forwarding state
[932656.714486] br-guest: port 3(wlan3) entered disabled state
[932656.869320] IPv6: ADDRCONF(NETDEV_CHANGE): wlan3: link becomes ready
[932656.876022] br-guest: port 3(wlan3) entered forwarding state
[932656.881921] br-guest: port 3(wlan3) entered forwarding state
[932657.404425] br-lan: port 3(wlan0) entered forwarding state
[932657.854498] br-guest: port 2(wlan2) entered forwarding state
[932658.434436] br-lan: port 2(wlan1) entered forwarding state
[932658.874432] br-guest: port 3(wlan3) entered forwarding state
[932680.425787] br-guest: port 3(wlan3) entered disabled state
[932680.442596] device wlan3 left promiscuous mode
[932680.447279] br-guest: port 3(wlan3) entered disabled state
[932680.467863] br-guest: port 2(wlan2) entered disabled state
[932680.485729] device wlan2 left promiscuous mode
[932680.490436] br-guest: port 2(wlan2) entered disabled state
[932680.505002] device wlan1 left promiscuous mode
[932680.509700] br-lan: port 2(wlan1) entered disabled state
[932680.523775] device wlan0 left promiscuous mode
[932680.528530] br-lan: port 3(wlan0) entered disabled state
[932683.130864] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[932683.169412] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[932683.183967] device wlan0 entered promiscuous mode
[932683.197266] device wlan1 entered promiscuous mode
[932683.813544] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[932683.820249] br-lan: port 2(wlan0) entered forwarding state
[932683.826004] br-lan: port 2(wlan0) entered forwarding state
[932683.841229] device wlan2 entered promiscuous mode
[932683.857367] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
[932683.863484] br-guest: port 2(wlan2) entered forwarding state
[932683.869386] br-guest: port 2(wlan2) entered forwarding state
[932684.174365] br-guest: port 2(wlan2) entered disabled state
[932684.265577] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[932684.272265] br-guest: port 2(wlan2) entered forwarding state
[932684.278193] br-guest: port 2(wlan2) entered forwarding state
[932684.868399] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[932684.875079] br-lan: port 3(wlan1) entered forwarding state
[932684.880820] br-lan: port 3(wlan1) entered forwarding state
[932684.905988] device wlan3 entered promiscuous mode
[932684.912111] IPv6: ADDRCONF(NETDEV_UP): wlan3: link is not ready
[932684.918275] br-guest: port 3(wlan3) entered forwarding state
[932684.924142] br-guest: port 3(wlan3) entered forwarding state
[932685.174351] br-guest: port 3(wlan3) entered disabled state
[932685.305978] IPv6: ADDRCONF(NETDEV_CHANGE): wlan3: link becomes ready
[932685.312646] br-guest: port 3(wlan3) entered forwarding state
[932685.318582] br-guest: port 3(wlan3) entered forwarding state
[932685.824311] br-lan: port 2(wlan0) entered forwarding state
[932686.274310] br-guest: port 2(wlan2) entered forwarding state
[932686.874321] br-lan: port 3(wlan1) entered forwarding state
[932687.314318] br-guest: port 3(wlan3) entered forwarding state

After running wifi, I am able to connect again.

MAC addresses found in logs:
9c:d6:43:29:cc:18: DAP-2695, wlan0
9e:d6:43:29:cc:18: DAP-2695, wlan2

c0:ee:fb:4a:18:b7: OnePlus 2, Android 6.0.1
b0:df:3a:12:79:80: Samsung SM-T520, Android 5.1.1

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

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

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

Default htmode

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

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

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

Default channel

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

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

I have been using LEDE 17.01 on a WR841N v8, with a simple 2.4 GHz AP (’mixed-psk’ security).

Recently I have seen this kernel warning in the logs: it might be nothing or it might be something important, who knows.

Feb 23 17:23:59 AP4 kernel: [62871.843902] ------------[ cut here ]------------
Feb 23 17:23:59 AP4 kernel: [62871.848752] WARNING: CPU: 0 PID: 0 at compat-wireless-2016-10-08/net/mac80211/rx.c:4180 0x80e2529c [mac80211@80e00000+0x5f500]()
Feb 23 17:23:59 AP4 kernel: [62871.860717] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 113 (0x71)
Feb 23 17:23:59 AP4 kernel: [62871.870518] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 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_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack ipta
Feb 23 17:23:59 AP4 kernel: [62871.930136] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.50 #0
Feb 23 17:23:59 AP4 kernel: [62871.936073] Stack : 80386534 00000000 00000001 803e0000 00000000 00000000 00000000 00000000
Feb 23 17:23:59 AP4 kernel: [62871.936073] #011  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Feb 23 17:23:59 AP4 kernel: [62871.936073] #011  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Feb 23 17:23:59 AP4 kernel: [62871.936073] #011  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Feb 23 17:23:59 AP4 kernel: [62871.936073] #011  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Feb 23 17:23:59 AP4 kernel: [62871.936073] #011  ...
Feb 23 17:23:59 AP4 kernel: [62871.973122] Call Trace:[<80071a50>] 0x80071a50
Feb 23 17:23:59 AP4 kernel: [62871.977762] [<80071a50>] 0x80071a50
Feb 23 17:23:59 AP4 kernel: [62871.981372] [<800817e8>] 0x800817e8
Feb 23 17:23:59 AP4 kernel: [62871.984987] [<80e2529c>] 0x80e2529c [mac80211@80e00000+0x5f500]
Feb 23 17:23:59 AP4 kernel: [62871.991120] [<80081844>] 0x80081844
Feb 23 17:23:59 AP4 kernel: [62871.994729] [<802a385c>] 0x802a385c
Feb 23 17:23:59 AP4 kernel: [62871.998352] [<80e2529c>] 0x80e2529c [mac80211@80e00000+0x5f500]
Feb 23 17:23:59 AP4 kernel: [62872.004468] [<8025fea8>] 0x8025fea8
Feb 23 17:23:59 AP4 kernel: [62872.008086] [<8026008c>] 0x8026008c
Feb 23 17:23:59 AP4 kernel: [62872.011694] [<80d08388>] 0x80d08388 [ath9k_common@80d08000+0x47e0]
Feb 23 17:23:59 AP4 kernel: [62872.018112] [<81ba77dc>] 0x81ba77dc [ath9k@81ba0000+0x16650]
Feb 23 17:23:59 AP4 kernel: [62872.023975] [<81ba77bc>] 0x81ba77bc [ath9k@81ba0000+0x16650]
Feb 23 17:23:59 AP4 kernel: [62872.029854] [<81ba4a44>] 0x81ba4a44 [ath9k@81ba0000+0x16650]
Feb 23 17:23:59 AP4 kernel: [62872.035704] [<800843a8>] 0x800843a8
Feb 23 17:23:59 AP4 kernel: [62872.039327] [<80083d64>] 0x80083d64
Feb 23 17:23:59 AP4 kernel: [62872.042937] [<800a7e08>] 0x800a7e08
Feb 23 17:23:59 AP4 kernel: [62872.046547] [<8006a950>] 0x8006a950
Feb 23 17:23:59 AP4 kernel: [62872.050169] [<80060bf4>] 0x80060bf4
Feb 23 17:23:59 AP4 kernel: [62872.053769] 
Feb 23 17:23:59 AP4 kernel: [62872.055314] ---[ end trace 90699e3e72694b86 ]---
Feb 23 17:24:02 AP4 kernel: [62875.131392] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00024300


03.03.2017587Base systemBug ReportMediumLowno wwan with qmi based modem quectel ec20AllNew Task Description

uqmi hangs on certain commands resulting in a half-connected wwan connection.

device: apu1d
modem: quectel ec20 / qualcom based
affected versions: lede 17.01, trunk

good uqmi version: 2016-08-23-eb1dec7d0dc283a7f61aa574a443a0ab61f8793f
bad uqmi version: 2016-12-19-8ceeab69-1

 1553 root      3288 S    {qmi.sh} /bin/sh ./qmi.sh qmi setup lte {"ifname":"wwan0","proto":"qmi","apn":"internet","
 1620 root      9024 S    uqmi -s -d /dev/cdc-wdm0 --wda-set-data-format 802.3
 1817 root      3072 S    grep qmi
config interface 'lte'
	option ifname 'wwan0'
	option proto 'qmi'
	option apn 'internet'
	option device '/dev/cdc-wdm0'
	option dhcp '1'
05.03.2017598Base systemBug ReportMediumLow842nd doesnt flash successful with factory image using ...lede-17.01New Task Description

Device: 842nd v3.1
LEDE: 17.01

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

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

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

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

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

08.03.2017607KernelBug ReportMediumLowKernel BUG: Bad page state in process ntpd-hotplugTrunkNew Task Description

While doing wireless benchmarks between two TP-Link WR841 running the latest LEDE, one of them (the AP) showed the stack trace below. It does not seem to impact the behaviour of the system, though: everything seems to work correctly after the stack trace.

The device is TL-WR841N v8, with a snapshot build r3670-154b3a6 (kernel is 4.4.52).

It occurred about one minute after I plugged the WAN port to the Internet, which explains why ntpd-hotplug appears in the log. There was still a heavy amount of wireless traffic (both when I plugged the WAN, and when the stack trace occurred).

Wed Mar  8 22:02:31 2017 kern.alert kernel: [ 1913.427453] BUG: Bad page state in process ntpd-hotplug  pfn:015fa
Wed Mar  8 22:02:31 2017 kern.emerg kernel: [ 1913.433936] page:8102bf40 count:-2130657536 mapcount:16711936 mapping:  (null) index:0xff00ff00
Wed Mar  8 22:02:31 2017 kern.emerg kernel: [ 1913.442939] flags: 0x0()
Wed Mar  8 22:02:31 2017 kern.alert kernel: [ 1913.445561] page dumped because: nonzero _count
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.450237] Modules linked in: ath9k ath9k_common pppoe ppp_async ath9k_hw 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_CT slhc 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_coWed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.509878] CPU: 0 PID: 1501 Comm: ntpd-hotplug Not tainted 4.4.52 #0
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.516549] Stack : 803e49f0 00000000 00000001 80440000 818f16a4 8042ee63 803c5ff4 000005dd
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.516549] 	  804a378c 803d0000 803d0000 803d0000 803d0000 800a7640 803cb6e4 80430000
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.516549] 	  00000003 803d0000 803c9af0 81809d74 803d0000 800a55bc 803d0000 803d0000
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.516549] 	  803d0000 801f5800 00000000 00000000 00000000 00000000 00000000 00000000
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.516549] 	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.516549] 	  ...
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.553574] Call Trace:
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.556121] [<80071eb0>] show_stack+0x50/0x84
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.560630] [<800d57e4>] bad_page+0xec/0x11c
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.565069] [<800d59b0>] free_pages_prepare+0x19c/0x1f8
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.570474] [<800d6c74>] __free_pages_ok+0x2c/0x31c
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.575554] [<80261278>] __kfree_skb+0x28/0xb0
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.580155] [<8023871c>] ag71xx_tx_packets+0x154/0x2c8
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.585486] [<80239530>] ag71xx_poll+0x6c/0x5c0
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.590203] [<8026f748>] net_rx_action+0x10c/0x2c8
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.595183] [<800841c8>] __do_softirq+0x250/0x298
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.600066] [<8006a9e0>] plat_irq_dispatch+0xd4/0x10c
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.605297] 
Wed Mar  8 22:02:31 2017 kern.warn kernel: [ 1913.606843] Disabling lock debugging due to kernel taint
09.03.2017609Base systemFeature RequestMediumLowprocd: implement runlevel 1TrunkNew Task Description

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

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

04.05.2017760Base systemBug ReportVery LowLowMQmaker WiTi / mt76x2e / 2.4 GHz / no minstrel sampling...TrunkNew Task Description

very bad performance for all neighbours on r3900

# cat /sys/kernel/debug/ieee80211/phy1/netdev:wlan1/stations/a0:f3:c1:ce:56:80/rc_stats
              best   ____________rate__________    ________statistics________    _____last____    ______sum-of________
mode guard #  rate  [name   idx airtime  max_tp]  [avg(tp) avg(prob) sd(prob)]  [retry|suc|att]  [#success | #attempts]
CCK    LP  1          1.0M  120   10548     0.0       0.0       0.0      0.0       0     0 0             0   0
CCK    LP  1          2.0M  121    5476     0.0       0.0       0.0      0.0       0     0 0             0   0
CCK    LP  1          5.5M  122    2411     2.4       0.0       0.0      0.0       0     0 0             0   0
CCK    LP  1         11.0M  123    1535     4.8       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  1  ABCDP  MCS0     0    1477     4.8       0.0       0.0      0.0       1     0 0             0   0
HT20  LGI  1         MCS1     1     739     9.7       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  1         MCS2     2     493    14.6       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  1         MCS3     3     369    17.0       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  1         MCS4     4     246    24.4       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  1         MCS5     5     185    29.2       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  1         MCS6     6     164    31.7       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  1         MCS7     7     148    34.1       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  2         MCS8    10     739     9.7       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  2         MCS9    11     369    17.0       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  2         MCS10   12     246    24.4       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  2         MCS11   13     185    29.2       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  2         MCS12   14     123    36.6       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  2         MCS13   15      93    43.9       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  2         MCS14   16      82    46.3       0.0       0.0      0.0       0     0 0             0   0
HT20  LGI  2         MCS15   17      74    48.8       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  1         MCS0    30    1329     4.8       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  1         MCS1    31     665     9.7       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  1         MCS2    32     443    14.6       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  1         MCS3    33     332    19.5       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  1         MCS4    34     222    26.8       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  1         MCS5    35     166    31.7       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  1         MCS6    36     148    34.1       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  1         MCS7    37     133    36.6       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  2         MCS8    40     665     9.7       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  2         MCS9    41     332    19.5       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  2         MCS10   42     222    26.8       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  2         MCS11   43     166    31.7       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  2         MCS12   44     111    39.0       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  2         MCS13   45      83    46.3       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  2         MCS14   46      74    48.8       0.0       0.0      0.0       0     0 0             0   0
HT20  SGI  2         MCS15   47      67    51.2       0.0       0.0      0.0       0     0 0             0   0

Total packet count::    ideal 7625      lookaround 407
Average # of aggregated frames per A-MPDU: 1.0

root@witi7:~ :) arping -I wlan1 10.63.102.195
ARPING to 10.63.102.195 from 10.63.140.195 via wlan1
Unicast reply from 10.63.102.195 [a0:f3:c1:ce:56:80] 491.552ms
Unicast reply from 10.63.102.195 [a0:f3:c1:ce:56:80] 600.276ms
Unicast reply from 10.63.102.195 [a0:f3:c1:ce:56:80] 747.811ms
Unicast reply from 10.63.102.195 [a0:f3:c1:ce:56:80] 748.426ms
Unicast reply from 10.63.102.195 [a0:f3:c1:ce:56:80] 511.603ms
Unicast reply from 10.63.102.195 [a0:f3:c1:ce:56:80] 403.993ms
Unicast reply from 10.63.102.195 [a0:f3:c1:ce:56:80] 601.602ms
Unicast reply from 10.63.102.195 [a0:f3:c1:ce:56:80] 371.090ms

root@witi7:~ :) ping -c1 10.63.102.195
PING 10.63.102.195 (10.63.102.195): 56 data bytes
64 bytes from 10.63.102.195: seq=0 ttl=64 time=2414.528 ms

--- 10.63.102.195 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 2414.528/2414.528/2414.528 ms

root@witi7:~ :) iw dev wlan1 station get a0:f3:c1:ce:56:80
Station a0:f3:c1:ce:56:80 (on wlan1)
        inactive time:  150 ms
        rx bytes:       32573998
        rx packets:     63413
        tx bytes:       1038834
        tx packets:     8318
        tx retries:     133088
        tx failed:      8318
        rx drop misc:   30946
        signal:         -60 [-67, -60] dBm
        signal avg:     -59 [-67, -59] dBm
        tx bitrate:     6.5 MBit/s MCS 0
        rx bitrate:     6.5 MBit/s MCS 0
        authorized:     yes
        authenticated:  yes
        associated:     yes
        preamble:       long
        WMM/WME:        yes
        MFP:            no
        TDLS peer:      no
        DTIM period:    0
        beacon interval:250
        connected time: 8652 seconds

# uci show wireless (2.4ghz)
wireless.radio1=wifi-device
wireless.radio1.type='mac80211'
wireless.radio1.country='US'
wireless.radio1.frag='off'
wireless.radio1.path='pci0000:00/0000:00:01.0/0000:02:00.0'
wireless.radio1.chanbw='20'
wireless.radio1.channel='5'
wireless.radio1.distance='100'
wireless.radio1.beacon_int='250'
wireless.radio1.hwmode='11n'
wireless.radio1.htmode='HT20'
wireless.radio1.txpower='23'

wireless.@wifi-iface[2]=wifi-iface
wireless.@wifi-iface[2].device='radio1'
wireless.@wifi-iface[2].network='wlanadhocRADIO1'
wireless.@wifi-iface[2].mode='adhoc'
wireless.@wifi-iface[2].mcast_rate='6000'
wireless.@wifi-iface[2].macaddr='8c:bc:c0:43:c9:09'
wireless.@wifi-iface[2].bssid='02:ca:ff:ee:ba:be'
wireless.@wifi-iface[2].ssid='ffintern.2GHz'

wireless.@wifi-iface[3]=wifi-iface
wireless.@wifi-iface[3].device='radio1'
wireless.@wifi-iface[3].network='wlanRADIO1'
wireless.@wifi-iface[3].encryption='none'
wireless.@wifi-iface[3].mode='ap'
wireless.@wifi-iface[3].macaddr='8e:bc:c0:43:c9:0a'
wireless.@wifi-iface[3].max_inactivity='10'
wireless.@wifi-iface[3].ssid='weimar.freifunk.net'
wireless.@wifi-iface[3].disassoc_low_ack='1'

Showing tasks 1 - 50 of 534 Page 1 of 111 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing