Rut240 lan connection dropping packets

Teltonika Networks
1

Performing a simple ping we lose more than 60% of the packets. Sometimes it does not reach the device in the other end at all. WiFi works fine. It seems the device in the other end keeps asking for DHCP messages in a loop as if there is a message that does not reach in time and the DHCP protocol restarts. Both RUT and the DUT shows an IP has been assigned. The DUT uses a USB to ETH adapter which works fine with other routers.

I would happily share all the logs I have. We use both TRB and RUT devices as a getway to our measurement solutions and this issue has been appearing all over the place.

3

Hello,

Firstly, what firmware version do you have installed on your RUT240?

How many devices are connected to RUT240? Does the issue occur on all of them? Is the issue sporadic or is it persistent?

Are you connected directly to RUT240 or is there a device in-between, like another router or a switch?

Have you tried connecting without the adapter? Perhaps you tried a different LAN port or ethernet cable?

You mentioned that sometimes the pings do not reach the device on the other end. Are pings to RUT240 itself successful? Have you tried pinging that device from RUT240 itself?

You have also mentioned that:

Would it be possible for you to provide more details about this point? Does it occur on other devices as well? If so, what do those devices have in common? Maybe they have a switch connected to them, or they are using the same adapters?

Finally, what services do you have configured? Maybe you have some custom scripts running on the device?

Kind Regards,

4

Hello,

Firstly, what firmware version do you have installed on your RUT240?

RUT2_R_00.07.05

How many devices are connected to RUT240? Does the issue occur on all of them? Is the issue sporadic or is it persistent?

There is just one device. The issue occurs all the time it is connected to it via LAN.

Are you connected directly to RUT240 or is there a device in-between, like another router or a switch?

Directly connected

Have you tried connecting without the adapter? Perhaps you tried a different LAN port or ethernet cable?

Connection via WiFi works. There is no ETH port in our device. Other adapter and cables show no improvement.

You mentioned that sometimes the pings do not reach the device on the other end. Are pings to RUT240 itself successful? Have you tried pinging that device from RUT240 itself?

I could not try to ping from the device to the RUT as the device was out in the field already. I was relying on RMS to figure it out.

Would it be possible for you to provide more details about this point? Does it occur on other devices as well? If so, what do those devices have in common? Maybe they have a switch connected to them, or they are using the same adapters?

What I meant was the our devices are being shipped with the same adapter and cables and either a RUT240 or TRB140. There is no switch. I tried to reproduce it at our HQ but I had no “luck”. That issue happened in the US with a RUT240 and Belgium with a TRB140. For the RTU240 I had the chance to ask the customer to try to connect via WiFi which worked. The same linux device works with other routers.

Finally, what services do you have configured? Maybe you have some custom scripts running on the device?

There are no services configured. We expect that the default settings would work with a SIM card inserted.

5

Hello,

You are shipping the devices (either RUT240 or TRB140) to your clients. All RUTs/TRBs in those set-ups have the same linux-device connected to them. The issue with dropped packets occured on one RUT240 and on one TRB140 so far. However, you are unable to reproduce the issue at your HQ. I.e. there are multiple similar setups, but there are only 2 cases where this issue is present. Is my understand correct here?

Are you sure this is not an issue with the mobile connectivity? For example, a poor signal (bad SINR)?

How are you testing this? From which device are you pinging?

If possible, could you please try using RMS connect or RMS VPN to access the device in LAN or RUT, and then try pinging the LAN IP of RUT. Does it drop the packets?

Kind Regards,

6

You are shipping the devices (either RUT240 or TRB140) to your clients. All RUTs/TRBs in those set-ups have the same linux-device connected to them. The issue with dropped packets occured on one RUT240 and on one TRB140 so far. However, you are unable to reproduce the issue at your HQ. I.e. there are multiple similar setups, but there are only 2 cases where this issue is present. Is my understand correct here?

Yes so far we identified this issue at two customers.

Are you sure this is not an issue with the mobile connectivity? For example, a poor signal (bad SINR)?
How are you testing this? From which device are you pinging?
If possible, could you please try using RMS connect or RMS VPN to access the device in LAN or RUT, and then try pinging the LAN IP of RUT. Does it drop the packets?

Exactly, with the RUT240 I was able to access the RMS and that is how I identified that the DHCP was looping and pings from the RUT to the DUT were being dropped. Accessing the RMS worked without any lags, so I do not think the problem was with the mobile carrier, I also thought it could be it. For the TRB case, since it was mounted in a pole out in the field, the customer could not get me the IMEI and Serial Number so I could try to access it. In the end, they ended up disassembling it. The ping drops are always from the RUT to the DUT as I could not do the other way around.

I have all the teltonika logs and our logs saved in case it helps.

7

Hello,

Could you kindly provide some System logs where the issue can be seen? System logs are available in System → Maintenance → Troubleshoot → View system logs. If there are any sensitive details, like public IP addresses, please ensure to redact or hide them before sharing the logs here.

Also, could you please try connecting to RUT and try pinging DUT from the CLI/SSH (username is ‘root’) or from the troubleshoot page in the WebUI (diagnostics section). Does it drop the packets?

It would also be great if you could access the device via CLI/SSH and share the output of the ifconfig command as well.

Kind Regards,

8

Syslog


[LOGGING INFORMATION]

