RUTX50 / Multiple disconnection / LAN UP and Down

[down]

Hello, I do have a Unifi networks. Using UDM-SE as router.

Firmware and router are all up to date from yesterday.

I have connected the RUTX50 (LAN3 or 4) to the WAN1 interface of my UDM. The RUT is connected to my external antenna. Since I have it (3 months) I do have multiple disconnection.

There is a regular UP and Down of my LAN4, after reading this forum, I have moved the connection to LAn3, same pb. The ethernet cable I am using is a CAT7.

see logs:

568;2025-07-17 15:39:54;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
569;2025-07-17 15:39:56;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
570;2025-07-17 15:39:57;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
571;2025-07-17 15:39:59;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
572;2025-07-17 15:40:00;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
573;2025-07-17 15:40:01;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
574;2025-07-17 15:40:01;Switch Events;network;notice;Port speed for port LAN4 changed from 1000 baseT to 100 baseT
575;2025-07-17 15:40:47;Health checker;network;notice;IPv4 connectivity restored
576;2025-07-17 18:48:30;Health checker;network;notice;IPv4 connectivity started to fail
577;2025-07-17 18:48:39;Health checker;network;notice;IPv6 connectivity started to fail
578;2025-07-17 18:58:03;Health checker;network;notice;DNS resolution started to fail
579;2025-07-17 21:44:18;Mobile Data;network;info;Mobile data disconnected (internal modem)
580;2025-07-17 21:44:28;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
581;2025-07-17 21:44:33;Mobile Data;network;info;Mobile data connected (internal modem)
582;2025-07-17 21:44:33;Network Type;network;info;Joined 5G-NSA network (internal modem)
583;2025-07-17 21:44:33;Network Operator;network;info;Connected to 24405 operator (internal modem)
584;2025-07-17 21:44:39;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
585;2025-07-17 21:44:39;Switch Events;network;notice;Port speed for port LAN4 changed from 100 baseT to 1000 baseT
586;2025-07-17 21:44:40;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
587;2025-07-17 21:44:42;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
588;2025-07-17 21:44:43;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
589;2025-07-17 21:44:44;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
590;2025-07-17 21:44:45;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
591;2025-07-17 21:44:45;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
592;2025-07-17 21:44:45;Switch Events;network;notice;Port speed for port LAN4 changed from 1000 baseT to 100 baseT
593;2025-07-18 01:47:36;Health checker;network;notice;DNS resolution restored
594;2025-07-18 01:48:36;Health checker;network;notice;IPv4 connectivity restored
595;2025-07-18 11:35:01;Fota;system;notice;Firmware update to RUTX_R_00.07.16.1 is now available
596;2025-07-18 17:55:23;Health checker;network;notice;IPv4 connectivity started to fail
597;2025-07-18 17:56:26;Health checker;network;notice;IPv4 connectivity restored
598;2025-07-18 18:25:00;Health checker;network;notice;IPv4 connectivity started to fail
599;2025-07-18 18:26:33;Health checker;network;notice;DNS resolution started to fail
600;2025-07-18 19:37:01;Health checker;network;notice;DNS resolution restored
601;2025-07-18 19:38:01;Health checker;network;notice;IPv4 connectivity restored
602;2025-07-18 21:56:14;Health checker;network;notice;IPv4 connectivity started to fail
603;2025-07-18 21:56:35;Health checker;network;notice;DNS resolution started to fail
604;2025-07-18 23:39:51;Health checker;network;notice;IPv4 connectivity restored
605;2025-07-18 23:39:54;Health checker;network;notice;DNS resolution restored
606;2025-07-19 05:02:36;Fota;system;notice;Firmware update to RUTX_R_00.07.16.1 is now available
607;2025-07-19 05:02:39;Mobile Data;network;info;Mobile data connected (internal modem)
608;2025-07-19 05:02:39;Network Type;network;info;Joined 5G-NSA network (internal modem)
609;2025-07-19 05:02:39;Network Operator;network;info;Connected to 24405 operator (internal modem)
610;2025-07-19 05:02:41;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
611;2025-07-19 05:02:41;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
612;2025-07-19 05:02:41;Switch Events;network;notice;Port speed for port LAN4 changed from 100 baseT to 1000 baseT
613;2025-07-19 05:02:42;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
614;2025-07-19 05:02:44;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
615;2025-07-19 05:02:45;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
616;2025-07-19 05:02:47;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
617;2025-07-19 05:02:48;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
618;2025-07-19 05:02:50;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
619;2025-07-19 05:03:01;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
620;2025-07-19 05:03:03;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
621;2025-07-19 05:03:04;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
622;2025-07-19 05:03:08;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
623;2025-07-19 05:03:09;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
624;2025-07-19 05:03:11;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
625;2025-07-19 05:03:11;Switch Events;network;notice;Port speed for port LAN4 changed from 1000 baseT to 100 baseT
626;2025-07-19 05:03:34;Health checker;network;notice;IPv4 connectivity restored
627;2025-07-19 05:03:35;Health checker;network;notice;IPv6 connectivity restored
628;2025-07-19 16:55:31;Health checker;network;notice;IPv4 connectivity started to fail
629;2025-07-19 16:55:40;Health checker;network;notice;IPv6 connectivity started to fail
630;2025-07-19 16:59:53;Health checker;network;notice;DNS resolution started to fail
631;2025-07-19 18:01:44;Health checker;network;notice;IPv4 connectivity restored
632;2025-07-19 18:01:44;Health checker;network;notice;IPv6 connectivity restored
633;2025-07-19 18:01:44;Health checker;network;notice;DNS resolution restored
634;2025-07-20 07:23:24;Mobile Data;network;info;Mobile data connected (internal modem)
635;2025-07-20 07:23:24;Network Type;network;info;Joined 5G-NSA network (internal modem)
636;2025-07-20 07:23:24;Network Operator;network;info;Connected to 24405 operator (internal modem)
637;2025-07-20 07:23:24;Fota;system;notice;Firmware update to RUTX_R_00.07.16.1 is now available
638;2025-07-20 07:23:26;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
639;2025-07-20 07:23:33;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
640;2025-07-20 07:23:33;Switch Events;network;notice;Port speed for port LAN4 changed from 1000 baseT to 100 baseT
641;2025-07-20 07:24:19;Health checker;network;notice;IPv4 connectivity restored
642;2025-07-20 12:30:17;Health checker;network;notice;IPv4 connectivity started to fail
643;2025-07-20 12:30:26;Health checker;network;notice;IPv6 connectivity started to fail
644;2025-07-20 12:32:02;Health checker;network;notice;DNS resolution started to fail
645;2025-07-20 13:27:51;Mobile Data;network;info;Mobile data disconnected (internal modem)
646;2025-07-20 13:27:57;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
647;2025-07-20 13:27:57;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
648;2025-07-20 13:27:57;Switch Events;network;notice;Port speed for port LAN4 changed from 100 baseT to 1000 baseT
649;2025-07-20 13:27:58;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
650;2025-07-20 13:28:00;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
651;2025-07-20 13:28:06;Mobile Data;network;info;Mobile data connected (internal modem)
652;2025-07-20 13:28:06;Network Type;network;info;Joined 5G-NSA network (internal modem)
653;2025-07-20 13:28:06;Network Operator;network;info;Connected to 24405 operator (internal modem)
654;2025-07-20 13:28:06;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
655;2025-07-20 13:28:14;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
656;2025-07-20 13:28:15;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
657;2025-07-20 13:28:17;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
658;2025-07-20 13:28:17;Switch Events;network;notice;Port speed for port LAN4 changed from 1000 baseT to 100 baseT
659;2025-07-20 17:02:05;Health checker;network;notice;IPv4 connectivity restored
660;2025-07-20 17:02:08;Health checker;network;notice;DNS resolution restored
661;2025-07-22 10:02:44;Health checker;network;notice;IPv4 connectivity started to fail
662;2025-07-22 10:05:29;Health checker;network;notice;DNS resolution started to fail
663;2025-07-22 11:05:07;Health checker;network;notice;IPv4 connectivity restored
664;2025-07-22 11:05:11;Health checker;network;notice;DNS resolution restored
665;2025-07-23 08:21:41;Mobile Data;network;info;Mobile data connected (internal modem)
666;2025-07-23 08:21:41;Network Type;network;info;Joined 5G-NSA network (internal modem)
667;2025-07-23 08:21:41;Network Operator;network;info;Connected to 24405 operator (internal modem)
668;2025-07-23 08:21:41;Fota;system;notice;Firmware update to RUTX_R_00.07.16.1 is now available
669;2025-07-23 08:21:43;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
670;2025-07-23 08:21:45;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
671;2025-07-23 08:21:47;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
672;2025-07-23 08:21:49;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
673;2025-07-23 08:21:50;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
674;2025-07-23 08:21:52;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
675;2025-07-23 08:21:53;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
676;2025-07-23 08:21:57;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
677;2025-07-23 08:21:57;Switch Events;network;notice;Port speed for port LAN4 changed from 1000 baseT to 100 baseT
678;2025-07-23 08:22:36;Health checker;network;notice;IPv4 connectivity restored
679;2025-07-24 12:52:16;Startup;system;notice;Device startup completed
680;2025-07-24 12:52:18;Switch Events;network;notice;Port link state of port CPU/WiFi (1000 baseT) changed to UP
681;2025-07-24 12:52:18;Switch Events;network;notice;Port link state of port LAN2 (1000 baseT) changed to UP
682;2025-07-24 12:52:18;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
683;2025-07-25 11:35:01;Fota;system;notice;Firmware update to RUTX_R_00.07.16.2 is now available
684;2025-07-25 19:49:28;Health checker;network;notice;IPv4 connectivity started to fail
685;2025-07-25 19:49:37;Health checker;network;notice;IPv6 connectivity started to fail
686;2025-07-25 19:52:32;Health checker;network;notice;DNS resolution started to fail
687;2025-07-25 19:55:43;Mobile Data;network;info;Mobile data connected (internal modem)
688;2025-07-25 19:55:43;Network Type;network;info;Joined 5G-NSA network (internal modem)
689;2025-07-25 19:55:43;Network Operator;network;info;Connected to 24405 operator (internal modem)
690;2025-07-25 19:55:46;Fota;system;notice;Firmware update to RUTX_R_00.07.16.2 is now available
691;2025-07-25 19:56:38;Health checker;network;notice;IPv4 connectivity restored
692;2025-07-25 19:56:38;Health checker;network;notice;IPv6 connectivity restored
693;2025-07-25 19:56:41;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
694;2025-07-25 19:56:43;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
695;2025-07-25 19:56:44;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
696;2025-07-25 19:56:45;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
697;2025-07-25 19:56:46;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
698;2025-07-25 19:56:48;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
699;2025-07-25 19:56:49;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
700;2025-07-25 19:56:51;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
701;2025-07-25 19:56:51;Switch Events;network;notice;Port speed for port LAN4 changed from 1000 baseT to 100 baseT
702;2025-07-27 16:07:37;Mobile Data;network;info;Mobile data connected (internal modem)
703;2025-07-27 16:07:37;Network Type;network;info;Joined 5G-NSA network (internal modem)
704;2025-07-27 16:07:37;Network Operator;network;info;Connected to 24405 operator (internal modem)
705;2025-07-27 16:07:38;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
706;2025-07-27 16:07:43;Fota;system;notice;Firmware update to RUTX_R_00.07.16.2 is now available
707;2025-07-27 16:11:05;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
708;2025-07-27 16:11:07;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
709;2025-07-27 16:12:34;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
710;2025-07-27 16:12:36;Switch Events;network;notice;Port link state of port LAN4 (1000 baseT) changed to UP
711;2025-07-27 16:24:53;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
712;2025-07-27 16:25:03;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
713;2025-07-27 16:25:03;Switch Events;network;notice;Port speed for port LAN4 changed from 1000 baseT to 100 baseT
714;2025-07-29 10:54:35;Switch Events;network;notice;Port link state of port LAN2 (1000 baseT) changed to UP
715;2025-07-29 10:56:35;Web UI;connections;notice;"User ""admin"" successfully authenticated on HTTPS from 192.168.1.6 to 192.168.1.1"
716;2025-07-29 10:56:38;Fota;system;notice;Firmware update to RUTX_R_00.07.16.3 is now available
717;2025-07-29 11:00:18;Firmware;system;info;Firmware RUTX_R_00.07.14.3 successfully upgraded to RUTX_R_00.07.16.3
718;2025-07-29 11:03:56;Mobile Data;network;info;Mobile data connected (internal modem)
719;2025-07-29 11:03:56;Network Type;network;info;Joined 5G-NSA network (internal modem)
720;2025-07-29 11:03:56;Network Operator;network;info;Connected to 24405 operator (internal modem)
721;2025-07-29 11:04:04;Switch Events;network;notice;Port link state of port LAN4 changed to DOWN
722;2025-07-29 11:04:09;Switch Events;network;notice;Port link state of port LAN4 (100 baseT) changed to UP
723;2025-07-29 11:04:55;Health checker;network;notice;IPv4 connectivity restored
724;2025-07-29 11:04:55;Health checker;network;notice;IPv6 connectivity restored

