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
02.05.2017751Base systemFeature RequestVery LowVery LowAdd customisable SIGINT behaviour to procdlede-17.01Unconfirmed Task Description

I am running LEDE 17.01.1 on a Linksys NSLU2.

The device has a power button on the front panel, which will boot the device when pressed when power is present. If the button is pressed when the device is running the device will reboot. I would like to be able to configure the device to power off when the button is pressed instead.

I have tried editing some of the stock scripts in /etc/rc.button to no effect. I ran across this page on the OpenWrt wiki, which suggests that pressing the button causes SIGINT to be delivered to PID 1.

I took a look at the procd git repository, and procd reboots the system when it catches SIGINT. If this were configurable then procd could take specific action, such as powering the device down, when it receives a hardware interrupt.

30.04.2017747Base systemBug ReportVery LowLowdefault dns service doesn't provide qname minimizationTrunkUnconfirmed Task Description

Supply the following if possible:

- Device problem occurs on

All

- Software versions of LEDE release, packages, etc.

All

- Steps to reproduce

* Perform a DNS resolution

qname minimization reduces the amount of information to sent via each lookup, this is to my knowledge not supported by dnsmasq which is the default DNS resolver in LEDE. It would be nice if support was added to it, or if it was replaced by some other name server that tries to reduce the amount of information leaked to foreign servers.

The spec:
https://tools.ietf.org/html/draft-ietf-dnsop-qname-minimisation-09

Unbound plugs this leak, does it lack anything that LEDE uses?

28.04.2017740Base systemBug ReportVery LowMediumWRT54 Router Power LED continually flasheslede-17.01Unconfirmed Task Description
  • LEDE 17.01.1
  • WRT54G v3 and WRT54GS
  • after installing, power LED continually flashes
  • no noticeable difference in LED between failsafe/actual moment of soft reboot//when router is up
  • I had to failsafe the WRT54G multiple times due to other initial config errors (attempting to bridge wlan0 to LAN, which was possible in another OS), I could only identify failsafe by Pinging it then SSHing quickly
  • The method I described to identify failsafe is not mentioned in documentation
24.04.2017732Base systemBug ReportVery LowVery LowD-Link DIR-615 D2 (ramips rt305x) Wireless LED Not Flas...AllUnconfirmed Task Description

I have a D-Link DIR-615 D2 (dir-615-d-squashfs-factory.bin), Its all working fine however the LED for the wireless light dosnt flash nor show activity to show is been used as it shows a solid green WiFi light. LANs from 1-4 all flash perfectly so no issue here.

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

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

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

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

20.04.2017727Base systemBug ReportVery LowLowUSB not working on TL-WDR4900 v1.xTrunkUnconfirmed Task Description

USB ports are empty but hub is deteched periodically.

dmesg | grep -i usb
[ 0.029483] usbcore: registered new interface driver usbfs
[ 0.029537] usbcore: registered new interface driver hub
[ 0.029580] usbcore: registered new device driver usb
[ 2.075954] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 2.104850] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
[ 2.138024] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
[ 2.144048] hub 1-0:1.0: USB hub found
[ 2.535450] usb 1-1: new high-speed USB device number 2 using fsl-ehci
[ 2.728493] hub 1-1:1.0: USB hub found
[ 3.511480] usb 1-1: USB disconnect, device number 2
[ 3.814034] usb 1-1: new high-speed USB device number 3 using fsl-ehci
[ 3.952117] hub 1-1:1.0: USB hub found
[ 4.484403] usb 1-1: USB disconnect, device number 3
[ 4.730021] usb 1-1: new high-speed USB device number 4 using fsl-ehci
[ 4.868111] hub 1-1:1.0: USB hub found
[ 5.265649] usb 1-1: USB disconnect, device number 4
[ 5.510021] usb 1-1: new high-speed USB device number 5 using fsl-ehci
[ 6.098025] usb 1-1: device not accepting address 5, error -71
[ 6.398018] usb 1-1: new high-speed USB device number 7 using fsl-ehci

[ 986.577885] usb 1-1: USB disconnect, device number 124
[ 986.821924] usb 1-1: new high-speed USB device number 125 using fsl-ehci
[ 986.960029] hub 1-1:1.0: USB hub found
[ 991.933221] usb 1-1: USB disconnect, device number 125
[ 992.177825] usb 1-1: new high-speed USB device number 126 using fsl-ehci
[ 992.315980] hub 1-1:1.0: USB hub found
[ 1001.763764] usb 1-1: USB disconnect, device number 126
[ 1002.009660] usb 1-1: new high-speed USB device number 127 using fsl-ehci
[ 1002.159774] hub 1-1:1.0: USB hub found
[ 1006.033730] usb 1-1: USB disconnect, device number 127
[ 1006.281597] usb 1-1: new high-speed USB device number 2 using fsl-ehci
[ 1006.419736] hub 1-1:1.0: USB hub found
[ 1009.824073] usb 1-1: USB disconnect, device number 2
[ 1010.076110] usb 1-1: new high-speed USB device number 3 using fsl-ehci

cat /sys/kernel/debug/usb/devices

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 4.04
S: Manufacturer=Linux 4.4.61 ehci_hcd
S: Product=Freescale On-Chip EHCI Host Controller
S: SerialNumber=fsl-ehci.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 88 Spd=480 MxCh= 4
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=05e3 ProdID=0608 Rev=85.36
S: Product=USB2.0 Hub
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms

lsusb -v

Bus 001 Device 090: ID 05e3:0608 Genesys Logic, Inc. Hub
Device Descriptor:

bLength                18
bDescriptorType         1
bcdUSB               2.00
bDeviceClass            9 Hub
bDeviceSubClass         0 Unused
bDeviceProtocol         1 Single TT
bMaxPacketSize0        64
idVendor           0x05e3 Genesys Logic, Inc.
idProduct          0x0608 Hub
bcdDevice           85.36
iManufacturer           0 
iProduct                1 USB2.0 Hub
iSerial                 0 
bNumConfigurations      1
Configuration Descriptor:
  bLength                 9
  bDescriptorType         2
  wTotalLength           25
  bNumInterfaces          1
  bConfigurationValue     1
  iConfiguration          0 
  bmAttributes         0xe0
    Self Powered
    Remote Wakeup
  MaxPower              100mA
  Interface Descriptor:
    bLength                 9
    bDescriptorType         4
    bInterfaceNumber        0
    bAlternateSetting       0
    bNumEndpoints           1
    bInterfaceClass         9 Hub
    bInterfaceSubClass      0 Unused
    bInterfaceProtocol      0 Full speed (or root) hub
    iInterface              0 
    Endpoint Descriptor:
      bLength                 7
      bDescriptorType         5
      bEndpointAddress     0x81  EP 1 IN
      bmAttributes            3
        Transfer Type            Interrupt
        Synch Type               None
        Usage Type               Data
      wMaxPacketSize     0x0001  1x 1 bytes
      bInterval              12

Hub Descriptor:

bLength               9
bDescriptorType      41
nNbrPorts             4
wHubCharacteristic 0x00e9
  Per-port power switching
  Per-port overcurrent protection
  TT think time 32 FS bits
  Port indicators
bPwrOn2PwrGood       50 * 2 milli seconds
bHubContrCurrent    100 milli Ampere
DeviceRemovable    0x00
PortPwrCtrlMask    0xff

Hub Port Status:

 Port 1: 0000.0100 power
 Port 2: 0000.0100 power
 Port 3: 0000.0100 power
 Port 4: 0000.0100 power

Device Qualifier (for other device speed):

bLength                10
bDescriptorType         6
bcdUSB               2.00
bDeviceClass            9 Hub
bDeviceSubClass         0 Unused
bDeviceProtocol         0 Full speed (or root) hub
bMaxPacketSize0        64
bNumConfigurations      1

Device Status: 0×0001

Self Powered

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:

bLength                18
bDescriptorType         1
bcdUSB               2.00
bDeviceClass            9 Hub
bDeviceSubClass         0 Unused
bDeviceProtocol         1 Single TT
bMaxPacketSize0        64
idVendor           0x1d6b Linux Foundation
idProduct          0x0002 2.0 root hub
bcdDevice            4.04
iManufacturer           3 Linux 4.4.61 ehci_hcd
iProduct                2 Freescale On-Chip EHCI Host Controller
iSerial                 1 fsl-ehci.0
bNumConfigurations      1
Configuration Descriptor:
  bLength                 9
  bDescriptorType         2
  wTotalLength           25
  bNumInterfaces          1
  bConfigurationValue     1
  iConfiguration          0 
  bmAttributes         0xe0
    Self Powered
    Remote Wakeup
  MaxPower                0mA
  Interface Descriptor:
    bLength                 9
    bDescriptorType         4
    bInterfaceNumber        0
    bAlternateSetting       0
    bNumEndpoints           1
    bInterfaceClass         9 Hub
    bInterfaceSubClass      0 Unused
    bInterfaceProtocol      0 Full speed (or root) hub
    iInterface              0 
    Endpoint Descriptor:
      bLength                 7
      bDescriptorType         5
      bEndpointAddress     0x81  EP 1 IN
      bmAttributes            3
        Transfer Type            Interrupt
        Synch Type               None
        Usage Type               Data
      wMaxPacketSize     0x0004  1x 4 bytes
      bInterval              12

