Users that are not expert users of OpenWrt (those that can build their own images) should consider 16/64 as an absolute minimum for any device, with at least 128 MB of RAM being preferred.
Unfortunately, 19.07 appears to be the last stable release supporting this device and 19.07 was also the last stable release to support the ar71xx target. The MAC1200R v1 was not migrated from the ar71xx target to the ath79 target as of the 21.02 stable release.
Hi there.
Successfully installed 22.03.0-rc4 on these devices, with various configs (router, mesh, AP)
x86-64 miniPC
Linksys MR8300 (ipq4019 generic)
Netgear R6220 (mt7621)
Netgear 3700v2 (ath79 generic). I have several of these as low-end APs. I have tested 22.03.0-rc4 on one, but I will reverse it back to 21.02 because it has a lower memory print.
Is flow offloading fixed? Like for realsies? Can someone who previously had problems (ipv6 sites like google and facebook simply stop responding in a few minutes + general non-responsiveness) please test and post?
I've been waiting for flow offload to be fixed for over a year now, and want to upgrade only for that.
I use TP-Link AC1750 (Archer A7=C7 v5) in a fairly vanilla (internet->wifi/lan, guest radio) configuration. The only weird thing I have is ddns and vnstat. Those have previously worked seamlessly with sysupgrade (I had problems with the regular firmware upgrade before starting to use sysupgrade like the router stopped responding, and obviously I have to redownload and redo the config for the "non-standard" packages like ddns).
I also have a question - if I upgrade via sysupgrade to rc4, keeping configuration, is it likely to work seamlessly, and then also from rc4 to the release version? I read about problems with configs not working with migration to rc3 (?). I know nothing is ever "guaranteed" because open source, large team, etc. but still - has anyone tried and did it work for rc4?
re: sysupgrade, it's more important what the delta is between what you're coming from and moving to. If your current setup is pre-DSA, you'll probably want to strongly consider manually setting everything up from scratch versus just a straight config-preservation upgrade. If you're already on RC1, for example, it's a very direct migration to RC4 (and final).
Installed iptables-nft, now the warning is only for vpn policy routing, mwan3 is now gone from the iptable list.
Made my image again, with only the extra packages, somehow iptables-legacy showed op in my config.This is now gone.Only FW4 is in my image. But still it tells me that mwan3 and vpr is using iptables.
It seems when I make an interface for a bridge with a VLAN - it doesn't work without editing the /etc/config/network file. I discovered this on a devices used as managed switch/AP - the config allows for WiFi.
Works:
config interface 'guest'
option proto 'none'
option device 'br-guest'
Doesn't work (made by LuCI):
config interface 'guest'
option proto 'none'
option device 'br-guest'
option type 'bridge' #<---------
Tried it on one of my BT hub5a. Seems to have the boot issue quite bad on the router I tried it on. Sometimes it boots successfully, occasionally it appears to hang with the LEDs off and appears dead, but mostly seems to repeatedly boot. I've not got serial connections soldered on to check the console.
Have some strange issue with NAT on the TOTOLINK X5000R
I have two different subnets on the router.
The one is just br-lan with static IP and gateway, it's linked with some wireless networks, there is no DHCP and no NAT.
The second network is connected to WAN and the WLAN NETWORK, WLAN is using "unspecified device" network for NAT, there are static IP on this network and DHCP enabled. This configuration works on the 21 versions and not working on the 22.x.
The problem is that in second subnet, clients are successfully connected to wireless network, getting IP, but can not connect to WAN, no internet, NAT is broken. I have tried clean install, tried all options, no luck. Any thoughts?