[MatasR]

Hello,

The confusing part is when you mention that “LAN4” was connected to the WAN1 interface of your device. Do you have your WAN port of the RUT (which is technically the LAN4) set up as a LAN port? Additionally, not necessarily the root cause of the issue, but the cable you’re using might be problematic, do you have a different one you could try & test?

What firmware version is your RUT device running on currently?

Regards,

Matas.

[down]

Have a look to this post It was my first post concerning my WAN pb.

New cable in place.

• Firmware version

  RUTX_R_00.07.16.3

• Firmware build date

  2025-07-24 14:11:38

• Internal modem firmware version

  RG501QEUAAR12A11M4G

• Kernel version

  6.6.92

UDM-SE + RUTX50 WAN down

Hello, New to this brand, I have received this morning my modem. After a thousand of update, the modem has been connected to my external antenna, I do have a 5G connection. When doing a speed test on it, I do have the right values. I haven’t touch anything on the internal firewall. I have change the APN value to “internet4”, I have the right public IP number. But I do not have internet when connecting my device to my UDM-SE on the WAN port. On the modem when MOB1S1A1 has type: mobile, IP: …

[MatasR]

I see. Just have to clarify still - you’re trying to give internet from the RUTX50 to the UDM, or take internet? From what I’ve gathered, you seem to be wanting to take internet.