Hub Descriptor:

bLength               9
bDescriptorType      41
nNbrPorts             1
wHubCharacteristic 0x0009
  Per-port power switching
  Per-port overcurrent protection
  TT think time 8 FS bits
bPwrOn2PwrGood       10 * 2 milli seconds
bHubContrCurrent      0 milli Ampere
DeviceRemovable    0x00
PortPwrCtrlMask    0xff

Hub Port Status:

 Port 1: 0000.0503 highspeed power enable connect

Device Status: 0×0001

Self Powered


19.04.2017723Base systemBug ReportVery LowMediumath10k fails station mode for QCA986x/988xlede-17.01Unconfirmed Task Description

Set-Up:

  • Board: NXP/Freescale Layerscape TWR-LS1021A Router/AP
  • Wireless Network Adapter: Qualcomm Atheros PCI QCA986x/988x 802.11ac
  • OS: LEDE (derivative from OpenWrt) Reboot/SNAPSHOT/r3044-21356a6

On host: menuconfig:

  • Kernel modules > Wireless Drivers: kmod-ath10k, kmod-ath, kmod-cfg80211, kmod-mac80211
  • Firmware: ath10k-firmware-qca988x
  • Network: wpad, wpa-cli
  • netifd + ubus + uci

On TWR-LS1021A:
Just in order to test if WiFi card is really QCA986x/988x 802.11ac:
root@lede:/# cat /sys/bus/pci/devices/0000\:01\:00.0/vendor

0x168c

root@lede:/# cat /sys/bus/pci/devices/0000\:01\:00.0/device

0x003c

Google: PCI 168c 0x003c gives QCA986x/988x


During the first boot, boot scripts create: /etc/config/wireless with the following contents:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'soc/3400000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
        option htmode 'VHT80'
        option disabled '1'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'none'

We remove: option disabled ‘1’ (WiFi is disabled by default → enable it) and reboot.

Boot with USB-serial output:

…
[    6.270954] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    6.450972] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[    6.461643] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.474916] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[    6.484102] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
[    6.494431] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.507497] firmware ath10k!cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[    6.528736] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[    6.537986] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[    6.548737] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00016 api 5 features no-p2p,raw-mode,mfp crc32 0c5668f8
[    6.599443] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[    6.609853] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.623269] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[    6.632927] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[    7.775018] ath10k_pci 0000:01:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
…
[   11.014199] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   11.022336] device wlan0 entered promiscuous mode
[   11.336732] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
…

Remarks:

  • pre-cal/cal-pci error messages are connected to pre-calibration issues, so ignore them
  • board-2.bin error: indeed /lib/firmware/ath10k/QCA988X/hw2.0/ contains only board.bin and firmware-5.bin. we have tried to copy hw2.0/board-2.bin from QCA proprietary driver but then: [ 6.590282] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003c,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA988X/hw2.0/board-2.bin

Nevertheless, the driver is correctly started in AP mode:
root@lede:/# iwconfig

wlan0     IEEE 802.11  Mode:Master  Tx-Power=20 dBm   
          RTS thr:off   Fragment thr:off
          Power Management:off

root@lede:/# ifconfig

wlan0     Link encap:Ethernet  HWaddr 00:0E:8E:59:7D:8F  
          inet6 addr: fe80::20e:8eff:fe59:7d8f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:128 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:15588 (15.2 KiB)

Now try to switch to station mode with WPA:
AP: 802.11a, channel 36: 5.18 GHz, SSID: iwl3xxx, Security mode: WPA/PSK, CCMP/AES (WPA/RSN), Password: password

TWR-LS1021A: /etc/config/wireless:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'soc/3400000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'wlan'
        option mode 'sta'
        option ssid 'iwl3xxx'
        option encryption 'psk'
        option key 'password'

config interface 'wlan'
        option ifname 'default_radio0'
        option proto 'static'
        option ipaddr '192.168.0.2'
        option netmask '255.255.255.0'

root@lede:/# iwconfig

wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

It correctly switches to managed mode but no ESSID and no AP are assigned. Direct WPA supplicant employment also fails:

We create WPA config file /a:

country=00
network={
  ssid="iwl3xxx"
  psk="password"
  scan_ssid=1
  key_mgmt=WPA-PSK
  pairwise=CCMP TKIP
  group=CCMP TKIP
}

Start WPA supplicant:
root@lede:/# wpa_supplicant -c /a -i wlan0 -D nl80211

Successfully initialized wpa_supplicant
wlan0: SME: Trying to authenticate with 00:18:92:05:b6:ec (SSID='iwl3xxx' freq=5180 MHz)
[ 2736.691425] wlan0: authenticate with 00:18:92:05:b6:ec
[ 2736.702348] wlan0: send auth to 00:18:92:05:b6:ec (try 1/3)
[ 2736.709540] wlan0: authenticated
wlan0: Trying to associate with 00:18:92:05:b6:ec (SSID='iwl3xxx' freq=5180 MHz)
[ 2736.717183] wlan0: associate with 00:18:92:05:b6:ec (try 1/3)
[ 2736.725522] wlan0: RX AssocResp from 00:18:92:05:b6:ec (capab=0x411 status=0 aid=1)
[ 2736.734827] wlan0: associated
[ 2736.738114] wlan0: deauthenticating from 00:18:92:05:b6:ec by local choice (Reason: 3=DEAUTH_LEAVING)
wlan0: Associated with 00:18:92:05:b6:ec
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:18:92:05:b6:ec reason=3 locally_generated=1
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="iwl3xxx" auth_failures=1 duration=10 reason=WRONG_KEY

Though the key is correct, the driver delivers WRONG_KEY message. In order to eliminate any security issues, we switch to insecure communication:
AP: 802.11a, channel 36: 5.18 GHz, SSID: iwl3xxx, Security mode: NONE

TWR-LS1021A: WPA config file /a:

country=00
network={
  ssid="iwl3xxx"
  scan_ssid=1
  key_mgmt=NONE
}

Start WPA supplicant:
root@lede:/# wpa_supplicant -c /a -i wlan0 -D nl80211

Successfully initialized wpa_supplicant
wlan0: SME: Trying to authenticate with 00:18:92:05:b6:ec (SSID='iwl3xxx' freq=5180 MHz)
[   26.011997] wlan0: authenticate with 00:18:92:05:b6:ec
[   26.069291] wlan0: send auth to 00:18:92:05:b6:ec (try 1/3)
[   26.075992] wlan0: authenticated
wlan0: Trying to associate with 00:18:92:05:b6:ec (SSID='iwl3xxx' freq=5180 MHz)
[   26.087236] wlan0: associate with 00:18:92:05:b6:ec (try 1/3)
[   26.094140] wlan0: RX AssocResp from 00:18:92:05:b6:ec (capab=0x401 status=0 aid=1)
[   26.103088] wlan0: associated
[   26.106163] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: Associated with 00:18:92:05:b6:ec
wlan0: CTRL-EVENT-CONNECTED - Connection to 00:18:92:05:b6:ec completed [id=0 id_str=]
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[   36.117315] wlan0: deauthenticating from 00:18:92:05:b6:ec by local choice (Reason: 3=DEAUTH_LEAVING)
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:18:92:05:b6:ec reason=3 locally_generated=1

So, WPA supplicant reports: we were authenticated and associated, connection completed. And then we leave WiFi by local choice. WireShark shows that deauthenticate-request comes from from us to access point.

Result: ath10k fails station mode for QCA986x/988x

19.04.2017720Base systemBug ReportVery LowLowgpio-button-hotplug: missing debounce for IRQ GPIOsTrunkUnconfirmed Task Description

I’ve noticed that some (multiple random) hardware in the fields suffers from weird factory resets without somebody pressing the button (it is physical not possible that someone could reach the button). I’ve noticed that it only happens with hardware that supports GPIO IRQs and which uses gpio-button-hotplug.

Problem seems to be that:

* CPU registers a really short 1 on the GPIO line
* IRQ is triggered
* gpio-button-hotplug handles the IRQ and noticed that the GPIO line is 0
* gpio-button-hotplug thinks that this was a button release after a really long button press
* factory reset is triggered by /etc/rc.button/reset

It looks like this can be fixed by checking if the button was actually pressed before calculating the holding time and sending the userspace event.

But there is a possible second problem caused by the missing debounce. The (incorrect) 1 on the GPIO line could be there long enough that the interrupt handler registers a press then directly receives a button release. This would trigger a REBOOT (even when not wanted). This (maybe) can be fixed by using a 5ms timer until accepting a key press.

19.04.2017718Base systemBug ReportVery LowLownetifd fails to set rps for WDSTrunkUnconfirmed Task Description

netifd sets the packet steering for all interfaces it controls to better spread the load over multiple cores. But it fails to set it for wds interfaces like wlan0.sta1. As result, the performance in WDS setups is limited by a single core of a multi-core device.

