@OatmealDrifter kinda funny, I have this router too, this post was the first hit on google (i did not specify the router name)
What’s also striking is that I also have 2 subnets on lan (which should work?) for almost the same reason.
Did you ever figure it out? Was it the 2 subnets or something else?
This is not the correct use of subnets. Each network interface should have exactly one subnet (the only exception here is for unmanaged networks such as those used on an ap which will have no address).
Right so I need to do something like this I guess
or change every static ip on those devices/ vm’s that use the old subnet,
I've taken the liberty of moving your posts to a new thread so we can focus on your specific configs and topology.
Can you draw a diagram of your network topology (a photo of a sketch on paper is sufficient) and also post your complete config:
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button (red circle; this works best in the 'Markdown' composer view in the blue oval):
Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
Thanks, I will provide the files soon.
What’s weird is that it didn’t happen at all yesterday. So it’s possible there is some funkiness going on with WiFi .
I still think it’s some wifi connectivity issue. I saw some other (unrelated to lan/wifi) errors in the logs that I fixed, so we’ll see if it gets better now.
But from what were saying originally was:
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ip6assign '60'
list ipaddr '192.168.1.1/24'
list ipaddr '192.168.100.1/24'
isn’t a “supported” configuration (it is however possible to set this via LuCi)? i don’t need dhcp on the 192.168.100.1/24 subnet so that’s fine.
I know that I must have a seondary interface (lan2) if i want dhcp.
It is acceptable to have multiple addresses on a given interface, but they must be in the same subnet.
If you need another subnet, you need to create another network interface.
What are your specific goals?
On my other openwrt install, I had the 192.168.100 subnet as default. Now when I got the GL-MT6000 router I decided to stick with the default openwrt subnet (192.168.1).
But some of my stuff had static IP set to the 192.168.100. subnet, so to keep things simple, I added that. Plan is to move over to the openwrt default network but since the configuration didn’t seem to cause any big issues, I haven’t moved over all devices/vm’s yet.
You can create an alias based interface...
config interface 'oldlan'
option device '@lan'
option proto 'static'
list ipaddr '192.168.100.1/24'
(don't forget to remove this address from the original lan).
That said, you should make the effort to complete the IP address updates as soon as you reasonably can.
Infrastructure devices (like routers, APs, switches) often are best to have setup with static IPs so that a DHCP server outage doesn't cause them all to become unreachable, but beyond that, using DHCP and then DHCP reservations generally makes things easier -- you can quite easily reassign addresses as needed without needing to go to each device individually.
Are you certain that multiple subnets in an interface stanza are an issue? The new list ipaddr <IP>/<CIDR> syntax seems to have been added to not need alias interfaces for this purpose.
Yes. I'm certain.
I'm pretty sure that the examples in that link are incorrect. Adding multiple addresses is legit and valid for a single subnet (for example, maybe you want to assign 192.168.42.1/24 and 192.168.42.25.24). But each network interface is supposed to have just a single subnet. If you want additional subnets, you use additional network interfaces.
I'm just asking because I recently used that syntax to have a stable local management IP while setting up some new devices (router and AP) for a family member and it seemed to work fine (first subnet in the list is used for DHCP, further IP addresses were reachable normally within their subnet).
To me, it seems to work too. The original question from me was not exactly the same since the topic got split up.
I’ve had some issues in the past doing something similar to this in OpenWRT but that was years ago.
I’ve moved most devices now, I might reconsider adding a “proper” secondary subnet for some of them tho’, since it’s quite handy to have.