Regarding these disconnections of your ports, could you try disabling auto-negotiation under Network → Ports → Port Settings → Select your LAN4 (WAN) port → Press Edit → Disable Auto Negotiation → Save & Apply. You can also try playing with the Link speed setting, switching it between 10 / 100 / 1000 mbps.

Let me know if this helps to improve the situation,

M.

[down]

Hello,

After reseted the device many times, I do not have anymore access to internet.

I am now permanently on my backup line.

I have read on this forum that I am not the only one to have a pb when using the UDM-SE from Unifi.

My full config:

Firmware version
RUTX_R_00.07.16.3
Firmware build date
2025-07-24 14:11:38
Internal modem firmware version
RG501QEUAAR12A11M4G
Kernel version
6.6.92

The config not working of my RUTX50:


Network/LAN
status: running
type: bridge
device: br-LAN

lan interface config:
General settings: 
Enable ON
Use WAN port as LAN: ON
Enable DHCPv4: off
Enable DHCPv6: off

IPv6 settings: off

Advanced settings:
Force link: ON
Use gw metric: 0
Override MTU: 1500

Physical settings:
Bridge interfaces ON
STP and IGMP Off


Wireless all Off

mob1s1a1 interface config:
Enable: On
protocole: mobile
Mode: passthrough
Subnet selection: Auto
PDP type: IPV4/IPv6
SIM: SIM1
APN: internet4
Authentication type: None
Disable DHCPv4: Off

