Home Network Community > 5G/4G Wi-Fi Routers/MiFi > Unstable LTE Connection with Archer MR500 and MR550
< 5G/4G Wi-Fi Routers/MiFi

Solution Unstable LTE Connection with Archer MR500 and MR550

123...

Solution Unstable LTE Connection with Archer MR500 and MR550

SolutionUnstable LTE Connection with Archer MR500 and MR550
Unstable LTE Connection with Archer MR500 and MR550
2024-01-04 02:05:23 - last edited 2024-01-04 02:12:30
Tags: #Network Connectivity #Official
Model: Archer MR500   Archer MR550  
Hardware Version: V1
Firmware Version:

This Article Applies to:

Archer MR500(EU) V1, Archer MR550(EU) V1

 

Phenomenon Description:

Some users have encountered internet dropouts with the Archer MR500 and MR550 routers after a certain period of normal operation. When attempting to log into the web page, an error message is displayed, indicating that the internet is not connected. Temporary resolution can be achieved by rebooting the router, but the issue might happen again after a while.

 

Workaround:

If you encounter similar issues, we recommend trying the following beta firmware and monitor if the internet will be more stable.

Archer MR500: Archer_MR500(EU)_V1_1.7.0_Build_20231122

Archer MR550: Archer_MR550(EU)_V1_1.5.0_Build_20230828

 

Note: Please be sure you have read the Terms and Conditions for TP-Link Beta Firmware before proceeding.

 

Further Troubleshooting Suggestions:

If the problem still exists after installing the above beta firmware,  please provide the following information for further troubleshooting:

1. When the issue happens again, please login the web interface, share with us screenshots of Advanced->Status page, Advanced->Network->Internet page.

