[SOLVED] OpenWrt One update from 24.10.6 to 25.12.2 no IP assigned

Installing and Using OpenWrt Network and Wireless Configuration
1

Hey

I have 3 openwrt router and two of them updated just fine. The third one is a bit more configuration involved, mainly to pass on VLANS.

After the update there is no IP assigned for the OpenWrt One router. So might be an DHCP issue but I haven’t figured it out yet. Could be also related to the VLAN configuration.

I’ll leave the configs below. Maybe someone had the issue as well?

OpenWrt One:

{
        "kernel": "6.6.127",
        "hostname": "OpenWrt-One",
        "system": "ARMv8 Processor rev 4",
        "model": "OpenWrt One",
        "board_name": "openwrt,one",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.6",
                "revision": "r29141-81be8a8869",
                "target": "mediatek/filogic",
                "description": "OpenWrt 24.10.6 r29141-81be8a8869",
                "builddate": "1773709139"
        }
}

DHCP:

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option cachesize '1000'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option nonwildcard '1'
        option localservice '1'
        option ednspacket_max '1232'
        option filter_aaaa '0'
        option filter_a '0'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'

config dhcp 'one'
        option interface 'one'
        option start '100'
        option limit '150'
        option leasetime '12h'

config dhcp 'one_only'
        option interface 'one_only'
        option start '100'
        option limit '150'
        option leasetime '12h'

firewall:

config defaults
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option synflood_protect '1'

config zone
        option name 'wan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option masq '1'
        option mtu_fix '1'
        list network 'wan'
        list network 'wan6'

config rule
        option src 'wan'
        option name 'Allow HTTP, HTTPS from WAN'
        list proto 'tcp'
        option dest_port '80 443'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCP-Renew'
        option src 'wan'
        option proto 'udp'
        option dest_port '68'
        option target 'ACCEPT'
        option family 'ipv4'

config rule
        option name 'Allow-Ping'
        option src 'wan'
        option proto 'icmp'
        option icmp_type 'echo-request'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-IGMP'
        option src 'wan'
        option proto 'igmp'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCPv6'
        option src 'wan'
        option proto 'udp'
        option dest_port '546'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-MLD'
        option src 'wan'
        option proto 'icmp'
        option src_ip 'fe80::/10'
        list icmp_type '130/0'
        list icmp_type '131/0'
        list icmp_type '132/0'
        list icmp_type '143/0'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Input'
        option src 'wan'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        list icmp_type 'router-solicitation'
        list icmp_type 'neighbour-solicitation'
        list icmp_type 'router-advertisement'
        list icmp_type 'neighbour-advertisement'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Forward'
        option src 'wan'
        option dest '*'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config redirect
        option target 'DNAT'
        list proto 'tcp'
        option src 'wan'
        option src_dport '38745'
        option dest_ip '192.168.1.1'
        option dest_port '38745'
        option name 'Allow ssh on wan'

config zone
        option name 'one_only'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'one_only'

config forwarding
        option src 'one_only'
        option dest 'wan'

network:

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fdd5:cea4:57d9::/48'
        option packet_steering '1'

config device
        option name 'VLANS'
        option type 'bridge'
        list ports 'eth0'
        list ports 'eth1'

config bridge-vlan
        option device 'VLANS'
        option vlan '1'
        list ports 'eth0:t'
        list ports 'eth1:t'

config bridge-vlan
        option device 'VLANS'
        option vlan '3'
        list ports 'eth0:u*'

config bridge-vlan
        option device 'VLANS'
        option vlan '50'
        list ports 'eth0:t'
        list ports 'eth1:t'

config bridge-vlan
        option device 'VLANS'
        option vlan '55'
        list ports 'eth0:t'
        list ports 'eth1:t*'

config bridge-vlan
        option device 'VLANS'
        option vlan '80'
        list ports 'eth0:t'
        list ports 'eth1:t'

config interface 'one_only'
        option proto 'static'
        option device 'VLANS.1'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        list dns '192.168.50.215'

config interface 'private50'
        option proto 'none'
        option device 'VLANS.50'

config interface 'checks'
        option proto 'none'
        option device 'VLANS.55'

config interface 'IoT80'
        option proto 'none'
        option device 'VLANS.80'

config interface 'wan'
        option device 'VLANS.3'
        option proto 'dhcp'

config interface 'wan6'
        option device 'VLANS.3'
        option proto 'dhcpv6'

So once I update to the latest version 25.12.2 I’m also not able to connect directly or via switch to the device anymore.

As I mentioned above, it might be related to the VLANS and/or DHCP configuration. Both ports are VLAN tagged.

Thanks!

2

The problem has nothing to do with the update. The issue is instead with the firewall config. You do not allow input from the one_only network and the one network doesn’t isn’t associated with a firewall zone.

3

Thanks!

I’ll test it once the issue OSError: [Errno 28] No space left on device: '/srv/store/…' is solved.

The one network is probably something related from some setups before one_only. I got rid off it.

Didn’t noticed the input reject option. Thanks. Need to allow dhcp. Just wondering why does it work this way on v24.10.6 but not with v25.12.2?

Edit:

I just installed the squashfs-sysupgrade file and restored the backup with the same issue. I think its something else. The switch at least works though.

4

You linked another thread - can you show the post(s) that discuss the issue?

5

Nah, it’s the right one LuCI Attended Sysupgrade support thread - #791 by BIGFAT. Just scroll to the bottom. Just a few ran into that issue.

This is probably a similar one Can't upgrade 25.10.0 on WRT32X

Edit:

But it seems to be solved anyway. I can also use the firmware-selector again which ran into the same issue.

6

It's over 700 posts. Surely you jest.

Cool.

I see now, this is an error on the server. That wasn't clear initially. Thanks for the clarification.

7

Hehe, nope no jest. That’s actually poping up if you run into that issue via sysupgrade. There is this link LuCI Attended Sysupgrade support thread - #791 by BIGFAT to get support.

Yeah, I thought an issue on the device itself but makes totally sense.

8

@psherman
I'm trying to fight this game again.
I'm pinging you because we've set this up beforehand here Two openwrt routers with IoT devices on both? - #16 by psherman

So I updated it now to the latest version 25.12.4. The only thing I've changed before the update is that I Untagged port 1 which was tagged as well. The reason why I have done it is because I wouldn't have any chance to reach the router. So basically, I had to reset v25.12.4 falsh 24.10.7 and restore the backup.
That said that everything works like it is on v24 but not on 25.

I guess the issue is related on port0 (VLAN3 - WAN). There is nothing coming through. No internet, no DHCP assigned which would makes sense, to me at least, why port1 doesn't work either (tagged).
Are there any new firewall rules in v25?

9

I think here is the issue:

[Jun 7, 2026, 9:57:40 AM GMT+12] kern.info: [  515.922829] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[Jun 7, 2026, 9:57:40 AM GMT+12] kern.info: [  515.923364] VLANS: port 1(eth0) entered blocking state
[Jun 7, 2026, 9:57:40 AM GMT+12] kern.info: [  515.936413] VLANS: port 1(eth0) entered forwarding state
[Jun 7, 2026, 9:57:40 AM GMT+12] daemon.notice: netifd: Network device 'eth0' link is up
[Jun 7, 2026, 9:57:41 AM GMT+12] kern.info: [  516.827839] mtk_soc_eth 15100000.ethernet eth0: Link is Down
[Jun 7, 2026, 9:57:41 AM GMT+12] daemon.notice: netifd: Network device 'eth0' link is down
[Jun 7, 2026, 9:57:41 AM GMT+12] kern.info: [  516.933198] VLANS: port 1(eth0) entered disabled state
[Jun 7, 2026, 9:57:43 AM GMT+12] kern.info: [  518.407342] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

Maybe related to this Wan eth interface goes up and down periodically - #2 by anon22003091

10

It is best to look at your config.

11

Hey

I'm back to v24 and restored my backup. So It's the same again as in the first post.

12

If the config is really the same as in the initial post, then my original observation may still apply...

There were possibly other issues in your setup at the time -- you had talked about running out of space and a few other things.

That being said... what is the current status in terms of what is and is not working?

13

There were possibly other issues in your setup at the time -- you had talked about running out of space and a few other things.

The out of space issue is not an issue anymore.

I'm now on v25 again and I allowed input on one_only and deleted one network (no need) and also untagged port1 to have access to the router.

Here is the output on v25:

One:


{
        "kernel": "6.12.87",
        "hostname": "OpenWrt-One",
        "system": "ARMv8 Processor rev 4",
        "model": "OpenWrt One",
        "board_name": "openwrt,one",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "25.12.4",
                "firmware_url": "https://downloads.openwrt.org/",
                "revision": "r32933-4ccb782af7",
                "target": "mediatek/filogic",
                "description": "OpenWrt 25.12.4 r32933-4ccb782af7",
                "builddate": "1778712129"
        }
}

DHCP:

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option cachesize '1000'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option nonwildcard '1'
        option localservice '1'
        option ednspacket_max '1232'
        option filter_aaaa '0'
        option filter_a '0'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/odhcpd.leases'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'
        option piodir '/tmp/odhcpd-piodir'
        option hostsdir '/tmp/hosts'

config dhcp 'one_only'
        option interface 'one_only'
        option start '100'
        option limit '150'
        option leasetime '12h'

firewall:

config defaults
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option synflood_protect '1'

config zone
        option name 'wan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option masq '1'
        option mtu_fix '1'
        list network 'wan'
        list network 'wan6'

config rule
        option src 'wan'
        option name 'Allow HTTP, HTTPS from WAN'
        list proto 'tcp'
        option dest_port '80 443'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCP-Renew'
        option src 'wan'
        option proto 'udp'
        option dest_port '68'
        option target 'ACCEPT'
        option family 'ipv4'

config rule
        option name 'Allow-Ping'
        option src 'wan'
        option proto 'icmp'
        option icmp_type 'echo-request'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-IGMP'
        option src 'wan'
        option proto 'igmp'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCPv6'
        option src 'wan'
        option proto 'udp'
        option dest_port '546'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-MLD'
        option src 'wan'
        option proto 'icmp'
        option src_ip 'fe80::/10'
        list icmp_type '130/0'
        list icmp_type '131/0'
        list icmp_type '132/0'
        list icmp_type '143/0'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Input'
        option src 'wan'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        list icmp_type 'router-solicitation'
        list icmp_type 'neighbour-solicitation'
        list icmp_type 'router-advertisement'
        list icmp_type 'neighbour-advertisement'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Forward'
        option src 'wan'
        option dest '*'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config redirect
        option target 'DNAT'
        list proto 'tcp'
        option src 'wan'
        option src_dport '38745'
        option dest_ip '192.168.1.1'
        option dest_port '38745'
        option name 'Allow ssh on wan'

config zone
        option name 'one_only'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'one_only'
        list device 'VLANS.1'

config forwarding
        option src 'one_only'
        option dest 'wan'

network:

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fdd5:cea4:57d9::/48'
        option packet_steering '1'
        option dhcp_default_duid '0004bed34fa98ff74d80963a59e3e5c0708a'

config device
        option name 'VLANS'
        option type 'bridge'
        list ports 'eth0'
        list ports 'eth1'

config bridge-vlan
        option device 'VLANS'
        option vlan '1'
        list ports 'eth0:t'
        list ports 'eth1:u*'

config bridge-vlan
        option device 'VLANS'
        option vlan '3'
        list ports 'eth0:u*'

config bridge-vlan
        option device 'VLANS'
        option vlan '50'
        list ports 'eth0:t'
        list ports 'eth1:t'

config bridge-vlan
        option device 'VLANS'
        option vlan '55'
        list ports 'eth0:t'
        list ports 'eth1:t'

config bridge-vlan
        option device 'VLANS'
        option vlan '80'
        list ports 'eth0:t'
        list ports 'eth1:t'

config interface 'one_only'
        option proto 'static'
        option device 'VLANS.1'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        list dns '192.168.50.215'

config interface 'private50'
        option proto 'none'
        option device 'VLANS.50'

config interface 'checks'
        option proto 'none'
        option device 'VLANS.55'

config interface 'IoT80'
        option proto 'none'
        option device 'VLANS.80'

config interface 'wan'
        option device 'VLANS.3'
        option proto 'dhcp'

config interface 'wan6'
        option device 'VLANS.3'
        option proto 'dhcpv6'
14

I'll take a look at the configs in a minute, but what is working and what is not right now?

It appears that this may not be the main router -- is that the case? If so, what's the upstream? Can you describe (or better yet -- diagram) the network topology?

15

On v24 everything works fine with this config (apart the change of the untagged/tagged port situation to access on port1 for v25).

On v25 the interface eth0 (WAN - port0) goes up and down:

[Jun 7, 2026, 9:57:40 AM GMT+12] kern.info: [  515.922829] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[Jun 7, 2026, 9:57:40 AM GMT+12] kern.info: [  515.923364] VLANS: port 1(eth0) entered blocking state
[Jun 7, 2026, 9:57:40 AM GMT+12] kern.info: [  515.936413] VLANS: port 1(eth0) entered forwarding state
[Jun 7, 2026, 9:57:40 AM GMT+12] daemon.notice: netifd: Network device 'eth0' link is up
[Jun 7, 2026, 9:57:41 AM GMT+12] kern.info: [  516.827839] mtk_soc_eth 15100000.ethernet eth0: Link is Down
[Jun 7, 2026, 9:57:41 AM GMT+12] daemon.notice: netifd: Network device 'eth0' link is down
[Jun 7, 2026, 9:57:41 AM GMT+12] kern.info: [  516.933198] VLANS: port 1(eth0) entered disabled state
[Jun 7, 2026, 9:57:43 AM GMT+12] kern.info: [  518.407342] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

So the VLANs from the other router can't be passed on to eth1 - switch and so on. So basically if I run the update from v24 to v25 (without changing the port1 to untagged) it will be stuck and I can't access the router because having the interface eth0 up and down all the time.

Just noticed this port 1(eth0), shouldn't be this port 0? port 1 is actually eth1.

Edit:

Can you describe (or better yet -- diagram) the network topology?

We ran through this on this thread - Two openwrt routers with IoT devices on both? - #8 by XsbSkRprwO

Nothing has really changed since then.

16

Your device does not have a switch, so you can actually use direct dotted notation.

That said, I'm not sure I understand the topology -- is the wan here actually being used as a wan? Where do the other VLANs come from/go to?

17

I just edit the post.

Edit:

Can you describe (or better yet -- diagram) the network topology?

We ran through this on this thread - Two openwrt routers with IoT devices on both? - #8 by XsbSkRprwO

Nothing has really changed since then.

It has a switch on eth1. So I'm passing the VLANs to a switch.

So basically on WAN(eth0) and switch(eth1) are used for VLANS (tagged).

Edit:

I'm on v24 again. If you need the config there again.

18

The linked post is quite old and I would have to read over the whole thing to understand it again... I'm not exactly sure when I'll have the time to dig that deep. You do have a diagram in it, but I find it really confusing...

For example, the diagram shows a firewall in two positions -- both of those appear to be distinct blocks relative to the OpenWrt One devices. Are they indeed some other device? Or is that referring to the firewall features in OpenWrt?

Also, you have a a modem connected to the patch panel and then 3 other connections to that same patch panel. What it doesn't show is how those connections relate to each other (that is to say that unlike a switch, we need to know where each cable actually goes since when you simplify the patch panel, each connection can boil down to a cable between two devices).

19

Yeah, I totally understand. Thank you anyway, I really appreciate it. I started this morning with a new diagram. I might finish it before September (v24 EOL) and hopefully understandable for everyone =)

20

It was indeed an issue with the cables. Actually even two weren't in a good nick anymore. The cable tester fished two failed cables. But now I can't use v24 anymore o_O ... really strange ... but the interface eth0 doesn't go up and down anymore on v25.

Anyhow, I'm going to start from scratch based on v25. If I run into any issues I'll start a new topic then. So it's not really solved. Do you prefer to add SOLVED to the thread topic?

Glad that you haven't spend more time on it. Thanks again! Very much!