Network/Internet status:
IPV4 status: Online
IPV6 status: Online
DNS status: Online

LAN4 port settings: 
Enable ON
Auto negotiation: On (same pb if Off)
Advertisement: 1000M-Full / 100M-Full

Network / DHCP / Server settings:
Server: Off

Network / DNS / General:
General settings: 
Inherited DNS servers:  2001:998:.... from mob1s1a1
Rebind protection: On

Advanced settings: all off except Filter private and Localise queries

Maintenance / Speed test

Download: 5.92 Mbps (it should be 350)
Upload: 0.33 Mbps (it should be 14Mbps)


Sytem Logs after a reboot of the RUT:

600 Thu Jul 31 19:43:59 2025 user.info trm-ntp  [8974]: get ntp time sync
601 Thu Jul 31 19:43:59 2025 daemon.info dnsmasq[8314]: read /etc/hosts - 12 names
602 Thu Jul 31 19:43:59 2025 daemon.info dnsmasq[8314]: read /tmp/hosts/dhcp.cfg01411c - 0 names
603 Thu Jul 31 19:43:59 2025 daemon.info dnsmasq-dhcp[8314]: read /etc/ethers - 0 addresses
604 Thu Jul 31 19:44:00 2025 user.notice nlbwmon: Reloading nlbwmon due to ifup of mob1s1a1_4 (qmimux0)
605 Thu Jul 31 19:44:00 2025 kern.info Mobile data connected (internal modem)
606 Thu Jul 31 19:44:00 2025 kern.info Joined 5G-NSA network (internal modem)
607 Thu Jul 31 19:44:00 2025 kern.info Connected to 24405 operator (internal modem)
608 Thu Jul 31 19:44:01 2025 user.notice firewall: Reloading firewall due to ifupdate of mob1s1a1 (wwan0)
609 Thu Jul 31 19:44:02 2025 user.notice nlbwmon: Reloading nlbwmon due to ifup of mobile_bridge (br-lan)
610 Thu Jul 31 19:44:03 2025 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_6 (qmimux0)
611 Thu Jul 31 19:44:04 2025 daemon.info dfota[6445]: WAN found on interface: mobile_bridge
612 Thu Jul 31 19:44:04 2025 daemon.info dfota[6445]: Preparing for gsm.modem0 update!
613 Thu Jul 31 19:44:04 2025 daemon.info dfota[6445]: Searching for updates...
614 Thu Jul 31 19:44:04 2025 user.notice nlbwmon: Reloading nlbwmon due to ifup of mob1s1a1_6 (qmimux0)
615 Thu Jul 31 19:44:05 2025 daemon.info dfota[6445]: No update found!
616 Thu Jul 31 19:44:06 2025 daemon.info dfota[6445]: Update script done!
617 Thu Jul 31 19:44:21 2025 kern.notice User "admin" successfully authenticated on HTTPS from 192.168.1.6 to 192.168.1.1
618 Thu Jul 31 19:44:21 2025 daemon.err uhttpd[3506]: vuci: accepted login for admin from 192.168.1.6
619 Thu Jul 31 19:44:57 2025 kern.notice IPv4 connectivity restored
620 Thu Jul 31 19:44:57 2025 kern.notice IPv6 connectivity restored

