Build for Belkin RT3200 (Linksys E8450) [UBI] and Redmi AX6S (Xiaomi AX3200)

diogenes · July 8, 2021, 8:42pm

Sure yeah, go ahead and try the latest build up there and tell me if it works for you:
https://owrt.plzh4x.me/mediatek-mt7622-linksys_e8450-ubi/2021-07-08_1625776312/

AndroidClone · July 9, 2021, 2:08am

wow that was super quick thanks! Usb is detected and succesfully formatted but I somehow missed the nfs-kernel-server in the list of dependencies. Once that is added to the firmware I should be able to share my pendrive. Thanks again!

diogenes · July 10, 2021, 5:40pm

Yup, I just put a new build up with nfs-kernel-driver

AndroidClone · July 11, 2021, 3:52am

Excellent she is up and running.

Dopam-IT_1987 · August 2, 2021, 11:47pm

are you sure than upnp work ? i didin't have wok at my home thanks

Dopam-IT_1987 · August 3, 2021, 6:44am

i has try but witouth success

my stepto your step 2 don't work

then i has remove the two packages and install just luci-app-upnp ...

slh · August 3, 2021, 6:54am

upnp is a software feature, it shouldn't be specific to the rt3200 at all.

Dopam-IT_1987 · August 3, 2021, 7:00am

thank you for the answer @slh but I have an xbox, a ps5 and a pc I have no other way to use upnp, by disabling upnp and reinstalling it tells me confiles has been placed in etc / config / upnpd different , now upnpdopkg,

I tried on another router version openwrt (not rt3200 belkin) and upnp works immediately

hnyman · August 3, 2021, 7:04am

The new default config files have been placed as upnpd-opkg for reference, so that your old settings have not been overwritten, and that you can compare your old config file to the current defaults, and possibly make the necessary changes. Quite normal.

Sure. There were no existing installation and no existing config files, so you get the current defaults and they apparently work.

Dopam-IT_1987 · August 3, 2021, 7:10am

ok thank you, yes the router is a mikrotik rb750gr3, so there is so far no solution to set up upnp on belkin rt3200? or have I done something wrong?

Summary

`
config upnpd 'config'
option download '1024'
option upload '512'
option internal_iface 'lan'
option port '5000'
option upnp_lease_file '/var/run/miniupnpd.leases'
option igdv1 '1'
option enabled '1'
option uuid '...............................'
option ext_ip_reserved_ignore '1'
option external_iface 'wan'
option log_output '1'
config perm_rule
option action 'allow'
option ext_ports '1024-65535'
option int_addr '0.0.0.0/0'
option int_ports '1024-65535'
option comment 'Allow high ports'

config perm_rule
option action 'deny'
option ext_ports '0-65535'
option int_addr '0.0.0.0/0'
option int_ports '0-65535'
option comment 'Default deny'`

and upnpdopkg

config upnpd config
	option enabled		0
	option enable_natpmp	1
	option enable_upnp	1
	option secure_mode	1
	option log_output	0
	option download		1024
	option upload		512
#by default, looked up dynamically from ubus
#	option external_iface	wan
	option internal_iface	lan
	option port		5000
	option upnp_lease_file	/var/run/miniupnpd.leases
	option igdv1		1

config perm_rule
	option action		allow
	option ext_ports	1024-65535
	option int_addr		0.0.0.0/0	# Does not override secure_mode
	option int_ports	1024-65535
	option comment		"Allow high ports"

config perm_rule
	option action		deny
	option ext_ports	0-65535
	option int_addr		0.0.0.0/0
	option int_ports	0-65535
	option comment		"Default deny"

maybe a solution here

Maybe a bit off topic...
But I leave this here for people that have to use a double NAT setup.
For example if you have to use your ISP router and your OpenWRT box behind it.

