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 In  descStatus
29.09.20192523KernelBug ReportVery LowHighRB750 randomly reboots after kernel warningsopenwrt-19.07Unconfirmed Task Description

Mikrotik RB750Gr3
LuCI openwrt-19.07 branch (git-19.267.59428-7b36dae) / OpenWrt 19.07-SNAPSHOT r10532-cf3b50377e

Router randomly reboots (it may be stable for hours or can reboot in a minute after power up). Seems like kernel problem.

Here are some logs I managed to fetch before the reboots:

Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.010562] ------------[ cut here ]------------
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.015202] WARNING: CPU: 2 PID: 0 at net/ipv4/tcp_output.c:2509 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.022158] invalid inflight: 1 state 1 cwnd 10 mss 1388
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.027441] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cdc_ncm cdc_ether xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.097872]  nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt cdc_wdm cdc_acm fuse ledtrig_usbport gpio_beeper input_core xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ehci_platform
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.169233]  sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.180291] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.14.143 #0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.186357] Stack : 00000000 00000000 00000000 81230398 00000000 00000000 00000000 00000000
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.194691]         00000000 00000000 00000000 00000000 00000000 00000001 8fc0dd30 ac07f596
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.203026]         8fc0ddc8 00000000 00000000 00004ea0 00000038 8049db58 00000007 00000000
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.211359]         00000000 80550000 0002c043 00000000 8fc0dd10 00000000 80570000 8050c6a0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.219690]         803cc8bc 000009cd 812303d8 81230398 00000000 802af9e8 00000008 805b0008
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.228022]         ...
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.230459] Call Trace:
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.230475] [<8049db58>] 0x8049db58
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.236372] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.239840] [<802af9e8>] 0x802af9e8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.243312] [<800101a0>] 0x800101a0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.246782] [<800101a8>] 0x800101a8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.250250] [<80486a9c>] 0x80486a9c
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.253722] [<800758a0>] 0x800758a0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.257243] [<80032588>] 0x80032588
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.260714] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.264185] [<80032610>] 0x80032610
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.267654] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.271126] [<803cf3d0>] 0x803cf3d0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.274596] [<8009d750>] 0x8009d750
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.278064] [<803cf7a8>] 0x803cf7a8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.281537] [<8009dd80>] 0x8009dd80
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.285007] [<803cf770>] 0x803cf770
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.288474] [<8008c2cc>] 0x8008c2cc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.291945] [<8008c588>] 0x8008c588
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.295413] [<8007cee8>] 0x8007cee8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.298883] [<804a49b8>] 0x804a49b8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.302357] [<80036f14>] 0x80036f14
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.305827] [<8025d440>] 0x8025d440
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.309296] [<8000b488>] 0x8000b488
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.312764]
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.314310] ---[ end trace a36c893f27b6a6f3 ]---
Sun Sep 29 18:56:25 2019 kern.alert kernel: [ 2442.525228] CPU 1 Unable to handle kernel paging request at virtual address 00000010, epc == 803be4a0, ra == 803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.535821] Oops[#1]:
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.538087] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G        W       4.14.143 #0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.545363] task: 8fc3be80 task.stack: 8fc5c000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.549869] $ 0   : 00000000 00000001 0000004a 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.555080] $ 4   : 8ea76f3c 00000001 0000d706 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.560290] $ 8   : 00034501 00000321 811d7440 00000322
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.565501] $12   : 8ea22180 8ea22180 8e9a8e00 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.570712] $16   : 8ea76e40 00001204 6375f4c6 ffffffff
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.575923] $20   : 00001204 00000001 00000000 00000002
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.581133] $24   : 00000000 8034b220
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.586344] $28   : 8fc5c000 8fc0bbb8 00000000 803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.591555] Hi    : 0000caa1
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.594419] Lo    : 47aec5c8
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.597285] epc   : 803be4a0 0x803be4a0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.601098] ra    : 803c4104 0x803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.604912] Status: 11007c03      KERNEL EXL IE
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.609082] Cause : 40800008 (ExcCode 02)
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.613066] BadVA : 00000010
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.615931] PrId  : 0001992f (MIPS 1004Kc)
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.620003] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cdc_ncm cdc_ether xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.690391]  nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt cdc_wdm cdc_acm fuse ledtrig_usbport gpio_beeper input_core xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ehci_platform
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.761710]  sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.772740] Process swapper/1 (pid: 0, threadinfo=8fc5c000, task=8fc3be80, tls=00000000)
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.780788] Stack : 00000204 8034def4 8ea76e40 00000000 8ea76e40 8ea76e40 00001204 803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.789123]         8f346480 8056ba00 00000000 8015000a 00018bc3 8fc0bc74 00000004 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.797457]         80550000 8ea76f3c 00000002 00000001 91946e37 00000000 00000018 91946e37
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.805791]         00000000 91946e37 00000000 00000001 80570000 8050c458 00000000 00000002
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.814125]         00018bc3 00000018 8ee92564 8e9a0600 00000000 00000000 00000001 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.822457]         ...
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.824891] Call Trace:
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.824903] [<8034def4>] 0x8034def4
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.830852] [<803c4104>] 0x803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.834335] [<8015000a>] 0x8015000a
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.837825] [<803c4efc>] 0x803c4efc
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.841318] [<803c6f34>] 0x803c6f34
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.844788] [<803a98a0>] 0x803a98a0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.848313] [<803d1bc0>] 0x803d1bc0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.851802] [<803d2f18>] 0x803d2f18
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.855307] [<8e86426c>] 0x8e86426c [nf_conntrack_ipv4@8e864000+0x1420]
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.861893] [<803a9da0>] 0x803a9da0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.865406] [<803aa078>] 0x803aa078
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.868887] [<803a9940>] 0x803a9940
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.872360] [<803a9c10>] 0x803a9c10
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.402270] ------------[ cut here ]------------
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.406908] WARNING: CPU: 1 PID: 0 at net/ipv4/tcp_output.c:2509 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.413864] invalid inflight: 1 state 1 cwnd 10 mss 1388
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.419148] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cdc_ncm cdc_ether xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.489628]  nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt cdc_wdm cdc_acm fuse ledtrig_usbport gpio_beeper input_core xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ehci_platform
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.561103]  sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.572189] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.143 #0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.578264] Stack : 00000000 00000000 00000000 81222398 00000000 00000000 00000000 00000000
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.586600]         00000000 00000000 00000000 00000000 00000000 00000001 8fc0bd30 ac07f596
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.594938]         8fc0bdc8 00000000 00000000 00004f18 00000038 8049db58 00000007 00000000
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.603273]         00000000 80550000 0008bb1d 00000000 8fc0bd10 00000000 80570000 8050c6a0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.611605]         803cc8bc 000009cd 812223d8 81222398 00000000 802af9e8 00000004 805b0004
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.619937]         ...
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.622376] Call Trace:
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.622394] [<8049db58>] 0x8049db58
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.628288] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.631755] [<802af9e8>] 0x802af9e8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.635228] [<800101a0>] 0x800101a0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.638699] [<800101a8>] 0x800101a8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.642170] [<80486a9c>] 0x80486a9c
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.645638] [<800758a0>] 0x800758a0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.649107] [<80032588>] 0x80032588
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.652580] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.656052] [<80032610>] 0x80032610
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.659528] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.663008] [<803cf3d0>] 0x803cf3d0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.666478] [<8009d750>] 0x8009d750
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.669947] [<803cf7a8>] 0x803cf7a8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.673420] [<8009dd80>] 0x8009dd80
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.676890] [<803cf770>] 0x803cf770
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.680358] [<8008c2cc>] 0x8008c2cc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.683829] [<80063018>] 0x80063018
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.687300] [<8008c588>] 0x8008c588
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.690768] [<8007cee8>] 0x8007cee8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.694244] [<804a49b8>] 0x804a49b8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.697717] [<80036f14>] 0x80036f14
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.701185] [<8025d440>] 0x8025d440
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.704662] [<8000b488>] 0x8000b488
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.708131]
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.709665] ---[ end trace 0dde230055179878 ]---
12.10.20192546Base systemBug ReportVery LowMediumXiaomi Router Pro (R3P) WiFi Issuesopenwrt-19.07Unconfirmed Task Description

Supply the following if possible:

- Device problem occurs on
Xiaomi Router Pro (R3P)

- Software versions of OpenWrt/LEDE release, packages, etc.
OpenWrt SNAPSHOT r11131-e78c1baa9f / LuCI Master (git-19.271.67895-cf887ba)

- Steps to reproduce
Using connection by WiFi 2.4G and 5G

The most important functionality of wifi router still does not work properly.

Unfortunately, the wifi of this great wifi router does not work properly with OpenWRT. Unfortunately, the original ROM for this wifi connectivity is far better than when using OpenWRT.

The main problem is with the instability of the connection, constantly every 40 or 60 seconds, is totally lost and unfortunately do not log any files so we can analyze.

The connection simply drops, becomes a few seconds dead, and then comes back.

This problem is greatest with 2.4G connections that is no more than one or two minutes long.

There are several user comments on the forum: https://forum.openwrt.org/t/support-for-xiaomi-wifi-r3p-pro/20290

Are you working to solve this problem? Can I contribute something?

09.10.20192541KernelBug ReportMediumLowHardware offloading causes some flows to fail to be NAT...openwrt-19.07New Task Description

Just after a reboot, some flows are not NATed: packets from a machine in the LAN are sent to the WAN port with a private source IP address.

This is on a Linksys RE6500 (ramips mt7621) running openwrt 19.07-SNAPSHOT r10578-b3d70f628.
It is configured with flow_offloading and flow_offloading_hw.

Here is a tcpdump capture showing the problem on the WAN port (172.23.184.0/24 is my LAN address space):

root@openwrt:~# tcpdump -n -i eth0.20 net 172.23.184.0/24
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0.20, link-type EN10MB (Ethernet), capture size 262144 bytes
18:51:21.756552 IP 172.23.184.119.51001 > 91.224.XX.YY.52001: UDP, length 112
18:51:22.651556 IP 172.23.184.119.51001 > 91.224.XX.YY.52001: UDP, length 148
18:51:26.681032 IP 172.23.184.119.51001 > 91.224.XX.YY.52001: UDP, length 768
18:51:27.771654 IP 172.23.184.119.51001 > 91.224.XX.YY.52001: UDP, length 148

Here is what conntrack -L says:

udp      17 55 src=172.23.184.119 dst=91.224.XX.YY sport=51001 dport=52001 packets=93 bytes=20412 [UNREPLIED] src=91.224.XX.YY dst=172.23.184.119 sport=52001 dport=51001 packets=0 bytes=0 mark=0 use=1

Notice the second dst= that shows the private IP address of the LAN machine.

After restarting the firewall, the flow is correctly NAT-ed and conntrack -L shows the correct entry (193.33.ZZ.WW is my public IP address):

udp      17 175 src=172.23.184.119 dst=91.224.XX.YY sport=51001 dport=52001 packets=4 bytes=704 [UNREPLIED] src=91.224.XX.YY dst=193.33.ZZ.WW sport=52001 dport=51001 packets=0 bytes=0 mark=0 use=1

Note: when I only enable flow_offloading, the issue does not appear anymore, so this really seems to be an issue with the hw offloading integration in the firewall.

31.07.20181719Base systemBug ReportVery LowCriticalNo wireless interfaces on the UniFi AP AC Lite on the f...openwrt-18.06Unconfirmed Task Description

The same issue as this, but on the final release: https://bugs.openwrt.org/index.php?do=details&task_id=1663&string=unifi&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=

03.08.20181726Base systemBug ReportVery LowCriticalNetifd lockup when USB LTE modem was restartedopenwrt-18.06Unconfirmed Task Description

OpenWrt 18.06.0, r7188-b0b5c64c22
Device: Xiaomi Mir3G
Modem: Huawei E3372

How to reproduce:
1. Bring up wwan interface
2. Reconnect modem (or echo ‘at^reset’ > /dev/ttyUSB0)
3. See in logs:

Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.710901] usb 1-1: USB disconnect, device number 3
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.716646] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.725206] option 1-1:1.0: device disconnected
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.730738] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.739145] option 1-1:1.1: device disconnected
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.744808] huawei_cdc_ncm 1-1:1.2 wwan0: unregister 'huawei_cdc_ncm' usb-1e1c0000.xhci-1, Huawei CDC NCM device
Fri Aug  3 16:59:02 2018 daemon.notice netifd: Network device 'wwan0' link is down
Fri Aug  3 16:59:02 2018 daemon.notice netifd: Network alias 'wwan0' link is down
Fri Aug  3 16:59:02 2018 daemon.notice netifd: Interface 'wwan_4' has link connectivity loss
Fri Aug  3 16:59:02 2018 daemon.notice netifd: Interface 'wwan_4' is disabled
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Source 94.247.111.10 offline
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Source 195.91.239.8 offline
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Source 91.207.136.50 offline
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Source 195.210.189.106 offline
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Can't synchronise: no selectable sources
Fri Aug  3 16:59:02 2018 daemon.notice netifd: wwan_4 (4421): udhcpc: SIOCGIFINDEX: No such device
Fri Aug  3 16:59:02 2018 daemon.notice netifd: wwan_4 (4421): udhcpc: received SIGTERM
Fri Aug  3 16:59:03 2018 daemon.notice netifd: wwan (4800): Stopping network wwan
Fri Aug  3 16:59:03 2018 daemon.notice netifd: wwan (4800): Can't open device /dev/ttyUSB1.
Fri Aug  3 16:59:03 2018 daemon.notice netifd: wwan (4800): Failed to disconnect
Fri Aug  3 16:59:03 2018 daemon.notice netifd: Interface 'wwan' is now down
Fri Aug  3 16:59:03 2018 daemon.warn dnsmasq[4567]: no servers found in /tmp/resolv.conf.auto, will retry
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.683961] usb 1-1: new high-speed USB device number 4 using xhci-mtk
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.867590] option 1-1:1.0: GSM modem (1-port) converter detected
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.874380] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.882334] option 1-1:1.1: GSM modem (1-port) converter detected
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.889115] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.915707] huawei_cdc_ncm 1-1:1.2: resetting NTB format to 16-bit
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.926799] huawei_cdc_ncm 1-1:1.2: MAC-Address: 00:1e:10:1f:00:00
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.933038] huawei_cdc_ncm 1-1:1.2: setting rx_max = 16384
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.938957] huawei_cdc_ncm 1-1:1.2: NDP will be placed at end of frame for this device.
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.947454] huawei_cdc_ncm 1-1:1.2: cdc-wdm0: USB WDM device
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.955970] huawei_cdc_ncm 1-1:1.2 wwan0: register 'huawei_cdc_ncm' at usb-1e1c0000.xhci-1, Huawei CDC NCM device, 00:1e:10:1f:00:00
Fri Aug  3 16:59:10 2018 daemon.notice netifd: Interface 'wwan' is setting up now
Fri Aug  3 16:59:10 2018 daemon.notice netifd: wwan (5197): Stopping network wwan
Fri Aug  3 16:59:11 2018 daemon.notice netifd: wwan (5197): sending ->
Fri Aug  3 16:59:15 2018 daemon.notice netifd: Interface 'wwan' is now down