[down]

Little update, I have now internet, but with a very slow speed …. When running the speed test from the RTU, I am at around 9Mbps … It should be 350

New logs:

848 Thu Jul 31 20:41:17 2025 kern.info Joined 5G-NSA network (internal modem)
849 Thu Jul 31 20:41:17 2025 kern.info Connected to 24405 operator (internal modem)
850 Thu Jul 31 20:41:17 2025 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_4 (qmimux0)
851 Thu Jul 31 20:41:19 2025 daemon.notice wpa_supplicant[4932]: Set new config for phy phy1
852 Thu Jul 31 20:41:19 2025 daemon.notice hostapd: Set new config for phy phy0:
853 Thu Jul 31 20:41:19 2025 daemon.notice wpa_supplicant[4932]: Set new config for phy phy0
854 Thu Jul 31 20:41:19 2025 daemon.notice hostapd: Set new config for phy phy1:
855 Thu Jul 31 20:41:19 2025 daemon.info dnsmasq[13128]: read /etc/hosts - 12 names
856 Thu Jul 31 20:41:19 2025 daemon.info dnsmasq[13128]: read /tmp/hosts/dhcp.cfg01411c - 0 names
857 Thu Jul 31 20:41:19 2025 daemon.notice netifd: Wireless device 'radio1' is now up
858 Thu Jul 31 20:41:20 2025 user.notice nlbwmon: Reloading nlbwmon due to ifup of mob1s1a1_4 (qmimux0)
859 Thu Jul 31 20:41:20 2025 kern.info Mobile data connected (internal modem)
860 Thu Jul 31 20:41:20 2025 kern.info Joined 5G-NSA network (internal modem)
861 Thu Jul 31 20:41:20 2025 kern.info Connected to 24405 operator (internal modem)
862 Thu Jul 31 20:41:22 2025 daemon.notice wpa_supplicant[4932]: Set new config for phy phy0
863 Thu Jul 31 20:41:22 2025 daemon.notice hostapd: Set new config for phy phy0:
864 Thu Jul 31 20:41:22 2025 daemon.notice netifd: Wireless device 'radio0' set retry=3
865 Thu Jul 31 20:41:22 2025 daemon.notice netifd: Wireless device 'radio1' set retry=3
866 Thu Jul 31 20:41:22 2025 daemon.notice netifd: Wireless device 'radio0' is now up
867 Thu Jul 31 20:42:58 2025 kern.notice kernel: User "admin" changed Dhcp configuration in "/network/lan" page
868 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[13128]: exiting on receipt of SIGTERM
869 Thu Jul 31 20:43:00 2025 daemon.err procd: Got unexpected signal 1
870 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: started, version 2.89 cachesize 150
871 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: compile time options: IPv6 GNU-getopt no-RTC no-DBus UBus no-i18n no-regex no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
872 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: UBus support enabled: connected to system bus
873 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq-dhcp[16746]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
874 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for test
875 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for onion
876 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for localhost
877 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for local
878 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for invalid
879 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for bind
880 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for lan
881 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: reading /tmp/resolv.conf.d/resolv.conf.auto
882 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using nameserver 195.197.54.100#53
883 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using nameserver 195.74.0.47#53
884 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using nameserver 2001:998:20::20#53
885 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using nameserver 2001:998:20::40#53
886 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for test
887 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for onion
888 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for localhost
889 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for local
890 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for invalid
891 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for bind
892 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: using only locally-known addresses for lan
893 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: read /etc/hosts - 12 names
894 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq[16746]: read /tmp/hosts/dhcp.cfg01411c - 4 names
895 Thu Jul 31 20:43:00 2025 daemon.info dnsmasq-dhcp[16746]: read /etc/ethers - 0 addresses
896 Thu Jul 31 20:43:20 2025 daemon.info dnsmasq-dhcp[16746]: DHCPDISCOVER(br-lan) 84.222.XXX.XXX 70:a7:41:68:f4:ce
897 Thu Jul 31 20:43:20 2025 daemon.info dnsmasq-dhcp[16746]: DHCPOFFER(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
898 Thu Jul 31 20:43:20 2025 daemon.info dnsmasq-dhcp[16746]: DHCPREQUEST(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
899 Thu Jul 31 20:43:20 2025 daemon.info dnsmasq-dhcp[16746]: DHCPACK(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
900 Thu Jul 31 20:45:13 2025 kern.notice IPv4 connectivity started to fail
901 Thu Jul 31 20:45:23 2025 kern.notice kernel: User "admin" changed Network configuration in "/network/ports/ports_settings" page
902 Thu Jul 31 20:45:25 2025 daemon.info mobifd: Service reload initiated
903 Thu Jul 31 20:45:32 2025 daemon.info dnsmasq-dhcp[16746]: DHCPDISCOVER(br-lan) 84.222.XXX.XXX 70:a7:41:68:f4:ce
904 Thu Jul 31 20:45:32 2025 daemon.info dnsmasq-dhcp[16746]: DHCPOFFER(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
905 Thu Jul 31 20:45:32 2025 daemon.info dnsmasq-dhcp[16746]: DHCPREQUEST(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
906 Thu Jul 31 20:45:32 2025 daemon.info dnsmasq-dhcp[16746]: DHCPACK(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
907 Thu Jul 31 20:45:34 2025 daemon.notice netifd: Wireless device 'radio0' set retry=3
908 Thu Jul 31 20:45:34 2025 daemon.notice netifd: Wireless device 'radio1' set retry=3
909 Thu Jul 31 20:45:34 2025 kern.notice Port link state of port LAN4 changed to DOWN
910 Thu Jul 31 20:45:36 2025 kern.notice Port link state of port LAN4 (10 baseT) changed to UP
911 Thu Jul 31 20:45:36 2025 kern.notice Port speed for port LAN4 changed from 1000 baseT to 10 baseT
912 Thu Jul 31 20:45:37 2025 daemon.info dnsmasq-dhcp[16746]: DHCPDISCOVER(br-lan) 84.222.XXX.XXX 70:a7:41:68:f4:ce
913 Thu Jul 31 20:45:37 2025 daemon.info dnsmasq-dhcp[16746]: DHCPOFFER(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
914 Thu Jul 31 20:45:37 2025 daemon.info dnsmasq-dhcp[16746]: DHCPREQUEST(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
915 Thu Jul 31 20:45:37 2025 daemon.info dnsmasq-dhcp[16746]: DHCPACK(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
916 Thu Jul 31 20:46:20 2025 kern.notice IPv4 connectivity restored
917 Thu Jul 31 20:47:04 2025 kern.notice kernel: User "admin" changed Network configuration in "/network/ports/ports_settings" page
918 Thu Jul 31 20:47:07 2025 daemon.info mobifd: Service reload initiated
919 Thu Jul 31 20:47:10 2025 kern.notice Port link state of port LAN4 changed to DOWN
920 Thu Jul 31 20:47:10 2025 kern.notice Port link state of port LAN4 (100 baseT) changed to UP
921 Thu Jul 31 20:47:10 2025 kern.notice Port speed for port LAN4 changed from 10 baseT to 100 baseT
922 Thu Jul 31 20:47:10 2025 daemon.notice netifd: Wireless device 'radio0' set retry=3
923 Thu Jul 31 20:47:10 2025 daemon.notice netifd: Wireless device 'radio1' set retry=3
924 Thu Jul 31 20:47:10 2025 daemon.info dnsmasq-dhcp[16746]: DHCPDISCOVER(br-lan) 84.222.XXX.XXX 70:a7:41:68:f4:ce
925 Thu Jul 31 20:47:10 2025 daemon.info dnsmasq-dhcp[16746]: DHCPOFFER(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
926 Thu Jul 31 20:47:10 2025 daemon.info dnsmasq-dhcp[16746]: DHCPREQUEST(br-lan) 192.168.1.116 70:a7:41:68:f4:ce
927 Thu Jul 31 20:47:10 2025 daemon.info dnsmasq-dhcp[16746]: DHCPACK(br-lan) 192.168.1.116 70:a7:41:68:f4:ce

[MatasR]

If you’ve changed port-settings post-reset, and the negotiation to ~10mbps, then that’s what you’re going to get, if you haven’t already, you can try enabling auto-negotiation again to see if the speeds rise again.

Logs aren’t going to show anything that could tell us why the speeds are low, it depends on the setup and many other various factors, which range from physical to digital.

Regards,

M.

[down]

Dear sir,

So nothing wrong with my config ?

I might be wrong, but when the speedtest has been done from the RUT, it has nothing to do with the port settings …. Right ?

I have change again the port seetings to auto-negotiation to On and speed to 1000M-Full … Nothing has changed.

Thx

[MatasR]

So the main question I have, since the thread was initially created in regards to your LAN port switching from UP to DOWN - is this still an issue? Or are we moving to an issue where your speeds are slow? Could you clarify?

Regards,

M.

[down]

It start by up and down, now it is very slow … Do you want me to reopen a new ticket ?

[MatasR]

No, a new ticket won’t be necessary. I’d like to clarify then just to be sure - is the UP/DOWN problem gone now?

If it is, I’ve sent you a form to fill out so we can continue our conversation in private, to avoid accidentally leaking any sensitive information. In the Ticket ID field, simply enter the thread’s number, which is **14914**.

Thank you,
M.

[down]

the support form has been submitted