I changed the WAN DNS server from the ISP default to 1.1.1.1,9.9.9.9
On SAVE, Route 10 became unresponsive and no way of getting to the cloud controller.
There is an issue with teh DHCP service on it just not stable, slightess change and the unit locks up, forecd to go through muliple resets and remove the unit from cloud controller to regain access.
The unit is not stable enough for production, I am reaching a point of putting my Unifi Gateway back inplay as, the most basic of changes is crashing or locking up the Route 10. I would rather the Route10 just worked.
So far have experience the need to RESET and Reinstall
- Setting Static IP for LAN deviecs
- Changing the WAN DNS servers
- LAN ports Native LAN changed from VLAN1 to another when editing LAN device IP/Static, LAN IP/DHCP resulting in lockign out switches and Access Points
looks like interaction with the units DHCP side of this is frought with danger.
DHCP is a core service for a router, there is obviously something wrong in the setup or config.
Please can someone from **Team ALTA ** take a look at whats happening.
@Quackers Thank you for letting us know you are experiencing stability issued. All of what you have listed is certainly abnormal behavior. There should be no issues making the changes you are.
I will have a member of our support team reach out ASAP to look at what’s going on. Can you send me a DM with a phone number and email address we can use to reach out directly?
Thank you for your patience and for working with us. We will get this resolved.
Thank you for reaching out, much appreciated, I will be happy to work with the team to get this sorted.
@Alta-Chase
I removed a IoT device then assigned a sticky IP to the device, changed Icon,
Usual behaviour Port change Native VLAN from 1 to 20:
18 11:03:29 OpenWrt daemon.alert cfg: run “uci commit dhcp”
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “diff /etc/config/dhcp.orig /etc/config/dhcp”
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “echo > /etc/config/upnpd”
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “uci set upnpd.config=upnpd”
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “uci set upnpd.config.enabled=‘0’”
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “uci commit upnpd”
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “/etc/init.d/miniupnpd stop”
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run "if /etc/init.d/radiusd running; then /etc/init.d/radiusd st18vpn:03:29 OpenWrt daemon.alert cfg: vpn servers is not an array
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run "/etc/init.d/avaradiusd running; then /etc/init.d/radiusd st18vpn:03:29 OpenWrt daemon.alert cfg: vpn servers is not an array
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “/etc/init.d/avahi-daemonavahi-daemondaemon.conf /etc/avahi/.avahi-daemon.conf”
Nov 18 11:03:29 OpenWrt daemon.info avahi-daemon[12510]: Files changed, reloading.
Nov 18 11:03:29 OpenWrt daemon.info avahi-daemon[12510]: No service file found in /etc/avahi/services.
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “/etc/init.d/avahi-daemon enable”
Nov 18 11:03:29 OpenWrt daemon.alert cfg: Warn: /etc/ini… rc: 256
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “uci set syslogd.remote.host=‘’”
Nov 18 11:03:29 OpenWrt daemon.info avahi-daemon[12510]: Files changed, reloading.
Nov 18 11:03:29 OpenWrt daemon.info avahi-daemon[12510]: No service file found in /etc/avahi/services.
Nov 18 11:03:29 OpenWrt daemon.alert cfg: run “uci set syslogd.remote.port=‘’”
Nov 18 11:03:30 OpenWrt daemon.notice rc: [2024/11/18 11:03:30:2238] N: JSON: {“stats”:120}
Nov 18 11:03:30 OpenWrt daemon.notice rc: [2024/11/18 11:03:30:4574] N: JSON: {“reqStats”:{“start”:1731927749,“stop”:1731927810,“period”:“seconds”,“clientId”:“MAoT9ACov7h7q6nhOWzk”}}
Nov 18 11:03:32 OpenWrt daemon.notice netifd: Network device ‘eth0’ link is up
Nov 18 11:03:32 OpenWrt daemon.notice netifd: 8021q ‘eth0.15’ link is up
Nov 18 11:03:32 OpenWrt daemon.notice netifd: 8021q ‘eth0.20’ link is up
Nov 18 11:03:32 OpenWrt kern.info kernel: [80867.750738] nss-dp 3a500000.dp1 eth0: PHY Link up speed: 2500
Nov 18 11:03:32 OpenWrt kern.info kernel: [80867.750910] br-lan_15: port 1(eth0.15) entered blocking state
Nov 18 11:03:32 OpenWrt kern.info kernel: [80867.750914] br-lan_15: port 1(eth0.15) entered forwarding state
Nov 18 11:03:32 OpenWrt kern.info kernel: [80867.750969] br-lan_20: port 1(eth0.20) entered blocking state
Nov 18 11:03:32 OpenWrt kern.info kernel: [80867.750972] br-lan_20: port 1(eth0.20) entered forwarding state
Nov 18 11:03:32 OpenWrt kern.warn kernel: [80867.751014] Set globle Ageing time set to 300 which is same for all bridge
Nov 18 11:03:32 OpenWrt kern.warn kernel: [80867.751016] Set globle Ageing time set to 300 which is same for all bridge
Nov 18 11:04:10 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 11:04:30 OpenWrt daemon.notice rc: [2024/11/18 11:04:30:7795] N: JSON: {“stats”:120}
Nov 18 11:05:10 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 11:05:31 OpenWrt daemon.notice rc: [2024/11/18 11:05:31:2218] N: JSON: {“stats”:120}
something is not happy…. changed an ICON and set a NAME, GREP for failed:
Nov 18 12:50:00 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 12:51:01 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 12:52:01 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 12:53:02 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 12:54:02 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 12:55:03 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 12:56:03 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 12:57:04 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 12:58:04 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 12:59:05 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Nov 18 13:00:05 OpenWrt user.notice root: failed to send crash: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 –
Can you reproduce this on a minimal site with just the Route10 and a couple of the devices you know are working incorrectly? I have been unable to reproduce any of your reports so far.
I will give this idea a go on the weekend, cant afford loss of service during this week.
Just want to understand the logic here - If I change say a STATIC IP in teh ghui from 192.168.20.9 to 192.168.20.12 —
What I see is any DHCP change seems to reload the whole router config, is this correct behaviour?
Why would. a DHCP address change, cause a Port to change it’s native VLAN?
note: Simple change of one Sticky IP to Another for a device - Same blocking issue on a Port
Route10:~# cat /var/log/messages | grep “eth2”
Nov 19 12:03:10 OpenWrt kern.info kernel: [82051.098635] br-lan_20: port 5(eth2) entered disabled state
Nov 19 12:03:12 OpenWrt daemon.notice netifd: Network device ‘eth2’ link is up
Nov 19 12:03:12 OpenWrt daemon.notice netifd: 8021q ‘eth2.15’ link is up
Nov 19 12:03:12 OpenWrt kern.info kernel: [82053.307133] nss-dp 3a508000.dp3 eth2: PHY Link up speed: 1000
Nov 19 12:03:12 OpenWrt kern.info kernel: [82053.307227] br-lan_20: port 5(eth2) entered blocking state
Nov 19 12:03:12 OpenWrt kern.info kernel: [82053.307230] br-lan_20: port 5(eth2) entered forwarding state
Nov 19 12:03:12 OpenWrt kern.info kernel: [82053.307671] br-lan_15: port 3(eth2.15) entered blocking state
Nov 19 12:03:12 OpenWrt kern.info kernel: [82053.307674] br-lan_15: port 3(eth2.15) entered forwarding state
Nov 19 12:07:12 OpenWrt daemon.alert cfg: run “uci set network.@device[-1].ifname=‘eth2’”
Nov 19 12:07:12 OpenWrt daemon.alert cfg: run “uci set network.@device[-1].name=‘eth2.15’”
Nov 19 12:07:12 OpenWrt daemon.alert cfg: run “uci set network.@device[-1].ifname=‘eth2’”
Nov 19 12:07:12 OpenWrt daemon.alert cfg: run “uci set network.@device[-1].name=‘eth2.20’”
Nov 19 12:07:12 OpenWrt daemon.alert cfg: run “uci set network.@device[-1].ports=‘eth2 eth0 eth5 eth4’”
Nov 19 12:07:12 OpenWrt daemon.alert cfg: run “uci set network.@device[-1].ports=‘eth2.15 eth0.15 eth5.15 eth4.15’”
Nov 19 12:07:12 OpenWrt daemon.alert cfg: run “uci set network.@device[-1].ports=‘eth2.20 eth0.20 eth5.20 eth4.20’”
Nov 19 12:07:12 OpenWrt kern.warn kernel: [82293.471584] nss_ppe_lag_update_slave[131]:ffffff803be53538: Upper dev is not LAG for dev: eth2
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.472197] br-lan_20: port 3(eth2.20) entered blocking state
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.472201] br-lan_20: port 3(eth2.20) entered disabled state
Nov 19 12:07:12 OpenWrt kern.warn kernel: [82293.472275] nss_ppe_lag_update_slave[131]:ffffff803be53b48: Upper dev is not LAG for dev: eth2.20
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.472873] device eth2.20 entered promiscuous mode
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.472935] br-lan_20: port 3(eth2.20) entered blocking state
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.472938] br-lan_20: port 3(eth2.20) entered forwarding state
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.473021] br-lan_20: port 5(eth2) entered disabled state
Nov 19 12:07:12 OpenWrt kern.warn kernel: [82293.503717] nss_ppe_lag_update_slave[131]:ffffff803be53b58: Upper dev is not LAG for dev: eth2
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.503904] device eth2.15 left promiscuous mode
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.503967] br-lan_15: port 3(eth2.15) entered disabled state
Nov 19 12:07:12 OpenWrt kern.warn kernel: [82293.536096] nss_ppe_lag_update_slave[131]:ffffff803be53b58: Upper dev is not LAG for dev: eth2.15
Nov 19 12:07:12 OpenWrt kern.warn kernel: [82293.536782] nss_ppe_lag_update_slave[131]:ffffff803be53768: Upper dev is not LAG for dev: eth2
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.555455] device eth2.20 left promiscuous mode
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.555459] device eth2 left promiscuous mode
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.555552] br-lan_20: port 3(eth2.20) entered disabled state
Nov 19 12:07:12 OpenWrt kern.warn kernel: [82293.572070] nss_ppe_lag_update_slave[131]:ffffff803be53b58: Upper dev is not LAG for dev: eth2.20
Nov 19 12:07:12 OpenWrt kern.warn kernel: [82293.572978] nss_ppe_lag_update_slave[131]:ffffff803be53768: Upper dev is not LAG for dev: eth2
Nov 19 12:07:12 OpenWrt kern.info kernel: [82293.595510] nss-dp 3a508000.dp3 eth2: PHY Link is down
Nov 19 12:07:13 OpenWrt kern.warn kernel: [82293.723834] nss_ppe_lag_update_slave[131]:ffffff803be53538: Upper dev is not LAG for dev: eth2
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.724474] br-lan_15: port 3(eth2.15) entered blocking state
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.724484] br-lan_15: port 3(eth2.15) entered disabled state
Nov 19 12:07:13 OpenWrt kern.warn kernel: [82293.724574] nss_ppe_lag_update_slave[131]:ffffff803be53b48: Upper dev is not LAG for dev: eth2.15
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.725179] device eth2.15 entered promiscuous mode
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.725181] device eth2 entered promiscuous mode
Nov 19 12:07:13 OpenWrt kern.warn kernel: [82293.726246] nss_ppe_lag_update_slave[131]:ffffff803be53538: Upper dev is not LAG for dev: eth2
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.727026] br-lan_20: port 3(eth2.20) entered blocking state
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.727037] br-lan_20: port 3(eth2.20) entered disabled state
Nov 19 12:07:13 OpenWrt kern.warn kernel: [82293.727188] nss_ppe_lag_update_slave[131]:ffffff803be53b48: Upper dev is not LAG for dev: eth2.20
Nov 19 12:07:13 OpenWrt daemon.notice netifd: Network device ‘eth2’ link is down
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.727831] device eth2.20 entered promiscuous mode
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.728314] br-lan: port 1(eth2) entered blocking state
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.728323] br-lan: port 1(eth2) entered disabled state
Nov 19 12:07:13 OpenWrt kern.warn kernel: [82293.728491] nss_ppe_lag_update_slave[131]:ffffff803be53b48: Upper dev is not LAG for dev: eth2
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.728789] br-lan: port 1(eth2) entered blocking state
Nov 19 12:07:13 OpenWrt kern.info kernel: [82293.728792] br-lan: port 1(eth2) entered forwarding state
Nov 19 12:07:13 OpenWrt daemon.notice netifd: 8021q ‘eth2.15’ link is down
Nov 19 12:07:13 OpenWrt daemon.alert cfg: run “uci set lldpd.config.interface=‘eth0 eth1 eth2 eth3 eth4 eth5’”
Nov 19 12:07:13 OpenWrt kern.info kernel: [82294.547583] br-lan: port 1(eth2) entered disabled state
Nov 19 12:07:16 OpenWrt daemon.notice netifd: Network device ‘eth2’ link is up
Nov 19 12:07:16 OpenWrt daemon.notice netifd: 8021q ‘eth2.15’ link is up
Nov 19 12:07:16 OpenWrt daemon.notice netifd: 8021q ‘eth2.20’ link is up
Nov 19 12:07:16 OpenWrt kern.info kernel: [82296.787974] nss-dp 3a508000.dp3 eth2: PHY Link up speed: 1000
Nov 19 12:07:16 OpenWrt kern.info kernel: [82296.788027] br-lan: port 1(eth2) entered blocking state
Nov 19 12:07:16 OpenWrt kern.info kernel: [82296.788031] br-lan: port 1(eth2) entered forwarding state
Nov 19 12:07:16 OpenWrt kern.info kernel: [82296.788183] br-lan_15: port 3(eth2.15) enteredstrong text blocking state
Nov 19 12:07:16 OpenWrt kern.info kernel: [82296.788186] br-lan_15: port 3(eth2.15) entered forwarding state
Nov 19 12:07:16 OpenWrt kern.info kernel: [82296.788231] br-lan_20: port 3(eth2.20) entered blocking state
Nov 19 12:07:16 OpenWrt kern.info kernel: [82296.788234] br-lan_20: port 3(eth2.20) entered forwarding state
@Alta-Josh
did notice one odd entry in the. dhcp.leases
1732079008 00:1e:2b:01:cd:88 192.168.20o.8 IoT1 ff:71:7b:fd:ca:00:02:00:00:ab:11:b4:38:a8:9f:6f:12:9a:cb
All other entries have 01: + the mac address
so would expect IoT 1 to look like this:
1732079008 00:1e:2b:01:cd:88 192.168.200.8 IOT1 01:00:1e:2b:01:cd:88
Any ideas?
Bit more digging around foun has 2 devices with the same IP 192.168.200.8
Changed one to .28
will see what happens after the leases expires on the .8 device
1 Like