Now ``ifup wwan`` or ``ifdown wwan`` doesn’t do anything until restart of netifd process.

10.08.20181759Base systemBug ReportVery LowCritical SQM fine in 17.01.4, can’t keep up with line speed in ...openwrt-18.06Unconfirmed Task Description

Netgear R7800 running 17.01.4 kept up with my ISP line speed (nominal 250Mbps/15Mbps) when configured to use SQM with cake/piece_of_cake.
In 18.06, it cannot keep up
Possibly the same root cause as issue 1598

DSLreports speed test with SQM enabled in 17.01.4 (223.1/14.71 Mbps):
http://www.dslreports.com/speedtest/29614883

and with 18.06 ( 95.8/14.16 Mbps):
http://www.dslreports.com/speedtest/36981183

root@LEDE:~# cat /etc/config/sqm

config queue 'eth1'
	option qdisc_advanced '0'
	option verbosity '5'
	option upload '15000'
	option linklayer 'ethernet'
	option overhead '18'
	option debug_logging '1'
	option download '232750'
	option interface 'eth0.2'
	option enabled '1'
	option qdisc 'cake'
	option script 'piece_of_cake.qos'

Sample tc output after running the DSLreports speed test

root@LEDE:~# tc -d qdisc
qdisc noqueue 0: dev lo root refcnt 2 
qdisc mq 0: dev eth0 root 
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc mq 0: dev eth1 root 
qdisc fq_codel 0: dev eth1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc noqueue 0: dev br-lan root refcnt 2 
qdisc noqueue 0: dev eth1.1 root refcnt 2 
qdisc cake 8012: dev eth0.2 root refcnt 2 bandwidth 15Mbit besteffort triple-isolate split-gso rtt 100.0ms noatm overhead 18 
qdisc ingress ffff: dev eth0.2 parent ffff:fff1 ---------------- 
qdisc noqueue 0: dev br-guest root refcnt 2 
qdisc noqueue 0: dev br-iot root refcnt 2 
qdisc noqueue 0: dev wlan0 root refcnt 2 
qdisc noqueue 0: dev wlan1 root refcnt 2 
qdisc noqueue 0: dev wlan1-1 root refcnt 2 
qdisc noqueue 0: dev wlan1-2 root refcnt 2 
qdisc noqueue 0: dev wlan0-1 root refcnt 2 
qdisc fq_codel 0: dev ovpns0 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc fq_codel 0: dev ovpns1 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc cake 8013: dev ifb4eth0.2 root refcnt 2 bandwidth 232750Kbit besteffort triple-isolate wash split-gso rtt 100.0ms noatm overhead 18 

root@LEDE:~# tc -s qdisc
qdisc noqueue 0: dev lo root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc mq 0: dev eth0 root 
 Sent 351709498 bytes 2034499 pkt (dropped 0, overlimits 0 requeues 65185) 
 backlog 0b 0p requeues 65185
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
 Sent 351709498 bytes 2034499 pkt (dropped 0, overlimits 0 requeues 65185) 
 backlog 0b 0p requeues 65185
  maxpacket 1514 drop_overlimit 0 new_flow_count 60774 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc mq 0: dev eth1 root 
 Sent 4385184093 bytes 3164614 pkt (dropped 0, overlimits 0 requeues 109126) 
 backlog 0b 0p requeues 109126
qdisc fq_codel 0: dev eth1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
 Sent 4385184093 bytes 3164614 pkt (dropped 0, overlimits 0 requeues 109126) 
 backlog 0b 0p requeues 109126
  maxpacket 1514 drop_overlimit 0 new_flow_count 137321 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc noqueue 0: dev br-lan root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev eth1.1 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc cake 8012: dev eth0.2 root refcnt 2 bandwidth 15Mbit besteffort triple-isolate split-gso rtt 100.0ms noatm overhead 18 
 Sent 41321462 bytes 92960 pkt (dropped 919, overlimits 39456 requeues 0) 
 backlog 0b 0p requeues 0
 memory used: 194432b of 4Mb
 capacity estimate: 15Mbit
 min/max network layer size:           28 /    1500
 min/max overhead-adjusted size:       46 /    1518
 average network hdr offset:           14

                  Tin 0
  thresh         15Mbit
  target          5.0ms
  interval      100.0ms
  pk_delay        672us
  av_delay        211us
  sp_delay         11us
  backlog            0b
  pkts            93879
  bytes        42712828
  way_inds            6
  way_miss          392
  way_cols            0
  drops             919
  marks               0
  ack_drop            0
  sp_flows            0
  bk_flows            1
  un_flows            0
  max_len         12112
  quantum           457

qdisc ingress ffff: dev eth0.2 parent ffff:fff1 ---------------- 
 Sent 143870988 bytes 121001 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev br-guest root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev br-iot root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan0 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan1 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan1-1 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan1-2 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan0-1 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc fq_codel 0: dev ovpns0 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
 Sent 2015423 bytes 2972 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev ovpns1 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
 Sent 228 bytes 3 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc cake 8013: dev ifb4eth0.2 root refcnt 2 bandwidth 232750Kbit besteffort triple-isolate wash split-gso rtt 100.0ms noatm overhead 18 
 Sent 148570176 bytes 120706 pkt (dropped 297, overlimits 622 requeues 0) 
 backlog 0b 0p requeues 0
 memory used: 661056b of 11637500b
 capacity estimate: 232750Kbit
 min/max network layer size:           46 /    1500
 min/max overhead-adjusted size:       64 /    1518
 average network hdr offset:           14

                  Tin 0
  thresh     232750Kbit
  target          5.0ms
  interval      100.0ms
  pk_delay        245us
  av_delay         45us
  sp_delay          4us
  backlog            0b
  pkts           121003
  bytes       149019834
  way_inds            6
  way_miss          384
  way_cols            0
  drops             297
  marks               0
  ack_drop            0
  sp_flows            0
  bk_flows            1
  un_flows            0
  max_len         12112
  quantum          1514
24.08.20181812KernelBug ReportVery LowCriticalkmod-usb-serial-wwan does not build .ko moduleopenwrt-18.06Unconfirmed Task Description

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

 

I’ve checkout out de most recent OpenWRT 18.06.1 sources from github (commit hash 79518b7a4b0e1b65ba320ee699630b5072f1df51) and
wanted to install it on a MT7621A device. I selected the usb-serial and usb-serial-wwan packages and built them as built-in
kernel modules but I saw the usb_wwan module was not present nor loaded.

I than tried to build as package-only and noticed no usb_wwan.ko was present in the /lib/modules directory after installation.
I’m not sure if this is a kernel bug rather than something wrong with OpenWRT makefiles.

This bug effectively makes 4G cards unusable.


30.08.20181824Base systemBug ReportVery LowCriticalCisco / Meraki MR24 locks up after a day or so using 18...openwrt-18.06Unconfirmed Task Description

Upgrade an MR24 from LEDE 17.01.5 to 18.06.1, and wait a day. Device locks up. WIFI is still advertised, but lan port is no longer pingable.

 


30.09.20181872Base systemBug ReportVery LowCriticalArcher C2600 v1.0 tftp recovery is brokenopenwrt-18.06Unconfirmed Task Description

After i have flashed Openwrt 18.06.1 on my Archer c2600 the tftp recovery dont work anymore. I updated the Openwrt factory image over the web interface. Now i have tried to flash back the original firmware over tftp but it dont work. Im able to start the recovery, and the image is transferred over tftp from my pc, but the router just reboots and load Openwrt again. If i try to flash the Openwrt factory image it also dont work this way anymore. This is a big problem, because somebody would have trouble with the system, he would not be able to recover the router. Also because its not very easy to connect the serial port from the router.


03.10.20181878KernelBug ReportVery LowCriticalFsck privately repaired the file system ext4 on my hdd...openwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on x86-64
- Software versions of OpenWrt/LEDE release, packages, etc.openwrt18.06 55bbd8
- Steps to reproduce.booting and the log showed:

[ 21.237803] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 21.272692] EXT4-fs (sda9): Errors on filesystem, clearing orphan list.
[ 21.272692]
[ 21.281161] EXT4-fs (sda9): recovery complete
[ 21.317228] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 22.061620] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 22.069917] br-lan: port 1(eth0) entered blocking state
[ 22.075803] br-lan: port 1(eth0) entered forwarding state
[ 22.081750] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 23.607322] EXT4-fs (sda10): 3 orphan inodes deleted
[ 23.612459] EXT4-fs (sda10): recovery complete
[ 23.708324] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 26.560650] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 27.547143] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 27.567936] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 27.674344] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 30.029453] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 30.949532] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 30.969532] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 31.076454] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 33.381486] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 34.252398] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 34.272320] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 34.386849] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 36.883663] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 37.787051] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 37.808077] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 37.914149] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 40.179819] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 41.121988] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 41.143438] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 41.249342] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 45.605695] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 46.626671] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 46.646619] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 46.761479] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 49.141156] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 50.029110] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 50.057517] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 50.171446] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 52.634916] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 53.630485] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 53.651385] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 53.765666] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 56.181064] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 57.106498] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 57.127788] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 57.226070] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 59.531087] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 60.476052] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 60.496576] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 60.602792] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 62.968986] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 63.853172] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 63.873463] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 63.980377] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 66.434813] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 67.379340] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 67.425858] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 67.541354] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 69.678280] F2FS-fs (sdb3): Magic Mismatch, valid(0xf2f52010) - read(0×0)
[ 69.685327] F2FS-fs (sdb3): Can’t find valid F2FS filesystem in 1th superblock
[ 69.693925] F2FS-fs (sdb3): Magic Mismatch, valid(0xf2f52010) - read(0×0)
[ 69.700936] F2FS-fs (sdb3): Can’t find valid F2FS filesystem in 2th superblock
[ 69.708463] F2FS-fs (sdb3): Magic Mismatch, valid(0xf2f52010) - read(0×0)
[ 69.715499] F2FS-fs (sdb3): Can’t find valid F2FS filesystem in 1th superblock
[ 69.723034] F2FS-fs (sdb3): Magic Mismatch, valid(0xf2f52010) - read(0×0)
[ 69.730039] F2FS-fs (sdb3): Can’t find valid F2FS filesystem in 2th superblock
[ 69.978884] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 71.390695] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 71.410966] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 71.517413] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 73.339283] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 74.259796] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 74.279939] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 74.377566] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 76.068444] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 76.960511] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 76.981847] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 77.079687] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 78.675960] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 79.687038] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 79.708336] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 79.806743] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 81.486004] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 82.438683] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 82.460115] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 82.574661] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 84.356267] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 85.274004] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 85.295104] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 85.409756] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 87.105830] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 88.151523] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 88.173126] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 88.269852] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 90.191325] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 91.112146] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 91.132150] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 91.238595] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 93.101835] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 94.013109] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 94.033603] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 94.131548] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 95.877771] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 96.848488] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 96.869262] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 96.975183] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)

then i booted my linuxmint,displayed file system error needs to be fixed


10.12.20181995Base systemBug ReportVery LowCriticalHuawei HG655b stuck in bootloopopenwrt-18.06Unconfirmed Task Description

The router reboots continuously while booting into OpenWrt 18.06.1. The same thing happens on version 18.06.0 as well.
Last working one is LEDE 17.01.6 .

Boot log:

CFE version 1.0.37-102.6 for BCM96368 (32bit,SP,BE)
Build Date: Fri Apr 16 15:18:13 CST 2010 (lihua@IBM_x3500)
Copyright (C) 2000-2008 Broadcom Corporation.

Parallel flash device: name AM29LV320MB, id 0x2200, size 8192KB
CPU type 0x2A031: 400MHz, Bus: 160MHz, Ref: 64MHz
CPU running TP0
Total memory: 67108864 bytes (64MB)
Boot Address 0xb8000000


Board IP address                  : 192.168.1.1:ffffff00
Host IP address                   : 192.168.1.100
Gateway IP address                :
Run from flash/host (f/h)         : f
Default host run file name        : vmlinux
Default host flash file name      : bcm963xx_fs_kernel
Boot delay (0-9 seconds)          : 1
Boot image (0=latest, 1=previous) : 0
Board Id (0-6)                    : HW65x
Number of MAC Addresses (1-32)    : 11
Base MAC Address                  : 02:10:18:01:00:01
PSI Size (1-64) KBytes            : 64
Main Thread Number [0|1]          : 0