To reproduce: enable an AP in /etc/config/wireless. Enable the wds option for the AP interface. Connect a client to the AP and check /sys/devices/*/net/wlan*.sta1/queues/rx-*/rps_cpus. All BITS for all available CPUs should be enabled (when it would work). It stays currently at 0.

19.04.2017717Base systemBug ReportVery LowHighWRT3200ACM USB 3.0 ProblemAllUnconfirmed Task Description

I can´t get my Seagate Expansion Portable 1TB STEA1000400 USB3.0 drive to be be recognized on the USB 3.0 port of the router after a reboot or cold start on WRT3200 but if i remove and hotplug the drive, it is automatically detected and can be mounted.
It happens with images from Openwrt 15.05.1, LEDE 17.01.1 and many snapshots from both projects that i have installed. I have no problem with another usb2.0 drive from Samsung that is installed in another USB2.0 port.

After Cold START or REBOOT

 root@LEDE:~# dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.20 (ag33e33@ubuntu) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3963-7ae58be) ) #0 SMP Wed Apr 12 16:12:18 2017
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: Linksys WRT3200ACM
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 131072
[    0.000000] free_area_init_node: node 0, pgdat c0646900, node_mem_map dfbf9000
[    0.000000]   Normal zone: 1024 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 131072 pages, LIFO batch:31
[    0.000000] percpu: Embedded 13 pages/cpu @dfbce000 s22732 r8192 d22324 u53248
[    0.000000] pcpu-alloc: s22732 r8192 d22324 u53248 alloc=13*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock6 ro rootdelay=1 rootfstype=jffs2 earlyprintk mtdparts=armada-nand:2048K(uboot)ro,128K(u_env),256K(s_env),256K@8064K(devinfo),1920K@8320K(sysdiag),80m@10m(kernel),74m@16m(rootfs),80m@90m(alt_kernel),74m@96m(alt_rootfs),160m@10m(ubifs),-@170m(syscfg)
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 512848K/524288K available (4545K kernel code, 180K rwdata, 1244K rodata, 280K init, 310K bss, 11440K reserved, 0K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xe0800000 - 0xff800000   ( 496 MB)
                   lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                   modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                     .text : 0xc0008000 - 0xc0478918   (4547 kB)
                     .init : 0xc05d4000 - 0xc061a000   ( 280 kB)
                     .data : 0xc061a000 - 0xc0647200   ( 181 kB)
                      .bss : 0xc0647200 - 0xc0694a00   ( 310 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] mvebu_mbus: [Firmware Warn]: deprecated mbus-mvebu Device Tree, suspend/resume will not work
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 D prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001
[    0.000000] Selected CPU frequency (16) unsupported
[    0.000000] Switching to timer-based delay loop, resolution 40ns
[    0.000002] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899345900ns
[    0.000008] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[    0.000114] Calibrating local timer... 933.22MHz.
[    0.060032] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=250000)
[    0.060037] pid_max: default: 32768 minimum: 301
[    0.060076] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.060079] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.060274] CPU: Testing write buffer coherency: ok
[    0.060365] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.060376] Setting up static identity map for 0x8280 - 0x82d8
[    0.060434] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4
[    0.060494] mvebu-pmsu: Initializing Power Management Service Unit
[    0.060904] Booting CPU 1
[    0.061041] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.061070] Brought up 2 CPUs
[    0.061075] SMP: Total of 2 processors activated (100.00 BogoMIPS).
[    0.061078] CPU: All CPU(s) started in SVC mode.
[    0.062739] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.062790] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.062796] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.062831] pinctrl core: initialized pinctrl subsystem
[    0.063142] NET: Registered protocol family 16
[    0.063575] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.090041] cpuidle: using governor ladder
[    0.090171] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
[    0.090177] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
[    0.120467] reg-fixed-voltage xhci0-vbus: could not find pctldev for node /soc/internal-regs/pinctrl@18000/xhci0-vbus-pins, deferring probe
[    0.120607] SCSI subsystem initialized
[    0.120687] libata version 3.00 loaded.
[    0.120790] usbcore: registered new interface driver usbfs
[    0.120815] usbcore: registered new interface driver hub
[    0.120835] usbcore: registered new device driver usb
[    0.121329] clocksource: Switched to clocksource armada_370_xp_clocksource
[    0.121647] NET: Registered protocol family 2
[    0.121869] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.121890] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.121920] TCP: Hash tables configured (established 4096 bind 4096)
[    0.121941] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.121952] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.122009] NET: Registered protocol family 1
[    0.122021] PCI: CLS 0 bytes, default 64
[    0.122803] Crashlog allocated RAM at address 0x3f00000
[    0.122877] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[    0.124945] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.124953] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.125699] io scheduler noop registered
[    0.125703] io scheduler deadline registered (default)
[    0.126071] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
[    0.126671] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 0000:00
[    0.126679] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    0.126683] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[    0.126687] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.126701] pci 0000:00:01.0: [11ab:6820] type 01 class 0x060400
[    0.126784] pci 0000:00:02.0: [11ab:6820] type 01 class 0x060400
[    0.126859] PCI: bus0: Fast back to back transfers disabled
[    0.126864] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.126870] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.126918] pci 0000:01:00.0: [11ab:2b40] type 00 class 0x020000
[    0.126933] pci 0000:01:00.0: reg 0x10: [mem 0x40000000-0x401fffff 64bit pref]
[    0.126943] pci 0000:01:00.0: reg 0x18: [mem 0x40200000-0x402fffff 64bit pref]
[    0.127002] pci 0000:01:00.0: supports D1 D2
[    0.127005] pci 0000:01:00.0: PME# supported from D0 D1 D3hot D3cold
[    0.127068] PCI: bus1: Fast back to back transfers disabled
[    0.127073] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.127132] pci 0000:02:00.0: [11ab:2b40] type 00 class 0x020000
[    0.127151] pci 0000:02:00.0: reg 0x10: [mem 0x42000000-0x421fffff 64bit pref]
[    0.127162] pci 0000:02:00.0: reg 0x18: [mem 0x42200000-0x422fffff 64bit pref]
[    0.127244] pci 0000:02:00.0: supports D1 D2
[    0.127246] pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold
[    0.127310] PCI: bus2: Fast back to back transfers disabled
[    0.127315] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    0.127384] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe02fffff]
[    0.127390] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0400000-0xe06fffff]
[    0.127396] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit pref]
[    0.127405] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0200000-0xe02fffff 64bit pref]
[    0.127413] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.127418] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe02fffff]
[    0.127425] pci 0000:02:00.0: BAR 0: assigned [mem 0xe0400000-0xe05fffff 64bit pref]
[    0.127434] pci 0000:02:00.0: BAR 2: assigned [mem 0xe0600000-0xe06fffff 64bit pref]
[    0.127443] pci 0000:00:02.0: PCI bridge to [bus 02]
[    0.127448] pci 0000:00:02.0:   bridge window [mem 0xe0400000-0xe06fffff]
[    0.127646] mv_xor f1060800.xor: Marvell shared XOR driver
[    0.181754] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    0.181840] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.241717] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    0.241857] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.242621] console [ttyS0] disabled
[    0.262683] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 21, base_baud = 12500000) is a 16550A
[    0.983287] console [ttyS0] enabled
[    0.988691] loop: module loaded
[    0.992090] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[    1.001176] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[    1.010274] scsi host0: ahci-mvebu
[    1.013847] scsi host1: ahci-mvebu
[    1.017348] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 41
[    1.025306] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 41
[    1.033594] pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device
[    1.041369] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xda
[    1.047747] nand: AMD/Spansion S34ML02G2
[    1.051690] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[    1.059379] pxa3xx-nand f10d0000.flash: ECC strength 16, ECC step size 2048
[    1.066556] Bad block table found at page 131008, version 0x01
[    1.072752] Bad block table found at page 130944, version 0x01
[    1.078863] 11 ofpart partitions found on MTD device pxa3xx_nand-0
[    1.085074] Creating 11 MTD partitions on "pxa3xx_nand-0":
[    1.090582] 0x000000000000-0x000000200000 : "u-boot"
[    1.095830] 0x000000200000-0x000000220000 : "u_env"
[    1.100951] 0x000000220000-0x000000260000 : "s_env"
[    1.106089] 0x0000007e0000-0x000000820000 : "devinfo"
[    1.111433] 0x000000820000-0x000000a00000 : "sysdiag"
[    1.116797] 0x000000a00000-0x000005a00000 : "kernel1"
[    1.122301] 0x000001000000-0x000005a00000 : "ubi"
[    1.127404] 0x000005a00000-0x00000aa00000 : "kernel2"
[    1.132905] 0x000006000000-0x00000aa00000 : "rootfs2"
[    1.138362] 0x00000aa00000-0x000010000000 : "syscfg"
[    1.143774] 0x000000260000-0x000000820000 : "unused_area"
[    1.149701] libphy: Fixed MDIO Bus: probed
[    1.154064] libphy: orion_mdio_bus: probed
[    1.158297] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled
[    1.166962] mvneta f1070000.ethernet eth0: Using hardware mac address 60:38:e0:b9:ea:c0
[    1.175959] mvneta f1034000.ethernet eth1: Using random mac address a2:8d:5e:6d:ee:98
[    1.183881] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.190435] ehci-pci: EHCI PCI platform driver
[    1.194928] ehci-platform: EHCI generic platform driver
[    1.200245] ehci-orion: EHCI orion driver
[    1.204336] orion-ehci f1058000.usb: EHCI Host Controller
[    1.209765] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 1
[    1.217412] orion-ehci f1058000.usb: irq 37, io mem 0xf1058000
[    1.251329] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[    1.257480] hub 1-0:1.0: USB hub found
[    1.261254] hub 1-0:1.0: 1 port detected
[    1.265551] usbcore: registered new interface driver usb-storage
[    1.271723] armada38x-rtc f10a3800.rtc: rtc core: registered f10a3800.rtc as rtc0
[    1.279341] i2c /dev entries driver
[    1.294252] orion_wdt: Initial timeout 171 sec
[    1.298933] sdhci: Secure Digital Host Controller Interface driver
[    1.305146] sdhci: Copyright(c) Pierre Ossman
[    1.362546] ata1: SATA link down (SStatus 0 SControl 300)
[    1.367991] ata2: SATA link down (SStatus 0 SControl 300)
[    1.371354] mmc0: SDHCI controller on f10d8000.sdhci [f10d8000.sdhci] using ADMA
[    1.371428] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.377154] marvell-cesa f1090000.crypto: CESA device successfully registered
[    1.377556] NET: Registered protocol family 10
[    1.391590] NET: Registered protocol family 17
[    1.391604] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.391605] 8021q: 802.1Q VLAN Support v1.8
[    1.391661] Registering SWP/SWPB emulation handler
[    1.392791] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    1.392803] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 2
[    1.392861] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x00010010
[    1.392881] xhci-hcd f10f8000.usb3: irq 44, io mem 0xf10f8000
[    1.393134] hub 2-0:1.0: USB hub found
[    1.393160] hub 2-0:1.0: 1 port detected
[    1.393247] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    1.393253] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 3
[    1.393292] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.393478] hub 3-0:1.0: USB hub found
[    1.393501] hub 3-0:1.0: 1 port detected
[    1.393820] UBI: auto-attach mtd6
[    1.393824] ubi0: attaching mtd6
[    1.397930] random: fast init done
[    1.401551] mmc0: new high speed SDIO card at address 0001
[    1.593092] ubi0: scanning is finished
[    1.601334] ubi0: attached mtd6 (name "ubi", size 74 MiB)
[    1.606756] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.613664] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.620479] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.627475] ubi0: good PEBs: 592, bad PEBs: 0, corrupted PEBs: 0
[    1.633508] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    1.640759] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1419003487
[    1.649932] ubi0: available PEBs: 0, total reserved PEBs: 592, PEBs reserved for bad PEB handling: 40
[    1.659197] ubi0: background thread "ubi_bgt0d" started, PID 668
[    1.659208] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    1.659643] block ubiblock0_0: created from ubi0:0(rootfs)
[    1.659645] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    1.659829] mvsw61xx 10.mvsw61xx: Found MV88E6352 at f1072004.mdio-mi:10
[    1.659832] mvsw61xx 10.mvsw61xx: Using direct addressing
[    1.671972] armada38x-rtc f10a3800.rtc: setting system clock to 2101-11-05 12:45:50 UTC (4160637950)
[    1.705850] Waiting 1 sec before mounting root device...
[    1.852932] usb-storage 1-1:1.0: USB Mass Storage device detected
[    1.859142] scsi host2: usb-storage 1-1:1.0
[    2.722974] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    2.730260] Freeing unused kernel memory: 280K (c05d4000 - c061a000)
[    2.736655] This architecture does not have kernel memory protection.
[    2.855724] init: Console is alive
[    2.859203] init: - watchdog -
[    2.924338] scsi 2:0:0:0: Direct-Access     Samsung  S2 Portable           PQ: 0 ANSI: 2 CCS
[    3.111498] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.151660] sd 2:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[    3.159777] sd 2:0:0:0: [sda] Write Protect is off
[    3.164597] sd 2:0:0:0: [sda] Mode Sense: 28 00 00 00
[    3.165152] sd 2:0:0:0: [sda] No Caching mode page found
[    3.170490] sd 2:0:0:0: [sda] Assuming drive cache: write through
[    3.179038]  sda: sda1
[    3.183653] sd 2:0:0:0: [sda] Attached SCSI disk
[    3.188738] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    3.195221] ohci-platform: OHCI generic platform driver
[    3.200902] uhci_hcd: USB Universal Host Controller Interface driver
[    3.207556] ohci-pci: OHCI PCI platform driver
[    3.212156] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    3.228593] init: - preinit -
[    3.422394] mvneta f1070000.ethernet tmp0: renamed from eth0
[    3.462586] mvneta f1034000.ethernet eth0: renamed from eth1
[    3.512510] mvneta f1070000.ethernet eth1: renamed from tmp0
[    3.833291] mvneta f1034000.ethernet eth0: configuring for fixed link mode
[    3.840562] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    3.846607] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[    3.854578] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    5.909798] mount_root: loading kmods from internal overlay
[    5.921475] kmodloader: loading kernel modules from //etc/modules-boot.d/*
[    5.929503] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[    6.328768] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 806
[    6.357145] UBIFS (ubi0:1): recovery needed
[    6.403932] random: crng init done
[    6.431762] UBIFS (ubi0:1): recovery completed
[    6.436249] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    6.444117] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    6.454076] UBIFS (ubi0:1): FS size: 61329408 bytes (58 MiB, 483 LEBs), journal size 3047424 bytes (2 MiB, 24 LEBs)
[    6.464556] UBIFS (ubi0:1): reserved for root: 2896739 bytes (2828 KiB)
[    6.471198] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID DEE50754-EFFE-4990-A7A6-C97266C9BEF0, small LPT model
[    6.483473] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[    6.493882] block: extroot: not configured
[    6.531369] UBIFS (ubi0:1): un-mount UBI device 0
[    6.536097] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops
[    6.544028] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 809
[    6.591527] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    6.599392] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    6.609356] UBIFS (ubi0:1): FS size: 61329408 bytes (58 MiB, 483 LEBs), journal size 3047424 bytes (2 MiB, 24 LEBs)
[    6.619838] UBIFS (ubi0:1): reserved for root: 2896739 bytes (2828 KiB)
[    6.626483] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID DEE50754-EFFE-4990-A7A6-C97266C9BEF0, small LPT model
[    6.641627] mount_root: loading kmods from internal overlay
[    6.652909] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
[    6.670201] kmodloader: done loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
[    7.078279] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[    7.086484] block: extroot: not configured
[    7.132013] mount_root: switching to ubifs overlay
[    7.176201] ubi1: attaching mtd9
[    7.407547] ubi1: scanning is finished
[    7.415742] ubi1: attached mtd9 (name "syscfg", size 86 MiB)
[    7.421435] ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    7.428338] ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    7.435155] ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
[    7.442148] ubi1: good PEBs: 680, bad PEBs: 8, corrupted PEBs: 0
[    7.448177] ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
[    7.455430] ubi1: max/mean erase counter: 6/4, WL threshold: 4096, image sequence number: 1148089792
[    7.464603] ubi1: available PEBs: 0, total reserved PEBs: 680, PEBs reserved for bad PEB handling: 32
[    7.473869] ubi1: background thread "ubi_bgt1d" started, PID 824
[    7.485213] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 828
[    7.537764] UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "syscfg"
[    7.545202] UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    7.555161] UBIFS (ubi1:0): FS size: 80375808 bytes (76 MiB, 633 LEBs), journal size 4063232 bytes (3 MiB, 32 LEBs)
[    7.565642] UBIFS (ubi1:0): reserved for root: 3796347 bytes (3707 KiB)
[    7.572287] UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID A5EAB2F8-92D3-4D0B-A69A-9F6CA9A608B3, small LPT model
[    7.585463] urandom-seed: Seeding with /etc/urandom.seed
[    7.684142] procd: - early -
[    7.687055] procd: - watchdog -
[    8.315049] procd: - ubus -
[    8.371904] procd: - init -
[    8.546612] kmodloader: loading kernel modules from /etc/modules.d/*
[    8.557859] tun: Universal TUN/TAP device driver, 1.6
[    8.562965] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    8.571391] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[    8.580401] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    8.587876] cryptodev: driver 1.8 loaded.
[    8.592340] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
[    8.600387] Backport generated by backports.git backports-20160324-13-g24da7d3c
[    8.615059] <<Marvell 802.11ac Wireless Network Driver version 10.3.2.0-20170110>>
[    8.622702] pci 0000:00:01.0: enabling device (0140 -> 0142)
[    8.628443] ieee80211 phy0: priv->iobase0 = e0f80000
[    8.628454] ieee80211 phy0: priv->iobase1 = e1200000
[    8.628463] ieee80211 phy0: priv->pcmd_buf = ddf08000  priv->pphys_cmd_buf = 1df08000
[    8.636458] ieee80211 phy0: fw download start
[    8.699990] ieee80211 phy0: FwSize = 207660 downloaded Size = 207660 curr_iteration 65522
[   12.431324] ieee80211 phy0: fw download complete
[   12.431783] ieee80211 phy0: pcmd = ddf08000
[   12.449817] ieee80211 phy0: firmware version: 0x7080004
[   12.809338] ieee80211 phy0: firmware region code: 10
[   12.851995] ieee80211 phy0: 2G disabled, 5G enabled
[   12.856895] ieee80211 phy0: 4 TX antennas, 4 RX antennas
[   12.862298] pci 0000:00:02.0: enabling device (0140 -> 0142)
[   12.868032] ieee80211 phy1: priv->iobase0 = e1380000
[   12.868043] ieee80211 phy1: priv->iobase1 = e1600000
[   12.868052] ieee80211 phy1: priv->pcmd_buf = dddf0000  priv->pphys_cmd_buf = 1ddf0000
[   12.874418] ieee80211 phy1: fw download start
[   12.939175] ieee80211 phy1: FwSize = 207660 downloaded Size = 207660 curr_iteration 65527
[   14.327325] ieee80211 phy1: fw download complete
[   14.327812] ieee80211 phy1: pcmd = dddf0000
[   14.345344] ieee80211 phy1: firmware version: 0x7080004
[   14.706323] ieee80211 phy1: firmware region code: 10
[   14.750021] ieee80211 phy1: 2G enabled, 5G disabled
[   14.754934] ieee80211 phy1: 4 TX antennas, 4 RX antennas
[   14.762803] u32 classifier
[   14.765522]     input device check on
[   14.769196]     Actions configured
[   14.773037] Mirror/redirect action on
[   14.778285] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
[   14.790080] ip_tables: (C) 2000-2006 Netfilter Core Team
[   14.799009] mwifiex: rx work enabled, cpus 2
[   14.846998] usbcore: registered new interface driver ums-alauda
[   14.853672] usbcore: registered new interface driver ums-cypress
[   14.860218] usbcore: registered new interface driver ums-datafab
[   14.866723] usbcore: registered new interface driver ums-freecom
[   14.873187] usbcore: registered new interface driver ums-isd200
[   14.879542] usbcore: registered new interface driver ums-jumpshot
[   14.886112] usbcore: registered new interface driver ums-karma
[   14.892282] usbcore: registered new interface driver ums-sddr09
[   14.898499] usbcore: registered new interface driver ums-sddr55
[   14.904752] usbcore: registered new interface driver ums-usbat
[   14.917781] xt_time: kernel timezone is -0000
[   14.925132] PPP generic driver version 2.4.2
[   14.929843] NET: Registered protocol family 24
[   14.935112] kmodloader: done loading kernel modules from /etc/modules.d/*
[   15.469997] mwifiex_sdio mmc0:0001:1: info: FW download over, size 391772 bytes
[   15.831665] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[   15.864262] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x242 error, result=0x2
[   15.871261] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd 0x242 failed during       initialization
[   15.890625] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p5)
[   15.898674] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (15.68.7.p5)
[   16.052347] mvneta f1034000.ethernet eth0: configuring for fixed link mode
[   16.059309] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.065375] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   16.073372] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   16.081683] br-lan: port 1(eth0.1) entered blocking state
[   16.087106] br-lan: port 1(eth0.1) entered disabled state
[   16.092675] device eth0.1 entered promiscuous mode
[   16.097485] device eth0 entered promiscuous mode
[   16.103227] br-lan: port 1(eth0.1) entered blocking state
[   16.108650] br-lan: port 1(eth0.1) entered forwarding state
[   16.122758] mvneta f1070000.ethernet eth1: configuring for fixed link mode
[   16.130044] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   16.136169] mvneta f1070000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[   16.144170] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   16.342477] pppoe-wan: renamed from ppp0
[   16.900336] ieee80211 phy1: change: 0xffffffff
[   17.006509] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[   17.137396] ieee80211 phy0: change: 0xffffffff
[   17.271596] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   17.277594] br-lan: port 2(wlan1) entered blocking state
[   17.282955] br-lan: port 2(wlan1) entered disabled state
[   17.288408] device wlan1 entered promiscuous mode
[   17.293166] br-lan: port 2(wlan1) entered blocking state
[   17.298502] br-lan: port 2(wlan1) entered forwarding state
[   17.304255] br-lan: port 2(wlan1) entered disabled state
[   17.309734] br-lan: port 3(wlan0) entered blocking state
[   17.315091] br-lan: port 3(wlan0) entered disabled state
[   17.320543] device wlan0 entered promiscuous mode
[   17.327109] ieee80211 phy0: change: 0x100
[   17.344423] ieee80211 phy0: change: 0x40
[   17.380440] ieee80211 phy1: change: 0x100
[   17.392530] ieee80211 phy1: change: 0x42
[   17.593821] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[   17.600257] br-lan: port 2(wlan1) entered blocking state
[   17.605603] br-lan: port 2(wlan1) entered forwarding state
[   17.611269] ieee80211 phy0: change: 0x40
[   17.671185] ieee80211 phy1: change: 0x20
[   17.861365] ieee80211 phy0: change: 0x40
[   17.993370] ieee80211 phy0: change: 0x100
[   18.060535] ieee80211 phy0: change: 0x100
[   18.073629] ieee80211 phy0: change: 0x42
[   18.341340] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   18.347812] br-lan: port 3(wlan0) entered blocking state
[   18.353170] br-lan: port 3(wlan0) entered forwarding state
 root@LEDE:~# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 04e8:1f05 Samsung Electronics Co., Ltd S2 Portable [JMicron] (500GB)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

After i remove the cable and hotplug i get this additional lines in DMESG:

 #
[  527.103849] usb 3-1: new SuperSpeed USB device number 2 using xhci-hcd
[  527.134880] usb-storage 3-1:1.0: USB Mass Storage device detected
[  527.141155] scsi host3: usb-storage 3-1:1.0
[  528.154087] scsi 3:0:0:0: Direct-Access     Seagate  Expansion        1805 PQ: 0 ANSI: 6
[  529.455313] sd 3:0:0:0: [sdb] 1953525167 512-byte logical blocks: (1.00 TB/932 GiB)
[  529.463210] sd 3:0:0:0: [sdb] Write Protect is off
[  529.468032] sd 3:0:0:0: [sdb] Mode Sense: 33 00 00 08
[  529.473381] sd 3:0:0:0: [sdb] No Caching mode page found
[  529.478724] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[  529.499962]  sdb: sdb1 sdb2
[  529.503903] sd 3:0:0:0: [sdb] Attached SCSI disk
[  612.132851] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts:
root@LEDE:~# lsusb
Bus 003 Device 002: ID 0bc2:231b Seagate RSS LLC
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 04e8:1f05 Samsung Electronics Co., Ltd S2 Portable [JMicron] (500GB)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 


17.04.2017714Base systemBug ReportVery LowHighARP/Broadcast does not reach other clients in the same ...AllUnconfirmed Task Description

I have the default bridge with ethernet and WLAN in it. When i try to send data from a client to another, both connected to the same WLAN SSID, it doesn’t work (Destination unreachable).
Wireshark shows that it sends endless ARP requests to Broadcast, but the other clients in that WLAN never get it (and therefore can’t answer). The broadcast gets still delivery to every client connected through Ethernet. If i create a second WLAN SSID (even on the same adapter) and and add it to the bridge, it gets also all broadcast packets from the other WLAN...
So if i put the 2 clients in different WLAN SSIDs or ethernet they get the broadcast from each other, but not when both are connected to the same.

The isolate option is not set in the wireless config.
Archer C5 v1 with latest LEDE snapshot (no difference to 17.01 stable or rc).

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

13.04.2017710Base systemBug ReportVery LowLowFirewall gives warning msgs when kmod-ipt-nat6 is insta...lede-17.01Unconfirmed Task Description

After I installed kmod-ipt-nat6, firewall gives me these messages on every restart:

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

It looks like fw3 is trying to do something with IPv6 NAT and failing. Maybe it should not do it
as NAT6 is just for special cases. I’m using in order to be able to connect to openvpn on the router
from a lan client.

12.04.2017706Base systemBug ReportVery LowLowminor: iw / wrong output on weak stations for "inactive...TrunkUnconfirmed Task Description

seen with r3900 on a weak longshot with Ubiquiti Bullet M5.
after some time, “inactive time:” is sane again.

root@box:~ iw dev wlan0 station dump
Station ca:00:36:00:01:08 (on wlan0)
	inactive time:	4294964856 ms
	rx bytes:	12688
	rx packets:	132
	tx bytes:	0
	tx packets:	0
	tx retries:	0
	tx failed:	0
	rx drop misc:	0
	signal:  	-90 [-90] dBm
	signal avg:	-90 [-90] dBm
	tx bitrate:	6.0 MBit/s
	authorized:	yes
	authenticated:	yes
	associated:	yes
	preamble:	long
	WMM/WME:	yes
	MFP:		no
	TDLS peer:	no
	DTIM period:	0
	beacon interval:50
	short slot time:yes
	connected time:	249 seconds
Station 00:27:22:ca:09:f0 (on wlan0)
	inactive time:	4294964856 ms
	rx bytes:	109844
	rx packets:	394
	tx bytes:	0
	tx packets:	0
	tx retries:	0
	tx failed:	0
	rx drop misc:	0
	signal:  	-90 [-90] dBm
	signal avg:	-88 [-88] dBm
	tx bitrate:	6.0 MBit/s
	authorized:	yes
	authenticated:	yes
	associated:	yes
	preamble:	long
	WMM/WME:	yes
	MFP:		no
	TDLS peer:	no
	DTIM period:	0
	beacon interval:50
	short slot time:yes
	connected time:	248 seconds

root@box:~ uci show wireless
wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.country='US'
wireless.radio0.channel='40'
wireless.radio0.path='pci0000:00/0000:00:00.0'
wireless.radio0.hwmode='11na'
wireless.radio0.ht_capab='SHORT-GI-40' 'TX-STBC' 'RX-STBC1' 'DSSS_CCK-40'
wireless.radio0.htmode='HT20'
wireless.radio0.chanbw='20'
wireless.radio0.txpower='20'
wireless.radio0.beacon_int='50'
wireless.@wifi-iface[0]=wifi-iface
wireless.@wifi-iface[0].device='radio0'
wireless.@wifi-iface[0].network='wlan'
wireless.@wifi-iface[0].mode='adhoc'
wireless.@wifi-iface[0].bssid='02:ca:ff:ee:00:40'
wireless.@wifi-iface[0].macaddr='dc:9f:db:0c:c9:4a'
wireless.@wifi-iface[0].ssid='ffintern.5GHz'
10.04.2017698Base systemBug ReportVery LowCriticalNexx WT3020F wifi packet loss problemlede-17.01Unconfirmed Task Description

I have two this devices. I try to figure out which is the ideal firmware for it so I tested it with a few. I tested it with OpenWRT 15.05.1, LEDE 17.01.0 and Gargoyle 1.9.1/1.9.2. But I found a common issue. The device lose packets via wifi. Tested with several clients/devices. No matter what configuration I use. No problem on LAN but on wifi it lose a bunch of packets. Maybe it’s a driver issue? Would be good to figure out.

i.imgur.comqpycapq.jpg

I also noticed that the latency is unstable on wifi. I guess it’s also a related with this issue. Should I open another ticket for it?

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

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

Device: Dlink Dir-300 b7 with latest LEDE 17.01

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

06.04.2017682Base systemBug ReportVery LowLowWNR2000v3 bootloop after installing 17.01.0lede-17.01Unconfirmed Task Description

My Netgear WNR2000v3 goes into a bootloop after installing 17.01.0 but is fine with the Trunk snapshot from 6 April 2017.
When it starts up, it gives me 4 pings, then it stops responding until it wakes back up. When it stops responding,m the network interface acts like it is disconnected (no link), then it comes back up just before it responds to pings again.
I had time tonight to plug a serial console into it and record what it does when you install 17.01.0
These were installed with TFTP from the recovery (hold reset for ~30 seconds when powering up, then tftp the image to 192.168.1.1)
Attached are two bootlogs:

  1. Bootlog of the upgrade to 17.01 from recovery mode using the lede-17.01.0-r3205-59508e3-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img image (goes into a bootloop after the install): WNR2000V3To17.01UpgradeBootlog.txt
  2. Bootlog of the upgrade to the 6 April 2017 nightly (r3922-9613d97) using the lede-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img image (works as expected): WNR2000V3To6April17SnapshotUpgradeBootlog.txt

I saw the same thing installing lede-17.01.0-r3205-59508e3-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img from the factory web interface (Netgear wnr2000v3-V1.1.2.14) but I didnt save a bootlog of that

Let me know if more info is needed.

Aaron Z


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

Device: Netgear WNR2000v3

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

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

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

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

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

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

01.04.2017669Base systemFeature RequestVery LowLowCPE510: missing link details (via ethtool)lede-17.01Unconfirmed Task Description

I am using LEDE on a TP-Link CPE510 device.

The device contains one ethernet port (eth0) connected to two physical ports (eth0.1 and eth0.2).

I fail to retrieve ethernet status information (e.g. the currently negotiated link speed):

root@lede:/etc/opkg# ethtool eth0
Settings for eth0:
Cannot get device settings: No such device
        Current message level: 0x000000ff (255)
                               drv probe link timer ifdown ifup rx_err tx_err
        Link detected: yes

Thus it is not possible to detect the link speed. In my case this causes a problem with OLSRD2, since the negotiated link speed is required for the calculation of a proper routing metric.

Kernel initialization:

root@lede:/etc/opkg# dmesg |grep eth
[    1.298265] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[    3.319380] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.915811] eth0: link up (1000Mbps/Full duplex)
[    4.920540] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.729961] eth0: link down
[   15.741434] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   15.751276] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready
[   15.795536] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready
[   17.335865] eth0: link up (1000Mbps/Full duplex)
[   17.340597] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   17.388337] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
[   17.395183] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
[   51.404881] eth0: link down
[   56.905812] eth0: link up (1000Mbps/Full duplex)

Driver information:

root@lede:/etc/opkg# ethtool -i eth0
driver: ag71xx
version: 0.5.35
firmware-version: 
expansion-rom-version: 
bus-info: ag71xx.1
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

Do you have any hints, how I can investigate, why the detailed interface information is missing?

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

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

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

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


29.03.2017665Base systemBug ReportVery LowCriticalLede 17.01.0-r3205-59508e3 on Nucom 5010UN v2 acting as...lede-17.01Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: Nucom 5010UN v2 (brcm63xx)
- Software versions of LEDE release, packages, etc.: Just download and install latest Lede build (lede-17.01.0-r3205-59508e3) for Nucom 5010UN v2 from https://downloads.lede-project.org/releases/17.01.0/targets/brcm63xx/generic/lede-17.01.0-r3205-59508e3-brcm63xx-generic-R5010UNv2-squashfs-cfe.bin - Steps to reproduce: Configure Nucom 5010UN v2 as Wireless Routed Client
- Bug: After one hour or two, the Wireless Routed Clients looses connection with the Router it is connected to. It means, connecting by ssh or Luci website on Wireless Routed Client and running “ping 192.168.1.1” where 192.168.1.1 is the router it is connected to returns 100% of packets loss, also, “ping google.com” doesn’t work. But logging into Luci website and navigating to Network → WiFi, in Wireless Overview it shows as the Wireless Client Routed router is connected to the main one but there’s no working connection between them, at least pings are not working on both sides. Restarting the router seems to fix the issue but after one or two hours of uptime, the issue arises again.

Note, the bug was first introduced on OpenWrt Chaos Calmer 15.05 as OpenWrt Barrier Breaker does not suffer from this bug.

The following is as more complete explanation:

Hi,

i’ve just installed latest Lede-Project build, version 17.01.0-r3205-59508e3, on a Nucom 5010UN V2 router and everything seemed to work fine until i noticed that it keeps loosing Internet/network connection. The router is configured as Wireless Routed Client and the firmware was downloaded from https://downloads.lede-project.org/releases/17.01.0/targets/brcm63xx/generic/lede-17.01.0-r3205-59508e3-brcm63xx-generic-R5010UNv2-squashfs-cfe.bin

Also note, i think it’s a common bug inherited from OpenWrt as i suffered the same exact bug on an ADB P.DG A4001N1 router running latest build of OpenWrt, Chaos Calmer 15.05 and also 15.05.1. Also note that after posting on OpenWrt forums more users complained about the same bug.

Also, i want to state that in OpenWrt, the issue can be workarounded by downgrading to Barrier Breaker 14.07 which means the bug was introduced on the next build or next commits.

Anyway, my current setup is on Nucom 5010UN v2 is Wireless Routed Client [https://wiki.openwrt.org/doc/howto/clientmode#routed] + Static Route [https://wiki.openwrt.org/doc/recipes/routedclient#usingrouting] so clients on Nucom (Client Router) can “see” hosts on ADSL router (acting as AP).

I performed a clean install by resetting my custom configuration and the update went fine, but after reconfiguring the router as Wireless Routed Client it always happens that after being operating as Wifi Routed Client for about 2 hours suddenly it loses Internet connection/connection to AP. I say Internet connection because running a ping to google.com from ssh within inside the router doesn’t work but if i check through LUCI Network→Wifi it shows the router Wifi is still connected to the main ADSL router.

Here’s [https://forum.openwrt.org/viewtopic.php?pid=355180#p355180] a post on OpwnWrt site where i exposed the same issue for an ADB P.DG A4001N1 router and some other users replied complaining about the same issue.

These are the files modified by me through LUCI when configuring the routed as Wireless Routed Client, as i’ve been entirely configuring the router through LUCI except for the Static Route [https://wiki.openwrt.org/doc/recipes/routedclient#usingrouting] where i followed the indications on the link:
ddns
dhcp
dropbear
firewall
fstab
luci
network
rpcd
system
ucitrack
uh_t_tpd (I had to add underscores because of the buggy URL detection of the forum)
wireless

This is dhcp and dnmasq config:
cat etc config dhcp
config dnsmasq

      option domainneeded '1'
      option boguspriv '1'
      option localise_queries '1'
      option rebind_protection '1'
      option rebind_localhost '1'
      option local '/lan/'
      option domain 'lan'
      option expandhosts '1'
      option readethers '1'
      option leasefile '/tmp/dhcp.leases'
      option resolvfile '/tmp/resolv.conf.auto'
      option localservice '1'

config dhcp ‘lan’

      option interface 'lan'
      option dhcpv6 'server'
      option ra 'server'
      option ra_management '1'
      option start '100'
      option limit '150'
      option leasetime '12h'

config dhcp ‘wan’

      option interface 'wan'
      option ignore '1'

config odhcpd ‘odhcpd’

      option maindhcp '0'
      option leasefile '/tmp/hosts/odhcpd'
      option leasetrigger '/usr/sbin/odhcpd-update'

config host

      option name 'Host1'
      option mac 'XX:XX:XX:XX:XX:XY'
      option ip '192.168.2.2'

config host

      option name 'Host2'
      option mac 'XX:XX:XX:XX:XX:XZ'
      option ip '192.168.2.3'

config host

      option name 'ClientRouter'
      option mac 'XX:XX:XX:XX:XX:XX'
      option ip '192.168.2.92'

This is network:
cat etc config network
config interface ‘loopback’

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

config globals ‘globals’

      option ula_prefix 'fd05:6cbe:d307::/48'

config interface ‘lan’

      option force_link '1'
      option type 'bridge'
      option proto 'static'
      option netmask '255.255.255.0'
      option ip6assign '60'
      option _orig_ifname 'eth0.1'
      option _orig_bridge 'true'
      option ipaddr '192.168.2.1'
      option dns '8.8.8.8'
      option ifname 'eth0.1'

config switch

      option name 'eth0'
      option reset '1'
      option enable_vlan '1'

config switch_vlan

      option device 'eth0'
      option vlan '1'
      option ports '0 1 2 3 8t'

config interface ‘wwan’

      option proto 'dhcp'

This is wireless:
cat etc config wireless
config wifi-device ‘radio0’

      option type 'mac80211'
      option hwmode '11g'
      option path 'pci0000:00/0000:00:00.0/0000:01:00.0/bcma0:1'
      option disabled '0'
      option channel '13'
      option txpower '20'
      option country 'ES'

config wifi-device ‘radio1’

      option type 'mac80211'
      option path 'platform/ehci-platform/usb1/1-1/1-1:1.0'
      option txpower '20'
      option country 'ES'
      option hwmode '11a'
      option channel 'auto'

config wifi-iface

      option ssid 'MainADSLSSID'
      option device 'radio0'
      option mode 'sta'
      option bssid 'XX:XX:XX:XX:XX:YY'
      option key 'WiFiPassword'
      option encryption 'psk-mixed'
      option network 'wwan lan'
 


28.03.2017661Base systemBug ReportVery LowHighUSB hostless modem is not detected during boot - HooToo...lede-17.01Unconfirmed Task Description

After flashing my HooToo HT-TM02 with LEDE 17.01 I noticed that my hostless modem
ZTE MF823 is not detected when attached during boot. lsusb or cat /sys/kernel/debug/usb/devices
just shows nothing. Also dmesg is logging nothing regarding the device during boot.
If the modem is hotplugged, everything works fine. Same behaviour in OpenWRT Chaos Chalmer.

Tried unloading and reloading all usb related modules with no success. No detection at all.
Only unplugging and replugging helps. If the modem is detected after replugging, a
router reboot will detect it properly. A reboot without a forced detection via replugging leads to
no detection. Powering the router down, also results in no detection after rebooting.

If attached to a “non powered” USB-Hub it gets detected during boot, so no power issue here.

And the modem works perfekt after boot on a WD MyNet 600 with LEDE 17.01. So i think it’s a
platform related issue handling the usb modules.

Hope there is enough info for someone to find the bug.

THX.

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

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

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

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

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

Using LEDE Reboot 17.01.0 r3205-59508e3 on Lenovo Y1.
After setting the Inactivity timeout to something not 0 in luci (option demand ‘5’ in the config file),the dial procedure will be stopping at some stage,can’t establish a connect.
And the log will be like this:

May  7 08:48:52 OpenWrt daemon.info pppd[9714]: Plugin rp-pppoe.so loaded.
May  7 08:48:52 OpenWrt daemon.info pppd[9714]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.5
May  7 08:48:52 OpenWrt daemon.notice pppd[9714]: pppd 2.4.5 started by root, uid 0
May  7 08:48:52 OpenWrt daemon.info pppd[9714]: Using interface pppoe-wan
May  7 08:48:52 OpenWrt daemon.notice pppd[9714]: local  IP address 10.64.64.64
May  7 08:48:52 OpenWrt daemon.notice pppd[9714]: remote IP address 10.112.112.112

Without the demand option everything works fine:

May  7 09:08:43 OpenWrt daemon.info pppd[2712]: Plugin rp-pppoe.so loaded.
May  7 09:08:43 OpenWrt daemon.info pppd[2712]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.5
May  7 09:08:43 OpenWrt daemon.notice pppd[2712]: pppd 2.4.5 started by root, uid 0
May  7 09:08:48 OpenWrt daemon.info pppd[2712]: PPP session is 9873
May  7 09:08:48 OpenWrt daemon.warn pppd[2712]: Connected to 00:30:88:1f:30:07 via interface eth2
May  7 09:08:48 OpenWrt daemon.info pppd[2712]: Using interface pppoe-wan
May  7 09:08:48 OpenWrt daemon.notice pppd[2712]: Connect: pppoe-wan <--> eth2
May  7 09:08:48 OpenWrt daemon.notice pppd[2712]: PAP authentication succeeded
May  7 09:08:48 OpenWrt daemon.notice pppd[2712]: peer from calling number 00:30:88:1F:30:07 authorized
May  7 09:08:49 OpenWrt daemon.notice pppd[2712]: local  IP address 93.232.124.118
May  7 09:08:49 OpenWrt daemon.notice pppd[2712]: remote IP address 217.0.119.51
May  7 09:08:49 OpenWrt daemon.notice pppd[2712]: primary   DNS address 217.0.43.17
May  7 09:08:49 OpenWrt daemon.notice pppd[2712]: secondary DNS address 217.0.43.49

(these logs is copy from the openwrt bug ticketExternal Link because my log for this part had be override by massive “ieee80211 phy1: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2”,sincere apology,smile)
It seems to be a historied legacy bug from Openwrt BB (or AA),and there is a solution by changing 2 files to make pppd disconnect when inactivity but can’t re-dial:
1./etc/config/network, disable IPv6

config interface 'wan'
        option ipv6 0

2./lib/netifd/proto/ppp.sh: change nodefaultroute to defaultroute in the function of ppp_generic_setup()

	proto_run_command "$config" /usr/sbin/pppd \
		nodetach ipparam "$config" \
		ifname "$pppname" \
		${keepalive:+lcp-echo-interval $interval lcp-echo-failure ${keepalive%%[, ]*}} \
		${ipv6:++ipv6} \
		defaultroute \

Hope this stinking bug can be terminated in LEDE

21.03.2017649Base systemBug ReportVery LowLowWDS not working on ath9k-htc TrunkUnconfirmed Task Description

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

 

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

Here is a hostapd log on the WDS AP:

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

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

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

19.03.2017643PackagesBug ReportVery LowLowiwinfo scan reports "Scanning not possible" using mt76 ...lede-17.01Unconfirmed Task Description

I’m unable to consistently scan for access points using iwinfo.
I’m running a MT7688 chip with the mt76 mac80211 driver on LED 17.01

The scan works very intermittently, but mostly returns “Scanning not possible”.

My wireless config looks like:

config wifi-device 'radio0'
	option type 'mac80211'
	option channel '11'
	option hwmode '11g'
	option path 'platform/10300000.wmac'
	option htmode 'HT20'
	option disabled '0'

I’ve added some debugging code to iwinfo_nl80211.c to try and see where it’s failing. To run a scan I use the command:

iwinfo radio0 scan

iwinfo creates a temporary interface (tmp.radio0) and then calls nl80211_get_scanlist_nl, this returns a zero length iwinfo_scanlist_entry which causes “Scanning not possible” to be returned.
I’m happy to do some more debugging if I can be pointed in the right direction.

 


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

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

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

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

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

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

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

Hello,

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

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

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

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

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

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

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

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

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

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


CHAOS CALMER (15.05.1, r48532)


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

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

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

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

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

Cheers,
Vittorio

14.03.2017629Base systemBug ReportVery LowLowRealtek r8169 kernel errorlede-17.01Unconfirmed Task Description

My device is a homebuild router:
- MB: Gigabyte GA-970A-UD3P
- CPU: Unlocked AMD x3 405e
- Ram: 4 GB A-Data
- MB NIC: Realtek
- NIC: Intel PRO/1000

Installed the official Lede 17.01.0 x86/x64 ext4 build
Haven’t installed any other packages

I have configured the network as follows:
attached network file
where eth4 is the Realtek NIC

The result is in error.txt

13.03.2017625PackagesBug ReportVery LowMediumno default route written using proto=wwanlede-17.01Unconfirmed Task Description

LEDE_RELEASE=”LEDE Reboot 17.01-SNAPSHOT r6469+17-c114383”

Configure steps as follows:

Run ubus listen in backround
ubus -t 9999 listen &

uci del network.wwan
uci set network.wwan=interface
uci set network.wwan.proto=wwan
uci set network.wwan.defaultroute=’0’ uci set network.wwan.pincode= uci set network.wwan.apn= uci commit && /etc/init.d/network restart
...
{ “ubus.object.add”: {”id”:107055350,”path”:”network.interface.wwan_4”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wwan_4”} }
...

As you see default route should not be written immediately. You see default route in inactive section in ubus. So now lets set the default route for this interface

uci set network.wwan.defaultroute=’1’ uci commit && /etc/init.d/network reload

You see no ubus message as well no change of default route. Now lets use QMI proto directly

uci del network.wwan
uci set network.wwan=interface
uci set network.wwan.proto=qmi
uci set network.wwan.device=/dev/cdc-wdm0
uci set network.wwan.defaultroute=’0’ uci set network.wwan.pincode= uci set network.wwan.apn= uci commit && /etc/init.d/network restart
...
{ “ubus.object.add”: {”id”:107055350,”path”:”network.interface.wwan_4”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wwan_4”} }
...

So now lets set the default route for this interface and you see ubus messages comming up as well default route is set

uci set network.wwan.defaultroute=’1’ uci commit && /etc/init.d/network reload
{ “network.interface”: {”action”:”ifdown”,”interface”:”wwan”} }
{ “network.interface”: {”action”:”ifdown”,”interface”:”wwan_4”} }
root@RED50:/lib# { “ubus.object.remove”: {”id”:399408035,”path”:”network.interface.wwan_4”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wan2”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wwan”} }
{ “ubus.object.add”: {”id”:828745890,”path”:”network.interface.wwan_4”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wwan_4”} }


13.03.2017624PackagesBug ReportVery LowLowWrong default WAN interface on SQM & BCP38 packageslede-17.01Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: Archer C7v2
- Software versions of LEDE release, packages, etc.: 17.01 final
- Steps to reproduce: just install default packages

By default, SQM and BCP38 packages configure rules on eth1, but on C7 this is LAN interface and not WAN. Both must be changed to apply default configuration to eth0.
This behaviour cames from OpenWRT.

 


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

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

Netboot

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

Normal boot

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

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

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

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

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


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

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

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

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

Thanks in advance for any help.

 


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

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

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

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

07.03.2017605Base systemBug ReportVery LowLowLuCI wireless associated stations doesn't show noise db...TrunkUnconfirmed Task Description

With an Archer C7 v2 the list shows up the noise level in the associated stations doesn’t show up, instead it shows 0dBm and the bar icon shows empty bars. The noise level is display correctly inside the wifi configuration under the device options.

This only happens at least with the channel 112, I have tried all the channels below from 36-104 (44 and 108 jumps to 48 and 112 respectively because other nearly stations).

Can’t try the 4 channels above because radars and the next 4 above because in my country doesn’t exist channel 144.

I will try to test with less width than 80 MHz.

I set it to low because it seems that it only affect to the associated stations tables visualization and the wifi network works as it should.

06.03.2017600Base systemBug ReportVery LowLowRandom disconnection on 17.01TrunkUnconfirmed Task Description

Problem:

I upgrade my router from some years old dd-wrt to LEDE. “It works” and both the throughput and latency are vastly superior. However, it disconnect every couple hours for 2 minutes. Both my phone and my thinkpad are affected, so it is not a suddent regression in the client side. The old firmware showed no such interruption and could run a single connection TCP for months. At first, all packets stop being received and all sent timeout. After a while NetworkManager drop the (dead) Wifi conenction. Restarting networkmanager doesn’t restore the connection, only time does. The encryption and channel are the same as before.

Info:

Hostname	LEDE
Model	D-Link DIR-615 rev. I1
Firmware Version	LEDE Reboot 17.01.0 r3205-59508e3 / LuCI lede-17.01 branch (git-17.051.53299-a100738)
Kernel Version	4.4.50

SSHed into the rounter show nothing interesting in dmesg or the logs.

dmesg (client side)

[1750975.095083] wlp3s0: authenticate with c8:d3:a3:57:c1:0d
[1750975.097291] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 1/3)
[1750975.182387] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 2/3)
[1750975.340969] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 3/3)
[1750975.433683] wlp3s0: authentication with c8:d3:a3:57:c1:0d timed out
[1750986.745947] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1750986.783926] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1750986.784247] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1750986.973972] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1750986.974238] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1750986.988274] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1751024.037294] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1751024.037564] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1751024.232261] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1751024.232531] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1751024.246198] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1751035.933932] wlp3s0: authenticate with c8:d3:a3:57:c1:0d
[1751035.936358] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 1/3)
[1751035.941892] wlp3s0: authenticated
[1751035.942083] wlp3s0: associate with c8:d3:a3:57:c1:0d (try 1/3)
[1751035.946355] wlp3s0: RX AssocResp from c8:d3:a3:57:c1:0d (capab=0x431 status=0 aid=1)
[1751035.947757] wlp3s0: associated
[1751035.947784] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[1753524.568775] iwlwifi 0000:03:00.0: invalid BA notification: Q 16, tid 0, flow 65535
[1754028.350307] wlp3s0: deauthenticating from c8:d3:a3:57:c1:0d by local choice (Reason: 3=DEAUTH_LEAVING)
[1754029.418400] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[1754029.423879] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754029.435347] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754029.435766] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754029.643875] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754029.644146] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754029.658379] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754029.708225] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754033.134519] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754033.134793] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754033.338532] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754033.338803] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754033.352845] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754058.434794] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754058.447119] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754058.447392] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754058.645058] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754058.645328] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754058.659098] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754062.836641] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754062.836915] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754063.041653] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754063.041914] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754063.055581] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754063.070786] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754066.513509] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754066.513776] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754066.712341] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754066.712663] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754066.727003] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754082.615329] wlp3s0: authenticate with c8:d3:a3:57:c1:0d
[1754082.617891] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 1/3)
[1754082.711318] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 2/3)
[1754082.800197] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 3/3)
[1754082.890379] wlp3s0: authentication with c8:d3:a3:57:c1:0d timed out
[1754092.431334] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754092.442752] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754092.443037] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754092.642763] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754092.643027] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754092.657436] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754096.103393] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754096.103667] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754096.305383] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754096.305650] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[1754096.320213] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[1754099.851495] wlp3s0: authenticate with c8:d3:a3:57:c1:0d
[1754099.853971] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 1/3)
[1754100.000973] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 2/3)
[1754100.100010] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 3/3)
[1754100.234954] wlp3s0: authentication with c8:d3:a3:57:c1:0d timed out
[1754104.050494] wlp3s0: authenticate with c8:d3:a3:57:c1:0d
[1754104.052754] wlp3s0: send auth to c8:d3:a3:57:c1:0d (try 1/3)
[1754104.126844] wlp3s0: authenticated
[1754104.127569] wlp3s0: associate with c8:d3:a3:57:c1:0d (try 1/3)
[1754104.135916] wlp3s0: RX AssocResp from c8:d3:a3:57:c1:0d (capab=0x431 status=0 aid=1)
[1754104.138461] wlp3s0: associated
[1754104.138810] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready

What should I do to further debug this? I can build new images if necessary.

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

Vlan don’t work.


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

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

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

(example for 2 prefixes)

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

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

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

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

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

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

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

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

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

Software versions of LEDE release: lede 17 branch

Steps to reproduce:

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

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

We supply a command like:

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

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

If we create manually the dir with:

mkdir ./bin/targets/ar71xx/generic

The image building procedure completes successfully.

Is this desired behaviour or not?

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

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

Netgear R7800 running lede-17.01.

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

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

To reproduce:

Run the “client” on the R7800 using:

client 232.0.1.1 4545 100

Run the “server” on another system using:

server 232.0.1.1 4545 100 1000

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

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

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

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

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

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

log with driver included in release

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

log with alernative ath10k-ct from packages

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


28.02.2017568Base systemBug ReportVery LowVery LowFirst boot messages are not logged to filelede-17.01Unconfirmed Task Description

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

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

while the first message in the log file reads

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

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

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

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

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

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

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

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

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

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

This script does the activation:

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

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

The results (1 line = 1 second):

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

cake 

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


-----> fq_codel 

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

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

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

On WNDR3700v2:

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

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

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

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

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

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

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

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

 


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

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

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

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

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

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

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

 


21.02.2017543KernelBug ReportVery LowLowLED trigger netdev on a bridge is not interface sensiti...lede-17.01Unconfirmed Task Description

I have a bridge “br-wan” with “eth1” and “eth0.2” interfaces.

In Chaos I could set the led trigger to either of these interfaces separately. I could display either of the interfaces separately.

In 17.01 no matter what I choose “br-wan”, “eth0.2”, or “eth1” the led shows the full traffic through the bridge.

If this is made on purpose, could you point me to the code change please.

Showing tasks 701 - 750 of 811 Page 15 of 17<<First - 13 - 14 - 15 - 16 - 17 -

Available keyboard shortcuts

Tasklist

Task Details

Task Editing