2. When the issue happens again, please go to Advanced->System Tools->System Log page and save a log file(don't restart the router, or previous logs will be cleared)

3. Detailed description of the issue and let us know how often it happens.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer BE550 New Software Enhances System Stability and Optimizes MLO Network Stability. TL-WA3001 Supports EasyMesh, Speed Limit, Guest Network in AP Mode and/or Multi-SSID Mode. If you found the post or response helpful, please click Helpful. If an answer solves your problem, click "Recommended Solution" so that others can benefit from it.
  7      
 
  7      
 
#1
Options
123 Reply
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-17 09:00:17

Advanced Sunshine wrote

This Article Applies to:

Archer MR500(EU) V1, Archer MR550(EU) V1

 

Phenomenon Description:

Some users have encountered internet dropouts with the Archer MR500 and MR550 routers after a certain period of normal operation. When attempting to log into the web page, an error message is displayed, indicating that the internet is not connected. Temporary resolution can be achieved by rebooting the router, but the issue might happen again after a while.

 

Workaround:

If you encounter similar issues, we recommend trying the following beta firmware and monitor if the internet will be more stable.

Archer MR500: Archer_MR500(EU)_V1_1.7.0_Build_20231122

Archer MR550: Archer_MR550(EU)_V1_1.5.0_Build_20230828

 

Note: Please be sure you have read the Terms and Conditions for TP-Link Beta Firmware before proceeding.

 

Further Troubleshooting Suggestions:

If the problem still exists after installing the above beta firmware,  please provide the following information for further troubleshooting:

1. When the issue happens again, please login the web interface, share with us screenshots of Advanced->Status page, Advanced->Network->Internet page.

2. When the issue happens again, please go to Advanced->System Tools->System Log page and save a log file(don't restart the router, or previous logs will be cleared)

3. Detailed description of the issue and let us know how often it happens.

  @Sunshine regarding the reported issue and after following the above instructions the router failed again to connect to internet. Less frequent but it does lost its connection. You'll find the log in attachment. This issue causes tremendous inconvenience for our company operations and security. We request this matter to be addressed with utmost urgency. Thank you
 

 

File:
Router log.pdfDownload
  0  
  0  
#2
Options
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-18 03:21:56

  @xianrenzhang 

 

Hi, may I know if you are using MR500 or MR550? Optimus is your ISP, right?

Please also let us know how often does it happen now, and if you insert the same SIM card into other device at same location, will it work stable?

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer BE550 New Software Enhances System Stability and Optimizes MLO Network Stability. TL-WA3001 Supports EasyMesh, Speed Limit, Guest Network in AP Mode and/or Multi-SSID Mode. If you found the post or response helpful, please click Helpful. If an answer solves your problem, click "Recommended Solution" so that others can benefit from it.
  0  
  0  
#3
Options
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-18 09:50:06

  @Sunshine thanks for the reply. The model is the MR500 V1 EU, and the ISP is Optimus or PortalOptimus, from NOS provider. The SIM is brand new and was working in a MR200 V2 that got replaced by the MR500. The MR200 had the same issue, with the last available firmware it could hold for a week. If the router is programmed using a smart plug to shut off , forcing it to reboot the unit doesn't loose connection. Obviously this is not an acceptable working solution because it compromises security. The unit must stand by itself. I'm more inclined to assume it's a hardware flaw rather than firmware. 

Sunshine wrote

  @xianrenzhang 

 

Hi, may I know if you are using MR500 or MR550? Optimus is your ISP, right?

Please also let us know how often does it happen now, and if you insert the same SIM card into other device at same location, will it work stable?


 

Looking forward for your reply

  0  
  0  
#4
Options
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-19 07:14:13

  @xianrenzhang 

 

Hi, do you mean previous MR200 and current MR500 has similar issue? If so, we are still unable to confirm if it is related to the ISP base station as well.

 

In addition, MR500 supports reboot schedule feature which is on Advanced->System Tools->Reboot page, you could use this feature to let the router reboots on its own every day/week/month to see if it would solve the issue or not.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer BE550 New Software Enhances System Stability and Optimizes MLO Network Stability. TL-WA3001 Supports EasyMesh, Speed Limit, Guest Network in AP Mode and/or Multi-SSID Mode. If you found the post or response helpful, please click Helpful. If an answer solves your problem, click "Recommended Solution" so that others can benefit from it.
  0  
  0  
#5
Options
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-19 08:24:39 - last edited 2024-01-19 08:25:06

Hi  @Sunshine 
Set an automatic Rebooting of  the router either with its programming or a smart plug are not permanent solutions. 
 

We have sent the log of the router when it happened as requested. So the questions are :

What did it reveal? Did other users shared a log? If so what conclusions have you TPLink reached?


Thank you 

  0  
  0  
#6
Options
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-19 08:44:25

  @xianrenzhang 

 

Hi, the system log shows internet is not working at 08:42 but it doesn't show root cause. So we would like to confirm it is not the SIM card or ISP base station issue first, that is why I asked whether the same SIM card works fine and stable on other 4G devices.

 

At this moment, there is no other feedback yet regarding the beta firmware provided in this thread, if it still happens frequently with MR500 only, we would like to escalate your case to senior engineer for further debugging, please confirm how often it happens now with this beta firmware.

 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer BE550 New Software Enhances System Stability and Optimizes MLO Network Stability. TL-WA3001 Supports EasyMesh, Speed Limit, Guest Network in AP Mode and/or Multi-SSID Mode. If you found the post or response helpful, please click Helpful. If an answer solves your problem, click "Recommended Solution" so that others can benefit from it.
  0  
  0  
#7
Options
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-21 05:28:28

  @Sunshine 

I confirm the same issue with my mr500 v.1

Greece cosmote provider. 

I don't have second 4g modem to test.

I ve installed the beta firmware and i will come back with results.

If problem persist i will sent it back for refund 

  0  
  0  
#8
Options
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-21 19:29:41

  @Sunshine 

10 hours later and the connection problem came back.

I have installed latest beta firmware.

Nothing special about usage. Lost internet and login to router to see connection lost 

 

  0  
  0  
#9
Options
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-21 19:36:43

  @Babiz1 

Also it seems that i cant upload log file for reason.

  0  
  0  
#10
Options
Re:Unstable LTE Connection with Archer MR500 and MR550
2024-01-21 19:41:43

  @Babiz1 

2018-10-01 02:00:55 [5] 4G: init LTE module, set flowstat [enableDataLimit 0, enablePaymentDay 1, paymentDay 1, limitation 0, warningPercent 90]

2018-10-01 02:00:55 [5] 4G: LTE Module: profile num [2], default profile [1], active profile [1]

2018-10-01 02:00:55 [5] 4G: DM: profile num [2], default profile [1], active profile [1]

2018-10-01 02:00:56 [5] System: Enable IPv4 SPI Firewall

2018-10-01 02:00:56 [5] System: Enable IPv6 SPI Firewall

2018-10-01 02:01:03 [6] 4G: LTE connection up

2018-10-01 02:01:03 [5] 4G: LTE internet connected.

2024-01-21 07:24:37 [6] System: User(Mac:1C:6F:65:C5:8F:A2;IP:192.168.1.222) logs in.

2024-01-21 07:24:41 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 07:24:41 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 07:24:50 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 07:24:50 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 07:25:16 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 07:25:16 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 07:25:27 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 07:25:27 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 07:25:44 [5] 4G: networkPreferredMode: 2

2024-01-21 07:25:48 [6] 4G: USER: Get user's profile now.

 

2024-01-21 07:25:48 [6] 4G: USER: GetCurrProf result is: ipver:2 staticApn:0 authType:2 pkgName:PublicIP2 profname:PublicIP2 apn:vpn-internet usr: psw:  

 

2024-01-21 07:25:48 [6] 4G: USER: Get user's profile now.

 

2024-01-21 07:25:48 [6] 4G: USER: GetCurrProf result is: ipver:2 staticApn:0 authType:2 pkgName:PublicIP2 profname:PublicIP2 apn:vpn-internet usr: psw:  

 

2024-01-21 07:25:48 [5] 4G: set LTE static IP connection, needSetDefaultGw:1

2024-01-21 07:25:49 [6] 4G: ERROR: Commit data item failed.

 

2024-01-21 07:25:49 [6] 4G: USER: Network type is NONE.

 

2024-01-21 07:25:49 [6] 4G: USER: Get user's profile now.

 

2024-01-21 07:25:49 [6] 4G: USER: GetCurrProf result is: ipver:2 staticApn:0 authType:2 pkgName:PublicIP2 profname:PublicIP2 apn:vpn-internet usr: psw:  

 

2024-01-21 07:25:49 [6] 4G: USER: Start connecting to the network!

 

2024-01-21 07:25:49 [6] 4G: USER: Not registered, not currently searching!

 

2024-01-21 07:25:49 [6] 4G: USER: Not registered, searching!

 

2024-01-21 07:25:49 [6] 4G: USER: Registered with a network!

 

2024-01-21 07:25:49 [6] 4G: USER: Fail to connect to the network, start autoconnect!

 

2024-01-21 07:25:49 [6] 4G: USER: Get user's profile now.

 

2024-01-21 07:25:49 [6] 4G: USER: GetCurrProf result is: ipver:2 staticApn:0 authType:2 pkgName:PublicIP2 profname:PublicIP2 apn:vpn-internet usr: psw:  

 

2024-01-21 07:25:49 [6] 4G: ERROR: Setup the CGD-Cont command enqueue failed.

 

2024-01-21 07:25:49 [6] 4G: ERROR: The runtime parameter parse error.

 

2024-01-21 07:25:49 [6] 4G: ERROR: The maximum DHCP retry times reached.

 

2024-01-21 07:25:50 [5] 4G: lte internet disconnected.

2024-01-21 07:25:50 [6] 4G: LTE connection down

2024-01-21 07:25:52 [6] 4G: ERROR: In qm_util_decode_ucs2_80_81_82_encoding : Incoming buffer encoding used 0xff

 

2024-01-21 07:25:52 [6] 4G: ERROR: Input buffer not encoded in UCS2 80,81 or 82

 

2024-01-21 07:25:52 [6] 4G: ERROR: decode ucs2_80_81_82 fail!

 

2024-01-21 07:25:52 [6] 4G: ERROR: SIM GID1 is FF len=2

 

2024-01-21 07:25:52 [6] 4G: ERROR: Enable net driver cmd setup successfully.

 

2024-01-21 07:25:52 [6] 4G: USER: Connected to the network!

 

2024-01-21 07:25:52 [6] 4G: USER: Attach ip type is IPV4.

 

2024-01-21 07:25:52 [6] 4G: USER: Get user's profile now.

 

2024-01-21 07:25:52 [6] 4G: USER: GetCurrProf result is: ipver:2 staticApn:0 authType:2 pkgName:PublicIP2 profname:PublicIP2 apn:vpn-internet usr: psw:  

 

2024-01-21 07:25:52 [6] 4G: ERROR: at_msg=+CGDCONT: 0,"IPV4V6","","10.33.79.173,0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

+CGDCONT: 1,"IPV4V6","","10.33.79.173,0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

+CGDCONT: 2,"IPV4V6","vpn-internet","149.210.44.188,0

2024-01-21 07:25:52 [6] 4G: USER: Get user's profile now.

 

2024-01-21 07:25:52 [6] 4G: USER: GetCurrProf result is: ipver:2 staticApn:0 authType:2 pkgName:PublicIP2 profname:PublicIP2 apn:vpn-internet usr: psw:  

 

2024-01-21 07:25:52 [6] 4G: USER: Network type is LTE PLUS.

 

2024-01-21 07:25:57 [6] 4G: LTE connection up

2024-01-21 07:25:59 [5] 4G: LTE internet connected.

2024-01-21 07:26:02 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 07:26:03 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 07:47:54 [6] System: User(Mac:1C:6F:65:C5:8F:A2;IP:192.168.1.222) logs in.

2024-01-21 07:47:57 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 07:47:57 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 07:47:58 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 07:47:58 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 07:55:34 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 07:55:34 [5] DHCPD: Send NAK

2024-01-21 07:55:35 [5] DHCPD: Recv DISCOVER from 90:9A:4A:68:F5:D7

2024-01-21 07:55:35 [5] DHCPD: Send OFFER with ip 192.168.1.107

2024-01-21 07:55:35 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 07:55:35 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 08:51:58 [5] DHCPD: Recv REQUEST from 78:8A:86:E4:BB:6D

2024-01-21 08:51:58 [5] DHCPD: Send NAK

2024-01-21 08:52:01 [5] DHCPD: Recv DISCOVER from 78:8A:86:E4:BB:6D

2024-01-21 08:52:01 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 08:52:01 [5] DHCPD: Recv REQUEST from 78:8A:86:E4:BB:6D

2024-01-21 08:52:01 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 08:52:01 [5] DHCPD: Send NAK

2024-01-21 08:52:04 [5] DHCPD: Recv DISCOVER from 78:8A:86:E4:BB:6D

2024-01-21 08:52:04 [5] DHCPD: Send OFFER with ip 192.168.1.31

2024-01-21 08:52:04 [5] DHCPD: Recv REQUEST from 78:8A:86:E4:BB:6D

2024-01-21 08:52:05 [5] DHCPD: Send ACK to 192.168.1.31

2024-01-21 08:52:48 [5] DHCPD: Recv REQUEST from B4:6D:C2:04:E3:B5

2024-01-21 08:52:48 [5] DHCPD: Send NAK

2024-01-21 08:52:51 [5] DHCPD: Recv DISCOVER from B4:6D:C2:04:E3:B5

2024-01-21 08:52:51 [5] DHCPD: Send OFFER with ip 192.168.1.32

2024-01-21 08:52:52 [5] DHCPD: Recv REQUEST from B4:6D:C2:04:E3:B5

2024-01-21 08:52:52 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 08:52:52 [5] DHCPD: Send NAK

2024-01-21 08:52:55 [5] DHCPD: Recv DISCOVER from B4:6D:C2:04:E3:B5

2024-01-21 08:52:55 [5] DHCPD: Send OFFER with ip 192.168.1.33

2024-01-21 08:52:55 [5] DHCPD: Recv REQUEST from B4:6D:C2:04:E3:B5

2024-01-21 08:52:55 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 08:52:55 [5] DHCPD: Send NAK

2024-01-21 08:52:58 [5] DHCPD: Recv DISCOVER from B4:6D:C2:04:E3:B5

2024-01-21 08:52:58 [5] DHCPD: Send OFFER with ip 192.168.1.34

2024-01-21 08:52:58 [5] DHCPD: Recv REQUEST from B4:6D:C2:04:E3:B5

2024-01-21 08:52:58 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 08:52:58 [5] DHCPD: Send NAK

2024-01-21 08:53:01 [5] DHCPD: Recv DISCOVER from B4:6D:C2:04:E3:B5

2024-01-21 08:53:01 [5] DHCPD: Send OFFER with ip 192.168.1.35

2024-01-21 08:53:01 [5] DHCPD: Recv REQUEST from B4:6D:C2:04:E3:B5

2024-01-21 08:53:02 [5] DHCPD: Send ACK to 192.168.1.35

2024-01-21 08:55:37 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 08:55:37 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 09:14:32 [5] DHCPD: Recv REQUEST from F2:D8:C0:68:3E:B6

2024-01-21 09:14:33 [5] DHCPD: Send ACK to 192.168.1.106

2024-01-21 09:17:03 [5] DHCPD: Recv REQUEST from A2:08:08:C8:DC:D6

2024-01-21 09:17:03 [5] DHCPD: REQUEST ip 1f01a8c0 already reserved by 78:8A:86:E4:BB:6D

2024-01-21 09:17:03 [5] DHCPD: Send NAK

2024-01-21 09:17:03 [5] DHCPD: Recv DISCOVER from A2:08:08:C8:DC:D6

2024-01-21 09:17:03 [5] DHCPD: Send OFFER with ip 192.168.1.36

2024-01-21 09:17:03 [5] DHCPD: Recv REQUEST from A2:08:08:C8:DC:D6

2024-01-21 09:17:03 [5] DHCPD: Send ACK to 192.168.1.36

2024-01-21 09:25:36 [5] DHCPD: Recv REQUEST from F2:D8:C0:68:3E:B6

2024-01-21 09:25:36 [5] DHCPD: Send ACK to 192.168.1.106

2024-01-21 09:28:31 [5] DHCPD: Recv DISCOVER from 64:90:C1:6C:50:F2

2024-01-21 09:28:31 [5] DHCPD: Send OFFER with ip 192.168.1.37

2024-01-21 09:28:32 [5] DHCPD: Recv REQUEST from 64:90:C1:6C:50:F2

2024-01-21 09:28:32 [5] DHCPD: Send ACK to 192.168.1.37

2024-01-21 09:28:40 [4] IGMP: V2 igmp router occured! Not matching ours V3.

2024-01-21 09:28:46 [5] DHCPD: Recv REQUEST from 7E:17:8F:6B:E0:56

2024-01-21 09:28:46 [5] DHCPD: REQUEST ip 1401a8c0 is not in the address pool

2024-01-21 09:28:46 [5] DHCPD: Send NAK

2024-01-21 09:28:46 [5] DHCPD: Recv REQUEST from 7E:17:8F:6B:E0:56

2024-01-21 09:28:47 [5] DHCPD: REQUEST ip 1401a8c0 is not in the address pool

2024-01-21 09:28:47 [5] DHCPD: Send NAK

2024-01-21 09:28:47 [5] DHCPD: Recv DISCOVER from 7E:17:8F:6B:E0:56

2024-01-21 09:28:47 [5] DHCPD: Send OFFER with ip 192.168.1.38

2024-01-21 09:28:47 [5] DHCPD: Recv REQUEST from 7E:17:8F:6B:E0:56

2024-01-21 09:28:48 [5] DHCPD: Send ACK to 192.168.1.38

2024-01-21 09:29:48 [5] DHCPD: Recv DISCOVER from A6:71:AC:2B:D5:CE

2024-01-21 09:29:48 [5] DHCPD: Send OFFER with ip 192.168.1.39

2024-01-21 09:29:48 [5] DHCPD: Recv REQUEST from A6:71:AC:2B:D5:CE

2024-01-21 09:29:48 [5] DHCPD: Send ACK to 192.168.1.39

2024-01-21 09:30:18 [5] DHCPD: Recv DISCOVER from 9C:9D:7E:16:44:7E

2024-01-21 09:30:18 [5] DHCPD: Send OFFER with ip 192.168.1.40

2024-01-21 09:30:18 [5] DHCPD: Recv REQUEST from 9C:9D:7E:16:44:7E

2024-01-21 09:30:19 [5] DHCPD: Send ACK to 192.168.1.40

2024-01-21 09:39:22 [5] DHCPD: Recv REQUEST from F2:D8:C0:68:3E:B6

2024-01-21 09:39:22 [5] DHCPD: Send ACK to 192.168.1.106

2024-01-21 09:39:57 [5] DHCPD: Recv DISCOVER from 9C:9D:7E:16:44:7E

2024-01-21 09:39:57 [5] DHCPD: Send OFFER with ip 192.168.1.40

2024-01-21 09:39:57 [5] DHCPD: Recv REQUEST from 9C:9D:7E:16:44:7E

2024-01-21 09:39:58 [5] DHCPD: Send ACK to 192.168.1.40

2024-01-21 09:41:49 [5] DHCPD: Recv DISCOVER from 9C:9D:7E:16:44:7E

2024-01-21 09:41:49 [5] DHCPD: Send OFFER with ip 192.168.1.40

2024-01-21 09:42:50 [5] DHCPD: Lease for 192.168.1.40(Mac:9C:9D:7E:16:44:7E) expired.

2024-01-21 09:46:57 [5] DHCPD: Recv REQUEST from F2:D8:C0:68:3E:B6

2024-01-21 09:46:57 [5] DHCPD: Send ACK to 192.168.1.106

2024-01-21 09:52:03 [5] DHCPD: Lease for 192.168.1.30(Mac:00:00:00:00:00:00) expired.

2024-01-21 09:52:53 [5] DHCPD: Lease for 192.168.1.32(Mac:00:00:00:00:00:00) expired.

2024-01-21 09:52:57 [5] DHCPD: Lease for 192.168.1.33(Mac:00:00:00:00:00:00) expired.

2024-01-21 09:53:00 [5] DHCPD: Lease for 192.168.1.34(Mac:00:00:00:00:00:00) expired.

2024-01-21 09:55:39 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 09:55:39 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 10:55:41 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 10:55:41 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 11:05:19 [5] DHCPD: Recv REQUEST from F0:C8:14:D5:9B:48

2024-01-21 11:05:19 [5] DHCPD: Send NAK

2024-01-21 11:05:22 [5] DHCPD: Recv DISCOVER from F0:C8:14:D5:9B:48

2024-01-21 11:05:22 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 11:05:22 [5] DHCPD: Recv REQUEST from F0:C8:14:D5:9B:48

2024-01-21 11:05:23 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 11:05:23 [5] DHCPD: Send NAK

2024-01-21 11:05:26 [5] DHCPD: Recv DISCOVER from F0:C8:14:D5:9B:48

2024-01-21 11:05:26 [5] DHCPD: Send OFFER with ip 192.168.1.32

2024-01-21 11:05:26 [5] DHCPD: Recv REQUEST from F0:C8:14:D5:9B:48

2024-01-21 11:05:26 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 11:05:26 [5] DHCPD: Send NAK

2024-01-21 11:05:29 [5] DHCPD: Recv DISCOVER from F0:C8:14:D5:9B:48

2024-01-21 11:05:29 [5] DHCPD: Send OFFER with ip 192.168.1.33

2024-01-21 11:05:29 [5] DHCPD: Recv REQUEST from F0:C8:14:D5:9B:48

2024-01-21 11:05:29 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 11:05:29 [5] DHCPD: Send NAK

2024-01-21 11:05:32 [5] DHCPD: Recv DISCOVER from F0:C8:14:D5:9B:48

2024-01-21 11:05:32 [5] DHCPD: Send OFFER with ip 192.168.1.34

2024-01-21 11:05:32 [5] DHCPD: Recv REQUEST from F0:C8:14:D5:9B:48

2024-01-21 11:05:33 [5] DHCPD: Send ACK to 192.168.1.34

2024-01-21 11:30:45 [5] DHCPD: Recv REQUEST from 6E:73:49:D3:F0:8A

2024-01-21 11:30:45 [5] DHCPD: Send NAK

2024-01-21 11:30:47 [5] DHCPD: Recv REQUEST from 86:12:D2:DC:3C:18

2024-01-21 11:30:47 [5] DHCPD: Send ACK to 192.168.1.104

2024-01-21 11:55:41 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 11:55:41 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 12:05:24 [5] DHCPD: Lease for 192.168.1.30(Mac:00:00:00:00:00:00) expired.

2024-01-21 12:05:27 [5] DHCPD: Lease for 192.168.1.32(Mac:00:00:00:00:00:00) expired.

2024-01-21 12:05:30 [5] DHCPD: Lease for 192.168.1.33(Mac:00:00:00:00:00:00) expired.

2024-01-21 12:55:43 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 12:55:43 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 13:55:44 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 13:55:44 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 14:09:29 [5] DHCPD: Recv REQUEST from A2:F7:CF:15:FA:8B

2024-01-21 14:09:29 [5] DHCPD: Send NAK

2024-01-21 14:09:31 [5] DHCPD: Recv DISCOVER from EA:76:08:E4:9C:C1

2024-01-21 14:09:31 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 14:09:31 [5] DHCPD: Recv REQUEST from EA:76:08:E4:9C:C1

2024-01-21 14:09:31 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 14:09:31 [5] DHCPD: Send NAK

2024-01-21 14:09:31 [5] DHCPD: Recv DISCOVER from EA:76:08:E4:9C:C1

2024-01-21 14:09:31 [5] DHCPD: Send OFFER with ip 192.168.1.32

2024-01-21 14:09:31 [5] DHCPD: Recv REQUEST from EA:76:08:E4:9C:C1

2024-01-21 14:09:31 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 14:09:31 [5] DHCPD: Send NAK

2024-01-21 14:09:31 [5] DHCPD: Recv DISCOVER from EA:76:08:E4:9C:C1

2024-01-21 14:09:31 [5] DHCPD: Send OFFER with ip 192.168.1.33

2024-01-21 14:09:32 [5] DHCPD: Recv REQUEST from EA:76:08:E4:9C:C1

2024-01-21 14:09:32 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 14:09:32 [5] DHCPD: Send NAK

2024-01-21 14:09:32 [5] DHCPD: Recv DISCOVER from EA:76:08:E4:9C:C1

2024-01-21 14:09:32 [5] DHCPD: Send OFFER with ip 192.168.1.40

2024-01-21 14:09:32 [5] DHCPD: Recv REQUEST from EA:76:08:E4:9C:C1

2024-01-21 14:09:32 [5] DHCPD: Send ACK to 192.168.1.40

2024-01-21 14:34:20 [5] DHCPD: Recv REQUEST from A2:08:08:C8:DC:D6

2024-01-21 14:34:20 [5] DHCPD: Send ACK to 192.168.1.36

2024-01-21 14:38:10 [5] DHCPD: Recv DISCOVER from 0C:70:43:75:80:F0

2024-01-21 14:38:10 [5] DHCPD: Send OFFER with ip 192.168.1.41

2024-01-21 14:38:11 [5] DHCPD: Recv DISCOVER from 0C:70:43:75:80:F0

2024-01-21 14:38:11 [5] DHCPD: Send OFFER with ip 192.168.1.41

2024-01-21 14:38:11 [5] DHCPD: Recv REQUEST from 0C:70:43:75:80:F0

2024-01-21 14:38:12 [5] DHCPD: Send ACK to 192.168.1.41

2024-01-21 14:55:46 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 14:55:46 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 15:09:33 [5] DHCPD: Lease for 192.168.1.30(Mac:00:00:00:00:00:00) expired.

2024-01-21 15:09:33 [5] DHCPD: Lease for 192.168.1.32(Mac:00:00:00:00:00:00) expired.

2024-01-21 15:09:33 [5] DHCPD: Lease for 192.168.1.33(Mac:00:00:00:00:00:00) expired.

2024-01-21 15:15:26 [5] DHCPD: Recv REQUEST from 86:12:D2:DC:3C:18

2024-01-21 15:15:26 [5] DHCPD: Send ACK to 192.168.1.104

2024-01-21 15:15:53 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 15:15:53 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 15:15:53 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 15:15:53 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 15:15:59 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 15:15:59 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 15:15:59 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 15:15:59 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 15:17:00 [5] DHCPD: Lease for 192.168.1.30(Mac:50:A0:09:B2:39:0B) expired.

2024-01-21 15:51:51 [5] DHCPD: Recv REQUEST from A2:08:08:C8:DC:D6

2024-01-21 15:51:51 [5] DHCPD: Send ACK to 192.168.1.36

2024-01-21 15:55:49 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 15:55:49 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 16:06:12 [5] DHCPD: Recv REQUEST from B4:6D:C2:03:DD:C3

2024-01-21 16:06:12 [5] DHCPD: Send NAK

2024-01-21 16:06:15 [5] DHCPD: Recv DISCOVER from B4:6D:C2:03:DD:C3

2024-01-21 16:06:15 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 16:06:15 [5] DHCPD: Recv REQUEST from B4:6D:C2:03:DD:C3

2024-01-21 16:06:15 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 16:06:15 [5] DHCPD: Send NAK

2024-01-21 16:06:18 [5] DHCPD: Recv DISCOVER from B4:6D:C2:03:DD:C3

2024-01-21 16:06:18 [5] DHCPD: Send OFFER with ip 192.168.1.32

2024-01-21 16:06:18 [5] DHCPD: Recv REQUEST from B4:6D:C2:03:DD:C3

2024-01-21 16:06:18 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 16:06:18 [5] DHCPD: Send NAK

2024-01-21 16:06:21 [5] DHCPD: Recv DISCOVER from B4:6D:C2:03:DD:C3

2024-01-21 16:06:21 [5] DHCPD: Send OFFER with ip 192.168.1.33

2024-01-21 16:06:22 [5] DHCPD: Recv REQUEST from B4:6D:C2:03:DD:C3

2024-01-21 16:06:22 [5] DHCPD: Send ACK to 192.168.1.33

2024-01-21 16:34:07 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 16:34:07 [5] DHCPD: Send OFFER with ip 192.168.1.42

2024-01-21 16:34:12 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 16:34:12 [5] DHCPD: Send OFFER with ip 192.168.1.42

2024-01-21 16:34:16 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 16:34:16 [5] DHCPD: Send OFFER with ip 192.168.1.42

2024-01-21 16:34:42 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 16:34:42 [5] DHCPD: Send OFFER with ip 192.168.1.42

2024-01-21 16:35:43 [5] DHCPD: Lease for 192.168.1.42(Mac:50:A0:09:B2:39:0B) expired.

2024-01-21 16:55:51 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 16:55:51 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 17:06:18 [5] DHCPD: Lease for 192.168.1.30(Mac:00:00:00:00:00:00) expired.

2024-01-21 17:06:19 [5] DHCPD: Lease for 192.168.1.32(Mac:00:00:00:00:00:00) expired.

2024-01-21 17:17:49 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 17:17:49 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 17:18:52 [5] DHCPD: Lease for 192.168.1.30(Mac:50:A0:09:B2:39:0B) expired.

2024-01-21 17:55:53 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 17:55:53 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 18:29:47 [5] DHCPD: Recv REQUEST from E4:AA:EC:78:4C:72

2024-01-21 18:29:47 [5] DHCPD: Send NAK

2024-01-21 18:29:51 [5] DHCPD: Recv DISCOVER from E4:AA:EC:78:4C:72

2024-01-21 18:29:51 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 18:29:51 [5] DHCPD: Recv REQUEST from E4:AA:EC:78:4C:72

2024-01-21 18:29:51 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 18:29:51 [5] DHCPD: Send NAK

2024-01-21 18:29:54 [5] DHCPD: Recv DISCOVER from E4:AA:EC:78:4C:72

2024-01-21 18:29:54 [5] DHCPD: Send OFFER with ip 192.168.1.32

2024-01-21 18:29:54 [5] DHCPD: Recv REQUEST from E4:AA:EC:78:4C:72

2024-01-21 18:29:55 [5] DHCPD: Send ACK to 192.168.1.32

2024-01-21 18:46:30 [5] DHCPD: Recv DISCOVER from E4:AA:EC:25:5C:71

2024-01-21 18:46:30 [5] DHCPD: Send OFFER with ip 192.168.1.42

2024-01-21 18:46:30 [5] DHCPD: Recv REQUEST from E4:AA:EC:25:5C:71

2024-01-21 18:46:31 [5] DHCPD: Send ACK to 192.168.1.42

2024-01-21 18:53:47 [6] System: User(Mac:9C:9D:7E:16:44:7E;IP:192.168.1.235) logs in.

2024-01-21 18:53:53 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 18:53:53 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 18:53:56 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 18:53:56 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 19:06:27 [6] System: User(Mac:1C:6F:65:C5:8F:A2;IP:192.168.1.222) logs in.

2024-01-21 19:06:32 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 19:06:32 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 19:06:34 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 19:06:34 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 19:06:49 [5] DHCPD: Recv DISCOVER from 80:E8:2C:19:F4:3F

2024-01-21 19:06:49 [5] DHCPD: Send OFFER with ip 192.168.1.234

2024-01-21 19:06:49 [5] DHCPD: Recv REQUEST from 80:E8:2C:19:F4:3F

2024-01-21 19:06:50 [5] DHCPD: Send ACK to 192.168.1.234

2024-01-21 19:06:50 [5] DHCPD: Recv DISCOVER from E4:AA:EC:25:5C:71

2024-01-21 19:06:50 [5] DHCPD: Send OFFER with ip 192.168.1.42

2024-01-21 19:06:50 [5] DHCPD: Recv REQUEST from E4:AA:EC:25:5C:71

2024-01-21 19:06:50 [5] DHCPD: Send ACK to 192.168.1.42

2024-01-21 19:06:56 [5] DHCPD: Recv REQUEST from A2:08:08:C8:DC:D6

2024-01-21 19:06:56 [5] DHCPD: Send ACK to 192.168.1.36

2024-01-21 19:07:03 [5] DHCPD: Recv DISCOVER from E4:AA:EC:78:4C:72

2024-01-21 19:07:03 [5] DHCPD: Send OFFER with ip 192.168.1.32

2024-01-21 19:07:04 [5] DHCPD: Recv REQUEST from E4:AA:EC:78:4C:72

2024-01-21 19:07:04 [5] DHCPD: Send ACK to 192.168.1.32

2024-01-21 19:07:10 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 19:07:10 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 19:07:19 [5] DHCPD: Recv DISCOVER from 90:9A:4A:68:F5:D7

2024-01-21 19:07:19 [5] DHCPD: Send OFFER with ip 192.168.1.107

2024-01-21 19:07:19 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 19:07:20 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 19:07:48 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 19:07:48 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 19:08:03 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 19:08:03 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 19:12:13 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 19:12:13 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 19:15:36 [6] Httpd: DNS 212.205.212.205 resolve succeed for dns.msftncsi.com

2024-01-21 19:15:36 [6] Httpd: DNS 212.205.212.205 resolve succeed for www.msftncsi.com

2024-01-21 19:29:51 [5] DHCPD: Lease for 192.168.1.30(Mac:00:00:00:00:00:00) expired.

2024-01-21 19:46:11 [5] DHCPD: Recv DISCOVER from 0C:70:43:75:80:F0

2024-01-21 19:46:11 [5] DHCPD: Send OFFER with ip 192.168.1.41

2024-01-21 19:46:13 [5] DHCPD: Recv DISCOVER from 0C:70:43:75:80:F0

2024-01-21 19:46:13 [5] DHCPD: Send OFFER with ip 192.168.1.41

2024-01-21 19:46:13 [5] DHCPD: Recv REQUEST from 0C:70:43:75:80:F0

2024-01-21 19:46:14 [5] DHCPD: Send ACK to 192.168.1.41

2024-01-21 20:07:21 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 20:07:21 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 20:20:57 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 20:20:57 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 20:21:02 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 20:21:02 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 20:21:02 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 20:21:02 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 20:21:07 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 20:21:07 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 20:21:16 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 20:21:16 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 20:21:16 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 20:21:16 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 20:21:16 [5] DHCPD: Recv DISCOVER from 50:A0:09:B2:39:0B

2024-01-21 20:21:16 [5] DHCPD: Send OFFER with ip 192.168.1.30

2024-01-21 20:21:16 [5] DHCPD: Recv REQUEST from 50:A0:09:B2:39:0B

2024-01-21 20:21:16 [5] DHCPD: Wrong Server id or request an invalid ip

2024-01-21 20:21:16 [5] DHCPD: Send NAK

2024-01-21 20:21:16 [5] DHCPD: Recv REQUEST from 50:A0:09:B2:39:0B

2024-01-21 20:21:21 [5] DHCPD: Recv REQUEST from 50:A0:09:B2:39:0B

2024-01-21 20:21:21 [5] DHCPD: Recv REQUEST from 50:A0:09:B2:39:0B

2024-01-21 20:21:28 [5] DHCPD: Recv REQUEST from 50:A0:09:B2:39:0B

2024-01-21 20:21:28 [5] DHCPD: Recv REQUEST from 50:A0:09:B2:39:0B

2024-01-21 20:21:28 [5] DHCPD: Recv REQUEST from 50:A0:09:B2:39:0B

2024-01-21 20:21:28 [5] DHCPD: Recv REQUEST from 50:A0:09:B2:39:0B

2024-01-21 20:21:28 [5] DHCPD: Recv REQUEST from 50:A0:09:B2:39:0B

2024-01-21 20:26:02 [5] DHCPD: Recv REQUEST from F2:D8:C0:68:3E:B6

2024-01-21 20:26:02 [5] DHCPD: Server id not found and request an invalid ip

2024-01-21 20:26:02 [5] DHCPD: Send NAK

2024-01-21 20:26:02 [5] DHCPD: Recv DISCOVER from F2:D8:C0:68:3E:B6

2024-01-21 20:26:02 [5] DHCPD: Send OFFER with ip 192.168.1.106

2024-01-21 20:26:02 [5] DHCPD: Recv REQUEST from F2:D8:C0:68:3E:B6

2024-01-21 20:26:02 [5] DHCPD: Send ACK to 192.168.1.106

2024-01-21 20:27:47 [5] DHCPD: Recv DISCOVER from 6E:73:49:D3:F0:8A

2024-01-21 20:27:47 [5] DHCPD: Send OFFER with ip 192.168.1.43

2024-01-21 20:27:48 [5] DHCPD: Recv REQUEST from 6E:73:49:D3:F0:8A

2024-01-21 20:27:48 [5] DHCPD: Send ACK to 192.168.1.43

2024-01-21 20:52:02 [5] DHCPD: Recv REQUEST from 78:8A:86:E4:BB:6D

2024-01-21 20:52:02 [5] DHCPD: Send ACK to 192.168.1.31

2024-01-21 20:53:04 [5] DHCPD: Recv REQUEST from B4:6D:C2:04:E3:B5

2024-01-21 20:53:04 [5] DHCPD: Send ACK to 192.168.1.35

2024-01-21 21:07:23 [5] DHCPD: Recv REQUEST from 90:9A:4A:68:F5:D7

2024-01-21 21:07:23 [5] DHCPD: Send ACK to 192.168.1.107

2024-01-21 21:12:21 [5] DHCPD: Recv REQUEST from 6E:73:49:D3:F0:8A

2024-01-21 21:12:21 [5] DHCPD: Send ACK to 192.168.1.43

2024-01-21 21:12:40 [5] DHCPD: Recv REQUEST from 6E:73:49:D3:F0:8A

2024-01-21 21:12:40 [5] DHCPD: Send ACK to 192.168.1.43

2024-01-21 21:12:40 [6] 4G: USER: The network disconnected, start autoconnect!

 

2024-01-21 21:12:40 [6] 4G: USER: Get user's profile now.

 

2024-01-21 21:12:40 [6] 4G: USER: GetCurrProf result is: ipver:2 staticApn:0 authType:2 pkgName:PublicIP2 profname:PublicIP2 apn:vpn-internet usr: psw:  

 

2024-01-21 21:12:43 [5] 4G: lte internet disconnected.

2024-01-21 21:12:43 [6] 4G: LTE connection down

2024-01-21 21:14:02 [5] DHCPD: Recv REQUEST from 6E:73:49:D3:F0:8A

2024-01-21 21:14:02 [5] DHC

PD: Send ACK to 192.168.1.43

2024-01-21 21:14:43 [6] System: User(Mac:F2:D8:C0:68:3E:B6;IP:192.168.1.106) logs in.

2024-01-21 21:15:48 [5] DHCPD: Recv REQUEST from 86:12:D2:DC:3C:18

2024-01-21 21:15:48 [5] DHCPD: Send ACK to 192.168.1.104

2024-01-21 21:15:50 [5] DHCPD: Recv REQUEST from F2:D8:C0:68:3E:B6

2024-01-21 21:15:50 [5] DHCPD: Send ACK to 192.168.1.106

 

  0  
  0  
#11
Options
123...

Information

Helpful: 7

Views: 22765

Replies: 123

Tags

Network Connectivity Official
Related Articles
Archer MR500 regular internet disconnection
22087 1
  Unstable LTE Connection TL-MR100
465 0
LTE keeps disconnecting
29493 1
MR500 disconnection problem
1368 0
 TL-MR6400 unstable LTE connection
1477 0
Archer mr500 WPA3
937 1
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.