*** Press any key to stop auto run (2 seconds) ***
Auto run second count down: 0
LZMA: Prossible old LZMA format, trying to decompress..
Decompression OK!
Entry at 0x80a00000
Closing network.
Disabling Switch ports.
Flushing Receive Buffers...
0 buffers found.
Closing DMA Channels.
Starting program at 0x80a00000
[    0.000000] Linux version 4.9.120 (buildbot@builds-03.infra.lede-project.org) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r7102-3f3a2c9) ) #0 SMP Wed Aug 15 20:42:39 2018
[    0.000000] Detected Broadcom 0x6368 CPU revision b2
[    0.000000] CPU frequency is 400 MHz
[    0.000000] 64MB of RAM installed
[    0.000000] board_bcm963xx: Boot address 0xb8000000
[    0.000000] board_bcm963xx: CFE version: 1.0.37-102.6
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0002a031 (Broadcom BMIPS4350)
[    0.000000] board: board name: HW65x
[    0.000000] MIPS: machine is Huawei HG655b
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 04000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 16 bytes.
[    0.000000] Primary data cache 32kB, 2-way, VIPT, cache aliases, linesize 16 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] percpu: Embedded 12 pages/cpu @8108a000 s17440 r8192 d23520 u49152
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
[    0.000000] Kernel command line: rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
[    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Memory: 58636K/65536K available (3773K kernel code, 183K rwdata, 588K rodata, 1336K init, 227K bss, 6900K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=16, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:256
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000015] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.008130] Calibrating delay loop... 397.82 BogoMIPS (lpj=795648)
[    0.042781] pid_max: default: 32768 minimum: 301
[    0.047767] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.054541] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.069410] SMP: Booting CPU1...
[   11.992235] Primary instruction cache 64kB, VIPT, 4-way, linesize 16 bytes.
[   11.992251] Primary data cache 32kB, 2-way, VIPT, cache aliases, linesize 16 bytes
[   11.992575] CPU1 revision is: 0002a031 (Broadcom BMIPS4350)
[    0.121564] Synchronize counters for CPU 1:
[    0.121565] done.
[    0.121573] SMP: CPU1 is running
[    0.131460] Brought up 2 CPUs
[    0.142908] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.152949] futex hash table entries: 512 (order: 1, 8192 bytes)
[    0.159260] pinctrl core: initialized pinctrl subsystem
[    0.166652] NET: Registered protocol family 16
[    0.175484] Can't analyze schedule() prologue at 803baf08
[    0.197227] registering PCI controller with io_map_base unset
[    0.203139] registering PCI controller with io_map_base unset
[    0.234630] PCI host bridge to bus 0000:00
[    0.238879] pci_bus 0000:00: root bus resource [mem 0x30000000-0x37ffffff]
[    0.245938] pci_bus 0000:00: root bus resource [io  0x8000000-0x8007fff]
[    0.252837] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.259812] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.276363] pci 0000:00:01.0: BAR 0: assigned [mem 0x30000000-0x3000ffff]
[    0.284076] PCI host bridge to bus 0000:01
[    0.288281] pci_bus 0000:01: root bus resource [mem 0x38000000-0x3fffffff]
[    0.295332] pci_bus 0000:01: root bus resource [io  0x8008000-0x800ffff]
[    0.302249] pci_bus 0000:01: root bus resource [??? 0x00000000 flags 0x0]
[    0.309225] pci_bus 0000:01: No busn resource found for root bus, will use [bus 01-ff]
[    0.317823] pci 0000:01:1e.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.326326] pci 0000:01:1e.0: BAR 10: assigned [mem 0x38000000-0x3fffffff]
[    0.333401] pci 0000:01:1e.0: BAR 7: assigned [io  0x8008000-0x80080ff]
[    0.340186] pci 0000:01:1e.0: BAR 8: assigned [io  0x8008400-0x80084ff]
[    0.346986] pci 0000:01:1e.0: CardBus bridge to [bus 02-05]
[    0.352727] pci 0000:01:1e.0:   bridge window [io  0x8008000-0x80080ff]
[    0.359528] pci 0000:01:1e.0:   bridge window [io  0x8008400-0x80084ff]
[    0.366347] pci 0000:01:1e.0:   bridge window [mem 0x38000000-0x3fffffff]
[    0.380818] clocksource: Switched to clocksource MIPS
[    0.388361] NET: Registered protocol family 2
[    0.394665] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.401924] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[    0.408534] TCP: Hash tables configured (established 1024 bind 1024)
[    0.415436] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.421530] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.428514] NET: Registered protocol family 1
[    0.435230] Crashlog allocated RAM at address 0x3f00000
[    0.444861] random: fast init done
[    0.450589] workingset: timestamp_bits=30 max_order=14 bucket_order=0
[    0.471721] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.477733] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.512734] io scheduler noop registered
[    0.516874] io scheduler deadline registered (default)
[    0.525247] bcm6368-pinctrl 10000080.pin-controller: registered at mmio b0000080
[    0.534012] 10000100.serial: ttyS0 at MMIO 0x10000100 (irq = 10, base_baud = 1562500) is a bcm63xx_uart
[    0.543754] console [ttyS0] enabled
[    0.543754] console [ttyS0] enabled
[    0.550889] bootconsole [early0] disabled
[    0.550889] bootconsole [early0] disabled
[    0.559894] bcm63xx-rng bcm63xx-rng: registered RNG driver
[    0.566702] 18000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x001000
[    0.577107] Amd/Fujitsu Extended Query Table at 0x0040
[    0.582383]   Amd/Fujitsu Extended Query version 1.3.
[    0.587560] number of CFI chips: 1
[    0.591665] bcm63xxpart: Partition 0 is CFE offset 0 and length 10000
[    0.598317] bcm63xxpart: Partition 1 is nvram offset 7f0000 and length 10000
[    0.605576] bcm63xxpart: Partition 2 is linux offset 10000 and length 7e0000
[    0.612884] 3 bcm63xxpart partitions found on MTD device 18000000.nor
[    0.619494] Creating 3 MTD partitions on "18000000.nor":
[    0.624958] 0x000000000000-0x000000010000 : "CFE"
[    0.631868] 0x0000007f0000-0x000000800000 : "nvram"
[    0.638937] 0x000000010000-0x0000007f0000 : "linux"
[    0.646345] parser_imagetag: rootfs: CFE image tag at 0x0 CRC invalid (expected 0212102b, actual 24b1b887)
[    0.657859] bcm63xx-spi 10000800.spi: at [mem 0x10000800-0x10000f0b flags 0x200] (irq 9, FIFOs size 542)
[    0.669448] libphy: Fixed MDIO Bus: probed
[    0.717976] b53_common: found switch: BCM63xx, rev 0
[    0.723524] bcm63xx-wdt bcm63xx-wdt:  started, timer margin: 30 sec
[    0.733982] NET: Registered protocol family 10
[    0.741672] NET: Registered protocol family 17
[    0.746347] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    0.759683] 8021q: 802.1Q VLAN Support v1.8
[    0.774484] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    0.782230] Please append a correct "root=" boot option; here are the available partitions:
[    0.790832] 1f00              64 mtdblock0 [    0.794921]  (driver?)
[    0.797342] 1f01              64 mtdblock1 [    0.801455]  (driver?)
[    0.803858] 1f02            8064 mtdblock2 [    0.807994]  (driver?)
[    0.810425] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.820791] Rebooting in 1 seconds..
[    1.819072] triggering watchdog soft-reset...


17.12.20182009DocumentationBug ReportVery LowCriticalNetgear R8000 - Unable to install OpenWRT firmwareopenwrt-18.06Unconfirmed Task Description

Netgear R8000 - Unable to install OpenWRT firmware

https://openwrt.org/toh/netgear/r8000#tab__firmware_downloads

A recently purchased from Amazon Netgear R8000 (Nighthawk X6) refuses to accept the OpenWRT firmware file and there are not directions for an alternate installation method.

Full model from the back:

NETGEAR Nighthawk X6
AC3200 Tri-Band WiFiRouter
Model: R8000
FCCID: PY314200264
Made in Vietnam 272-12664-01

