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

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’écran 2021-08-03 à 09.40.59

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

Cheers.

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

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

1 Like

Master is also UBI based?

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

1 Like

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

1 Like

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

3 Likes

Hello look this discussion

Maybe October November full support

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

4 Likes

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

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

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

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

Could someone offer me a few pointers, on how to chase-down a problem?

I've got snapshot r17443-90e167abaa / git-21.226.86205-376af36 (UBI) installed on my E8450. After a spontaneous reboot, I find all the settings disappeared, and it seems that nothing but tempfs is mounted. This means I can't make any durable changes, and it seems I can't upgrade, as well, which I had thought might fix the default mount points. (I've tried via a direct install of downloaded images, and via luci-app-attendedsysupgrade.)

FWIW, it was behaving nicely for several weeks, before the reboot, with wi-fi and SQM, excellent throughput, etc.

When I say UBI, I'm pretty sure I followed the plan to migrate to UBI, and the splash-page claims it is running the UBI build.

Do you has install a last version of dango ? 0.6.0

Thanks for the reply. I didn't install that, but just worked from a downloaded installer. I can try it.

1 Like

you welcome you 're will do make install like this first

https://github.com/dangowrt/linksys-e8450-openwrt-installer/releases/download/v0.6.0/openwrt-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itb

then just after the last snapshot

https://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/openwrt-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb

you d'ont have the luci installed with luci

make an opkg update and opkg install luci after the all flash

Oops. I can't build the installer on OSX. But using the pre-built images at https://github.com/dangowrt/linksys-e8450-openwrt-installer/releases, with "force" on the recovery-installer, then installing the ubi-squashfs update, then reboot ... puts me right back into snapshot r17443-90e167abaa, with nothing but tmpfs.

we don't need a build image i didn't understand you want build

just the two files then go in putty for update

Okay, a post from dangowrt in this conversation helped me figure it out:
https://githubmemory.com/repo/dangowrt/linksys-e8450-openwrt-installer/issues/10

I was somehow stuck in initramfs/recovery mode. I force (re-)installed the ubi-squashfs-sysupgrade.itb that I originally used to install v0.5.3. This now showed /rom mounted.

Then, I used ssh and opkg to get 'auc' installed, and 'auc -f' was able to pull and install the new image.

I appreciate your help.

1 Like