UPNP also passes the public IP as info to the clients.
(I'm sure PS4 uses this info)
In a double NAT setup this will not work. (Because a private IP is passed over to the clients)
To fix this, change/add
option external_ip 'your public ip address'
to your miniupnpd conf.
It also possible to modify the miniupnpd init script to automatically get the public IP address.
And enable DMZ mode on your ISP router. (to the IP address of your OpenWRT box)
Or forward all high ports (1024-65535) to your OpenWRT box.
But for cgNAT, your ISP has to open/forward the ports or to give a public IP.

by shm0

thanks to @shm0 resolve with external ip

Capture d’écran 2021-08-03 à 09.40.59

loyukfai · August 16, 2021, 4:53pm

Sorry for a totally off-topic question, any idea (timeframe) when E8450 will be officially supported in OpenWrt?

Cheers.

hnyman · August 16, 2021, 5:05pm

It is already. (in the master, not yet in the releases based on older source code).

https://openwrt.org/toh/linksys/e8450

loyukfai · August 16, 2021, 5:10pm

Master is also UBI based?

hnyman · August 16, 2021, 5:14pm

Both versions are there.
https://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/

But the full easy installer for UBI needs to be built by yourself, or downloaded from Daniel/dangowrt's site

alleyu2 · August 17, 2021, 4:51am

Here you go Belkin RT3200/Linksys E8450 WiFi AX discussion - #272 by daniel

fonix232 · August 17, 2021, 9:13am

Basically, expect a 22.02 release (unlikely that the porting to 5.10 will happen for all major devices in this year).

Dopam-IT_1987 · August 17, 2021, 3:16pm

Hello look this discussion

Maybe October November full support

fonix232 · August 17, 2021, 3:36pm

I'm aware of that. But with the current speed of the 21.02 release, it's highly unlikely that the mainstream/core devices can be brought up to 5.10 kernel target before the end of the year. Focus right now is on getting 21.02 into a final stage, then the update to kernel-5.10, and only after that will we have a new release branch.

I also hope that the new major version gets branched before the end of the year - and also that a biannual release schedule can be picked up for faster device support - but realistically, it's not going to happen until early next year, hence the 22.02 prediction. It might be that we do get a 21.12 release, but it's getting more and more unlikely as we go into the second half of the year.

@daniel seems to know more about the status of master, so maybe he can confirm some details (like, how many devices are targeting 5.10 in master right now, if there's any blocking issues, etc.).

slh · August 17, 2021, 8:00pm

That question can be easily answered by anyone, just check the source:

github.com

openwrt/openwrt/blob/master/target/linux/mediatek/Makefile#L12


      
          #
          include $(TOPDIR)/rules.mk
          
          ARCH:=arm
          BOARD:=mediatek
          BOARDNAME:=MediaTek Ralink ARM
          SUBTARGETS:=mt7622 mt7623 mt7629 filogic
          FEATURES:=dt-overlay emmc fpu gpio nand pci pcie rootfs-part separate_ramdisk squashfs usb
          
          KERNEL_PATCHVER:=5.15
          KERNEL_TESTING_PATCHVER:=6.1
          
          include $(INCLUDE_DIR)/target.mk
          DEFAULT_PACKAGES += \
          	kmod-leds-gpio kmod-gpio-button-hotplug
          
          $(eval $(call BuildTarget))

KERNEL_TESTING_PATCHVER existing, and being specified as kernel 5.10 at least suggests that someone has taken the effort of porting the target in question and that the basics work to a considerable extent. Yes, you do have to traverse into the sub-targets, to get the full picture, e.g.:

github.com

openwrt/openwrt/blob/master/target/linux/mediatek/mt7622/target.mk#L7


      
          ARCH:=aarch64
          SUBTARGET:=mt7622
          BOARDNAME:=MT7622
          CPU_TYPE:=cortex-a53
          DEFAULT_PACKAGES += kmod-mt7622-firmware wpad-basic-mbedtls uboot-envtools
          KERNELNAME:=Image dtbs
          
          define Target/Description
          	Build firmware images for MediaTek MT7622 ARM based boards.
          endef

Or to use a different take:

$ git grep -e ^KERNEL_PATCHVER -e ^KERNEL_TESTING_PATCHVER | cat -
include/kernel-version.mk:KERNEL_PATCHVER ?= $(KERNEL)
target/linux/apm821xx/Makefile:KERNEL_PATCHVER:=5.4
target/linux/apm821xx/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/arc770/Makefile:KERNEL_PATCHVER:=5.4
target/linux/archs38/Makefile:KERNEL_PATCHVER:=5.4
target/linux/armvirt/Makefile:KERNEL_PATCHVER:=5.4
target/linux/armvirt/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/at91/Makefile:KERNEL_PATCHVER:=5.4
target/linux/ath25/Makefile:KERNEL_PATCHVER:=5.4
target/linux/ath79/Makefile:KERNEL_PATCHVER:=5.4
target/linux/ath79/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/bcm27xx/Makefile:KERNEL_PATCHVER=5.4
target/linux/bcm47xx/Makefile:KERNEL_PATCHVER:=5.4
target/linux/bcm47xx/Makefile:KERNEL_TESTING_PATCHVER:=5.4
target/linux/bcm4908/Makefile:KERNEL_PATCHVER:=5.4
target/linux/bcm4908/Makefile:KERNEL_TESTING_PATCHVER:=5.4
target/linux/bcm53xx/Makefile:KERNEL_PATCHVER:=5.4
target/linux/bcm53xx/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/bcm63xx/Makefile:KERNEL_PATCHVER:=5.4
target/linux/bcm63xx/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/bmips/Makefile:KERNEL_PATCHVER:=5.10
target/linux/gemini/Makefile:KERNEL_PATCHVER:=5.10
target/linux/imx6/Makefile:KERNEL_PATCHVER:=5.4
target/linux/imx6/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/ipq40xx/Makefile:KERNEL_PATCHVER:=5.4
target/linux/ipq40xx/Makefile:KERNEL_TESTING_PATCHVER:=5.4
target/linux/ipq806x/Makefile:KERNEL_PATCHVER:=5.4
target/linux/ipq806x/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/ipq807x/Makefile:KERNEL_PATCHVER:=5.4
target/linux/kirkwood/Makefile:KERNEL_PATCHVER:=5.4
target/linux/kirkwood/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/lantiq/Makefile:KERNEL_PATCHVER:=5.4
target/linux/lantiq/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/layerscape/Makefile:KERNEL_PATCHVER:=5.4
target/linux/malta/Makefile:KERNEL_PATCHVER:=5.4
target/linux/malta/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/mediatek/Makefile:KERNEL_PATCHVER:=5.4
target/linux/mediatek/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/mediatek/mt7622/target.mk:KERNEL_PATCHVER:=5.10
target/linux/mediatek/mt7623/target.mk:KERNEL_PATCHVER:=5.10
target/linux/mpc85xx/Makefile:KERNEL_PATCHVER:=5.4
target/linux/mpc85xx/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/mvebu/Makefile:KERNEL_PATCHVER:=5.4
target/linux/mvebu/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/mxs/Makefile:KERNEL_PATCHVER:=5.4
target/linux/mxs/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/octeon/Makefile:KERNEL_PATCHVER:=5.4
target/linux/octeon/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/octeontx/Makefile:KERNEL_PATCHVER:=5.4
target/linux/omap/Makefile:KERNEL_PATCHVER:=5.4
target/linux/oxnas/Makefile:KERNEL_PATCHVER:=5.4
target/linux/oxnas/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/pistachio/Makefile:KERNEL_PATCHVER:=5.4
target/linux/ramips/Makefile:KERNEL_PATCHVER:=5.4
target/linux/ramips/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/realtek/Makefile:KERNEL_PATCHVER:=5.4
target/linux/rockchip/Makefile:KERNEL_PATCHVER=5.4
target/linux/rockchip/Makefile:KERNEL_TESTING_PATCHVER=5.10
target/linux/sunxi/Makefile:KERNEL_PATCHVER:=5.4
target/linux/sunxi/Makefile:KERNEL_TESTING_PATCHVER:=5.4
target/linux/tegra/Makefile:KERNEL_PATCHVER := 5.4
target/linux/tegra/Makefile:KERNEL_TESTING_PATCHVER := 5.10
target/linux/uml/Makefile:KERNEL_PATCHVER:=5.4
target/linux/x86/Makefile:KERNEL_PATCHVER:=5.4
target/linux/x86/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/zynq/Makefile:KERNEL_PATCHVER:=5.4

So at least the following targets should be more or less fine:

$ git grep -e ^KERNEL_PATCHVER -e ^KERNEL_TESTING_PATCHVER | grep 5\\.10
target/linux/apm821xx/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/armvirt/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/ath79/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/bcm53xx/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/bcm63xx/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/bmips/Makefile:KERNEL_PATCHVER:=5.10
target/linux/gemini/Makefile:KERNEL_PATCHVER:=5.10
target/linux/imx6/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/ipq806x/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/kirkwood/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/lantiq/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/malta/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/mediatek/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/mediatek/mt7622/target.mk:KERNEL_PATCHVER:=5.10
target/linux/mediatek/mt7623/target.mk:KERNEL_PATCHVER:=5.10
target/linux/mpc85xx/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/mvebu/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/mxs/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/octeon/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/oxnas/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/ramips/Makefile:KERNEL_TESTING_PATCHVER:=5.10
target/linux/rockchip/Makefile:KERNEL_TESTING_PATCHVER=5.10
target/linux/tegra/Makefile:KERNEL_TESTING_PATCHVER := 5.10
target/linux/x86/Makefile:KERNEL_TESTING_PATCHVER:=5.10

fonix232 · August 18, 2021, 1:02pm

Yeah, one can do that - I was more thinking that a core developer working on OpenWrt might have a slightly quicker, OTOH answer, something like "most targets are running 5.10 without issues, but we have arch X having issues with this and that".