23.12.20182023PackagesBug ReportVery LowCriticalPPtP not connecting on Xiaomi Mi WiFi R3Gopenwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on : Xiaomi Mi WiFi R3G (https://openwrt.org/toh/xiaomi/mir3g)
- OpenWrt 18.06.1

Steps to reproduce:

1.opkg update
2.opkg install ppp-mod-pptp
3.opkg install kmod-nf-nathelper-extra
4.opkg install kmod-ipt-raw
5.disabled rebind attack protection from DNS and DHCP
6.added below custom rule on /etc/firewall.user

iptables -t raw -A OUTPUT -p tcp -m tcp --dport 1723 -j CT --helper pptp

7.setup the PPTP in the LUCI
8.reboot

Relevant Logs appearing repetitively:

Sun Dec 23 17:48:01 2018 daemon.notice pppd[22738]: pppd 2.4.7 started by root, uid 0
Sun Dec 23 17:48:02 2018 kern.info kernel: [ 1551.622787] pptp-ISP: renamed from ppp0
Sun Dec 23 17:48:02 2018 daemon.info pppd[22738]: Using interface pptp-ISP Sun Dec 23 17:48:02 2018 daemon.notice pppd[22738]: Connect: pptp-ISP ←→ pptp (red.connect.net.pk)
Sun Dec 23 17:48:03 2018 daemon.notice pppd[22738]: CHAP authentication succeeded
Sun Dec 23 17:48:03 2018 daemon.notice pppd[22738]: Connection terminated.
Sun Dec 23 17:48:03 2018 daemon.warn pppd[22740]: read returned zero, peer has closed
Sun Dec 23 17:48:03 2018 daemon.warn pppd[22740]: read returned zero, peer has closed
Sun Dec 23 17:48:03 2018 daemon.info pppd[22738]: Exit.
Sun Dec 23 17:48:03 2018 daemon.notice netifd: Interface ‘ISP’ is now down
Sun Dec 23 17:48:03 2018 daemon.notice netifd: Interface ‘ISP’ is setting up now
Sun Dec 23 17:48:03 2018 daemon.info pppd[22998]: Plugin pptp.so loaded.
Sun Dec 23 17:48:03 2018 daemon.info pppd[22998]: PPTP plugin version 1.00
Sun Dec 23 17:48:03 2018 daemon.notice pppd[22998]: pppd 2.4.7 started by root, uid 0


21.01.20192070PackagesBug ReportVery LowCriticalbn_wexpand in bn_div.c are not checked for failure and ...openwrt-18.06Unconfirmed Task Description

Hi,
The code in the openwrt/package/network/services/ead/src/tinysrp/bn_div.c should be fixed to check the bn_wexpand return value. The problem exists in multiple other projects including openssl with CVE (CVE-2009-3245)(https://github.com/openssl/openssl/commit/2d9dcd4ff0923347fab727ac90e8526dd65e4e07).

21.01.20192071PackagesBug ReportVery LowCriticalbn_wexpand return value vulnerable to memory leakopenwrt-18.06Unconfirmed Task Description

Hi,
The code in the openwrt/package/network/services/ead/src/tinysrp/bn_div.c should be fixed to check the bn_wexpand return value. The problem exists in multiple other projects including openssl with CVE (CVE-2009-3245)(https://github.com/openssl/openssl/commit/2d9dcd4ff0923347fab727ac90e8526dd65e4e07).

21.01.20192072PackagesBug ReportVery LowCriticalbn_wexpand return value vulnerable to memory leakopenwrt-18.06Unconfirmed Task Description

Hi,
The code in the openwrt/package/network/services/ead/src/tinysrp/bn_div.c should be fixed to check the bn_wexpand return value. The problem exists in multiple other projects including openssl with CVE (CVE-2009-3245)(https://github.com/openssl/openssl/commit/2d9dcd4ff0923347fab727ac90e8526dd65e4e07).

23.01.20192080PackagesBug ReportVery LowCriticalWan IPV6 interface with 6rd protocol reports bad mac ad...openwrt-18.06Unconfirmed Task Description

Device used is BT Home Hub 5 v1.2.
Openwrt release is 18.06.1,
6rd package version is 9-4
ISP is Free (France)

“Wan” interface, IPV4, with Dchp client protocol is up and works fine on physical interface dsl0.836.
Mac address has to be overriden because ISP uses a fixed mac address, different for each Freebox, it’s own dsl modem/box.

“Wan6”, IPV6, interface with 6rd protocol is up but the mac reported in the not the same as those reported in “Wan” interface.

As you could see on the attached capture of the “Interfaces overview”, the mac address reported is the “Wan” IpV4 address !!!

Wan6 interface is up but frames are rejected by ISP because the mac address is not those one expected as for “Wan” interface. Mac address can’t be overriden on these interface.

network config is attached.



Cromagnon31

25.02.20192145Base systemBug ReportVery LowCriticalNo IPv4 adresses offered on LAN of GL-AR150 if no LAN c...openwrt-18.06Unconfirmed Task Description

This is 100 % reproducible with a fresh and unchanged installation of OpenWRT 18.06.2 on a GL-Inet GL-AR150, and it gave me quite some headache until I found out what’s happening here:

If a LAN cable is plugged during the device’s boot process and one does a DHCP request when it’s ready, the router offers an IPv4 address (as expected) and one can access it on 192.168.1.1. This is also the case for a DHCP request via WLAN, as soon as one does enable it.

If however the device is powered up without a LAN cable being plugged, no IPv4 address will be offered, neither for a LAN nor for a WLAN connection. One can connect to the router via the IPv6 address to be found in /etc/resov.conf (on the client) though, but not via IPv4. This is also the case if a LAN cable is plugged after booting.

Looking at /var/etc/dnsmasq.conf.cfg01411c, it does contain the line

  dhcp-range=set:lan,192.168.1.100,192.168.1.249,255.255.255.0,12h

if a LAN cable has been plugged during bootup, and no such entry if none has been plugged.

This makes the device completely unusable for what I intend to use it ... as this happens with a completely unaltered, fresh installation, I suppose this is no misconfiguration but a bug?

09.07.20192370Base systemBug ReportVery LowCriticalCPE210 V1.1 Brick after update 18.06.04openwrt-18.06Unconfirmed Task Description

Trying to update to the latest version (openwrt-18.06.4-ar71xx-generic-cpe210-220-v1-squashfs-sysupgrade.bin) has failed and has entered into safeloader. I put it to your knowledge in case there is a fault in the firmware.

CPE210 V1.1 with openwrt-18.06.2-ar71xx-generic-cpe210-220-v1-squashfs-sysupgrade.bin

With a USB serial cable:

“TP-LINK SafeLoader (Build time: Jun 12 2015 - 09:49:53)
CPU: 560MHz AHB: 225MHz DDR: 64MB
Performing LED check.. PASS
Press CTRL+B to enter SafeLoader: 1
Flash Manufacturer: Unknown(0xc8)
Flash Device ID: Unknown(0×4017)
Data flash init failed.
open user-config failed.
open user-config failed.

enet0 port4 up

TFTP server address is 192.168.0.100; our address is 192.168.0.254
Get filename ‘recovery.bin’.

TFTP error: Starting again.
faddr is 0×0, fsize is 0×0 reserved is 0x83832c86, load_reserved_size is 0×0 WARNING: Data loaded outside of the reserved load area, memory corruption may occur.
##Warning: File is unidentiable. Try downloading

TFTP server address is 192.168.0.100; our address is 192.168.0.254
Get filename ‘vmlinuz’.

TFTP error: Starting again.
faddr is 0×0, fsize is 0×0 reserved is 0×83832206, load_reserved_size is 0×0 WARNING: Data loaded outside of the reserved load area, memory corruption may occur.
##ERROR: Can’t download image.

Password”

25.07.20192405Base systemBug ReportVery LowCriticalsnmpd bad interaction with rc.local (gets emptied when ...openwrt-18.06Unconfirmed Task Description

Easy to reproduce:
1) Have something in rc.local
2) Restart snmpd
3) Look again to rc.local is empty

 

I’ve tested this with several models:
ZBT-WG3526 (16M)
TP-Link Archer C2600
GL.iNet GL-AR300M
TP-LINK Archer C7 v4
SamKnows Whitebox 8

It looks that from time to time, rc.local gets “emptied”.

I’m using cacti to monitor several routers, and from time to time, if an interface is reset (link down, etc.), it looks like cacti gets confused, so I need to restart snmpd.

It looks that that creates the problem, because after that, rc.local is empty.

I’ve been trying to find the problem since I flashed all the routers with 18.06.4 (stable), because initially this was happening when rebooting, so I was not able to find why ... now, I’m almost sure that it is the snmpd restart which creates the problem.


19.06.20181598Base systemBug ReportVery LowHighregression: network performance on IPQ806X (R7800) has ...openwrt-18.06Unconfirmed Task Description

Device problem occurs on: Netgear R7800
oftware versions of OpenWrt/LEDE release: Latest 18.06 branch revision

I’ve run an iperf3 test, I have records of automated tests that I run every 2 hours that show the usual performance is 380Mbps to bouygues.iperf.fr, however on 18.06 the max attainable is just over 60Mbps in a single threaded test. I need to go to at least 10 threads to get close to 380Mbps.

I reverted to stock and a 17.01 build to verify that there was no issue with the internet connection here, and they all showed the old behaviour.

This speed is unnafected by flow offload being off or on.

 
root@router01:~# iperf3 -c bouygues.iperf.fr -p 5207 -R
Connecting to host bouygues.iperf.fr, port 5207
Reverse mode, remote host bouygues.iperf.fr is sending
[  5] local xxx.xxx.xxx.xxx port 45674 connected to 89.84.1.222 port 5207
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  7.45 MBytes  62.5 Mbits/sec
[  5]   1.00-2.00   sec  7.31 MBytes  61.3 Mbits/sec
[  5]   2.00-3.00   sec  7.63 MBytes  64.0 Mbits/sec
[  5]   3.00-4.00   sec  7.64 MBytes  64.1 Mbits/sec
[  5]   4.00-5.00   sec  7.57 MBytes  63.5 Mbits/sec
[  5]   5.00-6.00   sec  7.63 MBytes  64.0 Mbits/sec
[  5]   6.00-7.00   sec  7.47 MBytes  62.6 Mbits/sec
[  5]   7.00-8.00   sec  7.85 MBytes  65.8 Mbits/sec
[  5]   8.00-9.00   sec  7.77 MBytes  65.2 Mbits/sec
[  5]   9.00-10.00  sec  7.86 MBytes  65.9 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  77.7 MBytes  65.2 Mbits/sec    0             sender
[  5]   0.00-10.00  sec  76.2 MBytes  63.9 Mbits/sec                  receiver

iperf Done.


16.07.20181663Base systemBug ReportVery LowHighUniFi AP AC LITE on rc2: Wireless interfaces not recogn...openwrt-18.06Unconfirmed Task Description

I’ve upgraded a UniFi AP AC LITE from 17.01.4 to 18.06 rc2 (without keeping the settings), and the resulting system didn’t recognize any of the two wireless radios (checked over SSH as well, the interfaces were not there under the sysfs).
For now I’ve downgraded to 17.01.4 but I’m happy to do the upgrade again if details are missing.
Cheers!

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

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

 

Problem occurs on Netgear R6100

Software version 18.06 rc2 (also on rc1)

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

Attaching dmesg and logread from boot of 18.06 rc2

31.07.20181716Base systemBug ReportVery LowHighZyxel Keenetic doesn't save any settingsopenwrt-18.06Unconfirmed Task Description

OpenWRT 18.06.00 RC1, RC2...
Zyxel Keenetic (ramips, rt305x, kn-squashfs-sysupgrade.bin)

Probably due to low memory (4MB) router does not save any settings and after reboot it have factory settings again and again. Also it doesn't have factory reset button in LUCI and does not react on Reset button.

06.08.20181742KernelBug ReportVery LowHighOpenWrt18.06 is not working on Netgear WNR1000 v2 due t...openwrt-18.06Unconfirmed Task Description

Netgear WNR1000 v2
OpenWrt 18.06 is unable to mount jffs2 with the following message:
daemon.err mount_root: failed - mount -t jffs2 /dev/mtdblock5 /rom/overlay: Invalid argument

Snapshot is working.

14.08.20181778Base systemBug ReportVery LowHighrelease 18.06 does not work for recent RouterBoard 450G...openwrt-18.06Unconfirmed Task Description

OpenWrt 18.06. does not work on at least some RB45Gs, because the yaffs2-Image for the kernel in

openwrt-18.06.0-ar71xx-mikrotik-nand-large-squashfs-sysupgrade.bin

seems to be created with a pagesize of 2048, but my recent RB450G contains a NAND-Chip with a pagesize of 4096 (as displayed by the linux-kernel). Flashing this image onto this chip with “nandwrite -o”, inside function platform_nand_pre_upgrade() in file target/linux/ar71xx/base-files/lib/upgrade/platform.sh, screws up oop-data and renders the kernel-nand-partition unbootable, unreadable, unwritable and even unerasable (at least with “mtd erase”).

See attached File cap1.txt for an installation log. The Installation seemed to work just fine, but the device did not bool any more.
See attached File cap2.txt for a log of a netboot-session after that. The kernel showed up 6 new “Bad eraseblock”s and “mtd erase” did not work any more.
After restoring Mikrotik’s RouterOS to the device with their NetInstall-Application, the “bad eraseblock”s were gone, which prooves, that the NAND-Chip is not really defective and the “Bad eraseblock” are erroneous.

There seem to be RouterBoards with different NAND-Chips around: This page:

https://wikidevi.com/wiki/MikroTik_RouterBOARD_450G_%28RB450G%29

states that it is a “Hynix HY27UT084G2A”, but the Linux-Kernel states that
the Chip is from Toshiba. Hence the sysupgrade-procedure should probably prepared
for different yaffs2-page-sizes.

Workaround:

After quite some time, I figures out the following workaround:

  1. Netboot OpenWrt 18-06.
  2. Open the file /lib/upgrade/platform.sh with vi and comment out the nandwrite-call in line 760.
  3. Call sysupgrade as usual –> The Installation will not be bootable, but the kernel-Partition will still be accessable
  4. Netboot OpenWrt 14.07 (because v18.06 lacks yaffs2-kernel-support !)
  5. Manually install the kernel-file with:
mtd erase /dev/mtd5
mkdir /mnt/kernel
mount -t yaffs2 /dev/mtdblock5 /mnt/kernel
cd /mnt/kernel
wget -O kernel http://192.168.88.1:8080/openwrt-18.06.0-ar71xx-mikrotik-vmlinux-lzma.elf
chmod +x kernel
cd /
sync
umount /mnt/kernel

With this procedure I got a working installation.

25.08.20181816Base systemBug ReportVery LowHigh D-Link DWR-921 C3’s WWAN connection/LTE modem hangs/st...openwrt-18.06Unconfirmed Task Description

Internet connection stops working, pinging 8.8.8.8 directly from router doesn’t work. It seems to happen most often after 2 days since booting, but I’m pretty sure it had happened very soon after restarting too (restart was done because of this exact problem). Before it happens, everything works perfectly. Nothing like this happens on stock D-Link firmware.

logread output: attached
dmesg output: attached
Both done after I noticed internet is down in the morning, it had to go down at night.

Steps to reproduce:
flash OpenWrt 18.06.0 r7188-b0b5c64c22 / LuCI openwrt-18.06 branch (git-18.210.69179-6df9a57) factory image on DWR-921 C3
configure it the following way (this is exactly all the configuration that was done on the device prior to flashing openwrt):

passwd
uci set network.wwan=interface
uci set network.wwan.proto='qmi'
uci set network.wwan.device='/dev/cdc-wdm0'
uci set network.wwan.apn='internet'
uci set network.wwan.modes='lte'
uci commit network
uci set firewall.@zone[1].network='wan wwan wan6'
uci commit firewall
ifup wwan
opkg update
opkg install luci-proto-qmi
/etc/init.d/uhttpd restart
reboot

wait (2 days should be enough, but no warranties)

My attempts at working around the problem:
ifdown wwan and ifup wwan don’t help, same with restarting wwan in luci, output of uqmi -d /dev/cdc-wdm0 –get-data-status is “disconnected”. uqmi -d /dev/cdc-wdm0 –start-network doesn’t help.

I also tried playing with lte_modem_enable gpio. I’ll try this when the bug materializes again.
internet works ok
I do echo “0” > /sys/class/gpio/lte_modem_enable/value
then echo “1” > /sys/class/gpio/lte_modem_enable/value
internet doesn’t work
logread output:

Fri Aug 24 19:57:21 2018 kern.info kernel: [ 1133.343003] usb 1-1: USB disconnect, device number 2
Fri Aug 24 19:57:21 2018 kern.info kernel: [ 1133.357143] qmi_wwan 1-1:1.4 wwan0: unregister 'qmi_wwan' usb-101c0000.ehci-1, WWAN/QMI device
Fri Aug 24 19:57:21 2018 daemon.notice netifd: Network device 'wwan0' link is down
Fri Aug 24 19:57:21 2018 daemon.notice netifd: Network alias 'wwan0' link is down
Fri Aug 24 19:57:21 2018 daemon.notice netifd: Interface 'wwan_4' has link connectivity loss
Fri Aug 24 19:57:21 2018 daemon.notice netifd: Interface 'wwan_4' is disabled
Fri Aug 24 19:57:21 2018 daemon.notice netifd: wwan_4 (1378): udhcpc: SIOCGIFINDEX: No such device
Fri Aug 24 19:57:21 2018 daemon.notice netifd: wwan_4 (1378): udhcpc: SIOCGIFINDEX: No such device
Fri Aug 24 19:59:02 2018 kern.info kernel: [ 1179.698888] usb 1-1: new high-speed USB device number 3 using ehci-platform
Fri Aug 24 19:59:02 2018 kern.info kernel: [ 1179.846894] qmi_wwan 1-1:1.4: cdc-wdm0: USB WDM device
Fri Aug 24 19:59:02 2018 daemon.notice netifd: Interface 'wwan_4' is enabled
Fri Aug 24 19:59:02 2018 kern.info kernel: [ 1179.912948] qmi_wwan 1-1:1.4 wwan0: register 'qmi_wwan' at usb-101c0000.ehci-1, WWAN/QMI device, mac

ifup wwan, ifdown wwan and ifup wwan

Fri Aug 24 20:01:29 2018 daemon.notice netifd: Interface 'wwan_4' is disabled
Fri Aug 24 20:01:29 2018 daemon.notice netifd: wwan (2431): Stopping network wwan
Fri Aug 24 20:01:34 2018 daemon.notice netifd: Interface 'wwan' is now down
Fri Aug 24 20:01:34 2018 daemon.notice netifd: Interface 'wwan' is setting up now
Fri Aug 24 20:01:52 2018 daemon.notice netifd: wwan (2542): Stopping network wwan
Fri Aug 24 20:01:52 2018 daemon.notice netifd: wwan (2542): Command failed: Permission denied
Fri Aug 24 20:01:52 2018 daemon.notice netifd: Interface 'wwan' is now down
Fri Aug 24 20:01:52 2018 daemon.notice netifd: Interface 'wwan' is setting up now

ifup wwan

Fri Aug 24 20:03:17 2018 daemon.notice netifd: wwan (2765): Stopping network wwan
Fri Aug 24 20:03:17 2018 daemon.notice netifd: wwan (2765): Command failed: Permission denied
Fri Aug 24 20:03:17 2018 daemon.notice netifd: Interface 'wwan' is now down
Fri Aug 24 20:03:17 2018 daemon.notice netifd: Interface 'wwan' is setting up now

ifdown wwan

Fri Aug 24 20:04:06 2018 daemon.notice netifd: wwan (2850): Stopping network wwan
Fri Aug 24 20:04:06 2018 daemon.notice netifd: wwan (2850): Command failed: Permission denied
Fri Aug 24 20:04:06 2018 daemon.notice netifd: Interface 'wwan' is now down

ifup wwan

Fri Aug 24 20:04:22 2018 daemon.notice netifd: Interface 'wwan' is setting up now

few minutes later ifstatus wwan

{
    "up": false,
    "pending": true,
    "available": true,
    "autostart": true,
    "dynamic": false,
    "proto": "qmi",
    "data": {
       
    }
}

stopped wwan in luci

Fri Aug 24 20:08:23 2018 daemon.notice netifd: wwan (3540): Stopping network wwan
Fri Aug 24 20:08:23 2018 daemon.notice netifd: wwan (3540): Command failed: Permission denied
Fri Aug 24 20:08:23 2018 daemon.notice netifd: Interface 'wwan' is now down

started wwan in luci

Fri Aug 24 20:08:53 2018 daemon.notice netifd: Interface 'wwan' is setting up now
Fri Aug 24 20:08:54 2018 daemon.notice netifd: wwan (3631): "No effect"
Fri Aug 24 20:08:54 2018 daemon.notice netifd: wwan (3631): "Failed to connect to service"

internet still not working, I reboot and it works.

27.08.20181820Base systemBug ReportVery LowHigh18.06.0 release not working on Mercury MAC1200R v1 (ar7...openwrt-18.06Unconfirmed Task Description

I’m using TTL to flash in openwrt 18.06 via method on its wiki page, but it fail to boot. Log:

[    2.359088] squashfs: SQUASHFS error: unable to read id index table
[    2.365735] List of all partitions:
[    2.369291] 1f00             128 mtdblock0 [    2.373384]  (driver?)
[    2.375789] 1f01            1335 mtdblock1 [    2.379845]  (driver?)
[    2.382260] 1f02            6665 mtdblock2 [    2.386322]  (driver?)
[    2.388723] 1f03            4096 mtdblock3 [    2.392795]  (driver?)
[    2.395191] 1f04              64 mtdblock4 [    2.399250]  (driver?)
[    2.401663] 1f05            8000 mtdblock5 [    2.405726]  (driver?)
[    2.408120] No filesystem could mount root, tried: [    2.412894]  squashfs
[    2.415195]
[    2.416717] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[    2.426288] Rebooting in 1 seconds..

Then I flash back to 17.01.5 and it recovers. I also attached complete bootlog of both versions FYI.

04.09.20181832Base systemBug ReportVery LowHighTplink c2600 v1 Internet Connection with SQM / Layer Ca...openwrt-18.06Unconfirmed Task Description

I flashed OpenWrt 18.06.1 on my Tplink Archer c2600 v1.0
When i use SQM the Internet connection is slow ( 50% Slower than without SQM )
Without SQM the Internet Speed is normal again.
The SQM settings are the same that i use on my Tplink Archer C7 and on the C7 everything works
great.


11.09.20181841Base systemBug ReportVery LowHighuncontinuous WIFI 5G connection on WNDR4300 v1 with 18....openwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on WNDR4300 v1
- Software versions of OpenWrt/LEDE release 18.06.1
- Steps to reproduce: mobile phone connected to wifi 5G, disconnected sometimes and reconnected in a few seconds. 5G WIFI channel and power were changed for some times but did not work.

 


13.09.20181845Base systemBug ReportVery LowHighTL-WR840N v5 wifi troublesopenwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
TL-WR840N v5
access point config
wpa2 auto
DHCP off
- Software versions of OpenWrt/LEDE release, packages, etc.
18.06.1
snapshot
- Steps to reproduce

 

try connect more wifi clients over some hours and after this router is unusable over wifi
standart logs dont show any troubles

17.09.20181851Base systemBug ReportVery LowHighLoss of LAN<->WLAN connectivity on WR1043ND v4openwrt-18.06Unconfirmed Task Description

Hi
I am having repeatable issues with LuCI openwrt-18.06, observed on OpenWrt 18.06.1
The network connectivity between WAN and LAN is unstable, every couple of seconds the network stops responding. I can observe it as:
1. ping times: from 1ms to 10ms for devices in the same network as WAN interface
2. the remote desktop freezes and restarts
3. the network speed while copying files is very low (from 1MB/s to 5MB/s).

My configuration:
WAN - static IP
LAN - DHCP server
WLAN - Two WiFi networks.

I have removed all IPv6 system packets, disabled WLAN which did not make any difference, installed factory clean image and still this issue appears.
I am not seeing this issue when the TPLINK device works as the switch (WAN is not plugged, the network goes through LAN ports).
I am able to observe this issue at several devices.

19.09.20181855Base systemBug ReportVery LowHighUSB works ONLY with WiFi disabledopenwrt-18.06Unconfirmed Task Description

The problem occurs on Netgear WNDR3700v3 USING latest 18.06.

After setting up the router and installing required USB packages then rebooting the router, USB can’t be accessed. USB LED indicator light flickers few times during booting of the router, then shuts off. Using DMESG later I see that USB connects, then suddenly disconnects. The ONLY way to use USB functionality is to DISABLE WIFI.

To simply reproduce the issue, flash openwrt to your wndr3700v3, install required base USB packages.

1.) Disable wifi and find USB devices working normally.
2.) Enable Wifi and find USB devices not working and not being powered. (no led indicator on USB).

Use DMESG to see USB being recognized during boot and then simply later disconnected for no reason whatsoever.

The same issue did occur on 17.01. with the same behavior.

14.11.20181949Base systemBug ReportVery LowHighTL -1043ND V1 default gateway not foundopenwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
TP-LINK 1043ND version 1
- Software versions of OpenWrt/LEDE release, packages, etc.
18.06.1
- Steps to reproduce

 


20.12.20182015KernelBug ReportVery LowHighWi-fi repeater relayd stops working [mt7628 miwifi nano...openwrt-18.06Unconfirmed Task Description

Hi. I have a miwifi nano r1cl working as a relayd repeater. I’ve been using it for quite a long time with 18.06.1 with no issues at all. However I updated to OpenWrt 18.06-SNAPSHOT r7549-217219ee1d and I started having issues with wifi connectivity. At the beggining everything is well and runs just fine for like 5-10 minutes of usage, but then it stops working and I can’t connect to its wifi. If I have a look at the kernel log, I see lots of errors like these:

[ 8969.318135] mt76_wmac 10300000.wmac: MCU message 8 (seq 14) timed out
[ 8970.438153] mt76_wmac 10300000.wmac: MCU message 8 (seq 15) timed out
[ 8971.558140] mt76_wmac 10300000.wmac: MCU message 8 (seq 1) timed out
[ 8972.678146] mt76_wmac 10300000.wmac: MCU message 8 (seq 2) timed out
[ 8973.798146] mt76_wmac 10300000.wmac: MCU message 8 (seq 3) timed out
[ 8974.947917] mt76_wmac 10300000.wmac: MCU message 8 (seq 4) timed out
[ 8976.038230] mt76_wmac 10300000.wmac: MCU message 8 (seq 5) timed out
[ 8977.158154] mt76_wmac 10300000.wmac: MCU message 8 (seq 6) timed out
[ 8978.358299] mt76_wmac 10300000.wmac: MCU message 8 (seq 7) timed out
[ 8979.478170] mt76_wmac 10300000.wmac: MCU message 8 (seq 8) timed out
[ 8980.598384] mt76_wmac 10300000.wmac: MCU message 8 (seq 9) timed out
[ 8981.718183] mt76_wmac 10300000.wmac: MCU message 8 (seq 10) timed out
[ 8982.838278] mt76_wmac 10300000.wmac: MCU message 8 (seq 11) timed out
[ 8983.958213] mt76_wmac 10300000.wmac: MCU message 8 (seq 12) timed out
[ 8985.078184] mt76_wmac 10300000.wmac: MCU message 8 (seq 13) timed out
[ 8986.278180] mt76_wmac 10300000.wmac: MCU message 8 (seq 14) timed out
[ 8987.398184] mt76_wmac 10300000.wmac: MCU message 8 (seq 15) timed out
[ 8988.518184] mt76_wmac 10300000.wmac: MCU message 8 (seq 1) timed out
[ 8989.638188] mt76_wmac 10300000.wmac: MCU message 8 (seq 2) timed out
[ 8990.758273] mt76_wmac 10300000.wmac: MCU message 8 (seq 3) timed out

I’ll get back to 18.06.1 but I thought it might be useful to post about this.

26.12.20182026KernelBug ReportVery LowHighkernel ipq806x Oopsopenwrt-18.06Unconfirmed Task Description

Device: netgear,r7800
Version: 18.06.1

Steps to reproduce:
The crash will happen with 100% certainty, but what exactly causes the problem is a little hard to say. It looks like large internet frames on WAN interface somehow trigger the error.

The WAN interface (eth.2) is untagged, on the LAN ports besides 1 untagged VLAN, 3 untagged VLANs exist. Only (possibly) relevant extra installed package is ip-tiny; it isn’t used though for any custom configuration though.

From the syslog (from boot till Oops, seemingly non-related stuff redacted out):

Wed Dec 26 15:18:27 2018 kern.info kernel: [    0.000000] Booting Linux on physical CPU 0x0
Wed Dec 26 15:18:27 2018 kern.notice kernel: [    0.000000] Linux version 4.14.63 (buildbot@builds-03.infra.lede-project.org) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r7102-3f3a2c9)) #0 SMP Thu Aug 16 07:51:15 2018
Wed Dec 26 15:18:27 2018 kern.info kernel: [    0.000000] CPU: ARMv7 Processor [512f04d0] revision 0 (ARMv7), cr=10c5787d
Wed Dec 26 15:18:27 2018 kern.info kernel: [    0.000000] CPU: div instructions available: patching division code
Wed Dec 26 15:18:27 2018 kern.info kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Wed Dec 26 15:18:27 2018 kern.info kernel: [    0.000000] OF: fdt: Machine model: Netgear Nighthawk X4S R7800
...
Wed Dec 26 15:18:27 2018 kern.info kernel: [    1.304591] libphy: GPIO Bitbanged MDIO: probed
Wed Dec 26 15:18:27 2018 kern.info kernel: [    1.325983] switch0: Atheros AR8337 rev. 2 switch registered on gpio-0
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.210243] libphy: Fixed MDIO Bus: probed
Wed Dec 26 15:18:27 2018 kern.warn kernel: [    2.212378] ipq806x-gmac-dwmac 37200000.ethernet: PTP uses main clock
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.213549] stmmac - user ID: 0x10, Synopsys ID: 0x37
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.219747] ipq806x-gmac-dwmac 37200000.ethernet: Ring mode enabled
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.224876] ipq806x-gmac-dwmac 37200000.ethernet: DMA HW capability register supported
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.230859] ipq806x-gmac-dwmac 37200000.ethernet: Enhanced/Alternate descriptors
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.238924] ipq806x-gmac-dwmac 37200000.ethernet: Enabled extended descriptors
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.246483] ipq806x-gmac-dwmac 37200000.ethernet: RX Checksum Offload Engine supported
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.253511] ipq806x-gmac-dwmac 37200000.ethernet: COE Type 2
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.261323] ipq806x-gmac-dwmac 37200000.ethernet: TX Checksum insertion supported
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.267227] ipq806x-gmac-dwmac 37200000.ethernet: Wake-Up On Lan supported
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.274601] ipq806x-gmac-dwmac 37200000.ethernet: Enable RX Mitigation via HW Watchdog Timer
Wed Dec 26 15:18:27 2018 kern.warn kernel: [    2.282886] ipq806x-gmac-dwmac 37400000.ethernet: PTP uses main clock
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.290081] stmmac - user ID: 0x10, Synopsys ID: 0x37
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.296320] ipq806x-gmac-dwmac 37400000.ethernet: Ring mode enabled
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.301257] ipq806x-gmac-dwmac 37400000.ethernet: DMA HW capability register supported
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.307399] ipq806x-gmac-dwmac 37400000.ethernet: Enhanced/Alternate descriptors
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.315397] ipq806x-gmac-dwmac 37400000.ethernet: Enabled extended descriptors
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.322956] ipq806x-gmac-dwmac 37400000.ethernet: RX Checksum Offload Engine supported
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.329903] ipq806x-gmac-dwmac 37400000.ethernet: COE Type 2
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.337865] ipq806x-gmac-dwmac 37400000.ethernet: TX Checksum insertion supported
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.343699] ipq806x-gmac-dwmac 37400000.ethernet: Wake-Up On Lan supported
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.350995] ipq806x-gmac-dwmac 37400000.ethernet: Enable RX Mitigation via HW Watchdog Timer
...
Wed Dec 26 15:18:27 2018 kern.info kernel: [    2.428253] 8021q: 802.1Q VLAN Support v1.8
...
Wed Dec 26 15:18:27 2018 user.info kernel: [    3.839793] init: - watchdog -
...
Wed Dec 26 15:18:27 2018 user.info kernel: [    4.407941] kmodloader: loading kernel modules from /etc/modules-boot.d/*
...
Wed Dec 26 15:18:27 2018 user.info kernel: [    5.088295] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Wed Dec 26 15:18:27 2018 user.info kernel: [    5.098476] init: - preinit -
...
Wed Dec 26 15:18:27 2018 kern.info kernel: [    6.799339] Generic PHY fixed-0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:01, irq=POLL)
Wed Dec 26 15:18:27 2018 kern.info kernel: [    6.800863] dwmac1000: Master AXI performs any burst length
Wed Dec 26 15:18:27 2018 kern.info kernel: [    6.808373] ipq806x-gmac-dwmac 37400000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported
Wed Dec 26 15:18:27 2018 kern.info kernel: [    6.813856] ipq806x-gmac-dwmac 37400000.ethernet eth1: registered PTP clock
Wed Dec 26 15:18:27 2018 kern.info kernel: [    7.834378] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
...
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.015710] Generic PHY fixed-0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:01, irq=POLL)
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.016654] dwmac1000: Master AXI performs any burst length
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.016672] ipq806x-gmac-dwmac 37400000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.016873] ipq806x-gmac-dwmac 37400000.ethernet eth1: registered PTP clock
...
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.020482] device eth1.1 entered promiscuous mode
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.020487] device eth1 entered promiscuous mode
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.066212] device eth1.127 entered promiscuous mode
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.120009] device eth1.34 entered promiscuous mode
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.162731] device eth1.10 entered promiscuous mode
...
Wed Dec 26 15:18:31 2018 daemon.notice netifd: Interface 'wan' is enabled
Wed Dec 26 15:18:31 2018 daemon.notice netifd: Interface 'wan' is setting up now
Wed Dec 26 15:18:31 2018 daemon.notice netifd: Interface 'wan' is now up
...
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.174821] Generic PHY fixed-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:00, irq=POLL)
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.175880] dwmac1000: Master AXI performs any burst length
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.175902] ipq806x-gmac-dwmac 37200000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
Wed Dec 26 15:18:31 2018 kern.info kernel: [   35.176061] ipq806x-gmac-dwmac 37200000.ethernet eth0: registered PTP clock
...
Wed Dec 26 15:18:32 2018 kern.info kernel: [   36.072469] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
Wed Dec 26 15:18:32 2018 daemon.notice netifd: Network device 'eth1' link is up
Wed Dec 26 15:18:32 2018 daemon.notice netifd: VLAN 'eth1.1' link is up
Wed Dec 26 15:18:32 2018 daemon.notice netifd: VLAN 'eth1.10' link is up
Wed Dec 26 15:18:32 2018 daemon.notice netifd: VLAN 'eth1.34' link is up
Wed Dec 26 15:18:32 2018 daemon.notice netifd: VLAN 'eth1.127' link is up
...
Wed Dec 26 15:18:32 2018 daemon.notice netifd: Network device 'eth0' link is up
Wed Dec 26 15:18:32 2018 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Dec 26 15:18:32 2018 kern.info kernel: [   36.232391] ipq806x-gmac-dwmac 37200000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
...
Wed Dec 26 15:18:47 2018 daemon.info procd: - init complete -
...
Wed Dec 26 18:09:06 2018 kern.err kernel: [ 1488.045291] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:06 2018 kern.err kernel: [ 1488.546134] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:07 2018 kern.err kernel: [ 1489.546246] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:09 2018 kern.err kernel: [ 1491.546705] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:13 2018 kern.err kernel: [ 1495.548558] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:17 2018 kern.err kernel: [ 1499.548584] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:21 2018 kern.err kernel: [ 1503.548245] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:25 2018 kern.err kernel: [ 1507.549643] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:29 2018 kern.err kernel: [ 1511.551169] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:33 2018 kern.err kernel: [ 1515.552148] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:09:37 2018 kern.err kernel: [ 1519.553088] ipq806x-gmac-dwmac 37200000.ethernet eth0: len 1990 larger than size (1536)
Wed Dec 26 18:24:05 2018 kern.alert kernel: [ 2387.041393] Unable to handle kernel paging request at virtual address 64616f86
Wed Dec 26 18:24:05 2018 kern.alert kernel: [ 2387.041483] pgd = c0204000
Wed Dec 26 18:24:05 2018 kern.alert kernel: [ 2387.047548] [64616f86] *pgd=00000000
07.01.20192051Base systemBug ReportVery LowHighDHCP not working properly. openwrt-18.06Unconfirmed Task Description

I have WRT3200ACM and also EX6150v2 both using openwrt 18.06.01. With their stock firmware, my IOT devices like Mi LED and Wemo will connect just fine. With OpenWrt, some devices just not getting IP from the router/AP. Also, relayd is not working when the main router is using OpenWrt. If I use stock firmware as main AP then all problem solved. Seems like something wrong with OpenWrt’s DHCP system. I have also tried 18.06 version.

18.01.20192062Base systemBug ReportVery LowHighMTU is not set to 1508/1500 when using PPPoEopenwrt-18.06Unconfirmed Task Description

TP-LINK Archer C7, OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152).

Use PPPoE for WAN. Set MTU to 1508.

Observe ifconfig result. MTU is set at 1492, it should be 1500.

Add

config interface ‘eth0’

option ifname 'eth0'
option mtu '1508'

to /etc/config/network, ensure PPPoE MTU (as above) is set to 1508 and restart the network/reboot the router.

Observe ifconfig result. MTU is set at 1500 as expected.

23.01.20192081Base systemBug ReportVery LowHighSnapShot Install for TP-Link Archer C20 AC750 Hardly Wo...openwrt-18.06Unconfirmed Task Description

Dear Colleagues:

1) I have been testing basic networking functions of OpenWrt 18.06.1 “full Install” version on the above captioned device since 2018-10-16. This was done through BIN file download and install process. The operations tested appeared to be fine.

2) I was instructed to try a “snapshot Install” version to see if a recent Kernel update (2018-12-14, see link below.) is performing as intended. Upon powering on this version in the existing test-bed, however, the DHCP client PCs (with Xubuntu OS) appeared to see the LAN service by having their addresses assigned and were able to get response from the gateway when PINGing it with 192.168.1.1. However, attempting to use a web browser to access the router homepage at 192.168.1.1 failed. Also, the PCs could not get PINGing response from one another. Perhaps the earliest tell-tail sign is that as soon as the router is powered on with the “snapshot version”, the 2.4G WiFi status indicator LED is turned on, while the “full Install” version does not.

3) To verify, I downloaded and installed both full and snapshot versions of current BIN files from the OpenWrt website today and verified their integrity by checking the check-sums first. The above symptoms appeared to be repeatable after going through the processes a couple cycles alternating between the two versions.

Thanks for your attention,

Abe (2019-01-23 15:58)


10.02.20192114Base systemBug ReportVery LowHighWG302v1 (ixp4xx-generic) LAN (eth0) start and then stop...openwrt-18.06Unconfirmed Task Description

Hello

Device: Netgear WG302v1 ixp4xx
FW: 18.06.1 & 18.06.2

Device problem occurs at boot.
During boot LAN (eth0) become ready (LEDs are lit) and then stop after ~2 or ~3 seconds (LEDs are off).
WAN (radio) interface seems working but Ethernet (eth0) is down.
Impossible to get it up because ifconfig up have no effect.

No packages are installed only stock zImage and Shashfs.

With 18.06.1 (default config, IP after flashing) :
OpenWRT say that ethO is up and ready but eth0 and LEDs are off.
Impossible to reach LuCi or ping a computer with IP 192.168.1.10 (connected through serial console on device)
At boot eth0 stay up sometimes ~ 1 of 20.

With 18.06.2 (default config, IP after flashing) :
It seems there are more information during boot.
Kernel is reporting that br-lan: port 1(eth0) entered disabled stat
ifconfig up/down has no effect.

Step to reproduce:
Flash & boot.

You can find included as attached file 18.06.1 & 18.06.2 dmesg boot log.

Kind Regards

05.03.20192162Base systemBug ReportVery LowHighLinksys 3200ACM stop to function, no connection out of ...openwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on Linksys WRT 3200ACM
- Software versions of OpenWrt/LEDE release, packages, etc.
OpenWrt 18.06.2 r7676-cddd7b4c77 / LuCI openwrt-18.06 branch (git-19.020.41695-6f6641d)
+ IGMProxy (followed this tuturial https://oldwiki.archive.openwrt.org/doc/howto/udp_multicast)
- Steps to reproduce

 I have a large network with arround 200 Virtual Machines connected to the router, this router is great and looks like it can handle all of my VMs easly (my ISP router break after 80VMs) but out of nowhere sometimes the router stop to function, I cannot connect to it from LAN or WLAN. I am not sure if this is related with the VMs or if it is another issue

I had remote logs active, and the last time this ocurred I got this from the logs:
root# nc -u -4 -l 5555

<30>Mar  5 00:38:13 OpenWrt logread[6094]: Logread connected to 10.0.10.1:5555
<28>Mar  5 00:38:26 OpenWrt odhcpd[1791]: DHCPV6 RENEW IA_NA from 00020000ab1119a3c79428a626de on br-lan: no binding
<29>Mar  5 00:41:05 OpenWrt netifd: wan (2068): udhcpc: sending renew to 10.141.0.1
<29>Mar  5 00:41:05 OpenWrt netifd: wan (2068): udhcpc: lease of 188.250.74.185 obtained, lease time 3600
<13>Mar  5 00:42:40 OpenWrt root: testLog “Blah1”
<28>Mar  5 00:43:43 OpenWrt odhcpd[1791]: DHCPV6 RENEW IA_NA from 00020000ab114ef36bcb13e12a6c on br-lan: no binding
<28>Mar  5 00:43:46 OpenWrt odhcpd[1791]: DHCPV6 RENEW IA_NA from 00020000ab11ec7b577aa4a2257e on br-lan: no binding
<28>Mar  5 00:47:21 OpenWrt odhcpd[1791]: DHCPV6 RENEW IA_NA from 00020000ab11ee5cdb55e31e9275 on br-lan: no binding
<28>Mar  5 00:48:45 OpenWrt odhcpd[1791]: DHCPV6 RENEW IA_NA from 00020000ab1119a3c79428a626de on br-lan: no binding
<30>Mar  5 00:49:14 OpenWrt dnsmasq-dhcp[2944]: DHCPREQUEST(br-lan) 10.0.0.202 00:50:56:96:e6:32
<30>Mar  5 00:49:14 OpenWrt dnsmasq-dhcp[2944]: DHCPACK(br-lan) 10.0.0.202 00:50:56:96:e6:32 zen
<28>Mar  5 00:53:21 OpenWrt odhcpd[1791]: DHCPV6 RENEW IA_NA from 00020000ab114ef36bcb13e12a6c on br-lan: no binding
<28>Mar  5 00:53:26 OpenWrt odhcpd[1791]: DHCPV6 RENEW IA_NA from 00020000ab11ec7b577aa4a2257e on br-lan: no binding
<28>Mar  5 00:58:16 OpenWrt odhcpd[1791]: DHCPV6 RENEW IA_NA from 00020000ab11ee5cdb55e31e9275 on br-lan: no binding

Right after I reset the router power I did an logread and could get this:

Tue Mar  5 00:42:43 2019 user.info kernel: [    3.202957] kmodloader: loading kernel modules from /etc/modules-boot.d/*
Tue Mar  5 00:42:43 2019 user.info kernel: [    3.234044] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Tue Mar  5 00:42:43 2019 user.info kernel: [    3.243296] init: - preinit -
Tue Mar  5 00:42:43 2019 kern.info kernel: [    3.395512] mvneta f1070000.ethernet tmp0: renamed from eth0
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    3.401750] random: procd: uninitialized urandom read (4 bytes read)
Tue Mar  5 00:42:43 2019 kern.info kernel: [    3.441356] mvneta f1034000.ethernet eth0: renamed from eth1
Tue Mar  5 00:42:43 2019 kern.info kernel: [    3.481320] mvneta f1070000.ethernet eth1: renamed from tmp0
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    3.699138] random: jshn: uninitialized urandom read (4 bytes read)
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    3.730488] random: jshn: uninitialized urandom read (4 bytes read)
Tue Mar  5 00:42:43 2019 kern.info kernel: [    3.892827] mvneta f1034000.ethernet eth0: configuring for fixed/sgmii link mode
Tue Mar  5 00:42:43 2019 kern.info kernel: [    3.900629] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Tue Mar  5 00:42:43 2019 kern.info kernel: [    3.906643] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Tue Mar  5 00:42:43 2019 kern.info kernel: [    3.914852] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    6.969318] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 821
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    6.989686] UBIFS (ubi0:1): recovery needed
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.049827] UBIFS (ubi0:1): recovery completed
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.054334] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.062207] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.072173] UBIFS (ubi0:1): FS size: 65138688 bytes (62 MiB, 513 LEBs), journal size 3301376 bytes (3 MiB, 26 LEBs)
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.082681] UBIFS (ubi0:1): reserved for root: 3076660 bytes (3004 KiB)
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.089325] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 0A2948E0-EE94-4D03-A2AA-5BDE63AE5BFC, small LPT model
Tue Mar  5 00:42:43 2019 user.info kernel: [    7.102478] mount_root: switching to ubifs overlay
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.148010] ubi1: attaching mtd9
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.236995] random: crng init done
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.240412] random: 3 urandom warning(s) missed due to ratelimiting
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.380723] ubi1: scanning is finished
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.388751] ubi1: attached mtd9 (name "syscfg", size 86 MiB)
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.394452] ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.401361] ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.408179] ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.415174] ubi1: good PEBs: 680, bad PEBs: 8, corrupted PEBs: 0
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.421208] ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.428462] ubi1: max/mean erase counter: 8/4, WL threshold: 4096, image sequence number: 876597111
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.437550] ubi1: available PEBs: 0, total reserved PEBs: 680, PEBs reserved for bad PEB handling: 32
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.446817] ubi1: background thread "ubi_bgt1d" started, PID 829
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.457387] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 835
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.477892] UBIFS (ubi1:0): recovery needed
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.535464] UBIFS (ubi1:0): recovery completed
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.539966] UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "syscfg"
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.547410] UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.557398] UBIFS (ubi1:0): FS size: 80375808 bytes (76 MiB, 633 LEBs), journal size 4063232 bytes (3 MiB, 32 LEBs)
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.567882] UBIFS (ubi1:0): reserved for root: 3796347 bytes (3707 KiB)
Tue Mar  5 00:42:43 2019 kern.notice kernel: [    7.574529] UBIFS (ubi1:0): media format: w4/r0 (latest is w5/r0), UUID 61E88146-E8C2-4229-B3CE-3F574E1AD339, small LPT model
Tue Mar  5 00:42:43 2019 user.warn kernel: [    7.587144] urandom-seed: Seeding with /etc/urandom.seed
Tue Mar  5 00:42:43 2019 kern.info kernel: [    7.620917] mvneta f1034000.ethernet eth0: Link is Down
Tue Mar  5 00:42:43 2019 user.info kernel: [    7.692743] procd: - early -
Tue Mar  5 00:42:43 2019 user.info kernel: [    7.695657] procd: - watchdog -
Tue Mar  5 00:42:43 2019 user.info kernel: [    8.294006] procd: - watchdog -
Tue Mar  5 00:42:43 2019 user.info kernel: [    8.297241] procd: - ubus -
Tue Mar  5 00:42:43 2019 user.info kernel: [    8.350566] procd: - init -
Tue Mar  5 00:42:43 2019 user.info kernel: [    8.457200] kmodloader: loading kernel modules from /etc/modules.d/*
Tue Mar  5 00:42:43 2019 kern.info kernel: [    8.465564] ip6_tables: (C) 2000-2006 Netfilter Core Team
Tue Mar  5 00:42:43 2019 kern.info kernel: [    8.472404] Loading modules backported from Linux version wt-2017-11-01-0-gfe248fc2c180
Tue Mar  5 00:42:43 2019 kern.info kernel: [    8.480456] Backport generated by backports.git v4.14-rc2-1-31-g86cf0e5d
Tue Mar  5 00:42:43 2019 kern.info kernel: [    8.493859] <<Marvell Mac80211 Wireless PCIE Network Driver version 10.3.8.0-20181114>>
Tue Mar  5 00:42:43 2019 kern.info kernel: [    8.501934] pci 0000:00:01.0: enabling device (0140 -> 0142)
Tue Mar  5 00:42:43 2019 kern.debug kernel: [    8.507713] ieee80211 phy0: priv->pcmd_buf = de040000  priv->pphys_cmd_buf = 1e040000
Tue Mar  5 00:42:43 2019 kern.debug kernel: [    8.560127] ieee80211 phy0: fw download start
Tue Mar  5 00:42:43 2019 kern.debug kernel: [    8.560132] ieee80211 phy0: ddr init: download start
Tue Mar  5 00:42:43 2019 kern.debug kernel: [    8.560509] ieee80211 phy0: ddr init: download complete
Tue Mar  5 00:42:43 2019 kern.debug kernel: [    8.698421] ieee80211 phy0: FwSize = 450732 downloaded Size = 450732 curr_iteration 65521
Tue Mar  5 00:42:43 2019 kern.debug kernel: [   11.560105] ieee80211 phy0: fw download complete
Tue Mar  5 00:42:43 2019 kern.info kernel: [   11.560137] ieee80211 phy0: device node: /soc/pcie/pcie@1,0
Tue Mar  5 00:42:43 2019 kern.debug kernel: [   11.575295] ieee80211 phy0: pcmd = de040000
Tue Mar  5 00:42:43 2019 kern.info kernel: [   11.593337] ieee80211 phy0: firmware version: 0x9030206
Tue Mar  5 00:42:43 2019 kern.info kernel: [   11.900106] ieee80211 phy0: firmware region code: 30
Tue Mar  5 00:42:43 2019 kern.info kernel: [   11.938916] ieee80211 phy0: 2G disabled, 5G enabled
Tue Mar  5 00:42:43 2019 kern.info kernel: [   11.943846] ieee80211 phy0: 4 TX antennas, 4 RX antennas
Tue Mar  5 00:42:43 2019 kern.info kernel: [   11.949442] pci 0000:00:02.0: enabling device (0140 -> 0142)
Tue Mar  5 00:42:43 2019 kern.debug kernel: [   11.955288] ieee80211 phy1: priv->pcmd_buf = d98c0000  priv->pphys_cmd_buf = 198c0000
Tue Mar  5 00:42:43 2019 kern.debug kernel: [   11.963534] ieee80211 phy1: fw download start
Tue Mar  5 00:42:43 2019 kern.debug kernel: [   11.963540] ieee80211 phy1: ddr init: download start
Tue Mar  5 00:42:43 2019 kern.debug kernel: [   11.963922] ieee80211 phy1: ddr init: download complete
Tue Mar  5 00:42:43 2019 kern.debug kernel: [   12.105401] ieee80211 phy1: FwSize = 450732 downloaded Size = 450732 curr_iteration 65527
Tue Mar  5 00:42:43 2019 kern.debug kernel: [   13.296113] ieee80211 phy1: fw download complete
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.296154] ieee80211 phy1: device node: /soc/pcie/pcie@2,0
Tue Mar  5 00:42:43 2019 kern.debug kernel: [   13.311376] ieee80211 phy1: pcmd = d98c0000
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.329129] ieee80211 phy1: firmware version: 0x9030206
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.636119] ieee80211 phy1: firmware region code: 30
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.668957] ieee80211 phy1: 2G enabled, 5G disabled
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.673887] ieee80211 phy1: 4 TX antennas, 4 RX antennas
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.681691] hidraw: raw HID events driver (C) Jiri Kosina
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.690270] Bluetooth: Core ver 2.22
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.693906] NET: Registered protocol family 31
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.698374] Bluetooth: HCI device and connection manager initialized
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.704792] Bluetooth: HCI socket layer initialized
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.709700] Bluetooth: L2CAP socket layer initialized
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.714807] Bluetooth: SCO socket layer initialized
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.720159] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.725501] Bluetooth: BNEP filters: protocol multicast
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.730788] Bluetooth: BNEP socket layer initialized
Tue Mar  5 00:42:43 2019 kern.info kernel: [   13.736995] Bluetooth: vendor=0x2df, device=0x9136, class=255, fn=2
Tue Mar  5 00:42:43 2019 kern.info kernel: [   14.523809] Bluetooth: FW download over, size 695532 bytes
Tue Mar  5 00:42:43 2019 kern.err kernel: [   15.120137] sdio platform data not available
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.120809] usbcore: registered new interface driver btusb
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.131483] Bluetooth: HCI UART driver ver 2.3
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.135948] Bluetooth: HCI UART protocol H4 registered
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.141118] Bluetooth: HCI UART protocol BCSP registered
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.146452] Bluetooth: HCI UART protocol ATH3K registered
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.152373] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.158323] Bluetooth: HIDP socket layer initialized
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.163866] ip_tables: (C) 2000-2006 Netfilter Core Team
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.174072] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.181224] mwifiex_sdio mmc0:0001:1: WLAN FW already running! Skip FW dnld
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.188222] mwifiex_sdio mmc0:0001:1: WLAN FW is active
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.197355] Bluetooth: RFCOMM TTY layer initialized
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.202295] Bluetooth: RFCOMM socket layer initialized
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.207470] Bluetooth: RFCOMM ver 1.11
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.213242] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x242 error, result=0x2
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.220270] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd 0x242 failed during    initialization
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.231851] xt_time: kernel timezone is -0000
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.238144] PPP generic driver version 2.4.2
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.242945] NET: Registered protocol family 24
Tue Mar  5 00:42:43 2019 user.info kernel: [   15.248149] kmodloader: done loading kernel modules from /etc/modules.d/*
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.280879] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p71)
Tue Mar  5 00:42:43 2019 kern.info kernel: [   15.288929] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (15.68.7.p71)
Tue Mar  5 00:42:43 2019 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Tue Mar  5 00:42:43 2019 daemon.info logread[1570]: failed to send log data to 10.0.10.1:5555 via udp
Tue Mar  5 00:42:43 2019 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: started, version 2.80 cachesize 150
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: DNS service limited to local subnets
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: using local addresses only for domain test
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: using local addresses only for domain onion
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: using local addresses only for domain localhost
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: using local addresses only for domain local
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: using local addresses only for domain invalid
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: using local addresses only for domain bind
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: using local addresses only for domain lan
Tue Mar  5 00:42:43 2019 daemon.warn dnsmasq[1668]: no servers found in /tmp/resolv.conf.auto, will retry
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: read /etc/hosts - 4 addresses
Tue Mar  5 00:42:43 2019 daemon.info dnsmasq[1668]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Tue Mar  5 00:42:43 2019 authpriv.info dropbear[1695]: Not backgrounding
Tue Mar  5 00:42:43 2019 user.notice : Added device handler type: tunnel
Tue Mar  5 00:42:43 2019 user.notice : Added device handler type: Network device
Tue Mar  5 00:42:43 2019 user.notice : Added device handler type: bridge
Tue Mar  5 00:42:43 2019 user.notice : Added device handler type: veth
Tue Mar  5 00:42:43 2019 user.notice : Added device handler type: macvlan
Tue Mar  5 00:42:43 2019 user.notice : Added device handler type: 8021ad
Tue Mar  5 00:42:43 2019 user.notice : Added device handler type: 8021q
Tue Mar  5 00:42:43 2019 daemon.notice procd: /etc/init.d/network: 'radio2' is disabled
Tue Mar  5 00:42:43 2019 daemon.notice procd: /etc/init.d/network: 'radio2' is disabled
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/dhcp
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/radvd
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/wireless reload dependency on /etc/config/network
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/luci-splash
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/qos
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/miniupnpd
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/dhcp reload dependency on /etc/config/odhcpd
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up non-init /etc/config/fstab reload handler: /sbin/block mount
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/system reload trigger for non-procd /etc/init.d/led
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/luci_statistics
Tue Mar  5 00:42:43 2019 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/dhcp
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.425395] mvneta f1034000.ethernet eth0: configuring for fixed/sgmii link mode
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.432911] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.438808] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.446898] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.454694] br-lan: port 1(eth0.1) entered blocking state
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.460165] br-lan: port 1(eth0.1) entered disabled state
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.465718] device eth0.1 entered promiscuous mode
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.470541] device eth0 entered promiscuous mode
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.476222] br-lan: port 1(eth0.1) entered blocking state
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.481680] br-lan: port 1(eth0.1) entered forwarding state
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.487364] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'lan' is enabled
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'lan' is setting up now
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'lan' is now up
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'loopback' is enabled
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'loopback' is setting up now
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'loopback' is now up
Tue Mar  5 00:42:44 2019 daemon.notice procd: /etc/rc.d/S96led: setting up led WAN
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.499084] mvneta f1070000.ethernet eth1: configuring for fixed/rgmii-id link mode
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.507362] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.513433] mvneta f1070000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
Tue Mar  5 00:42:44 2019 kern.info kernel: [   16.523133] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'wan' is enabled
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'wan6' is enabled
Tue Mar  5 00:42:44 2019 daemon.notice netifd: bridge 'br-lan' link is up
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'lan' has link connectivity
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Network device 'eth0' link is up
Tue Mar  5 00:42:44 2019 daemon.notice netifd: VLAN 'eth0.1' link is up
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Network device 'lo' link is up
Tue Mar  5 00:42:44 2019 daemon.notice procd: /etc/rc.d/S96led: setting up led USB 1
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'loopback' has link connectivity
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Network device 'eth1' link is up
Tue Mar  5 00:42:44 2019 daemon.notice netifd: VLAN 'eth1.12' link is up
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'wan' is setting up now
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'wan6' has link connectivity
Tue Mar  5 00:42:44 2019 daemon.notice netifd: Interface 'wan6' is setting up now
Tue Mar  5 00:42:44 2019 daemon.notice procd: /etc/rc.d/S96led: setting up led USB 2
Tue Mar  5 00:42:44 2019 daemon.notice procd: /etc/rc.d/S96led: setting up led USB 2 SS
Tue Mar  5 00:42:44 2019 daemon.notice netifd: wan (2080): udhcpc: started, v1.28.4
Tue Mar  5 00:42:44 2019 daemon.err odhcp6c[2074]: Failed to send RS (Address not available)
Tue Mar  5 00:42:44 2019 daemon.info logread[1570]: Logread connected to 10.0.10.1:5555
Tue Mar  5 00:42:44 2019 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Tue Mar  5 00:42:44 2019 daemon.notice netifd: wan (2080): udhcpc: sending discover
Tue Mar  5 00:42:44 2019 user.notice mac80211: Failed command: iw phy phy0 set antenna all all
Tue Mar  5 00:42:44 2019 user.notice mac80211: Failed command: iw phy phy1 set antenna all all
Tue Mar  5 00:42:44 2019 daemon.notice netifd: radio0 (2027): command failed: Not supported (-95)
Tue Mar  5 00:42:44 2019 daemon.notice netifd: radio1 (2028): command failed: Not supported (-95)
Tue Mar  5 00:42:44 2019 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Tue Mar  5 00:42:44 2019 user.notice mac80211: Failed command: iw phy phy1 set distance 0
Tue Mar  5 00:42:44 2019 daemon.err odhcp6c[2074]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
Tue Mar  5 00:42:44 2019 daemon.info procd: - init complete -
Tue Mar  5 00:42:44 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Tue Mar  5 00:42:44 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Tue Mar  5 00:42:44 2019 kern.debug kernel: [   17.273258] ieee80211 phy0: change: 0xffffffff
Tue Mar  5 00:42:44 2019 kern.info kernel: [   17.379338] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Tue Mar  5 00:42:45 2019 kern.debug kernel: [   17.558204] ieee80211 phy1: change: 0xffffffff
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.647358] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.653379] br-lan: port 2(wlan0) entered blocking state
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.658719] br-lan: port 2(wlan0) entered disabled state
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.664173] device wlan0 entered promiscuous mode
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.668926] br-lan: port 2(wlan0) entered blocking state
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.674271] br-lan: port 2(wlan0) entered forwarding state
Tue Mar  5 00:42:45 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.679901] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.686973] br-lan: port 2(wlan0) entered disabled state
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.693189] br-lan: port 3(wlan1) entered blocking state
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.698534] br-lan: port 3(wlan1) entered disabled state
Tue Mar  5 00:42:45 2019 kern.info kernel: [   17.704004] device wlan1 entered promiscuous mode
Tue Mar  5 00:42:45 2019 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Mar  5 00:42:45 2019 daemon.notice netifd: wan (2080): udhcpc: sending select for 188.250.74.185
Tue Mar  5 00:42:45 2019 daemon.err odhcp6c[2074]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
Tue Mar  5 00:42:45 2019 daemon.notice netifd: wan (2080): udhcpc: lease of 188.250.74.185 obtained, lease time 3600
Tue Mar  5 00:42:45 2019 daemon.notice netifd: Interface 'wan' is now up
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: reading /tmp/resolv.conf.auto
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: using local addresses only for domain test
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: using local addresses only for domain onion
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: using local addresses only for domain localhost
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: using local addresses only for domain local
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: using local addresses only for domain invalid
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: using local addresses only for domain bind
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: using local addresses only for domain lan
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: using nameserver 212.55.154.174#53
Tue Mar  5 00:42:45 2019 daemon.info dnsmasq[1668]: using nameserver 212.55.154.190#53
Tue Mar  5 00:42:45 2019 user.notice firewall: Reloading firewall due to ifup of wan (eth1.12)
Tue Mar  5 00:42:45 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar  5 00:42:46 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar  5 00:42:46 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar  5 00:42:48 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar  5 09:00:06 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[1668]: exiting on receipt of SIGTERM
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: started, version 2.80 cachesize 150
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: DNS service limited to local subnets
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq-dhcp[2970]: DHCP, IP range 10.0.0.100 -- 10.0.1.93, lease time 12h
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain test
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain onion
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain localhost
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain local
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain invalid
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain bind
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain lan
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: reading /tmp/resolv.conf.auto
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain test
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain onion
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain localhost
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain local
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain invalid
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain bind
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using local addresses only for domain lan
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using nameserver 212.55.154.174#53
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: using nameserver 212.55.154.190#53
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: read /etc/hosts - 4 addresses
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq[2970]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Tue Mar  5 09:00:06 2019 daemon.info dnsmasq-dhcp[2970]: read /etc/ethers - 0 addresses
Tue Mar  5 09:00:06 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar  5 09:00:07 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar  5 09:00:07 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar  5 09:00:08 2019 daemon.notice netifd: Interface 'wan6' is now up
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: reading /tmp/resolv.conf.auto
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using local addresses only for domain test
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using local addresses only for domain onion
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using local addresses only for domain localhost
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using local addresses only for domain local
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using local addresses only for domain invalid
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using local addresses only for domain bind
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using local addresses only for domain lan
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using nameserver 212.55.154.174#53
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using nameserver 212.55.154.190#53
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using nameserver 2001:8a0:2106:5:212:55:154:174#53
Tue Mar  5 09:00:08 2019 daemon.info dnsmasq[2970]: using nameserver 2001:8a0:2206:5:212:55:154:190#53
Tue Mar  5 09:00:08 2019 user.notice firewall: Reloading firewall due to ifup of wan6 (eth1.12)
Tue Mar  5 09:00:08 2019 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->HT_SCAN
Tue Mar  5 09:00:08 2019 kern.debug kernel: [   22.710474] ieee80211 phy0: change: 0x100
Tue Mar  5 09:00:08 2019 daemon.err hostapd: Using interface wlan1 with hwaddr 24:f5:a2:2d:dd:a9 and ssid "Smells Like Teen Spirit"
Tue Mar  5 09:00:08 2019 kern.debug kernel: [   22.723547] ieee80211 phy0: change: 0x40
Tue Mar  5 09:00:08 2019 kern.debug kernel: [   22.727756] ieee80211 phy1: change: 0x100
Tue Mar  5 09:00:08 2019 kern.debug kernel: [   22.740123] ieee80211 phy1: change: 0x42
Tue Mar  5 09:00:08 2019 kern.info kernel: [   22.879165] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Tue Mar  5 09:00:08 2019 kern.info kernel: [   22.885619] br-lan: port 3(wlan1) entered blocking state
Tue Mar  5 09:00:08 2019 kern.info kernel: [   22.890967] br-lan: port 3(wlan1) entered forwarding state
Tue Mar  5 09:00:08 2019 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->ENABLED
Tue Mar  5 09:00:08 2019 daemon.notice hostapd: wlan1: AP-ENABLED
Tue Mar  5 09:00:08 2019 kern.debug kernel: [   22.940119] ieee80211 phy0: change: 0x40
Tue Mar  5 09:00:08 2019 daemon.notice netifd: Network device 'wlan1' link is up
Tue Mar  5 09:00:08 2019 daemon.info hostapd: wlan1: STA 2c:3a:e8:4e:a0:47 IEEE 802.11: associated (aid 1)
Tue Mar  5 09:00:08 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 2c:3a:e8:4e:a0:47
Tue Mar  5 09:00:08 2019 daemon.info hostapd: wlan1: STA 00:06:66:93:9f:db IEEE 802.11: associated (aid 2)
Tue Mar  5 09:00:08 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 00:06:66:93:9f:db
Tue Mar  5 09:00:08 2019 kern.debug kernel: [   23.160120] ieee80211 phy0: change: 0x40
Tue Mar  5 09:00:08 2019 kern.debug kernel: [   23.260115] ieee80211 phy0: change: 0x100
Tue Mar  5 09:00:08 2019 daemon.err hostapd: Using interface wlan0 with hwaddr 24:f5:a2:2d:dd:aa and ssid "Smells Like Old"
Tue Mar  5 09:00:08 2019 kern.debug kernel: [   23.273384] ieee80211 phy0: change: 0x100
Tue Mar  5 09:00:08 2019 kern.debug kernel: [   23.286427] ieee80211 phy0: change: 0x42
Tue Mar  5 09:00:09 2019 kern.info kernel: [   23.457122] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Tue Mar  5 09:00:09 2019 kern.info kernel: [   23.463562] br-lan: port 2(wlan0) entered blocking state
Tue Mar  5 09:00:09 2019 kern.info kernel: [   23.468899] br-lan: port 2(wlan0) entered forwarding state
Tue Mar  5 09:00:09 2019 daemon.notice hostapd: wlan0: interface state HT_SCAN->ENABLED
Tue Mar  5 09:00:09 2019 daemon.notice hostapd: wlan0: AP-ENABLED
Tue Mar  5 09:00:09 2019 daemon.notice netifd: Network device 'wlan0' link is up
Tue Mar  5 09:00:09 2019 daemon.warn odhcpd[1792]: A default route is present but there is no public prefix on br-lan thus we don't announce a default route!
Tue Mar  5 09:00:09 2019 daemon.info hostapd: wlan1: STA 68:c6:3a:95:72:fe IEEE 802.11: associated (aid 3)
Tue Mar  5 09:00:09 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 68:c6:3a:95:72:fe
Tue Mar  5 09:00:11 2019 daemon.info dnsmasq-dhcp[2970]: DHCPDISCOVER(br-lan) 2c:3a:e8:4e:a0:47
Tue Mar  5 09:00:11 2019 daemon.info dnsmasq-dhcp[2970]: DHCPOFFER(br-lan) 10.0.0.189 2c:3a:e8:4e:a0:47
Tue Mar  5 09:00:11 2019 daemon.warn dnsmasq-dhcp[2970]: DHCP packet received on eth1 which has no address
Tue Mar  5 09:00:11 2019 daemon.info dnsmasq[2970]: read /etc/hosts - 4 addresses
Tue Mar  5 09:00:11 2019 daemon.info dnsmasq[2970]: read /tmp/hosts/odhcpd - 0 addresses
Tue Mar  5 09:00:11 2019 daemon.info dnsmasq[2970]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Tue Mar  5 09:00:11 2019 daemon.info dnsmasq-dhcp[2970]: read /etc/ethers - 0 addresses
Tue Mar  5 09:00:12 2019 daemon.info hostapd: wlan1: STA 68:c6:3a:95:76:cc IEEE 802.11: associated (aid 4)
Tue Mar  5 09:00:12 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 68:c6:3a:95:76:cc
Tue Mar  5 09:00:14 2019 daemon.info hostapd: wlan1: STA 2c:3a:e8:4e:a0:47 IEEE 802.11: authenticated
Tue Mar  5 09:00:14 2019 daemon.info hostapd: wlan1: STA 00:06:66:93:9f:db IEEE 802.11: authenticated
Tue Mar  5 09:00:14 2019 daemon.info hostapd: wlan1: STA 68:c6:3a:95:72:fe IEEE 802.11: authenticated
Tue Mar  5 09:00:14 2019 daemon.info hostapd: wlan1: STA 68:c6:3a:95:76:cc IEEE 802.11: authenticated
Tue Mar  5 09:00:14 2019 daemon.info hostapd: wlan1: STA d8:63:75:18:1f:c0 IEEE 802.11: associated (aid 5)
Tue Mar  5 09:00:14 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED d8:63:75:18:1f:c0
Tue Mar  5 09:00:15 2019 daemon.info dnsmasq-dhcp[2970]: DHCPDISCOVER(br-lan) 00:06:66:93:9f:db
Tue Mar  5 09:00:15 2019 daemon.info dnsmasq-dhcp[2970]: DHCPOFFER(br-lan) 10.0.0.157 00:06:66:93:9f:db
Tue Mar  5 09:00:15 2019 daemon.warn dnsmasq-dhcp[2970]: DHCP packet received on eth1 which has no address
Tue Mar  5 09:00:17 2019 daemon.info hostapd: wlan1: STA 5c:cf:7f:66:c0:b7 IEEE 802.11: associated (aid 6)
Tue Mar  5 09:00:17 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 5c:cf:7f:66:c0:b7
Tue Mar  5 09:00:19 2019 daemon.info dnsmasq-dhcp[2970]: DHCPDISCOVER(br-lan) 68:c6:3a:95:72:fe
Tue Mar  5 09:00:19 2019 daemon.info dnsmasq-dhcp[2970]: DHCPOFFER(br-lan) 10.0.0.111 68:c6:3a:95:72:fe
Tue Mar  5 09:00:19 2019 daemon.warn dnsmasq-dhcp[2970]: DHCP packet received on eth1 which has no address
Tue Mar  5 09:00:19 2019 daemon.info dnsmasq-dhcp[2970]: DHCPDISCOVER(br-lan) 2c:3a:e8:4e:a0:47
Tue Mar  5 09:00:19 2019 daemon.info dnsmasq-dhcp[2970]: DHCPOFFER(br-lan) 10.0.0.189 2c:3a:e8:4e:a0:47
06.03.20192166Base systemBug ReportVery LowHighOpenwrt 18.06.2 build fails when ext4 is not chosen as ...openwrt-18.06Unconfirmed Task Description

upply the following if possible:
- Raspberry Pi Zero
- 18.06.2
- Go into menu, choose only ‘squashfs’ with defaults and bcm2708 as target. The ‘rootfs’ option disappears, and the build script fails with make world:

Output follows:

./gen_rpi_sdcard_img.sh /data/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_musl_eabi/linux-brcm2708_bcm2708/tmp/openwrt-brcm2708-bcm2708-rpi-squashfs-factory.img.gz /data/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_musl_eabi/linux-brcm2708_bcm2708/tmp/openwrt-brcm2708-bcm2708-rpi-squashfs-factory.img.gz.boot /data/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_musl_eabi/linux-brcm2708_bcm2708/root.squashfs 20
+ '[' 4 -eq 5 ']'
+ echo 'SYNTAX: ./gen_rpi_sdcard_img.sh <file> <bootfs image> <rootfs image> <bootfs size> <rootfs size>'
SYNTAX: ./gen_rpi_sdcard_img.sh <file> <bootfs image> <rootfs image> <bootfs size> <rootfs size>

Looks like the script isn’t passing proper paramaters unless I select ext4 image as well as squashfs image.

17.03.20192192Base systemFeature RequestVery LowHighEFI compatible images neededopenwrt-18.06Unconfirmed Task Description

Currently we are only getting msdos based images for x86_64. Much of the new hardware for that platform is increasingly only UEFI based. Some motherboards allow for a CSM (bios) boot, but not all. I know there is a workaround documented in the wiki, but I was unable to get it to work.

With x86_64 hardware we can get much greater openvpn speeds vs an off the shelf router. This enhancement would be a win for all those wanting to build their own with newer more efficient hardware with excellent AES-NI support.


19.04.20192245KernelBug ReportVery LowHighПроблема при загрзуки прошивки на устройствоopenwrt-18.06Unconfirmed Task Description

/code>Supply the following if possible:
- An error occurs when downloading the firmware
-Work on Openwrt 18.06, MT7621 processor
-No devices were connected
Worried about the error with NAND and CPU0, unless of course, I correctly determined that they are the cause

 


04.05.20192266Base systemBug ReportVery LowHighA panic when i newer 1806 in Hyper-Vopenwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- x86_64 Hyper-V
- 18.06.2 offcial image with mwan3, python, bbr
-
https://imgur.com/a/4SthMpw

13.05.20192280PackagesBug ReportVery LowHighbridge iface with NO-CARRIER unreachable over ipv6openwrt-18.06Unconfirmed Task Description

Supply the following if possible:

- Device problem occurs on

ubus -S call system board

{”kernel”:”4.14.113”,”hostname”:”to”,”system”:”ARMv7 Processor rev 1 (v7l)”,”model”:”Turris Omnia”,”board_name”:”armada-385-turris-omnia”,”release”:{”distribution”:”TurrisOS”,”version”:”4.0-beta1”,”revision”:”0663455801”,”target”:”mvebu\/cortexa9”,”description”:”TurrisOS 4.0-beta1 0663455801”}}


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


- Steps to reproduce

With no client (NO-CARRIER) connected to the br-iface its ipv6 is not accessible whilst ipv4 is. Connecting a client to the br-iface and its ipv6 becomes accessible.

It would be expected that the br-iface is accessible not only via ipv4 but also ipv6 regardless of the Carrier state as long as the br-iface is up.

config globals 'globals'
	option ula_prefix 'fd30:d64c:1eed::/48'

config interface 'mgt'
	option type 'bridge'
	option bridge_empty '1'
	option proto 'static'
	option ipaddr '192.168.112.12'
	option netmask '255.255.255.0'
	list ip6addr 'fd30:d64c:1eed:4c3a::12'
	option ip6assign '64'
	option ip6hint '4c3a'
	option ip6ifaceid 'random'
	option ifname 'lan3'
ifstatus mgt
{
        "up": true,
        "pending": false,
        "available": true,
        "autostart": true,
        "dynamic": false,
        "uptime": 44703,
        "l3_device": "br-mgt",
        "proto": "static",
        "device": "br-mgt",
        "updated": [
                "addresses"
        ],
        "metric": 0,
        "dns_metric": 0,
        "delegation": true,
        "ipv4-address": [
                {
                        "address": "192.168.112.12",
                        "mask": 24
                }
        ],
        "ipv6-address": [
                {
                        "address": "fd30:d64c:1eed:4c3a::12",
                        "mask": 128
                }
        ],
        "ipv6-prefix": [

        ],
        "ipv6-prefix-assignment": [
                {
                        "address": "fd30:d64c:1eed:4c3a::",
                        "mask": 64,
                        "local-address": {
                                "address": "fd30:d64c:1eed:4c3a:17c8:d407:23a0:d524",
                                "mask": 64
                        }
                }
        ],
        "route": [

        ],
        "dns-server": [

        ],
        "dns-search": [

        ],
        "inactive": {
                "ipv4-address": [

                ],
                "ipv6-address": [

                ],
                "route": [

                ],
                "dns-server": [

                ],
                "dns-search": [

                ]
        },
        "data": {

        }
}
ip l show up | grep mgt
8: lan3@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-mgt state LOWERLAYERDOWN mode DEFAULT group default qlen 1000
18: br-mgt: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
ip -o a show br-mgt
18: br-mgt    inet 192.168.112.12/24 brd 192.168.112.255 scope global br-mgt\       valid_lft forever preferred_lft forever
18: br-mgt    inet6 fd30:d64c:1eed:4c3a:17c8:d407:23a0:d524/64 scope global tentative noprefixroute \       valid_lft forever preferred_lft forever
18: br-mgt    inet6 fd30:d64c:1eed:4c3a::12/128 scope global tentative \       valid_lft forever preferred_lft forever
  • ip routing tables of the br-iface with NO-CARRIER
ip route show table all dev br-mgt
192.168.112.0/24 proto kernel scope link src 192.168.112.12 linkdown
broadcast 192.168.112.0 table local proto kernel scope link src 192.168.112.12 linkdown
local 192.168.112.12 table local proto kernel scope host src 192.168.112.12
broadcast 192.168.112.255 table local proto kernel scope link src 192.168.112.12 linkdown
fd30:d64c:1eed:4c3a::12 proto kernel metric 256 linkdown pref medium
fd30:d64c:1eed:4c3a::/64 proto static metric 1024 linkdown pref medium
ff00::/8 table local metric 256 linkdown pref medium
 
  • ip routing tables of the br-iface with CARRIER
ip route show table all dev br-mgt
192.168.112.0/24 proto kernel scope link src 192.168.112.12
broadcast 192.168.112.0 table local proto kernel scope link src 192.168.112.12
local 192.168.112.12 table local proto kernel scope host src 192.168.112.12
broadcast 192.168.112.255 table local proto kernel scope link src 192.168.112.12
fd30:d64c:1eed:4c3a::12 proto kernel metric 256 pref medium
fd30:d64c:1eed:4c3a::/64 proto static metric 1024 pref medium
fe80::/64 proto kernel metric 256 pref medium
anycast fd30:d64c:1eed:4c3a:: table local proto kernel metric 0 pref medium
local fd30:d64c:1eed:4c3a::12 table local proto kernel metric 0 pref medium
local fd30:d64c:1eed:4c3a:17c8:d407:23a0:d524 table local proto kernel metric 0 pref medium
anycast fe80:: table local proto kernel metric 0 pref medium
local fe80::da58:d7ff:fe00:797a table local proto kernel metric 0 pref medium
ff00::/8 table local metric 256 pref medium

Comparing the ip routing tables of the different Carrier states it is apparent that NO-CARRIER state is short of a few routing entries pertaining to ipv6.

14.06.20192319PackagesBug ReportVery LowHighusbmode bug which is fixed in usb-modeswitch...openwrt-18.06Unconfirmed Task Description

I wrote a bug report but then the bug report said wrong token and I lost the report... :(

Now again but shorter version. The usb-modeswitch (which seems to be an openwrt project, a rewrite of original usb_modeswitch https://git.openwrt.org/project/usbmode.git ) needs to set some devices to config 0 before switching to config 3.

BTW this is fixed in usb-modeswitch... Here is the link to discussion about this:
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2710&start=22

Some devices need to be set to config 0 first to be able to switch to config 3. Otherwise they hang...

Here a working example:

root@OpenWrt:~# echo 0 > /sys/bus/usb/devices/1-2/bConfigurationValue
root@OpenWrt:~# echo 3 > /sys/bus/usb/devices/1-2/bConfigurationValue
root@OpenWrt:~# umbim -d /dev/cdc-wdm0 caps

devicetype: 0001 - embedded
cellularclass: 0001
voiceclass: 0001 - no-voice
simclass: 0002
dataclass: 8000003F
smscaps: 0003
controlcaps: 0001
maxsessions: 0003
deviceid: 867377023108313
firmwareinfo: 11.617.06.00.00
hardwareinfo: RM1ME909ASM

root@OpenWrt:~#

A non-working example (after reboot):

root@OpenWrt:~# echo 3 > /sys/bus/usb/devices/1-2/bConfigurationValue
root@OpenWrt:~# umbim -d /dev/cdc-wdm0 caps
ERROR: mbim message timeout
root@OpenWrt:~#

At least one other person in OpenWRT bug tracker confirms this:
https://bugs.openwrt.org/index.php?do=details&task_id=1424

Although he has another problem with looping messages (probably unrelated to this bug)
https://forum.openwrt.org/t/usbmode-sits-in-loop-after-install/12624

22.06.20192332Base systemBug ReportVery LowHighCustom DNS servers settings not work on WAN6 interface openwrt-18.06Waiting on reporter Task Description

Supply the following if possible:
- Device problem occurs on
x86-64 virtual machine hosted by ESXI6.7u2

- Software versions of OpenWrt/LEDE release, packages, etc.
OpenWrt 18.06.2 r7676-cddd7b4c77 / LuCI openwrt-18.06 branch (git-19.170.32094-4d6d8bc)

- Steps to reproduce
all steps performed on LUCI
1. Set WAN interface to ignore peer DNS to use custom DNS 127.0.0.1
2. Set WAN6 interface to ignore peer DNS to use custom DNS ::1
3. Start WAN (PPPOE) and WAN6 (DNCPv6 client)

issue: Check effective DNS, custom WAN6 DNS setting is ignored

/tmp/resolv.conf.auto
# Interface lan
nameserver 127.0.0.1
# Interface wan
nameserver 127.0.0.1
# Interface wan_6
nameserver 240e:58:c000:1600:180:168:255:118
nameserver 240e:58:c000:1000:116:228:111:18


24.06.20192336PackagesBuild FailureVery LowHighBuild fail with php7openwrt-18.06Unconfirmed Task Description

Hi all,
When using openwrt builder and adding package in make command, build fails because PHP7 packages are missing in repository and packages lists.
could you take a look please ?
have a nice day

25.06.20192339Base systemBug ReportVery LowHighFailed to download the package listopenwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: OpenWRT 18.06.2 inside lxc container
- Software versions of OpenWrt/LEDE release, packages, etc.: both amd64 and aarch64
- Steps to reproduce

$ opkg update
~ # opkg update
Downloading http://downloads.openwrt.org/releases/18.06.2/targets/x86/64/packages/Packages.gz Updated list of available packages in /var/opkg-lists/openwrt_core
Downloading http://downloads.openwrt.org/releases/18.06.2/targets/x86/64/packages/Packages.sig Signature check passed.
Downloading http://downloads.openwrt.org/releases/18.06.2/packages/x86_64/base/Packages.gz * Failed to download the package list from http://downloads.openwrt.org/releases/18.06.2/packages/x86_64/base/Packages.gz **


Showing tasks 1 - 50 of 908 Page 1 of 191 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing