Luci Attended Sysupgrade issue when keeping configurations

Did an upgrade from 25.12.4 to 25.12.6 on a Linksys E8450. The wan definitions in the network config file got messed up.

Someone else had this same issue on different hardware a few days before this issue on 10/29/26. It is posted on the 25.12.6 announcement post.

Had asked Luci to generate a firmware image that I downloaded. Then asked Luci to flash that firmware after I uploaded it. After the boot, the internet was not reachable. Found bad wan entries in the network config file.

Below is pasted the before and after network config file. Note the "bad" wan entries.

One oddity is that there were a couple of comments in the network config file right before the wan entries. Those comments did not get carried over to the new network file. (likely not a factor, but thought it should be mentioned).

 before network file

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        list ipaddr '127.0.0.1/8'

config globals 'globals'
        option dhcp_default_duid '00042df4415ccff14a4aa65020bffbf424a9'
        option ula_prefix 'fdc9:9744:88dd::/48'
        option packet_steering '1'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ip6assign '60'
        list ipaddr '192.168.4.1/24'
        option multipath 'off'

#### was this way from luci chg 10/28/26 list ipaddr '192.168.4.1/24'
#### tried 10/28/26 to fix ethernet, did not work: option ipaddr '192.168.4.1/24'

config interface 'wan'
        option device 'wan'
        option proto 'dhcp'
        option type 'bridge'

config interface 'wan6'
        option device 'wan'
        option proto 'dhcpv6'
        option type 'bridge'
        option auto '0'
        option reqaddress 'try'
        option reqprefix 'auto'
        option norelease '1'
        option multipath 'off'

config device
        option type 'bridge'
        option name 'br-guest'

config interface 'guest'
        option proto 'static'
        option device 'br-guest'
        option multipath 'off'
        list ipaddr '192.168.8.1/24'

after network file

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        list ipaddr '127.0.0.1/8'

config globals 'globals'
        option dhcp_default_duid '00042df4415ccff14a4aa65020bffbf424a9'
        option ula_prefix 'fdc9:9744:88dd::/48'
        option packet_steering '1'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ip6assign '60'
        list ipaddr '192.168.4.1/24'
        option multipath 'off'

config interface 'wan'
        option device 'br-wan'
        option proto 'dhcp'

config interface 'wan6'
        option device 'br-wan6'
        option proto 'dhcpv6'
        option auto '0'
        option reqaddress 'try'
        option reqprefix 'auto'
        option norelease '1'
        option multipath 'off'

config device
        option type 'bridge'
        option name 'br-guest'

config interface 'guest'
        option proto 'static'
        option device 'br-guest'
        option multipath 'off'
        list ipaddr '192.168.8.1/24'

config device
        option name 'br-wan'
        option type 'bridge'

config device
        option name 'br-wan6'
        option type 'bridge'

In-line comments using the pound sign are not saved.

Since your before and after examples both have bad WAN configs, can you describe your desired WAN setup?

We'll help you fix it.

URL?

Thanks for your help!
Here is the url of the other person with a similar issue:

I have the router working ok now. You've made me aware that my current wan stmts do not match the network entries going into the upgrade. Here is what I have running. It does not have the "option type 'bridge'" line on the wan6 entry.
currently running wan and wan6 entries:

config interface 'wan'
        option device 'wan'
        option proto 'dhcp'
        option type 'bridge'

config interface 'wan6'
        option device 'wan6'
        option proto 'dhcpv6'
        option auto '0'
        option reqaddress 'try'
        option reqprefix 'auto'
        option norelease '1'
        option multipath 'off'

Please let me know where my entries are "bad".

That's difficult because you have thing missing, but I'll try:

  • (before) you have an interface configuration for wan, but no device configuration
  • It's unclear why you are making guest, wan, and wan6 bridges
  • you added no physical ports to these bridges

Looks good.

You said: "It's unclear why you are making guest, wan, and wan6 bridges".
To my understanding of all this, I had nothing to do with the wan and wan6 bridges.
I installed this software for the first time back in June and added guest networks. So that is likely why I have a guest bridge. I don't remember if Luci did all that for me or if I had to make changes to the network file myself.
However, I had nothing to do with wan and wan6 bridges (at least to my understanding). Those showed up during the upgrade process.

Does that all make sense? Seems like a bug to me.

Noticed today there is another post with this same issue. That totals 3 posts with this issue. Here is the post:

FWIW, the problem begins with the before network file.

The type 'bridge' option is a relic of an old syntax and has no place in the interface sections.

This did not affect the operation of the wan interface in the previous software version (except that a wan bridge wouldn't work). After the upgrade, an unsuccessful attempt is made to adapt the (incorrect) interface(s) configuration using the new syntax, the wan interface has not been added to br-wan in the corresponding device section, resulting in a bridge with no member(s).

Now the question is how option type 'bridge' ended up in the interface section.

This could be the answer.

Thank you so much for your post. It likely clarifies why the upgrade created bad wan and wan6 statements. It is always good to know the root cause of an issue. One good thing about having to do this digging / troubleshooting is the side benefit of learning more about this software! I am thankful that I have 2 identical routers, one being production and the second being test. With this software, I would hate to be in the situation of having just a production router that may not work after flashing an upgrade.