OpenWrt 21.02.0 - First Stable Release

Did your WAN work out of the box? Mine didn't. The network device eth0 was greyed out. Once I edited network device eth0 to Accept local (Accept packets with local source addresses), eth0 became non-greyed and WAN got an ip-address from DHCP server.

These should have been there before as well. A qdisc can either be built-into a kernel or live in a loadable kernel module. OpenWrt does not have a reliable autoloading system for kernel modules, so sqm tries to load a few modules essential for its functionality, but some, e.g. fq_codel, are built into OpenWrt's kernel, so the loading fails and you get an error message. verify_qdisc() will later check whether a qdisc is actually working to deal with potentially built-in modules.
Upstream sqm unconditionally silences these errors, but that will also hide real errors of users trying to load modules that are not built-in and not found as modules. Not sure how often that triggers, but especially for novices that would be somewhat hard to debug without an error message.

1 Like

Linksys MR8300 v1.1
Installation succesfull from stock firmware UI, despite being a pain to find the right URL :frowning:
wifi0 (qca 9886) not working. It is enabled, but can't be found by client devices. It is a documented issue which is also on the EA8300 apparently.
My version is 1.1, maybe some tiny differences from version 1.0 ?
I have tried CT and standard ath10k firmware, changing country region and changing power, nothing seems to work. If someone is willing to help I can experiment.

I have a PPPoE connection and had no issues. Just had to configure the VLAN ID for the WAN and enter my credentials and it worked.

1 Like

That is not what the release notes said. And if it is duplicating a v19.07 setting why does it work differently to v19.07, so the same browsers regard v21.02 as insecure.

In 19.07 the HTTPS enabling libraries were not installed by default, so you did not connect with HTTPS unless you installed the needed SSL libraries (and the required libustream wrapper). Thus you did not receive the certificate warning, although the redirection option was set as enabled.

For 21.02 the SSL + libustream libraries are installed by default so there is HTTPS capability. And if you sysupgrade with settings from 19.07, your old dormant setting from 19.07 with the "redirect to https" enabled becomes effective. And thus you get a warning.

But for a new 21.02 installation (or a sysupgrade without settings), the HTTPS redirection is set as disabled, so there is no warning (if you just connect with http).

5 Likes

I found instructions indicating it might be possible to do a sort of upgrade: Linksys WRT3200ACM & 21.02.0-RC1 popup message - #7 by hnyman

So I renamed /etc/config/network and /etc/config/system to network.old and system.old and flashed retaining the configuration.

This worked as expected. I had to re-create my guest network and attach my guest wireless to it. Then I setup the VLANs for the wired network.

Is it well known with the DSA devices the WAN MAC address changes when upgrading from previous versions? This is problematic with ISPs like Ziply Fiber where after two leases you can't get another until the lease time for a previous lease expires (four hours in this case).

Good news, with this version my WAN speed is still good: https://www.speedtest.net/my-result/d/e50d8588-fa34-475f-b26f-7e6392d3e64d

Has newer happend to me yet, it is kind of hard to happen. The MAC is hardware coded.

Are you sure you don’t use some kind of MAC override?

It seems a MAC override was created during the upgrade. I have removed it.

1 Like

I think the better solution would have been to initially have HTTPS off, whatever the previous set-up had been, and tell users how to set it up. Doing nothing in v19.07 looked like nothing was switched on, and the default for v21.02 should have been the same behaviour, with a clear explanation.

I'm not in a rush to reboot my system to install v21.02, because that shows up as a possible line fault to my ISP, and they drop the connection speed. It's nothing to do with any software or hardware here. And all I have found on openwrt.org about HTTPS misbehaviour is pretty old, often blaming new browser versions.

I hope somebody can explain how to get HTTPS running.

Https is as standard OFF. It was only ON in Rc1.

The instruction for uhttpd is the same as it has always been.

Does offloading is working on
development snapshots?

reboot problem on hlk-7628n

root@OpenWrt:/# reboot
root@OpenWrt:/# [  202.398701] lan2: port 1(wlan0-1) entered disabled state
[  202.427143] device wlan0-1 left promiscuous mode
[  202.436366] lan2: port 1(wlan0-1) entered disabled state
[  202.500821] device wlan0 left promiscuous mode
[  202.509852] br-lan: port 2(wlan0) entered disabled state
[  204.876249] br-lan: port 1(eth0.1) entered disabled state
[  204.940155] device eth0.1 left promiscuous mode
[  204.949211] device eth0 left promiscuous mode
[  204.958016] br-lan: port 1(eth0.1) entered disabled state
[  211.069541] reboot: Restarting system