[Dmesg]
Wed Nov  1 01:54:31 2023 kern.notice Port link state of port CPU/WiFi changed to UP
Wed Nov  1 01:54:31 2023 kern.notice Port speed for port CPU/WiFi changed to 1000 baseT
Wed Nov  1 01:54:31 2023 kern.notice Port link state of port LAN1 changed to UP
Wed Nov  1 01:54:31 2023 kern.notice Port speed for port LAN1 changed to 10 baseT
Wed Nov  1 01:54:32 2023 daemon.notice netifd: mob1s1a1 (2681): Starting network mob1s1a1 using APN: sp.telus.com
Wed Nov  1 01:54:33 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --set-client-id wds,17 --release-client-id wds --modify-profile --profile-identifier 3gpp,1 --profile-name profile1 --roaming-disallowed-flag no    --auth-type none  --apn sp.telus.com  --pdp-type ip
Wed Nov  1 01:54:35 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
Wed Nov  1 01:54:36 2023 kern.info kernel: [   83.013409] br-lan: port 2(wlan0) entered blocking state
Wed Nov  1 01:54:36 2023 kern.info kernel: [   83.017384] br-lan: port 2(wlan0) entered disabled state
Wed Nov  1 01:54:36 2023 kern.info kernel: [   83.023258] device wlan0 entered promiscuous mode
Wed Nov  1 01:54:36 2023 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Wed Nov  1 01:54:36 2023 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Wed Nov  1 01:54:36 2023 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Wed Nov  1 01:54:36 2023 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->ACS
Wed Nov  1 01:54:36 2023 daemon.notice hostapd: wlan0: ACS-STARTED
Wed Nov  1 01:54:37 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --get-client-id wds
Wed Nov  1 01:54:38 2023 daemon.info dnsmasq[1803]: exiting on receipt of SIGTERM
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: Connected to system UBus
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: started, version 2.85 cachesize 150
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-regex no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: UBus support enabled: connected to system bus
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq-dhcp[3517]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain test
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain onion
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain localhost
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain local
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain invalid
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain bind
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain lan
Wed Nov  1 01:54:39 2023 daemon.warn dnsmasq[3517]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: read /etc/hosts - 4 addresses
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Nov  1 01:54:39 2023 daemon.notice netifd: mob1s1a1 (2681): 17
Wed Nov  1 01:54:39 2023 daemon.notice netifd: mob1s1a1 (2681): cid4: 17
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq-dhcp[3517]: read /etc/ethers - 0 addresses
Wed Nov  1 01:54:39 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --wds-bind-mux-data-port --mux-id 1 --ep-iface-number 4 --set-client-id wds,17
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: read /etc/hosts - 4 addresses
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq[3517]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Nov  1 01:54:39 2023 daemon.info dnsmasq-dhcp[3517]: read /etc/ethers - 0 addresses
Wed Nov  1 01:54:40 2023 user.info kernel: [   87.380610] kmodloader: loading kernel modules from /etc/modules-late.d/*
Wed Nov  1 01:54:40 2023 user.info kernel: [   87.428008] kmodloader: done loading kernel modules from /etc/modules-late.d/*
Wed Nov  1 01:54:41 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --set-ip-family ipv4 --set-client-id wds,17
Wed Nov  1 01:54:41 2023 kern.notice ip_blockd service is enabled, initialized firewall rules
Wed Nov  1 01:54:41 2023 daemon.notice netifd: Wireless device 'radio0' is now up
Wed Nov  1 01:54:41 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 3000 --set-client-id wds,17 --start-network --apn sp.telus.com --profile 1  --auth-type none --username  --password
Wed Nov  1 01:54:42 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 01:54:42 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 01:54:43 2023 daemon.notice netifd: mob1s1a1 (2681): pdh4: -2026589824
Wed Nov  1 01:54:43 2023 daemon.notice hostapd: wlan0: ACS-COMPLETED freq=2447 channel=8
Wed Nov  1 01:54:43 2023 daemon.notice netifd: mob1s1a1 (2681): -2026589824
Wed Nov  1 01:54:43 2023 daemon.notice netifd: mob1s1a1 (2681): Setting up qmimux0
Wed Nov  1 01:54:43 2023 daemon.notice netifd: mob1s1a1 (2681): Setting dynamic MTU: 1460 on qmimux0
Wed Nov  1 01:54:44 2023 daemon.notice netifd: Interface 'mob1s1a1' is now up
Wed Nov  1 01:54:44 2023 daemon.notice netifd: Network device 'wwan0' link is up
Wed Nov  1 01:54:44 2023 cron.err crond[3738]: crond (busybox 1.34.1) started, log level 5
Wed Nov  1 01:54:45 2023 daemon.notice netifd: mob1s1a1 (2681): Setting up qmimux0 V4 DCHP
Wed Nov  1 01:54:45 2023 daemon.notice netifd: Interface 'mob1s1a1_4' is enabled
Wed Nov  1 01:54:45 2023 daemon.notice netifd: Network device 'qmimux0' link is up
Wed Nov  1 01:54:45 2023 daemon.notice netifd: Interface 'mob1s1a1_4' has link connectivity
Wed Nov  1 01:54:45 2023 daemon.notice netifd: Interface 'mob1s1a1_4' is setting up now
Wed Nov  1 01:54:45 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 01:54:45 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 01:54:46 2023 kern.info Leased 192.168.1.195 IP address for client 00:e0:4c:68:02:fe - xl3 in LAN
Wed Nov  1 01:54:47 2023 daemon.notice netifd: mob1s1a1_4 (3851): udhcpc: started, v1.34.1
Wed Nov  1 01:54:48 2023 kern.info kernel: [   94.597282] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Wed Nov  1 01:54:48 2023 kern.info kernel: [   94.602741] br-lan: port 2(wlan0) entered blocking state
Wed Nov  1 01:54:48 2023 kern.info kernel: [   94.607587] br-lan: port 2(wlan0) entered forwarding state
Wed Nov  1 01:54:48 2023 daemon.notice netifd: Network device 'wlan0' link is up
Wed Nov  1 01:54:48 2023 daemon.notice hostapd: wlan0: interface state ACS->ENABLED
Wed Nov  1 01:54:48 2023 daemon.notice hostapd: wlan0: AP-ENABLED
Wed Nov  1 01:54:48 2023 daemon.notice netifd: mob1s1a1_4 (3851): udhcpc: broadcasting discover
Wed Nov  1 01:54:48 2023 daemon.notice netifd: mob1s1a1_4 (3851): udhcpc: broadcasting select for 25.65.156.201, server 25.65.156.202
Wed Nov  1 01:54:48 2023 daemon.notice netifd: mob1s1a1_4 (3851): udhcpc: lease of 25.65.156.201 obtained from 25.65.156.202, lease time 7200
Wed Nov  1 01:54:50 2023 daemon.notice netifd: Interface 'mob1s1a1_4' is now up
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain test
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain onion
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain localhost
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain local
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain invalid
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain bind
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: using only locally-known addresses for domain lan
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: using nameserver 75.153.171.39#53
Wed Nov  1 01:54:50 2023 daemon.info dnsmasq[3517]: using nameserver 75.153.171.40#53
Wed Nov  1 01:54:51 2023 user.warn mwan3-hotplug[3743]: hotplug called on loopback before mwan3 has been set up
Wed Nov  1 01:54:51 2023 daemon.info mobifd: Connection setup completed for 'mob1s1a1'
Wed Nov  1 01:54:53 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 01:54:53 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 01:54:54 2023 cron.err crond[4110]: crond (busybox 1.34.1) started, log level 5
Wed Nov  1 01:54:56 2023 daemon.err insmod: module is already loaded - arc4
Wed Nov  1 01:54:56 2023 daemon.err insmod: module is already loaded - sha1_generic
Wed Nov  1 01:54:56 2023 daemon.err insmod: module is already loaded - slhc
Wed Nov  1 01:54:56 2023 daemon.err insmod: module is already loaded - crc-ccitt
Wed Nov  1 01:54:56 2023 daemon.err insmod: module is already loaded - ppp_generic
Wed Nov  1 01:54:56 2023 daemon.err insmod: module is already loaded - ppp_async
Wed Nov  1 01:54:56 2023 daemon.err insmod: module is already loaded - ppp_mppe
Wed Nov  1 01:55:00 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 01:55:00 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 01:55:00 2023 user.warn mwan3-hotplug[4241]: hotplug called on mob1s1a1 before mwan3 has been set up
Wed Nov  1 01:55:05 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1 (wwan0)
Wed Nov  1 01:55:08 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 01:55:08 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:05:23 2023 kern.warn kernel: [  117.377163] process 'ntpclient' launched '/usr/sbin/ntpd-hotplug' with NULL argv: empty string added
Wed Nov  1 18:05:27 2023 cron.err crond[4993]: crond (busybox 1.34.1) started, log level 5
Wed Nov  1 18:05:27 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:05:27 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:05:32 2023 daemon.notice procd: /etc/rc.d/S96led: setting up led LAN
Wed Nov  1 18:05:32 2023 daemon.notice procd: /etc/rc.d/S96led: setting up led WAN
Wed Nov  1 18:05:33 2023 daemon.info dnsmasq[3517]: read /etc/hosts - 4 addresses
Wed Nov  1 18:05:33 2023 daemon.info dnsmasq[3517]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Nov  1 18:05:33 2023 daemon.info dnsmasq-dhcp[3517]: read /etc/ethers - 0 addresses
Wed Nov  1 18:05:36 2023 kern.notice Device startup completed
Wed Nov  1 18:05:40 2023 user.warn mwan3-hotplug[5393]: hotplug called on mob1s1a1_4 before mwan3 has been set up
Wed Nov  1 18:05:41 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:05:41 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:05:42 2023 kern.info Leased 192.168.1.195 IP address for client 00:e0:4c:68:02:fe - xl3 in LAN
Wed Nov  1 18:05:45 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:05:45 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:05:47 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_4 (qmimux0)
Wed Nov  1 18:05:54 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:05:54 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:05:58 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:05:58 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:01 2023 daemon.info dnsmasq[3517]: read /etc/hosts - 4 addresses
Wed Nov  1 18:06:01 2023 daemon.info dnsmasq[3517]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Nov  1 18:06:02 2023 daemon.info dnsmasq-dhcp[3517]: read /etc/ethers - 0 addresses
Wed Nov  1 18:06:04 2023 daemon.err rms_mqtt[6439]: Applying certs
Wed Nov  1 18:06:04 2023 cron.err crond[6625]: crond (busybox 1.34.1) started, log level 5
Wed Nov  1 18:06:05 2023 kern.info Mobile data connected (internal modem)
Wed Nov  1 18:06:06 2023 kern.info Joined LTE network (internal modem)
Wed Nov  1 18:06:06 2023 kern.info Connected to TELUS operator (internal modem)
Wed Nov  1 18:06:08 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:08 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:11 2023 daemon.info procd: - init complete -
Wed Nov  1 18:06:11 2023 daemon.info dfota[5647]: Searching for WAN...
Wed Nov  1 18:06:11 2023 daemon.info dfota[5647]: WAN found on interface: mob1s1a1_4
Wed Nov  1 18:06:11 2023 daemon.info dfota[5647]: Preparing for gsm.modem0 update!
Wed Nov  1 18:06:12 2023 daemon.info dfota[5647]: Searching for updates...
Wed Nov  1 18:06:13 2023 daemon.info dfota[5647]: No update found!
Wed Nov  1 18:06:15 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:15 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:18 2023 cron.err crond[7107]: crond (busybox 1.34.1) started, log level 5
Wed Nov  1 18:06:20 2023 cron.err crond[7239]: crond (busybox 1.34.1) started, log level 5
Wed Nov  1 18:06:21 2023 daemon.info dfota[5647]: Update script done!
Wed Nov  1 18:06:23 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:23 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:27 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:27 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:06:31 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:31 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:06:42 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:42 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:45 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:45 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:49 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:49 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:59 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:06:59 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:13 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:13 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:12:18 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:18 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:12:25 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:25 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:33 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:33 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:45 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:45 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:54 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:54 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:58 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:12:58 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:13:02 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:13:02 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:13:13 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:13:13 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:13:21 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:13:21 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:13:30 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:13:30 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:13:44 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:13:44 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:13:52 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:13:52 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:14:03 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:03 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:11 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:11 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:25 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:25 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:30 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:30 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:14:33 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:33 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:14:37 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:37 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:14:46 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:46 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:50 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:50 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:59 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:14:59 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:15:14 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:15:14 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:16:42 2023 kern.notice Port link state of port LAN1 changed to DOWN
Wed Nov  1 18:16:56 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:16:56 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:16:56 2023 kern.notice Port link state of port LAN1 changed to UP
Wed Nov  1 18:16:56 2023 kern.notice Port speed for port LAN1 changed to 10 baseT
Wed Nov  1 18:17:03 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:17:03 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:17:19 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:17:19 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:17:24 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:17:24 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:17:35 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:17:35 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:17:42 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:17:42 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:17:48 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:17:48 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:18:04 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:04 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:09 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:09 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:14 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:14 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:25 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:25 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:28 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:28 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:18:33 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:33 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:18:46 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:46 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:51 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:51 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:59 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:18:59 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:12 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:12 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:14 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:14 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:19:19 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:19 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:19:24 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:24 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
Wed Nov  1 18:19:35 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:35 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:41 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:41 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:56 2023 daemon.info dnsmasq-dhcp[3517]: DHCPDISCOVER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:19:56 2023 daemon.info dnsmasq-dhcp[3517]: DHCPOFFER(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:22:14 2023 kern.notice Port link state of port LAN1 changed to DOWN
Wed Nov  1 18:22:28 2023 daemon.info dnsmasq-dhcp[3517]: DHCPREQUEST(br-lan) 192.168.1.195 00:e0:4c:68:02:fe
Wed Nov  1 18:22:28 2023 daemon.info dnsmasq-dhcp[3517]: DHCPACK(br-lan) 192.168.1.195 00:e0:4c:68:02:fe xl3
9

You system wont allow me to upload a zip file or more than 32k char. So I need to do it in multiple posts.

CLI ping

Screenshot 2023-11-01 at 15.32.33
Screenshot 2023-11-01 at 15.32.331259×791 80.5 KB

10

DUT ifconfig and routes

Oct 31 19:37:14 xl3 CommCore[168]: <INFO> Kernel IP routing table
                                   Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
                                   10.0.1.0        0.0.0.0         255.255.255.0   U     0      0        0 comm-host
Oct 31 19:37:15 xl3 CommCore[168]: <INFO> comm-host: connected to comm-host
                                           "comm-host"
                                           ethernet (veth), 9E:C0:00:70:6B:45, sw, mtu 1500
                                           inet4 10.0.1.2/24
                                           route4 10.0.1.0/24
                                           inet6 fe80::9cc0:ff:fe70:6b45/64
                                           route6 fe80::/64
                                           route6 ff00::/8

                                   enx00e04c6802fe: connecting (getting IP configuration) to Wired connection 2
                                           "enx00e04c6802fe"
                                           ethernet (r8152), 00:E0:4C:68:02:FE, hw, mtu 1500

                                   usb-local: unavailable
                                           "usb-local"
                                           ethernet (g_ether), 02:FF:EC:FF:FF:FF, hw, mtu 1500

                                   wlan0: unavailable
                                           "wlan0"
                                           wifi (brcmfmac), 00:25:CA:5B:96:F5, hw, mtu 1500

                                   sit0: unmanaged
                                           "sit0"
                                           iptunnel (sit), sw, mtu 1480

                                   lo: unmanaged
                                           "lo"
                                           loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
Oct 31 20:38:28 xl3 CommCore[168]: <INFO> Kernel IP routing table
                                   Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
                                   0.0.0.0         192.168.1.1     0.0.0.0         UG    20101  0        0 enx00e04c6802fe
                                   10.0.1.0        0.0.0.0         255.255.255.0   U     0      0        0 comm-host
                                   192.168.1.0     0.0.0.0         255.255.255.0   U     20101  0        0 enx00e04c6802fe
Oct 31 20:38:29 xl3 CommCore[168]: <INFO> enx00e04c6802fe: connected to Wired connection 2
                                           "enx00e04c6802fe"
                                           ethernet (r8152), 00:E0:4C:68:02:FE, hw, mtu 1500
                                           ip4 default
                                           inet4 192.168.1.195/24
                                           route4 0.0.0.0/0
                                           route4 192.168.1.0/24
                                           inet6 fe80::4747:23e4:f445:f4de/64
                                           route6 fe80::/64
                                           route6 ff00::/8

                                   comm-host: connected to comm-host
                                           "comm-host"
                                           ethernet (veth), 9E:C0:00:70:6B:45, sw, mtu 1500
                                           inet4 10.0.1.2/24
                                           route4 10.0.1.0/24
                                           inet6 fe80::9cc0:ff:fe70:6b45/64
                                           route6 fe80::/64
                                           route6 ff00::/8

                                   usb-local: unavailable
                                           "usb-local"
                                           ethernet (g_ether), 02:FF:EC:FF:FF:FF, hw, mtu 1500

                                   wlan0: unavailable
                                           "wlan0"
                                           wifi (brcmfmac), 00:25:CA:5B:96:F5, hw, mtu 1500

                                   sit0: unmanaged
                                           "sit0"
                                           iptunnel (sit), sw, mtu 1480

                                   lo: unmanaged
                                           "lo"
                                           loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

                                   DNS configuration:
                                           servers: 192.168.1.1
                                           domains: lan
                                           interface: enx00e04c6802fe

Notice that the address will be assigned and dropped in the dchp loop

11

DUT network manager logs

Oct 31 17:31:39 xl3 NetworkManager[85]: <warn>  [1698773499.8244] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.8248] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.8408] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6153
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.8410] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.8451] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.8542] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:31:39 xl3 NetworkManager[85]: <warn>  [1698773499.8631] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.8669] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.9255] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.9432] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.9444] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.9564] manager: NetworkManager state is now CONNECTING
Oct 31 17:31:39 xl3 NetworkManager[85]: <info>  [1698773499.9747] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:31:40 xl3 NetworkManager[85]: <info>  [1698773500.0031] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:31:40 xl3 NetworkManager[85]: <info>  [1698773500.0224] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:31:40 xl3 NetworkManager[85]: <info>  [1698773500.0472] dhcp4 (enx00e04c6802fe): dhclient started with pid 6190
Oct 31 17:32:24 xl3 NetworkManager[85]: <warn>  [1698773544.8249] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:32:24 xl3 NetworkManager[85]: <info>  [1698773544.8253] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:32:24 xl3 NetworkManager[85]: <info>  [1698773544.8433] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6190
Oct 31 17:32:24 xl3 NetworkManager[85]: <info>  [1698773544.8436] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:32:24 xl3 NetworkManager[85]: <info>  [1698773544.8533] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:32:24 xl3 NetworkManager[85]: <info>  [1698773544.8667] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:32:24 xl3 NetworkManager[85]: <warn>  [1698773544.8746] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:32:24 xl3 NetworkManager[85]: <info>  [1698773544.8823] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:32:25 xl3 NetworkManager[85]: <info>  [1698773545.0598] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:32:25 xl3 NetworkManager[85]: <info>  [1698773545.0919] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:32:25 xl3 NetworkManager[85]: <info>  [1698773545.1063] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:32:25 xl3 NetworkManager[85]: <info>  [1698773545.1161] manager: NetworkManager state is now CONNECTING
Oct 31 17:32:25 xl3 NetworkManager[85]: <info>  [1698773545.1234] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:32:25 xl3 NetworkManager[85]: <info>  [1698773545.1528] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:32:25 xl3 NetworkManager[85]: <info>  [1698773545.1950] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:32:25 xl3 NetworkManager[85]: <info>  [1698773545.2363] dhcp4 (enx00e04c6802fe): dhclient started with pid 6229
Oct 31 17:33:10 xl3 NetworkManager[85]: <warn>  [1698773590.8241] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:33:10 xl3 NetworkManager[85]: <info>  [1698773590.8244] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:33:10 xl3 NetworkManager[85]: <info>  [1698773590.8373] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6229
Oct 31 17:33:10 xl3 NetworkManager[85]: <info>  [1698773590.8410] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:33:10 xl3 NetworkManager[85]: <info>  [1698773590.8444] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:33:10 xl3 NetworkManager[85]: <info>  [1698773590.8645] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:33:10 xl3 NetworkManager[85]: <warn>  [1698773590.8816] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:33:10 xl3 NetworkManager[85]: <info>  [1698773590.8925] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:33:10 xl3 NetworkManager[85]: <info>  [1698773590.9929] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:33:11 xl3 NetworkManager[85]: <info>  [1698773591.0171] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:33:11 xl3 NetworkManager[85]: <info>  [1698773591.0254] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:33:11 xl3 NetworkManager[85]: <info>  [1698773591.0422] manager: NetworkManager state is now CONNECTING
Oct 31 17:33:11 xl3 NetworkManager[85]: <info>  [1698773591.0522] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:33:11 xl3 NetworkManager[85]: <info>  [1698773591.0747] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:33:11 xl3 NetworkManager[85]: <info>  [1698773591.1121] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:33:11 xl3 NetworkManager[85]: <info>  [1698773591.2097] dhcp4 (enx00e04c6802fe): dhclient started with pid 6268
Oct 31 17:33:56 xl3 NetworkManager[85]: <warn>  [1698773636.8249] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:33:56 xl3 NetworkManager[85]: <info>  [1698773636.8252] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:33:56 xl3 NetworkManager[85]: <info>  [1698773636.8409] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6268
Oct 31 17:33:56 xl3 NetworkManager[85]: <info>  [1698773636.8412] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:33:56 xl3 NetworkManager[85]: <info>  [1698773636.8513] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:33:56 xl3 NetworkManager[85]: <info>  [1698773636.8753] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:33:56 xl3 NetworkManager[85]: <warn>  [1698773636.8967] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:33:56 xl3 NetworkManager[85]: <info>  [1698773636.9243] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:38:56 xl3 NetworkManager[85]: <info>  [1698773936.8253] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:38:56 xl3 NetworkManager[85]: <info>  [1698773936.8428] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:38:56 xl3 NetworkManager[85]: <info>  [1698773936.8448] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:38:56 xl3 NetworkManager[85]: <info>  [1698773936.8561] manager: NetworkManager state is now CONNECTING
Oct 31 17:38:56 xl3 NetworkManager[85]: <info>  [1698773936.8648] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:38:56 xl3 NetworkManager[85]: <info>  [1698773936.8944] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:38:56 xl3 NetworkManager[85]: <info>  [1698773936.9150] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:38:56 xl3 NetworkManager[85]: <info>  [1698773936.9470] dhcp4 (enx00e04c6802fe): dhclient started with pid 6511
Oct 31 17:39:41 xl3 NetworkManager[85]: <warn>  [1698773981.8250] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:39:41 xl3 NetworkManager[85]: <info>  [1698773981.8253] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:39:41 xl3 NetworkManager[85]: <info>  [1698773981.8426] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6511
Oct 31 17:39:41 xl3 NetworkManager[85]: <info>  [1698773981.8429] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:39:41 xl3 NetworkManager[85]: <info>  [1698773981.8451] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:39:41 xl3 NetworkManager[85]: <info>  [1698773981.8659] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:39:41 xl3 NetworkManager[85]: <warn>  [1698773981.8821] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:39:41 xl3 NetworkManager[85]: <info>  [1698773981.8939] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:39:42 xl3 NetworkManager[85]: <info>  [1698773982.0157] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:39:42 xl3 NetworkManager[85]: <info>  [1698773982.0335] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:39:42 xl3 NetworkManager[85]: <info>  [1698773982.0413] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:39:42 xl3 NetworkManager[85]: <info>  [1698773982.0716] manager: NetworkManager state is now CONNECTING
Oct 31 17:39:42 xl3 NetworkManager[85]: <info>  [1698773982.0849] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:39:42 xl3 NetworkManager[85]: <info>  [1698773982.1242] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:39:42 xl3 NetworkManager[85]: <info>  [1698773982.1432] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:39:42 xl3 NetworkManager[85]: <info>  [1698773982.1809] dhcp4 (enx00e04c6802fe): dhclient started with pid 6550
Oct 31 17:40:27 xl3 NetworkManager[85]: <warn>  [1698774027.8247] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:40:27 xl3 NetworkManager[85]: <info>  [1698774027.8250] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:40:27 xl3 NetworkManager[85]: <info>  [1698774027.8424] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6550
Oct 31 17:40:27 xl3 NetworkManager[85]: <info>  [1698774027.8427] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:40:27 xl3 NetworkManager[85]: <info>  [1698774027.8523] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:40:27 xl3 NetworkManager[85]: <info>  [1698774027.8804] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:40:27 xl3 NetworkManager[85]: <warn>  [1698774027.9020] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:40:27 xl3 NetworkManager[85]: <info>  [1698774027.9210] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:40:28 xl3 NetworkManager[85]: <info>  [1698774028.0052] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:40:28 xl3 NetworkManager[85]: <info>  [1698774028.0191] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:40:28 xl3 NetworkManager[85]: <info>  [1698774028.0289] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:40:28 xl3 NetworkManager[85]: <info>  [1698774028.0776] manager: NetworkManager state is now CONNECTING
Oct 31 17:40:28 xl3 NetworkManager[85]: <info>  [1698774028.0892] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:40:28 xl3 NetworkManager[85]: <info>  [1698774028.1040] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:40:28 xl3 NetworkManager[85]: <info>  [1698774028.1097] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:40:28 xl3 NetworkManager[85]: <info>  [1698774028.1461] dhcp4 (enx00e04c6802fe): dhclient started with pid 6590
Oct 31 17:41:13 xl3 NetworkManager[85]: <warn>  [1698774073.8250] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:41:13 xl3 NetworkManager[85]: <info>  [1698774073.8253] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:41:13 xl3 NetworkManager[85]: <info>  [1698774073.8400] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6590
Oct 31 17:41:13 xl3 NetworkManager[85]: <info>  [1698774073.8402] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:41:13 xl3 NetworkManager[85]: <info>  [1698774073.8454] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:41:13 xl3 NetworkManager[85]: <info>  [1698774073.8745] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:41:13 xl3 NetworkManager[85]: <warn>  [1698774073.9066] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:41:13 xl3 NetworkManager[85]: <info>  [1698774073.9333] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:41:13 xl3 NetworkManager[85]: <info>  [1698774073.9898] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:41:14 xl3 NetworkManager[85]: <info>  [1698774073.9999] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:41:14 xl3 NetworkManager[85]: <info>  [1698774074.0013] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:41:14 xl3 NetworkManager[85]: <info>  [1698774074.0078] manager: NetworkManager state is now CONNECTING
Oct 31 17:41:14 xl3 NetworkManager[85]: <info>  [1698774074.0143] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:41:14 xl3 NetworkManager[85]: <info>  [1698774074.0303] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:41:14 xl3 NetworkManager[85]: <info>  [1698774074.0514] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:41:14 xl3 NetworkManager[85]: <info>  [1698774074.1143] dhcp4 (enx00e04c6802fe): dhclient started with pid 6631
Oct 31 17:41:59 xl3 NetworkManager[85]: <warn>  [1698774119.8247] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:41:59 xl3 NetworkManager[85]: <info>  [1698774119.8250] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:41:59 xl3 NetworkManager[85]: <info>  [1698774119.8417] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6631
Oct 31 17:41:59 xl3 NetworkManager[85]: <info>  [1698774119.8442] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:41:59 xl3 NetworkManager[85]: <info>  [1698774119.8551] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:41:59 xl3 NetworkManager[85]: <info>  [1698774119.8624] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:41:59 xl3 NetworkManager[85]: <warn>  [1698774119.8656] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:41:59 xl3 NetworkManager[85]: <info>  [1698774119.8714] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:46:59 xl3 NetworkManager[85]: <info>  [1698774419.8252] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:46:59 xl3 NetworkManager[85]: <info>  [1698774419.8351] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:46:59 xl3 NetworkManager[85]: <info>  [1698774419.8410] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:46:59 xl3 NetworkManager[85]: <info>  [1698774419.8526] manager: NetworkManager state is now CONNECTING
Oct 31 17:46:59 xl3 NetworkManager[85]: <info>  [1698774419.8611] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:46:59 xl3 NetworkManager[85]: <info>  [1698774419.8901] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:46:59 xl3 NetworkManager[85]: <info>  [1698774419.9131] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:46:59 xl3 NetworkManager[85]: <info>  [1698774419.9818] dhcp4 (enx00e04c6802fe): dhclient started with pid 6878
Oct 31 17:47:44 xl3 NetworkManager[85]: <warn>  [1698774464.8242] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.8245] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.8386] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6878
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.8389] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.8510] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.8630] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:47:44 xl3 NetworkManager[85]: <warn>  [1698774464.8716] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.8805] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.9514] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.9658] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.9725] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.9817] manager: NetworkManager state is now CONNECTING
Oct 31 17:47:44 xl3 NetworkManager[85]: <info>  [1698774464.9859] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:47:45 xl3 NetworkManager[85]: <info>  [1698774465.0113] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:47:45 xl3 NetworkManager[85]: <info>  [1698774465.0330] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:47:45 xl3 NetworkManager[85]: <info>  [1698774465.0658] dhcp4 (enx00e04c6802fe): dhclient started with pid 6916
Oct 31 17:48:29 xl3 NetworkManager[85]: <warn>  [1698774509.8249] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.8252] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.8483] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6916
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.8486] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.8561] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.8652] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:48:29 xl3 NetworkManager[85]: <warn>  [1698774509.8752] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.8835] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.9452] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.9664] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.9724] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:48:29 xl3 NetworkManager[85]: <info>  [1698774509.9925] manager: NetworkManager state is now CONNECTING
Oct 31 17:48:30 xl3 NetworkManager[85]: <info>  [1698774510.0043] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:48:30 xl3 NetworkManager[85]: <info>  [1698774510.0660] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:48:30 xl3 NetworkManager[85]: <info>  [1698774510.0830] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:48:30 xl3 NetworkManager[85]: <info>  [1698774510.1331] dhcp4 (enx00e04c6802fe): dhclient started with pid 6955
Oct 31 17:49:15 xl3 NetworkManager[85]: <warn>  [1698774555.8250] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:49:15 xl3 NetworkManager[85]: <info>  [1698774555.8253] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:49:15 xl3 NetworkManager[85]: <info>  [1698774555.8461] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6955
Oct 31 17:49:15 xl3 NetworkManager[85]: <info>  [1698774555.8464] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:49:15 xl3 NetworkManager[85]: <info>  [1698774555.8525] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:49:15 xl3 NetworkManager[85]: <info>  [1698774555.8808] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:49:15 xl3 NetworkManager[85]: <warn>  [1698774555.8951] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:49:15 xl3 NetworkManager[85]: <info>  [1698774555.9052] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:49:15 xl3 NetworkManager[85]: <info>  [1698774555.9843] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:49:16 xl3 NetworkManager[85]: <info>  [1698774556.0005] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:49:16 xl3 NetworkManager[85]: <info>  [1698774556.0130] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:49:16 xl3 NetworkManager[85]: <info>  [1698774556.0310] manager: NetworkManager state is now CONNECTING
Oct 31 17:49:16 xl3 NetworkManager[85]: <info>  [1698774556.0410] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:49:16 xl3 NetworkManager[85]: <info>  [1698774556.0734] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:49:16 xl3 NetworkManager[85]: <info>  [1698774556.1074] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:49:16 xl3 NetworkManager[85]: <info>  [1698774556.1624] dhcp4 (enx00e04c6802fe): dhclient started with pid 6994
Oct 31 17:50:01 xl3 NetworkManager[85]: <warn>  [1698774601.8250] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:50:01 xl3 NetworkManager[85]: <info>  [1698774601.8253] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:50:01 xl3 NetworkManager[85]: <info>  [1698774601.8417] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 6994
Oct 31 17:50:01 xl3 NetworkManager[85]: <info>  [1698774601.8420] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:50:01 xl3 NetworkManager[85]: <info>  [1698774601.8521] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:50:01 xl3 NetworkManager[85]: <info>  [1698774601.8963] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:50:01 xl3 NetworkManager[85]: <warn>  [1698774601.9222] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:50:01 xl3 NetworkManager[85]: <info>  [1698774601.9409] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:55:01 xl3 NetworkManager[85]: <info>  [1698774901.8254] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:55:01 xl3 NetworkManager[85]: <info>  [1698774901.8406] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:55:01 xl3 NetworkManager[85]: <info>  [1698774901.8459] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:55:01 xl3 NetworkManager[85]: <info>  [1698774901.8629] manager: NetworkManager state is now CONNECTING
Oct 31 17:55:01 xl3 NetworkManager[85]: <info>  [1698774901.8728] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:55:01 xl3 NetworkManager[85]: <info>  [1698774901.9026] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:55:01 xl3 NetworkManager[85]: <info>  [1698774901.9151] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:55:01 xl3 NetworkManager[85]: <info>  [1698774901.9504] dhcp4 (enx00e04c6802fe): dhclient started with pid 7241
Oct 31 17:55:46 xl3 NetworkManager[85]: <warn>  [1698774946.8250] dhcp4 (enx00e04c6802fe): request timed out
Oct 31 17:55:46 xl3 NetworkManager[85]: <info>  [1698774946.8253] dhcp4 (enx00e04c6802fe): state changed unknown -> timeout
Oct 31 17:55:46 xl3 NetworkManager[85]: <info>  [1698774946.8515] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 7241
Oct 31 17:55:46 xl3 NetworkManager[85]: <info>  [1698774946.8518] dhcp4 (enx00e04c6802fe): state changed timeout -> done
Oct 31 17:55:46 xl3 NetworkManager[85]: <info>  [1698774946.8604] device (enx00e04c6802fe): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 31 17:55:46 xl3 NetworkManager[85]: <info>  [1698774946.9039] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:55:46 xl3 NetworkManager[85]: <warn>  [1698774946.9239] device (enx00e04c6802fe): Activation: failed for connection 'Wired connection 2'
Oct 31 17:55:46 xl3 NetworkManager[85]: <info>  [1698774946.9410] device (enx00e04c6802fe): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 31 17:55:46 xl3 NetworkManager[85]: <info>  [1698774946.9917] policy: auto-activating connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:55:47 xl3 NetworkManager[85]: <info>  [1698774947.0012] device (enx00e04c6802fe): Activation: starting connection 'Wired connection 2' (63532478-23ea-33b2-95a7-a128b8bbe560)
Oct 31 17:55:47 xl3 NetworkManager[85]: <info>  [1698774947.0024] device (enx00e04c6802fe): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 31 17:55:47 xl3 NetworkManager[85]: <info>  [1698774947.0059] manager: NetworkManager state is now CONNECTING
Oct 31 17:55:47 xl3 NetworkManager[85]: <info>  [1698774947.0119] device (enx00e04c6802fe): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:55:47 xl3 NetworkManager[85]: <info>  [1698774947.0236] device (enx00e04c6802fe): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 31 17:55:47 xl3 NetworkManager[85]: <info>  [1698774947.0326] dhcp4 (enx00e04c6802fe): activation: beginning transaction (timeout in 45 seconds)
Oct 31 17:55:47 xl3 NetworkManager[85]: <info>  [1698774947.0626] dhcp4 (enx00e04c6802fe): dhclient started with pid 7279
Oct 31 17:56:24 xl3 NetworkManager[85]: <info>  [1698774984.1810] device (enx00e04c6802fe): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 31 17:56:24 xl3 NetworkManager[85]: <info>  [1698774984.2001] dhcp4 (enx00e04c6802fe): canceled DHCP transaction, DHCP client pid 7279
Oct 31 17:56:24 xl3 NetworkManager[85]: <info>  [1698774984.2004] dhcp4 (enx00e04c6802fe): state changed unknown -> done
Oct 31 17:56:24 xl3 NetworkManager[85]: <info>  [1698774984.2310] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 31 17:56:32 xl3 NetworkManager[85]: <info>  [1698774992.2205] device (enx00e04c6802fe): carrier: link connected
Oct 31 17:56:32 xl3 NetworkManager[85]: <info>  [1698774992.2399] device (enx00e04c6802fe): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
12

Let me know how could I send you the full logs.

13

This topic was automatically closed after 15 days. New replies are no longer allowed.