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
06.02.20202817KernelBuild FailureVery LowLowcompiler complain 'asm/types.h' file not found when com...openwrt-19.07Unconfirmed Task Description

Compile on macOS 10.15.3 (19D76)

uname -a

Darwin TioudeMBP.lan 19.3.0 Darwin Kernel Version 19.3.0: Thu Jan  9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 x86_64 i386 MacBookPro11,5 Darwin

gcc –version

Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
Apple clang version 11.0.0 (clang-1100.0.33.17)
Target: x86_64-apple-darwin19.3.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

make target/linux/compile V=sc

make[1]: Entering directory `/Volumes/Coder/docker/openwrt/openwrt'
make[2]: Entering directory `/Volumes/Coder/docker/openwrt/openwrt/target/linux'
make[3]: Entering directory `/Volumes/Coder/docker/openwrt/openwrt/target/linux/x86'
rm -f /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/localversion
/Volumes/Coder/docker/openwrt/openwrt/scripts/kconfig.pl  + + /Volumes/Coder/docker/openwrt/openwrt/target/linux/generic/config-4.14 /Volumes/Coder/docker/openwrt/openwrt/target/linux/x86/config-4.14 /Volumes/Coder/docker/openwrt/openwrt/target/linux/x86/64/config-4.14 > /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.target
awk '/^(#[[:space:]]+)?CONFIG_KERNEL/{sub("CONFIG_KERNEL_","CONFIG_");print}' /Volumes/Coder/docker/openwrt/openwrt/.config >> /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.target
echo "# CONFIG_KALLSYMS_EXTRA_PASS is not set" >> /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.target
echo "# CONFIG_KALLSYMS_ALL is not set" >> /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.target
echo "CONFIG_KALLSYMS_UNCOMPRESSED=y" >> /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.target
/Volumes/Coder/docker/openwrt/openwrt/scripts/package-metadata.pl kconfig /Volumes/Coder/docker/openwrt/openwrt/tmp/.packageinfo /Volumes/Coder/docker/openwrt/openwrt/.config 4.14 > /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.override
/Volumes/Coder/docker/openwrt/openwrt/scripts/kconfig.pl 'm+' '+' /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.target /dev/null /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.override > /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.set
mv /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.set /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.old
grep -v INITRAMFS /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.old > /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.set
echo 'CONFIG_INITRAMFS_SOURCE=""' >> /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.set
echo '# CONFIG_INITRAMFS_FORCE is not set' >> /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.set
rm -rf /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/modules
cmp -s /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.set /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.prev || { cp /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.set /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config; cp /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.set /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.prev; }
export MAKEFLAGS= ; [ -d /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/user_headers ] || /Library/Developer/CommandLineTools/usr/bin/make -C /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167 HOSTCFLAGS="-O2 -I/Volumes/Coder/docker/openwrt/openwrt/staging_dir/host/include  -Wall -Wmissing-prototypes -Wstrict-prototypes" CROSS_COMPILE="x86_64-openwrt-linux-musl-" ARCH="x86" KBUILD_HAVE_NLS=no KBUILD_BUILD_USER="" KBUILD_BUILD_HOST="" KBUILD_BUILD_TIMESTAMP="Wed Jan 29 16:05:35 2020" KBUILD_BUILD_VERSION="0" HOST_LOADLIBES="-L/Volumes/Coder/docker/openwrt/openwrt/staging_dir/host/lib" CONFIG_SHELL="bash" V=1  cmd_syscalls= KERNELRELEASE=4.14.167 CC="x86_64-openwrt-linux-musl-gcc" INSTALL_HDR_PATH=/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/user_headers headers_install
grep '=[ym]' /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.config.set | LC_ALL=C sort | mkhash md5 > /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.vermagic
touch /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.configured
rm -f /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/vmlinux /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/System.map
/Library/Developer/CommandLineTools/usr/bin/make -C /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167 HOSTCFLAGS="-O2 -I/Volumes/Coder/docker/openwrt/openwrt/staging_dir/host/include  -Wall -Wmissing-prototypes -Wstrict-prototypes" CROSS_COMPILE="x86_64-openwrt-linux-musl-" ARCH="x86" KBUILD_HAVE_NLS=no KBUILD_BUILD_USER="" KBUILD_BUILD_HOST="" KBUILD_BUILD_TIMESTAMP="Wed Jan 29 16:05:35 2020" KBUILD_BUILD_VERSION="0" HOST_LOADLIBES="-L/Volumes/Coder/docker/openwrt/openwrt/staging_dir/host/lib" CONFIG_SHELL="bash" V=1  cmd_syscalls= KERNELRELEASE=4.14.167 CC="x86_64-openwrt-linux-musl-gcc" modules
make[4]: Entering directory `/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167'
/Library/Developer/CommandLineTools/usr/bin/make -f ./scripts/Makefile.build obj=arch/x86/entry/syscalls all
/Library/Developer/CommandLineTools/usr/bin/make -f ./scripts/Makefile.build obj=scripts/basic
rm -f .tmp_quiet_recordmcount
/Library/Developer/CommandLineTools/usr/bin/make -f ./scripts/Makefile.build obj=arch/x86/tools relocs
set -e; : '  CHK     include/config/kernel.release'; mkdir -p include/config/; 	echo "4.14.167$(bash ./scripts/setlocalversion .)" < include/config/auto.conf > include/config/kernel.release.tmp; if [ -r include/config/kernel.release ] && cmp -s include/config/kernel.release include/config/kernel.release.tmp; then rm -f include/config/kernel.release.tmp; else : '  UPD     include/config/kernel.release'; mv -f include/config/kernel.release.tmp include/config/kernel.release; fi
/Library/Developer/CommandLineTools/usr/bin/make -f ./scripts/Makefile.asm-generic \
	            src=uapi/asm obj=arch/x86/include/generated/uapi/asm
/Library/Developer/CommandLineTools/usr/bin/make -f ./scripts/Makefile.asm-generic \
	            src=asm obj=arch/x86/include/generated/asm