system stock at "reboot: Restarting system"

1 Like

please post your full kernel log so we can see the flash chip model

find flash: W25Q256FV

1 Like

@ahforoozani please post your full kernel log

Starting kernel ...

[    0.000000] Linux version 5.4.143 (builder@buildhost) (gcc version 8.4.0 (Ope                                                      nWrt GCC 8.4.0 r16279-5cc0535800)) #0 Tue Aug 31 22:20:08 2021
[    0.000000] Board has DDR2
[    0.000000] Analog PMU set to hw control
[    0.000000] Digital PMU set to hw control
[    0.000000] SoC Type: MediaTek MT7628AN ver:1 eco:2
[    0.000000] printk: bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019655 (MIPS 24KEc)
[    0.000000] MIPS: machine is HILINK HLK-7628N
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 byt                                                      es
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32480
[    0.000000] Kernel command line: console=ttyS0,57600 rootfstype=squashfs,jffs                                                      2
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, li                                                      near)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, line                                                      ar)
[    0.000000] Writing ErrCtl register=0002ebfe
[    0.000000] Readback ErrCtl register=0002ebfe
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 122360K/131072K available (5086K kernel code, 206K rwdata                                                      , 636K rodata, 1228K init, 205K bss, 8712K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 256
[    0.000000] intc: using register map from devicetree
[    0.000000] random: get_random_bytes called from 0x805cda28 with crng_init=0
[    0.000000] CPU Clock: 580MHz
[    0.000000] timer_probe: no matching timers found
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_i                                                      dle_ns: 6590553264 ns
[    0.000010] sched_clock: 32 bits at 290MHz, resolution 3ns, wraps every 74051                                                      15902ns
[    0.015408] Calibrating delay loop... 385.02 BogoMIPS (lpj=770048)
[    0.059466] pid_max: default: 32768 minimum: 301
[    0.068797] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linea                                                      r)
[    0.083136] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes,                                                       linear)
[    0.104699] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ma                                                      x_idle_ns: 7645041785100000 ns
[    0.123907] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.137424] pinctrl core: initialized pinctrl subsystem
[    0.150659] NET: Registered protocol family 16
[    0.187315] workqueue: max_active 576 requested for napi_workq is out of rang                                                      e, clamping between 1 and 512
[    0.210324] clocksource: Switched to clocksource MIPS
[    0.221368] thermal_sys: Registered thermal governor 'step_wise'
[    0.221784] NET: Registered protocol family 2
[    0.242375] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear                                                      )
[    0.257442] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096                                                       bytes, linear)
[    0.273930] TCP established hash table entries: 1024 (order: 0, 4096 bytes, l                                                      inear)
[    0.289000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.302926] TCP: Hash tables configured (established 1024 bind 1024)
[    0.315631] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.328489] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.342578] NET: Registered protocol family 1
[    0.351142] PCI: CLS 0 bytes, default 32
[    0.363826] workingset: timestamp_bits=14 max_order=15 bucket_order=1
[    0.385187] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.396649] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORIT                                                      Y) (c) 2001-2006 Red Hat, Inc.
[    0.432082] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2                                                      52)
[    0.449975] mt7621_gpio 10000600.gpio: registering 32 gpios
[    0.461251] mt7621_gpio 10000600.gpio: registering 32 gpios
[    0.472481] mt7621_gpio 10000600.gpio: registering 32 gpios
[    0.483757] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.499291] printk: console [ttyS0] disabled
[    0.507735] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 28, base_baud                                                       = 2500000) is a 16550A
[    0.525555] printk: console [ttyS0] enabled
[    0.525555] printk: console [ttyS0] enabled
[    0.542020] printk: bootconsole [early0] disabled
[    0.542020] printk: bootconsole [early0] disabled
[    0.561322] 10000d00.uart1: ttyS1 at MMIO 0x10000d00 (irq = 29, base_baud = 2                                                      500000) is a 16550A
[    0.580264] spi-mt7621 10000b00.spi: sys_freq: 193333333
[    0.610426] spi-nor spi0.0: w25q256 (32768 Kbytes)
[    0.619995] 4 fixed-partitions partitions found on MTD device spi0.0
[    0.632586] Creating 4 MTD partitions on "spi0.0":
[    0.642091] 0x000000000000-0x000000030000 : "u-boot"
[    0.653122] 0x000000030000-0x000000040000 : "u-boot-env"
[    0.664810] 0x000000040000-0x000000050000 : "factory"
[    0.676008] 0x000000050000-0x000002000000 : "firmware"
[    0.691376] 2 uimage-fw partitions found on MTD device firmware
[    0.703171] Creating 2 MTD partitions on "firmware":
[    0.713029] 0x000000000000-0x0000001e7c81 : "kernel"
[    0.724026] 0x0000001e7c81-0x000001fb0000 : "rootfs"
[    0.735072] mtd: device 5 (rootfs) set to be root filesystem
[    0.748517] 1 squashfs-split partitions found on MTD device rootfs
[    0.760853] 0x0000004e0000-0x000001fb0000 : "rootfs_data"
[    0.773501] libphy: Fixed MDIO Bus: probed
[    0.793342] rt3050-esw 10110000.esw: link changed 0x00
[    0.805606] mtk_soc_eth 10100000.ethernet eth0: mediatek frame engine at 0xb0                                                      100000, irq 5
[    0.824233] NET: Registered protocol family 10
[    0.837749] Segment Routing with IPv6
[    0.845242] NET: Registered protocol family 17
[    0.854141] bridge: filtering via arp/ip/ip6tables is no longer available by                                                       default. Update your scripts to load br_netfilter if you need this.
[    0.879822] 8021q: 802.1Q VLAN Support v1.8
[    0.898303] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
[    0.919377] Freeing unused kernel memory: 1228K
[    0.928377] This architecture does not have kernel memory protection.
[    0.941138] Run /sbin/init as init process
[    1.526329] random: fast init done
[    2.053393] init: Console is alive
[    2.060559] init: - watchdog -
[    3.227227] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.413070] kmodloader: done loading kernel modules from /etc/modules-boot.d/                                                      *
[    3.437985] init: - preinit -
[    5.037594] random: jshn: uninitialized urandom read (4 bytes read)
[    5.138594] random: jshn: uninitialized urandom read (4 bytes read)
[    5.434428] random: jshn: uninitialized urandom read (4 bytes read)
[    5.941519] rt3050-esw 10110000.esw: link changed 0x00
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[    6.166279] urandom_read: 2 callbacks suppressed
[    6.166288] random: procd: uninitialized urandom read (4 bytes read)
[   10.862920] jffs2: notice: (449) jffs2_build_xattr_subsystem: complete buildi                                                      ng xattr subsystem, 93 of xdatum (54 unchecked, 38 orphan) and 139 of xref (40 d                                                      ead, 1 orphan) found.
[   10.910923] mount_root: switching to jffs2 overlay
[   10.927782] overlayfs: upper fs does not support tmpfile.
[   10.959923] urandom-seed: Seeding with /etc/urandom.seed
[   11.827206] procd: - early -
[   11.833225] procd: - watchdog -
[   12.584268] procd: - watchdog -
[   12.595127] procd: - ubus -
[   12.762593] random: ubusd: uninitialized urandom read (4 bytes read)
[   12.793104] random: ubusd: uninitialized urandom read (4 bytes read)
[   12.819073] random: ubusd: uninitialized urandom read (4 bytes read)
[   12.850937] procd: - init -
Please press Enter to activate this console.
[   15.715575] urngd: v1.0.2 started.
[   16.188035] random: crng init done
[   16.194858] random: 1 urandom warning(s) missed due to ratelimiting
[   17.395168] kmodloader: loading kernel modules from /etc/modules.d/*
[   17.736035] usbcore: registered new interface driver usbfs
[   17.747119] usbcore: registered new interface driver hub
[   17.757813] usbcore: registered new device driver usb
[   17.865355] tun: Universal TUN/TAP device driver, 1.6
[   17.958210] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   17.991884] ehci-fsl: Freescale EHCI Host controller driver
[   18.019508] ehci-platform: EHCI generic platform driver
[   18.040270] phy phy-10120000.usbphy.0: remote usb device wakeup disabled
[   18.053563] phy phy-10120000.usbphy.0: UTMI 16bit 30MHz
[   18.063924] ehci-platform 101c0000.ehci: EHCI Host Controller
[   18.075351] ehci-platform 101c0000.ehci: new USB bus registered, assigned bus                                                       number 1
[   18.091183] ehci-platform 101c0000.ehci: irq 26, io mem 0x101c0000
[   18.190342] ehci-platform 101c0000.ehci: USB 2.0 started, EHCI 1.00
[   18.217005] hub 1-0:1.0: USB hub found
[   18.242361] hub 1-0:1.0: 1 port detected
[   18.522420] usb 1-1: new high-speed USB device number 2 using ehci-platform
[   19.597656] usbcore: registered new interface driver cdc_wdm
[   20.249483] Loading modules backported from Linux version v5.10.42-0-g65859ec                                                      a4dff
[   20.264559] Backport generated by backports.git v5.10.42-1-0-gbee5c545
[   20.831089] usbcore: registered new interface driver usbserial_generic
[   20.844223] usbserial: USB Serial support registered for generic
[   20.977925] xt_time: kernel timezone is -0000
[   21.012586] usbcore: registered new interface driver cdc_ncm
[   21.381314] mt76_wmac 10300000.wmac: ASIC revision: 76280001
[   22.452738] mt76_wmac 10300000.wmac: Firmware Version: 20151201
[   22.464567] mt76_wmac 10300000.wmac: Build Time: 20151201183641
[   22.508237] mt76_wmac 10300000.wmac: firmware init done
[   22.738066] PPP generic driver version 2.4.2
[   22.795801] NET: Registered protocol family 24
[   22.856527] qmi_wwan 1-1:1.4: cdc-wdm0: USB WDM device
[   22.899549] qmi_wwan 1-1:1.4 wwan0: register 'qmi_wwan' at usb-101c0000.ehci-                                                      1, WWAN/QMI device, 22:ca:94:34:ea:cc
[   22.920387] usbcore: registered new interface driver qmi_wwan
[   23.135024] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for info                                                      rmation.
[   23.150605] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c                                                      4.com>. All Rights Reserved.
[   23.288625] usbcore: registered new interface driver cdc_mbim
[   23.361187] usbcore: registered new interface driver option
[   23.372424] usbserial: USB Serial support registered for GSM modem (1-port)
[   23.386745] option 1-1:1.0: GSM modem (1-port) converter detected
[   23.399165] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[   23.413089] option 1-1:1.1: GSM modem (1-port) converter detected
[   23.425542] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[   23.439493] option 1-1:1.2: GSM modem (1-port) converter detected
[   23.451957] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[   23.465902] option 1-1:1.3: GSM modem (1-port) converter detected
[   23.478412] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
[   23.801078] kmodloader: done loading kernel modules from /etc/modules.d/*
[   47.912124] br-lan: port 1(eth0.1) entered blocking state
[   47.922919] br-lan: port 1(eth0.1) entered disabled state
[   47.934053] device eth0.1 entered promiscuous mode
[   47.943603] device eth0 entered promiscuous mode
[   48.026491] br-lan: port 1(eth0.1) entered blocking state
[   48.037220] br-lan: port 1(eth0.1) entered forwarding state
[   48.910860] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   54.397491] br-lan: port 2(wlan0) entered blocking state
[   54.408113] br-lan: port 2(wlan0) entered disabled state
[   54.419079] device wlan0 entered promiscuous mode
[   61.398745] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   61.411740] br-lan: port 2(wlan0) entered blocking state
[   61.422343] br-lan: port 2(wlan0) entered forwarding state
[   61.452909] lan2: port 1(wlan0-1) entered blocking state
[   61.463511] lan2: port 1(wlan0-1) entered disabled state
[   61.474518] device wlan0-1 entered promiscuous mode
[   61.514433] lan2: port 1(wlan0-1) entered blocking state
[   61.524998] lan2: port 1(wlan0-1) entered forwarding state
[   61.732766] IPv6: ADDRCONF(NETDEV_CHANGE): lan2: link becomes ready
[   62.262691] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready


Linksys MR8300 v1.1 working with 21.02.0

I went back to stock firmware and setup the config. Than I flashed the factory image provide here (I was using a custom build with wpad-wolfssl). As I need mesh, I remove wpad-basic-wolfssl and install manually wpad-wolfssl. wifi0 (qca 9886) works fine, there is a trick I don't understand.
Everything work as expected now.

I have had some clear explanations of what is happening. The apparent switch in behaviour has its roots in a cock-up over default settings.

So far, nobody seems to know where the relevant instructions are, even when they assert they exist.

Using HTTPS has good security reasons. Perhaps I should caution readers that I have a deep aversion to what looks to be security by obscurity. I know what Kerckhoffs's principle is.

From personal experience: DLM can and does recognize the difference between a line fault and a line that was deliberately taken down. But it's having trouble telling the difference if the line goes down and almost immediately tries to synchronize again (as it happens with a reboot.) This can be avoided by deliberately keeping the line down for several minutes, I usually keep it down for 10 to 15 minutes and I haven't seen any punishments since.

1 Like