set -e; : '  CHK     include/generated/uapi/linux/version.h'; mkdir -p include/generated/uapi/linux/; 	(echo \#define LINUX_VERSION_CODE 265895; echo '#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))';) < Makefile > include/generated/uapi/linux/version.h.tmp; if [ -r include/generated/uapi/linux/version.h ] && cmp -s include/generated/uapi/linux/version.h include/generated/uapi/linux/version.h.tmp; then rm -f include/generated/uapi/linux/version.h.tmp; else : '  UPD     include/generated/uapi/linux/version.h'; mv -f include/generated/uapi/linux/version.h.tmp include/generated/uapi/linux/version.h; fi
rm -f include/linux/version.h
set -e; : '  CHK     include/generated/utsrelease.h'; mkdir -p include/generated/; 	if [ `echo -n "4.14.167" | wc -c ` -gt 64 ]; then echo '"4.14.167" exceeds 64 characters' >&2; exit 1; fi; (echo \#define UTS_RELEASE \"4.14.167\";) < include/config/kernel.release > include/generated/utsrelease.h.tmp; if [ -r include/generated/utsrelease.h ] && cmp -s include/generated/utsrelease.h include/generated/utsrelease.h.tmp; then rm -f include/generated/utsrelease.h.tmp; else : '  UPD     include/generated/utsrelease.h'; mv -f include/generated/utsrelease.h.tmp include/generated/utsrelease.h; fi
mkdir -p .tmp_versions ; rm -f .tmp_versions/*
/Library/Developer/CommandLineTools/usr/bin/make -f ./scripts/Makefile.build obj=.
mkdir -p kernel/
set -e; : '  CHK     include/generated/bounds.h'; mkdir -p include/generated/; 	(set -e; echo "#ifndef __LINUX_BOUNDS_H__"; echo "#define __LINUX_BOUNDS_H__"; echo "/*"; echo " * DO NOT MODIFY."; echo " *"; echo " * This file was generated by Kbuild"; echo " */"; echo ""; sed -ne 	's:^[[:space:]]*\.ascii[[:space:]]*"\(.*\)".*:\1:; /^->/{s:->#\(.*\):/* \1 */:; s:^->\([^ ]*\) [\$#]*\([^ ]*\) \(.*\):#define \1 \2 /* \3 */:; s:->::; p;}'; echo ""; echo "#endif" ) < kernel/bounds.s > include/generated/bounds.h.tmp; if [ -r include/generated/bounds.h ] && cmp -s include/generated/bounds.h include/generated/bounds.h.tmp; then rm -f include/generated/bounds.h.tmp; else : '  UPD     include/generated/bounds.h'; mv -f include/generated/bounds.h.tmp include/generated/bounds.h; fi
set -e; : '  CHK     include/generated/timeconst.h'; mkdir -p include/generated/; 	(echo 100 | bc -q kernel/time/timeconst.bc ) < kernel/time/timeconst.bc > include/generated/timeconst.h.tmp; if [ -r include/generated/timeconst.h ] && cmp -s include/generated/timeconst.h include/generated/timeconst.h.tmp; then rm -f include/generated/timeconst.h.tmp; else : '  UPD     include/generated/timeconst.h'; mv -f include/generated/timeconst.h.tmp include/generated/timeconst.h; fi
mkdir -p arch/x86/kernel/
set -e; : '  CHK     include/generated/asm-offsets.h'; mkdir -p include/generated/; 	(set -e; echo "#ifndef __ASM_OFFSETS_H__"; echo "#define __ASM_OFFSETS_H__"; echo "/*"; echo " * DO NOT MODIFY."; echo " *"; echo " * This file was generated by Kbuild"; echo " */"; echo ""; sed -ne 	's:^[[:space:]]*\.ascii[[:space:]]*"\(.*\)".*:\1:; /^->/{s:->#\(.*\):/* \1 */:; s:^->\([^ ]*\) [\$#]*\([^ ]*\) \(.*\):#define \1 \2 /* \3 */:; s:->::; p;}'; echo ""; echo "#endif" ) < arch/x86/kernel/asm-offsets.s > include/generated/asm-offsets.h.tmp; if [ -r include/generated/asm-offsets.h ] && cmp -s include/generated/asm-offsets.h include/generated/asm-offsets.h.tmp; then rm -f include/generated/asm-offsets.h.tmp; else : '  UPD     include/generated/asm-offsets.h'; mv -f include/generated/asm-offsets.h.tmp include/generated/asm-offsets.h; fi
mkdir -p ./tools
/Library/Developer/CommandLineTools/usr/bin/make LDFLAGS= MAKEFLAGS=" " O=/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167 subdir=tools -C ./tools/ objtool
mkdir -p /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool && /Library/Developer/CommandLineTools/usr/bin/make O=/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167 subdir=tools/objtool --no-print-directory -C objtool
error: unknown warning option '-Wstrict-aliasing=3'; did you mean '-Wstring-plus-int'? [-Werror,-Wunknown-warning-option]
/Library/Developer/CommandLineTools/usr/bin/make -C /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/build CFLAGS= LDFLAGS= /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/fixdep
/Library/Developer/CommandLineTools/usr/bin/make -f /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/build/Makefile.build dir=. obj=fixdep
/Library/Developer/CommandLineTools/usr/bin/make -C /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/lib/subcmd/ OUTPUT=/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/
/Library/Developer/CommandLineTools/usr/bin/make -C /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/build CFLAGS= LDFLAGS= /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/fixdep
/Library/Developer/CommandLineTools/usr/bin/make -f /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/build/Makefile.build dir=. obj=fixdep
  gcc -Wp,-MD,/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/.exec-cmd.o.d -Wp,-MT,/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/exec-cmd.o -Wbad-function-cast -Wdeclaration-after-statement -Wformat-security -Wformat-y2k -Winit-self -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wno-system-headers -Wold-style-definition -Wpacked -Wredundant-decls -Wshadow -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wwrite-strings -Wformat -fno-strict-aliasing -ggdb3 -Wall -Wextra -std=gnu99 -fPIC -O3 -Werror -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/include/ -D"BUILD_STR(s)=#s" -c -o /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/exec-cmd.o exec-cmd.c
In file included from exec-cmd.c:2:
In file included from /Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/include/linux/compiler.h:89:
/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/include/linux/types.h:10:10: fatal error: 'asm/types.h' file not found
#include <asm/types.h>
         ^~~~~~~~~~~~~
1 error generated.
mv: cannot stat '/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/.exec-cmd.o.tmp': No such file or directory
make[8]: *** [/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/exec-cmd.o] Error 1
make[7]: *** [/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/libsubcmd-in.o] Error 2
make[6]: *** [/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/objtool/libsubcmd.a] Error 2
make[5]: *** [objtool] Error 2
make[4]: *** [tools/objtool] Error 2
make[4]: Leaving directory `/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167'
make[3]: *** [/Volumes/Coder/docker/openwrt/openwrt/build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/.modules] Error 2
make[3]: Leaving directory `/Volumes/Coder/docker/openwrt/openwrt/target/linux/x86'
make[2]: *** [compile] Error 2
make[2]: Leaving directory `/Volumes/Coder/docker/openwrt/openwrt/target/linux'
time: target/linux/compile#1.48#1.67#3.81
make[1]: *** [target/linux/compile] Error 2
make[1]: Leaving directory `/Volumes/Coder/docker/openwrt/openwrt'
make: *** [target/linux/compile] Error 2

tree build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/include/asm

build_dir/target-x86_64_musl/linux-x86_64/linux-4.14.167/tools/include/asm
├── alternative-asm.h
├── atomic.h
├── barrier.h
├── bug.h
├── export.h
└── sections.h
07.02.20202818Base systemBug ReportVery LowLowCurrent time displayed incorrectly in v.19.07 system ta...openwrt-19.07Unconfirmed Task Description

- Device problem occurs on
Aerohive HiveAP-121

- Software versions of OpenWrt/LEDE release, packages, etc.
OpenWrt 19.07.1 r10911-c155900f66 / LuCI openwrt-19.07 branch git-20.029.45734-adbbd5c

- Steps to reproduce
This is evident when you have two AP (exact same hardware) side by side running v.19.07.1 and v.18.06.5

The issue:
After upgrading firmware from 18.06.5 to 19.07.1 we noticed that the current time reported incorrectly on the ‘System’ tab in GUI.

Please note, current time IS reported correctly in the ‘Status’ tab on both versions.

Please note, GUI is accessed using a desktop version of Debian GNU/Linux 10 (buster), with Firefox ESR 68.4.1esr (64-bit).

Please note, Firefox configuration has been modified - hardened to prevent remote sites code loaded to the browser to detect local time zone.

Using the same browser with the exact same configuration shows current time been displayed correctly in firmware v.18.06.5 and displayed incorrectly only on the system tab in firmware version 19.07.1.

Please see screenshots attached.

Development team - thank you for your efforts in writing this code and making it available free of charge. You guys are awesome! :)

Damien.


04.03.20202880KernelBug ReportVery LowLowwireless-regdb is outdated and faulty for at least "CH"...openwrt-19.07Assigned Task Description

The wireless-regdb Version 2019.06.03 has faulty Entries for at least “CH” and “LI”.
Some Ranges described for “CH” are even overlapping, which should not be the case AFAIK.

The Entries should actually be about the same as “DE”, fixed in commit 5dd4dbf709d38aab21cba0183cf26510054449f0 (git.kernel.org)

Source: See Link

05.03.20202884KernelBug ReportVery LowLowR7800 hangs and restarts after few daysopenwrt-19.07Unconfirmed Task Description

Supply the following if possible:
- NetGear r7800
- Openwrt 19.07.1 (But same on 18.06.X)

- Steps to reproduce.

 Just run for several days and it hangs. Yes this router is working hard (OpenVPN, Transmission, 3Proxy, external disk attached) 

Mar 5 11:09:19 OpenWrt kernel: [174516.662874] Unable to handle kernel NULL pointer dereference at virtual address 00000001
Mar 5 11:09:19 OpenWrt kernel: [174516.662886] pgd = c0204000
Mar 5 11:09:19 OpenWrt kernel: [174516.662897] [00000001] *pgd=00000000
Mar 5 11:09:19 OpenWrt kernel: [174516.662924] Internal error: Oops: 17 [#1] SMP ARM
Mar 5 11:09:19 OpenWrt kernel: [174516.662955] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY vhci_hcd usblp usbip_host usbip_core slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat sch_cake nf_conntrack sch_teql sch_sfq sch_red sch_prio
Mar 5 11:09:19 OpenWrt kernel: [174516.715123] sch_pie sch_multiq sch_gred sch_fq sch_dsmark sch_codel em_text em_nbyte em_meta em_cmp act_simple act_police act_pedit act_ipt act_gact act_csum libcrc32c sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred ledtrig_usbport nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb nat46 ip6_tunnel tunnel6 tun uas usb_storage uhci_hcd ext4 mbcache jbd2 crc32c_generic leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple ohci_platform ohci_hcd phy_qcom_dwc3 ahci ehci_platform sd_mod ahci_platform libahci_platform libahci libata scsi_mod ehci_hcd gpio_button_hotplug
Mar 5 11:09:19 OpenWrt kernel: [174516.778498] CPU: 0 PID: 5329 Comm: kworker/0:1 Not tainted 4.14.167 #0
Mar 5 11:09:19 OpenWrt kernel: [174516.800724] Hardware name: Generic DT based system
Mar 5 11:09:19 OpenWrt kernel: [174516.807255] Workqueue: events 0xc06542e8
Mar 5 11:09:19 OpenWrt kernel: [174516.812094] task: dcffd900 task.stack: d955e000
Mar 5 11:09:19 OpenWrt kernel: [174516.816261] pc : [<c07bdbf0>] lr : [<c0679b9c>] psr: 80000013
Mar 5 11:09:19 OpenWrt kernel: [174516.820953] sp : d955fd50 ip : 00000000 fp : dd769c28
Mar 5 11:09:19 OpenWrt kernel: [174516.827287] r10: 00000000 r9 : ffffffff r8 : 00000002
Mar 5 11:09:19 OpenWrt kernel: [174516.832584] r7 : d955fdd4 r6 : 20000013 r5 : 00000001 r4 : dd6406d8
Mar 5 11:09:19 OpenWrt kernel: [174516.837879] r3 : de806024 r2 : 1fffa6f0 r1 : 00000000 r0 : 00000001
Mar 5 11:09:19 OpenWrt kernel: [174516.844219] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none
Mar 5 11:09:19 OpenWrt kernel: [174516.850815] Control: 10c5787d Table: 5ba0806a DAC: 00000051
Mar 5 11:09:19 OpenWrt kernel: [174516.858107] Process kworker/0:1 (pid: 5329, stack limit = 0xd955e210)
Mar 5 11:09:19 OpenWrt kernel: [174516.863920] Stack: (0xd955fd50 to 0xd9560000)
Mar 5 11:09:19 OpenWrt kernel: [174516.870445] fd40: dd6406d8 00000001 20000013 c056ec00
Mar 5 11:09:19 OpenWrt kernel: [174516.874893] fd60: dd6406e4 fffffffe 00000000 c056fdd4 00000000 fffffffe 00000000 c033e164
Mar 5 11:09:19 OpenWrt kernel: [174516.883140] fd80: dd68f418 dd68f404 00000000 00000002 d955fdd4 c033e460 00000000 c0a158a8
Mar 5 11:09:19 OpenWrt kernel: [174516.891385] fda0: dd68f400 c0a13178 dd640780 00000002 2faf0800 2faf0800 23c34600 c033e4a8
Mar 5 11:09:19 OpenWrt kernel: [174516.899632] fdc0: 00000000 00003208 dd54c200 c0563e50 dd54c200 dd641400 2faf0800 23c34600
Mar 5 11:09:19 OpenWrt kernel: [174516.907879] fde0: dd54c200 dd640780 00000000 23c34600 dd4dac80 c0565674 dd4dac80 dd6404d8
Mar 5 11:09:19 OpenWrt kernel: [174516.916126] fe00: 23c34600 dd4cf900 2faf0800 2faf0800 23c34600 c05656a4 dd640780 23c34600
Mar 5 11:09:19 OpenWrt kernel: [174516.924371] fe20: 00000000 dd4dac80 dd7ad000 2faf0800 23c34600 c0565a6c dd769bc0 23c34600
Mar 5 11:09:19 OpenWrt kernel: [174516.932618] fe40: dd769c00 dda01010 dd7ad000 c0565ac8 dd78a200 dd769bc0 dd769c00 c05ad744
Mar 5 11:09:19 OpenWrt kernel: [174516.940865] fe60: c0a61004 00000000 dcc25140 dd7ad028 23c34600 2faf0800 00009c40 23c34600
Mar 5 11:09:19 OpenWrt kernel: [174516.949113] fe80: dcc25240 dcc2525c 00000000 dcc25280 000927c0 dcc3a200 dda07540 c0655234
Mar 5 11:09:19 OpenWrt kernel: [174516.957359] fea0: 00000000 c0654c74 00009c40 dcc3a200 00000000 c0a61004 00000000 00000001
Mar 5 11:09:19 OpenWrt kernel: [174516.965604] fec0: 000927c0 00000000 dda07540 c0651364 00000002 000c3500 000927c0 00000021
Mar 5 11:09:19 OpenWrt kernel: [174516.973851] fee0: dcc24380 dcc3a200 dcc24380 dcc24400 dcc24400 dcc25300 00000000 c065377c
Mar 5 11:09:19 OpenWrt kernel: [174516.982097] ff00: dcc243b8 00000000 dcc24384 dcc3a200 c0a1f104 00000000 00000000 c0654320
Mar 5 11:09:19 OpenWrt kernel: [174516.990343] ff20: dcc243b8 d750c280 dda07540 dda0a400 00000000 c03371d0 dda07558 ffffe000
Mar 5 11:09:19 OpenWrt kernel: [174516.998591] ff40: d750c280 dda07540 d750c298 dda07558 ffffe000 c0a02d00 00000008 c03376cc

 


16.03.20202904Base systemBug ReportVery LowLowusb-storage fails to load in pre-initopenwrt-19.07Unconfirmed Task Description

As per forum post:

https://forum.openwrt.org/t/usb-storage-fail-to-load-in-preinit/54903

Basically, installed openwrt, added external root, all looks correctly configured, but after reboot external root fails to mount.
searching in the logs we can see that usb-storage is only loaded after pre-init, but it is listed in /etc/modprobe-boot.d/ ... checking /rom/etc/modules-boot.d/ it is not there.

Either something is missing in the https://openwrt.org/docs/guide-user/additional-software/extroot_configuration to add the usb-storage to the pre-init, or something is broken that makes pre-init fail to load usb-storage when it should.

The same setup worked fine with a older openwrt version (15.01 IIRC)

Supply the following if possible:
- Device problem occurs on
asus wl-500w

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

- Steps to reproduce
Install openwrt
add external root
manually mount to confirm setup
reboot
external root not mounted nor switched to, logs show that usb-storage is only loaded after normal root is mounted
manual mount still works

 


22.03.20202919Base systemBug ReportVery LowLow18.06 to 19.07 upgrade fails [Netgear WNDR4300 v1]openwrt-19.07Unconfirmed Task Description

> If your device is not supported by the image You may encounter the error “Device not supported by this image” or “Image check failed”. In that case, please report the issue so that it can be fixed for the next 19.07.X minor release.

https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79


Tried to upgrade from

openwrt-18.06 branch (git-19.020.41695-6f6641d) / OpenWrt 18.06.2 r7676-cddd7b4c77

[to]

http://downloads.openwrt.org/releases/19.07.2/targets/ar71xx/nand/openwrt-19.07.2-ar71xx-nand-wndr4300-squashfs-sysupgrade.tar

I alternately receive the error “The connection was reset” or “Device not supported by this image”


> for LuCI: check “Force upgrade”

This option was not available

> for command-line sysupgrade: use sysupgrade -F -n <your-device-19.07-image-sysupgrade.bin>

This option succeeded and the new build is working normally, thanks

note: Once this issue is resolved, would it be feasible to host upgrade images on a free service like GitHub, so checks for new version could be performed through the web interface (similar to GL.Inet routers)

18.04.20203015KernelBug ReportVery LowLowag71xx crashes after increasing MTUopenwrt-19.07Unconfirmed Task Description

Tested on openwrt-19.07.2-ath79-generic-tplink_archer-c7-v5

Steps to reproduce:

root@OpenWrt:~# ip link set eth0 mtu 500
root@OpenWrt:~# ip link set eth0 down; ip link set eth0 up
root@OpenWrt:~# ip link set eth0 mtu 1500

After this, sending a large packet (ping -s 800) causes a kernel panic:

skbuff: skb_over_panic: text:802da154 len:846 put:846 head:8677e3e0 data:8677e422 tail:0x8677e770 end:0x8677e640 dev:<NULL>

The problem is the rx buffer management in target/linux/ath79/files/drivers/net/ethernet/atheros/ag71xx/ag71xx_main.c: ag71xx_change_mtu adjusts the MTU, but doesn’t adjust rx_buf_size (it’s only set in ag71xx_open).

The attached patch fixes it by always using a large receive buffer. Maybe it is better to change rx_buf_size from ag71xx_change_mtu, but I don’t know how to do that.

25.04.20203045KernelBug ReportVery LowLowIn kernel WiFi pcap filters filter too muchopenwrt-19.07Unconfirmed Task Description

In an Archer C7 just flashed with https://downloads.openwrt.org/releases/19.07.2/targets/ath79/generic/openwrt-19.07.2-ath79-generic-tplink_archer-c7-v2-squashfs-factory.bin (also with a custom build of the HEAD of the openwrt-19.07 branch) I find that “tcpdump -i wlan1 | grep Beacon” shows a lot of packets but “tcpdump -i wlan1 ‘type mgt subtype beacon’” doesn’t show anything (a packet from time to time, but very rarely and way less than without the filter). Doing the same after patching libpcap to force it to do the filtering in user-space fixes the issue.

04.05.20203065PackagesBug ReportVery LowLowiptables-mod-conntrack-extra package does not include c...openwrt-19.07Unconfirmed Task Description

The iptables-mod-conntrack-extra package does not include the connrate match extension.

There’s no mention of connrate in any other packages either, so as far as I can tell it doesn’t seem to be possible to use connrate on OpenWRT.

From the iptables documentation:


connrate

This module matches the current transfer rate in a connection.
connrate [!] [from]:[to]
Match against the current connection transfer rate being within ‘from’ and ‘to’ bytes per second. When the “!” argument is used before the range, the sense of the match is inverted.


16.05.20203100Base systemBug ReportVery LowLowminiupnpd.conf generated by /etc/init.d/miniupnpd uses ...openwrt-19.07Unconfirmed Task Description

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

  • OpenWrt 19.07.2, r10947-65030d81f3
  • miniupnpd - 2.1.20191006-4

I have both native IPv6 (wan_6 virtual interface from pppoe) and 6to4. I need 6to4 to connect to other 6to4 peers which is faster than native IPv6 (and sometimes native IPv6 cannot reach 6to4). /var/etc/miniupnpd.conf generated by /etc/init.d/miniupnpd uses 6to4 instead of native IPv6, the file contains the following lines

ext_ifname=pppoe-wan
ext_ifname6=6to4-wan6

I think it’s better to use native IPv6 interface by default.
Additionally, is it possible to add ipv6_disable option to the config? Buggy UPnP clients sometimes put IPv6 address in a IPv4 port mapping request, I’d like to check if disabling IPv6 UPnP would fix it, this problem is mentioned in https://github.com/miniupnp/miniupnp/issues/408

07.06.20203156KernelBug ReportVery LowLowsit non-ECTopenwrt-19.07Unconfirmed Task Description

Device: TP-Link Archer C6v2
OpenWrt: 19.07.3

When stateless mode enabled with 6in4 tunnel, kernel always spamming this errors. Anyway IPv6 working fine.

[  552.992200] sit: non-ECT from 193.0.203.203 with TOS=0xc1
[  553.672272] sit: non-ECT from 193.0.203.203 with TOS=0xc1
[  555.673655] sit: non-ECT from 193.0.203.203 with TOS=0xc1
[  559.668806] sit: non-ECT from 193.0.203.203 with TOS=0xc1
[  561.802355] sit: non-ECT from 193.0.203.203 with TOS=0xc1
[  561.803238] sit: non-ECT from 193.0.203.203 with TOS=0xc1
[  563.850841] sit: non-ECT from 193.0.203.203 with TOS=0xc1
[  565.898359] sit: non-ECT from 193.0.203.203 with TOS=0xc1
[  565.898456] sit: non-ECT from 193.0.203.203 with TOS=0xc1
[  565.899107] sit: non-ECT from 193.0.203.203 with TOS=0xc1


13.06.20203178Base systemBug ReportVery LowLowOpenWrt Radio 5.8Ghz PS4 slim openwrt-19.07Unconfirmed Task Description

I have a connection problem between PS4 slim in the 5.8 Ghz band
I am using a TpLink C59 OpenWrt router 19.07.3 r11063-85e04e9f46
All the devices work well in the 5.8GHz band but the PS4 does not link in the 5.8Hz band instead the PS4 works well in the 2.8Ghz band. I have this problem since I migrated to 19.07 with the previous version 18.06 the PS4 worked fine in band 5.8 Ghz
With all three versions of 19.07 the problem is the same.
I am using the Ar71xx driver but the problem repeats with Ath79
The PS4 works OK with other Access Points in band 5.8 Ghz
The failure also occurs without encryption and with a fixed IP.
From another device the ping fails when I ping against the PS4 in band 5.8 Ghz
Using the 2.4 GHz radio all OK
Someone had a similar problem.
Very good OpenWrt
Greetings and thanks


15.06.20203187Base systemBug ReportVery LowLowLinkSys 1900ACS - WLAN 5GHz - 802.11AC with 802.11N at...openwrt-19.07Unconfirmed Task Description

I was upgraded to my LinkSys WRT-1900ACS from LEDE 17.01.6 to OpenWRT 19.07.3.

With LEDE 17.01.6 I can set up 5GHz WLAN to use N and AC at the same time with two different SSID and with this setup some old devices can connect to this 5GHz WLAN with 802.11n correctly while my notebook can connect to 802.11AC on 5GHz network too (I used two different SSID setup both setting used 5GHz network).

After I upgraded to OpenWrt I found there is no option to set up both 802.11N and 802.11AC with 5GHz at the same time and my old WiFi devices need to use 2.4GHz network only.

With the OpenWrt 19.07.3 the ‘require_mode’ option can set globally so need to decide to use AC or N only for all 5GHz SSID.

Is there any way to set 5GHz with both N and AC at the same time or there is no option by technical reason?

20.06.20203193PackagesBuild FailureVery LowLowofficial bird2 build on ipq806x doesn't start and has b...openwrt-19.07Unconfirmed Task Description

Hi all,

I am running bird2 on Netgear R7800 for OSPF routing but it doesn’t start. Following are error messages I got:

# bird -c /etc/bird.conf -d
Bus error

# logread
Sat Jun 20 12:24:09 2020 daemon.info bird: Started
Sat Jun 20 12:24:09 2020 kern.err kernel: [572809.062848] Alignment trap: not handling instruction f44c0a1f at [<0006bb88>]
Sat Jun 20 12:24:09 2020 kern.alert kernel: [572809.062907] Unhandled fault: alignment exception (0x801) at 0x017c9634
Sat Jun 20 12:24:09 2020 kern.alert kernel: [572809.069111] pgd = d7668000
Sat Jun 20 12:24:09 2020 kern.alert kernel: [572809.075597] [017c9634] *pgd=5c0c6835, *pte=5ad3475f, *ppte=5ad34c7f


# dmesg
[571421.877597] Alignment trap: not handling instruction f44c0a1f at [<0006bb88>]
[571421.877645] Unhandled fault: alignment exception (0x801) at 0x0111b624
[571421.883832] pgd = dc258000
[571421.890385] [0111b624] *pgd=5e63a835, *pte=5c72975f, *ppte=5c729c7f

Environment
- OpenWrt 19.07.3, r11063-85e04e9f46
- bird2 - 2.0.7-2
- target ipq806x
- model Netgear R7800

# /etc/bird.conf
log syslog all;
router id 192.168.1.1;                                                                                                                                        
protocol device {                                                                                                                                       
}                                                                                                                                                       
protocol bfd {                                                                                                                                          
}                                                                                                                                                       
protocol direct {                                                                                                                                      
        interface "br-lan";                                                                                                                             
        ipv4;                   # Connect to default IPv4 table                                                                                         
        ipv6;                   # ... and to default IPv6 table                                                                                         
}                                                                                                                                                       
                                                                                                                                                        
# The Kernel protocol is not a real routing protocol. Instead of communicating                                                                          
# with other routers in the network, it performs synchronization of BIRD                                                                                
# routing tables with the OS kernel. One instance per table.                                                                                            
protocol kernel {                                                                                                                                       
        scan time 10;                                                                                                                                   
        merge paths;                                                                                                                                    
        ipv4 {                  # Connect protocol to IPv4 table by channel                                                                             
#             table master4;    # Default IPv4 table is master4                                                                                         
#             import all;       # Import to table, default is import all                                                                                
              export all;       # Export to protocol. default is export none                                                                            
        };                                                                                                                                              
#       learn;                  # Learn alien routes from the kernel                                                                                    
#       kernel table 10;        # Kernel table to synchronize with (default: main)                                                                      
}                                                                                                                                                       
                                                                                                                                                        
# Another instance for IPv6, skipping default options                                                                                                   
protocol kernel {                                                                                                                                       
        scan time 10;                                                                                                                                   
        merge paths;                                                                                                                                    
        ipv6 { export all; };                                                                                                                           
}                                                                                                                                                       
                                                                                                                                                        
# OSPF example, both OSPFv2 and OSPFv3 are supported                                                                                                    
protocol ospf v2 ospf4 {                                                                                                                                
        ipv4 {                                                                                                                                          
        };                                                                                                                                              
        area 0 {                                                                                                                                        
                interface "br-lan" {bfd;};                                                                                                              
        };                                                                                                                                              
}

This issue can be reproduced with the latest OpenWrt release 19.07.3, but it has been there for a long time.
A custom build of bird2 package with OpenWRT SDK doesn’t have this issue.

I am not sure this is the right place to report this issue. Could anyone help with this?

20.06.20203194KernelBug ReportVery LowLowKernel option needed for Atheros AR9565 mini-pcie compa...openwrt-19.07Unconfirmed Task Description

I have an x86_64 system with an Atheros AR9565 mini-pcie which is not recognized by Openwrt unless I recompile with the following options:
CONFIG_PACKAGE_kmod-ath9k=y
CONFIG_ATH9K_SUPPORT_PCOEM=y

I’m using Openwrt 19.07.3. In the prebuilt images I believe kmod-ath9k is being compiled with CONFIG_ATH9K_SUPPORT_PCOEM defaulting to =n. Is it possible to get this changed to CONFIG_ATH9K_SUPPORT_PCOEM=y in future prebuilt releases?

Thanks!

21.06.20203196Base systemBug ReportVery LowLowOpenWRT on Freescale's P2020RDBopenwrt-19.07Unconfirmed Task Description

I’m trying to run OpenWRT on a P2020RDB board, I managed to fetch the release mpc85xx initramfs.bin from here (I failed to get the snapshot one for Freescale over here as I received a 403 error), and then I pulled it into uboot using tftpboot, and placed it at address “0×1000000“, and ran “bootm 0×1000000” the kernel starts and then I get a call trace and some stuff get dumped:

XTM-330_P2020(FAILSAFE) => bootm 0x1000000                                                                                                                      [165/195]
WARNING: adjusting available memory to 30000000                                                                                                                          
## Booting kernel from FIT Image at 01000000 ...                                                                                                                         
   Using 'config@1' configuration                                                                                                                                        
   Trying 'kernel@1' kernel subimage                                                                                                                                     
     Description:  POWERPC OpenWrt Linux-4.14.180                                                                                                                        
     Type:         Kernel Image                                                                                                                                          
     Compression:  gzip compressed                                                                                                                                       
     Data Start:   0x010000ec                                                                                                                                            
     Data Size:    5128735 Bytes = 4.9 MiB                                                                                                                               
     Architecture: PowerPC                                                                                                                                               
     OS:           Linux                                                                                                                                                 
     Load Address: 0x00000000
     Entry Point:  0x00000000
     Hash algo:    crc32
     Hash value:   7754597c
     Hash algo:    sha1
     Hash value:   bd433c824dc74e015b759f3ab53ffe996b130f2e
   Verifying Hash Integrity ... crc32+ sha1+ OK
## Flattened Device Tree from FIT Image at 01000000
   Using 'config@1' configuration
   Trying 'fdt@1' FDT blob subimage
     Description:  POWERPC OpenWrt p2020rdb device tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x014e4448
     Data Size:    12550 Bytes = 12.3 KiB
     Architecture: PowerPC
     Hash algo:    crc32
     Hash value:   0d1ae91a
     Hash algo:    sha1
     Hash value:   fdbac0f412982769bdef3ba414fc6716b8a855d4
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Booting using the fdt blob at 0x14e4448 
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 00ff9000, end 00fff105 ... OK
[    0.000000] Memory CAM mapping: 256/256/256 Mb, residual: 256Mb
[    0.000000] Linux version 4.14.180 (builder@buildhost) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 r11063-85e04e9f46)) #0 SMP Sat May 16 18:32:20 2020
[    0.000000] Using P2020 RDB machine description
[    0.000000] bootconsole [udbg0] enabled
[    0.000000] CPU maps initialized for 1 thread per core
[    0.000000] -----------------------------------------------------
[    0.000000] phys_mem_size     = 0x30000000
[    0.000000] dcache_bsize      = 0x20
[    0.000000] icache_bsize      = 0x20
[    0.000000] cpu_features      = 0x0000000012100460
[    0.000000]   possible        = 0x0000000012120460
[    0.000000]   always          = 0x0000000000100000
[    0.000000] cpu_user_features = 0x84e08000 0x08000000
[    0.000000] mmu_features      = 0x00020010
[    0.000000] -----------------------------------------------------
mpc85xx_rdb_setup_arch()
[    0.000000] mpc85xx_qe_init: Could not find Quicc Engine node
[    0.000000] MPC85xx RDB board from Freescale Semiconductor
[    0.000000] barrier-nospec: using isync; sync as speculation barrier
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000000000-0x000000002fffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x000000002fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000002fffffff]
[    0.000000] MMU: Allocated 1088 bytes of context maps for 255 contexts
[    0.000000] percpu: Embedded 12 pages/cpu s18380 r8192 d22580 u49152
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 195072
[    0.000000] Kernel command line: root=/dev/sda1 rw rootdelay=30 console=ttyS0,115200 ramdisk_size=600000
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 705444K/786432K available (4400K kernel code, 176K rwdata, 548K rodata, 2620K init, 216K bss, 80988K reserved, 0K cma-reserved)
[    0.000000] Kernel virtual memory layout:
[    0.000000]   * 0xfffdf000..0xfffff000  : fixmap
[    0.000000]   * 0xfdffe000..0xfe000000  : early ioremap
[    0.000000]   * 0xf1000000..0xfdffe000  : vmalloc & ioremap
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16
[    0.000000] mpic: Setting up MPIC " OpenPIC  " version 1.2 at ffe40000, max 2 CPUs
[    0.000000] mpic: ISU size: 256, shift: 8, mask: ff
[    0.000000] mpic: Initializing for 256 sources
[    0.000000] mpc85xx_rdb_pic_init: Could not find qe-ic node
[    0.000010] clocksource: timebase: mask: 0xffffffffffffffff max_cycles: 0xf6018975a, max_idle_ns: 440795204712 ns
[    0.010162] clocksource: timebase mult[f000003] shift[24] registered
[    0.016543] pid_max: default: 32768 minimum: 301
[    0.021182] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.027710] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.035198] mpic: requesting IPIs...
[    0.039003] Hierarchical SRCU implementation.
[    0.043596] smp: Bringing up secondary CPUs ...
[    0.048509] smp: Brought up 1 node, 2 CPUs
[    0.052518] Using shared cache scheduler topology
[    0.058928] random: get_random_u32 called from 0xc0201c80 with crng_init=0
[    0.065843] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.075502] futex hash table entries: 512 (order: 2, 16384 bytes)
[    0.081889] NET: Registered protocol family 16
[    0.094212] Found FSL PCI host bridge at 0x00000000ffe0a000. Firmware bus number: 0->0
[    0.102052] PCI host bridge /pcie@ffe0a000 (primary) ranges:
[    0.107677]  MEM 0x0000000080000000..0x000000009fffffff -> 0x0000000080000000 
[    0.114869]   IO 0x00000000ffc00000..0x00000000ffc0ffff -> 0x0000000000000000
[    0.121993] /pcie@ffe0a000: PCICSRBAR @ 0xfff00000
[    0.126746] setup_pci_atmu: end of DRAM 30000000
[    0.131344] /pcie@ffe0a000: Setting PCI inbound window greater than memory size
[    0.146042] PCI: Probing PCI hardware
[    0.149766] fsl-pci ffe0a000.pcie: PCI host bridge to bus a000:00
[    0.155778] pci_bus a000:00: root bus resource [io  0x0000-0xffff]
[    0.161927] pci_bus a000:00: root bus resource [mem 0x80000000-0x9fffffff]
[    0.168774] pci_bus a000:00: root bus resource [bus 00-ff]
[    0.174535] pci a000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.182529] pci a000:00:00.0: PCI bridge to [bus 01-ff]
[    0.187722] PCI: Cannot allocate resource region 0 of device a000:00:00.0, will remap
[    0.195494] pci a000:00:00.0: BAR 0: no space for [mem size 0x00100000]
[    0.202057] pci a000:00:00.0: BAR 0: failed to assign [mem size 0x00100000]
[    0.208993] pci a000:00:00.0: PCI bridge to [bus 01]
[    0.213933] pci a000:00:00.0:   bridge window [io  0x0000-0xffff]
[    0.220002] pci a000:00:00.0:   bridge window [mem 0x80000000-0x9fffffff]
[    0.226764] pci_bus a000:00: Some PCI device resources are unassigned, try booting with pci=realloc
[    0.235925] /soc@ffe00000/timer@41100: cannot get timer frequency.
[    0.242059] /soc@ffe00000/timer@42100: cannot get timer frequency.
[    0.254462] clocksource: Switched to clocksource timebase
[    0.260493] NET: Registered protocol family 2
[    0.265162] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.272178] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.278670] TCP: Hash tables configured (established 8192 bind 8192)
[    0.285022] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.290884] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.297300] NET: Registered protocol family 1
[    2.607509] Crashlog allocated RAM at address 0x3f00000
[    2.612901] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[    2.622935] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    2.628700] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    2.639761] io scheduler noop registered
[    2.643605] io scheduler deadline registered (default)
[    2.649567] pcieport a000:00:00.0: enabling device (0106 -> 0107)
[    2.655875] pcieport a000:00:00.0: AER enabled with IRQ 24
[    2.661445] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
rserial8250.0: ttyS0 at MMIO 0xffe04500 (irq = 42, base_baud = 33333333) is a 16550A
[    2.681148] console [ttyS0] enabled
[    2.681148] console [ttyS0] enabled
[    2.688069] bootconsole [udbg0] disabled
[    2.688069] bootconsole [udbg0] disabled
[    2.696040] serial8250.0: ttyS1 at MMIO 0xffe04600 (irq = 42, base_baud = 33333333) is a 16550A
[    2.705190] console [ttyS0] disabled
[    2.708811] console [ttyS0] enabled
[    2.712565] ffe04600.serial: ttyS1 at MMIO 0xffe04600 (irq = 42, base_baud = 33333333) is a 16550
[    2.722481] Disabling lock debugging due to kernel taint
[    2.722487] fsl-lbc ffe05000.localbus: Chip select error: LTESR 0x00080000
[    2.734643] Machine check in kernel mode.
[    2.738637] Caused by (from MCSR=10008): 
[    2.738640] Bus - Read Data Bus Error
[    2.746282] Oops: Machine check, sig: 7 [#1]
[    2.750535] BE SMP NR_CPUS=2 P2020 RDB
[    2.754272] Modules linked in:
[    2.757319] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G   M            4.14.180 #0
[    2.764610] task: ef448000 task.stack: ef450000
[    2.769125] NIP:  c02995d0 LR: c028f240 CTR: c02995b0
[    2.774161] REGS: effe3f10 TRAP: 0204   Tainted: G   M             (4.14.180)
[    2.781276] MSR:  00029000 <CE,EE,ME>  CR: 24000282  XER: 00000000
[    2.787449] DEAR: f1200000 ESR: 00800000 
[    2.787449] GPR00: c028f524 ef451c20 ef448000 ef451c34 ef49c91c 00000020 ef451cc8 ef451cc8 
[    2.787449] GPR08: 00000002 00000002 f1200000 00000002 24000282 00000000 c049ae20 c049a00c 
[    2.787449] GPR16: c049ad84 c049adc0 c049add8 ef48f158 00000000 c049ad50 ef49c910 01000000 
[    2.787449] GPR24: c049a000 00000000 00000000 00000000 00000000 00000022 00000002 ef49c91c 
[    2.824804] Call Trace:
[    2.827240] [ef451c20] [ef451cd0] 0xef451cd0 (unreliable)
[    2.832625] [ef451c60] [c028f524] 0xc028f524
[    2.836882] [ef451c80] [c028e3dc] 0xc028e3dc
[    2.841138] [ef451cc0] [c02991a8] 0xc02991a8
[    2.845394] [ef451d40] [c028e2b8] 0xc028e2b8
[    2.849651] [ef451d60] [c029993c] 0xc029993c
[    2.853907] [ef451de0] [c0273138] 0xc0273138
[    2.858164] [ef451df0] [c02715b8] 0xc02715b8
[    2.862420] [ef451e20] [c02717f4] 0xc02717f4
[    2.866676] [ef451e40] [c026f634] 0xc026f634
[    2.870933] [ef451e70] [c0270a88] 0xc0270a88
[    2.875189] [ef451e90] [c0272158] 0xc0272158
[    2.879446] [ef451ea0] [c0003140] 0xc0003140
[    2.883702] [ef451f00] [c04d8b40] 0xc04d8b40
[    2.887959] [ef451f30] [c00032d0] 0xc00032d0
[    2.892215] [ef451f40] [c00103b0] 0xc00103b0
[    2.896470] Instruction dump:
[    2.899427] 48000008 0fe00000 7c0004ac 4e800020 81240018 8144000c 2f890001 40be000c 
[    2.907163] 7d2a28ae 48000028 2f890002 40be000c <7d2a2a2e> 48000018 2f890004 409e000c 
[    2.915079] ---[ end trace c9ea2fa8a0ac4ace ]---
[    2.920341] 
[    3.911837] Kernel panic - not syncing: Fatal exception
[    3.917450] Rebooting in 1 seconds..

Is there something wrong I’m doing? Or is this a bug upstream?

23.06.20203200KernelBug ReportVery LowLowSoftware flowoffload doesn't work with marked packetsopenwrt-19.07Unconfirmed Task Description

Software offload doesn’t work when custom routing table used:
How to examine:

# create ipset
ipset create IPNET hash:net
ipset add IPNET 139.59.209.225/32
# check ipset
ipset list IPNET
...
Number of entries: 1
Members:
139.59.209.225

# mark packets with dst to IPNET
iptables -t mangle -A PREROUTING -i br-lan -m set –match-set IPNET dst -j MARK –set-mark 0×1111 iptables -t mangle -A OUTPUT -m set –match-set IPNET dst -j MARK –set-mark 0×1111

# add custom routing table for marked packets
ip ru add fwmark 0×1111 lookup 8888 prio 10000

# add route for custom table 8888
ip route add default via 192.168.30.1 table 8888

# enable flow offload in /etc/config/firewall
config defaults

....
option flow_offloading '1'

/etc/init.d/firewall reload

check iptables:
Chain FORWARD (policy DROP 0 packets, 0 bytes)

  pkts      bytes target     prot opt in     out     source               destination         
    24     1947 forwarding_rule  all  --  any    any     anywhere             anywhere             /* !fw3: Custom forwarding rule chain */
    22     1819 FLOWOFFLOAD  all  --  any    any     anywhere             anywhere             /* !fw3: Traffic offloading */ ctstate RELATED,ESTABLISHED FLOWOFFLOAD
    22     1819 ACCEPT     all  --  any    any     anywhere             anywhere             ctstate RELATED,ESTABLISHED /* !fw3 */
     2      128 zone_lan_forward  all  --  br-lan any     anywhere             anywhere             /* !fw3 */
     0        0 zone_wan_forward  all  --  pppoe-wan any     anywhere             anywhere             /* !fw3 */
     0        0 zone_wan_forward  all  --  l2tpv3-hetzner any     anywhere             anywhere             /* !fw3 */
     0        0 zone_wan_forward  all  --  wg0    any     anywhere             anywhere             /* !fw3 */
     0        0 reject     all  --  any    any     anywhere             anywhere             /* !fw3 */


But packets with RELATED,ESTABLISHED don’t use custom routing (it seems what flowoffload don’t remember custom routing and try to send packets on table main). When I add manually custom route to main table - flow offload work again

08.07.20203218Base systemBug ReportVery LowLowhostapd log_level ingoredopenwrt-19.07Unconfirmed Task Description

Model: TP-Link Archer C7 v2
Architecture: Qualcomm Atheros QCA9558 ver 1 rev 0
Firmware Version :OpenWrt 19.07.2 r10947-65030d81f3 / LuCI openwrt-19.07 branch git-20.155.55664-f35803e
Kernel Version: 4.14.171

root@router:/tmp/run# uci show wireless | grep log
wireless.radio0.log_level='3'
wireless.radio1.log_level='3'
root@router:/tmp/run# cat hostapd-phy* | grep log
logger_syslog=127
logger_syslog_level=3
logger_stdout=127
logger_stdout_level=3
logger_syslog=127
logger_syslog_level=3
logger_stdout=127
logger_stdout_level=3
root@router:/tmp/run# hostapd_cli -i wlan0 log_level
Current level: INFO
Timestamp: 0
root@router:/tmp/run# hostapd_cli -i wlan1 log_level
Current level: INFO
Timestamp: 0
root@router:/tmp/run# hostapd_cli -i wlan1-1 log_level
Current level: INFO
Timestamp: 0
root@router:/tmp/run# hostapd_cli -i wlan1-1 log_level 2
FAIL
root@router:/tmp/run# opkg list-installed | grep hostapd
hostapd-common - 2019-08-08-ca8c2bd2-4
hostapd-utils - 2019-08-08-ca8c2bd2-4
root@router:/tmp/run# opkg list-installed | grep wpad
wpad - 2019-08-08-ca8c2bd2-4

Hello, I have a problem with the loglevel of hostapd. However the loglevel get ignored by the daemon and even the direct manipulation over hostapd_cli failed. Because of this the syslog get spammed by all the info messages.
It is predefined here: https://github.com/openwrt/openwrt/blob/openwrt-19.07/package/network/services/hostapd/Config.in But I don’t know why it is unchangeable at all

11.07.20203224Base systemBug ReportVery LowLowA VLAN goes out when a new VLAN is addedopenwrt-19.07Unconfirmed Task Description

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

 

Hostname OpenWrt
Model Linksys WRT1900ACS
Architecture ARMv7 Processor rev 1 (v7l)
Firmware Version OpenWrt 19.07.3 r11063-85e04e9f46 / LuCI openwrt-19.07 branch git-20.136.49537-fb2f363
Kernel Version 4.14.180

At the outset, there are two VLANs pre-existing: 1 (LAN) and 2 (WAN)
In LuCi, create the following VLANs: 10, 20, 21, 2200, 2204, 2208, 3000.

At that point, I created a new VLAN on the Network/Switch page in LuCi. The new VLAN had an initial default VID of 10, which I changed to 11. I set the tagging to my need (Tagged on CPU and LAN port 3, off on all other ports) without touching the other nine VLANs.

As soon as I hit Save & apply, VLAN 10 stopped working entirely.

Examining the configuration files, I find these two stanzas:

config switch_vlan

option device 'switch0'
option vlan '3'
option ports '5t 1t'
option vid '10'

. . .

config switch_vlan

option device 'switch0'
option vlan '10'
option ports '5t 1t'
option vid '11'

This leads me to the hypothesis that the “vlan” option of 10 is colliding with the “vid” option of 10 on another VLAN, though it seems like these should be separate, unrelated concepts.

My workaround was to redo my VLAN scheme so that former VLANs 10, 11, 20 and 21 are now 1000, 1100, 2000 and 2100 respectively, which was enough to prevent this collision, and it all works, but it seems like it should not have had the collision in the first place.

16.07.20203234ToolchainBug ReportVery LowLow19.07.2 imagebuilder does not work with (detect) gcc 10...openwrt-19.07Unconfirmed Task Description

Imagebuilder is unable to detect gcc/g++ on my system running gcc 10.1 FORCE=1 makes no difference, and seems to be ignored.

[naguz@blaptop openwrt-imagebuilder-19.07.2]$ make image FORCE=1 PROFILE=tplink_archer-c7-v2 FILES=files/
Checking 'working-make'... ok.
Checking 'case-sensitive-fs'... ok.
Checking 'proper-umask'... ok.
Checking 'gcc'... failed.
Checking 'working-gcc'... ok.
Checking 'g++'... failed.
Checking 'working-g++'... ok.
Checking 'ncurses'... ok.
Checking 'perl-thread-queue'... ok.
Checking 'tar'... ok.
Checking 'find'... ok.
Checking 'bash'... ok.
Checking 'patch'... ok.
Checking 'diff'... ok.
Checking 'cp'... ok.
Checking 'seq'... ok.
Checking 'awk'... ok.
Checking 'grep'... ok.
Checking 'getopt'... ok.
Checking 'stat'... ok.
Checking 'unzip'... ok.
Checking 'bzip2'... ok.
Checking 'wget'... ok.
Checking 'perl'... ok.
Checking 'python3-cleanup'... ok.
Checking 'python'... ok.
Checking 'git'... ok.
Checking 'file'... ok.
Checking 'ldconfig-stub'... ok.

Build dependency: Please install the GNU C Compiler (gcc) 4.8 or later
Build dependency: Please install the GNU C++ Compiler (g++) 4.8 or later

Prerequisite check failed. Use FORCE=1 to override.
make[1]: *** [Makefile:87: staging_dir/host/.prereq-build] Error 1
make: *** [Makefile:197: image] Error 2
[gert@blad openwrt-imagebuilder-19.07.2]$ 
19.07.20203239Base systemBug ReportVery LowLowVLAN tagging on ipq40xx (GL-B1300) no longer worksopenwrt-19.07Unconfirmed Task Description

GL-B1300, ipq40xx, 19.07-SNAPSHOT

https://forum.openwrt.org/t/vlan-tagging-on-ipq40xx-gl-b1300-no-longer-works/69569

The config below used to create VLAN 3 & 4 on the LAN ports, but not after the commit https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=8c191712558ce945993982b03abc5ce80e0fe230 : LAN clients cannot get their IP addresses

I build 19.07 WITHOUT that commit and it fixed the issue.

config switch

option name 'switch0'
option reset '1'
option enable_vlan '1'

config switch_vlan

option device 'switch0'
option vlan '3'
option vid '3'
option ports '3 0t'

config switch_vlan

option device 'switch0'
option vlan '4'
option vid '4'
option ports '4 0t'
23.07.20203246KernelBug ReportVery LowLowar8216.c and ar8327.c does not read incoming packets (R...openwrt-19.07Unconfirmed Task Description

Device is Dlink DIR615C1 running 19.07 doesn’t respond to pings. Device has been reset to factory defaults, but doesn’t respond to pings.

ifconfig shows no RX packets and no RX bytes on eth0 interface.

root@OpenWrt:/# ifconfig
br-lan Link encap:Ethernet HWaddr 00:22:B0:BA:50:1F

        inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
        UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        RX packets:0 errors:0 dropped:0 overruns:0 frame:0
        TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
        collisions:0 txqueuelen:1000
        RX bytes:0 (0.0 B)  TX bytes:378 (378.0 B)

eth0 Link encap:Ethernet HWaddr 00:22:B0:BA:50:1F

        UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        RX packets:0 errors:0 dropped:0 overruns:0 frame:0
        TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
        collisions:0 txqueuelen:1000
        RX bytes:0 (0.0 B)  TX bytes:1475 (1.4 KiB)
        Interrupt:4

Same DIR615C1 running 18.06.08 works fine.

If I compile the current snapshot with the 18.06.8 code from ar8216.c, ar8216.h, ar8327.c and ar8327.h (the last two were required because of compilation errors), the snapshot image with the older 18.06.8 ar8216 drivers works fine.

There are significant changes in the way the ar8216 is initialized and setup from 18.06.8 to 19.07.1 and the latter code is not reading incoming packets because RX packets and RX bytes are always 0.

Code found in

target/linux/generic/files/drivers/net/phy

Details at

https://forum.openwrt.org/t/lan-doesnt-work-in-19-07-2-custom-build/61945/

17.08.20203290PackagesBug ReportVery LowLowhostapd always sets ap_isolate to 1 no matter what the ...openwrt-19.07Unconfirmed Task Description

I have two devices that show the same problem - both TP-Link, but different models.
The problem is that the devices/clients connected to any of the wlans are always isolated no matter what the config “isolate clients” is set to.
These devices cannot ping and see each other but they can be pinged and they can ping devices from/to devices in lan.

Further more the generated /var/run/hostapd-phy0.conf and /var/run/hostapd-phy1.conf always have the ap_isolate=1

The tested devices are:

root@OpenWrt:~# ubus call system board
{
        "kernel": "4.14.180",
        "hostname": "OpenWrt",
        "system": "Qualcomm Atheros QCA9558 ver 1 rev 0",
        "model": "TP-Link Archer C7 v2",
        "board_name": "tplink,archer-c7-v2",
        "release": {
                "distribution": "OpenWrt",
                "version": "19.07.3",
                "revision": "r11063-85e04e9f46",
                "target": "ath79/generic",
                "description": "OpenWrt 19.07.3 r11063-85e04e9f46"
        }
}
root@OpenWrt:~# ubus call system board
{
        "kernel": "4.14.180",
        "hostname": "OpenWrt",
        "system": "Atheros AR9344 rev 2",
        "model": "TP-Link TL-WDR4300 v1",
        "board_name": "tplink,tl-wdr4300-v1",
        "release": {
                "distribution": "OpenWrt",
                "version": "19.07.3",
                "revision": "r11063-85e04e9f46",
                "target": "ath79/generic",
                "description": "OpenWrt 19.07.3 r11063-85e04e9f46"
        }
}

No packages have been updated manually on both devices.
Both devices has defaults sets coming with the default factory OpenWrt 19.07.3 image.
Both devices were set for their Network → Wireless → wlan0 (and wlan1) → Interface configuration → Advanced settings → Isolate clients UNCHECKED

Here is the config of one of the devices (/etc/config/wireless) and the respective generated /var/run/hostapd-phy0.conf

config wifi-device 'radio0'
	option type 'mac80211'
	option hwmode '11g'
	option path 'platform/ahb/18100000.wmac'
	option channel 'auto'
	option country 'BG'
	option htmode 'HT20'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option key 'XXXXXX'
	option ssid 'YYYYYYYY'
	option encryption 'psk2'

Even when option isolate ‘0’ is added manually using uci not luci, and restarting the device the respective hostapd-phy0.conf remains with ap_isolate=1

driver=nl80211
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2
country_code=BG
ieee80211d=1
hw_mode=g
beacon_int=100
channel=acs_survey



ieee80211n=1
ht_coex=0
ht_capab=[LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][DSSS_CCK-40]

interface=wlan0
ctrl_interface=/var/run/hostapd
ap_isolate=1
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=1
preamble=1
wmm_enabled=1
ignore_broadcast_ssid=0
uapsd_advertisement_enabled=1
utf8_ssid=1
multi_ap=0
wpa_passphrase=XXXXXX
auth_algs=1
wpa=2
wpa_pairwise=CCMP
ssid=YYYYYYYY
bridge=br-lan
wpa_disable_eapol_key_retries=0
wpa_key_mgmt=WPA-PSK
okc=0
disable_pmksa_caching=1
bssid=xx:xx:xx:xx:xx:xx

My guess is that hostapd/wpad doesn’t set properly the ap_isolate according to the config.

Please let me know if you need further info.

Thanks

 


24.08.20203301PackagesBug ReportVery LowLowCannot satisfy dependency on iptables-mod-tproxyopenwrt-19.07Waiting on reporter Task Description

One example is iptables-mod-tproxy. It is available in 19.07.0, but not in 19.07.1. This causes dependency issue when installing some packages.
How to reproduce:

# opkg install shadowsocks-libev-ss-rules
Installing shadowsocks-libev-ss-rules (3.2.5-5) to root...
Downloading http://downloads.openwrt.org/releases/19.07.1/packages/aarch64_cortex-a53/packages/shadowsocks-libev-ss-rules_3.2.5-5_aarch64_cortex-a53.ipk
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for shadowsocks-libev-ss-rules:
 *      iptables-mod-tproxy
 * opkg_install_cmd: Cannot install package shadowsocks-libev-ss-rules.

I reproduced it on aarch64_coretex_a53, but I see it’s missing for other platforms like a72 and x86_64, too.

It was reported here: https://github.com/openwrt/packages/issues/11457 But was closed and the maintainer said it belongs here.

05.09.20203323KernelBug ReportVery LowLowBuffalo WZR-600DHP needs kmod-usb-ohci for USB to workopenwrt-19.07Unconfirmed Task Description

In both openwrt-15.05.1-ar71xx-generic-wzr-600dhp-squashfs-tftp.bin and openwrt-19.07.3-ar71xx-generic-wzr-600dhp-squashfs-sysupgrade.bin USB did not work. Power was available at the USB port, but plugging in various USB devices did absolutely nothing. I had to install kmod-usb-ohci to make USB start working.

I feel this is a bug because in 19.07.3 kmod-usb-ehci is already installed. So, one might think that required USB modules are there and something is wrong.

I tried both USB 1.1 and 2.0 high speed devices before. The ohci module is required even to use USB 2.0 high speed devices.

06.09.20203327Base systemBug ReportVery LowLowEthernet LED assignments incorrect on Linkysys WRT32Xopenwrt-19.07Unconfirmed Task Description

Device: Linksys WRT32X
OpenWRT version: OpenWrt 19.07.3 r11063-85e04e9f46

The LAN/WAN link LEDs seem to be incorrectly assigned in OpenWRT (offset by 1):

- LAN Port 1 link results in no LED lighting
- LAN Ports 2-4 light LAN link LEDs 1-3 respectively
- WAN port lights LAN LED 4

The WAN LED is assigned to the correct (and default) interface (eth1) in LUCI. The rest of the LEDs are not configurable, leading me to believe the issue is with indexing of the LEDs themselves, as opposed to LED-Port assignment.

09.09.20203330Base systemBug ReportVery LowLowds-lite: too low default MTUopenwrt-19.07Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on TP-Link Archer C7 v5
- Software versions of OpenWrt/LEDE release, packages, etc.

OpenWrt 19.07.3 r11063-85e04e9f46 / LuCI openwrt-19.07 branch git-20.136.49537-fb2f363
ds-lite 7-4

- Steps to reproduce: install system, install ds-lite, the mtu for all dslite connections will be [1280|https://github.com/openwrt/openwrt/blob/master/package/network/ipv6/ds-lite/files/dslite.sh#L66] by default.

Because of it, if a VPN with ipv6 is used over ipv4, it’s completely broken.

tun0 w/ ipv6 -> [vpn client -> [dslite with mtu 1280] -> vpn server] -> private network

As far as I see, it should be relatively easy to make default MTU autoconfigurable with parent’s MTU-x (where 30 is 30, if I’m right)

18.12.20192687Base systemBug ReportVery LowVery LowWiFi LED does not dynamically track state of radio on Z...openwrt-19.07Unconfirmed Task Description

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

 

Occurs on ZBT-WE3526 (16M) an MT76 unit with 512MB Ram

Stock 19.07, but has been this way since 18.06.xx

Steps to reproduce:
Log into to LuCi and disable a wifi radio, LED remains on.

reboot, radiox LED is now off, so LED is only set at boot

Log back into luci, turn radio on, radio becomes operational (STAs can connect) but LED remains off.

Desired behavior: LED tracks state of radio without requiring a reboot.

03.02.20202803KernelBug ReportVery LowVery Lowmt76 kernel spam log with ingnoring tx power message openwrt-19.07Unconfirmed Task Description

ASUS RT-AC51U

Official build OpenWRT 19.07.1 without installed any add-ons packages.

System and kernel log all time are spammed by information about ignoring default 2.4G tx power even when in its set to default driver. This issue appears right after fresh installation and rebooting or changing wireless setting doesn’t fix it.

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


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

01.12.20192645Base systemBug ReportVery LowCritical18.06.3 - Broken compatibility with flash on bcm6538 ba...openwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: Pirelli A226M
- Software versions of OpenWrt/LEDE release: 18.06.3
- Steps to reproduce: just flash a 18.06.3 version or greater and verify the device won’t boot, hanging when it gets to mount local flash. 18.06.1 is working, never tried 18.06.2.

[    1.065798] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    1.073562] Please append a correct "root=" boot option; here are the available partitions:
[    1.082174] 1f00             128 mtdblock0 [    1.086283]  (driver?)
[    1.088718] 1f01           16128 mtdblock1 [    1.092823]  (driver?)
[    1.095210] 1f02             128 mtdblock2 [    1.099366]  (driver?)
[    1.101798] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
 


19.02.2017535KernelBug ReportVery LowHigh5GHz radios not working properly on Netgear R8000openwrt-18.06Unconfirmed Task Description

After upgrading my R8000 from Chaos Calmer (15.05.1) to LEDE Reboot (17.01.0-rc2, r3131-42f3c1f), I found that I could no longer get the 5GHz radios to work as before. The 2.4GHz radio is fine.

In CC I was using the following configuration:
- radio0 on channel 149, country code ‘00’, VHT80
- radio2 on channel 48, country code ‘00’, VHT80

The firmware apparently only accepts 00 and US as country codes, which is why I was using 00. This discussed at length in: https://forum.openwrt.org/viewtopic.php?id=55367&p=19 (and previous pages)

In 17.01.0-rc2, I can’t get radio0 to come up at all. radio2 can be configured, still on channel 48 and country 00, but in VHT40 mode. If I use VHT80, it stays disabled.

This was discussed previously in this forum post: https://forum.lede-project.org/t/r8000-5ghz-wifi-issue/236 and I get the same error messages and channel selection as the OP, so I will not repeat them here.

I’m not sure if this issue is really related to the country code setting, but I will note that the factory system apparently sets the country code to “EU”:

root@x6:~# nvram show | grep country_code
wl1_country_code=EU
wl0_country_code=EU
wl2_country_code=EU
wl_country_code=
root@x6:~#

I see that LEDE carries a patch on brcmfmac which translates the configured country code to an internal code for the firmware on this specific model (https://git.lede-project.org/?p=source.git;a=blob_plain;f=package/kernel/mac80211/patches/863-brcmfmac-add-in-driver-tables-with-country-codes.patch;hb=refs/heads/lede-17.01). I’m willing to test patches if anyone knows the right internal country code for Europe.

28.05.20181568Base systemBug ReportVery LowHighD-Link DIR-645 not maintaining WLAN connectionopenwrt-18.06Unconfirmed Task Description

- Device problem occurs on
D-Link DIR-645 Rev. A1

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

- Steps to reproduce
Setup the wireless connection. After some time the WLAN connection stops working. A restart is necessary to regain WLAN.

Topic is discussed in the forums:
https://forum.lede-project.org/t/d-link-dir-645-wifi-interface-not-maintaining-connection/6277

I am able and willing to provide log files. But I am new to the business of debugging itself. Help and guidance welcome!

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.


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

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.

Showing tasks 101 - 150 of 1113 Page 3 of 23 - 1 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing