Remote Logging Question
Remote Logging Question

I have my controller configured for remote logging and the log entries are stored on my NAS. Before adding the controller to the network, the gateway (ER706W) was configured for remote logging in standalone mode. The problem now is that the gateway is continuing to send logs to the remote server with the same information that the controller is sending (such as DHCP assignments). My question... How do I disable remote logging in the gateway which is now controlled by the controller?
Update: I disabled remote logging on the controller. The gateway is continuing to send logs which tells me remote logging in the gateway was not disabled when adopted by the controller. I believe the only solution is to have the controller forget the gateway, then factory reset the gateway, and finally have the controller adopt the gateway again. Hopefully, someone from Tp-Link can confirm this. If this is the case, then it is a bug that needs to be fixed in a future software update.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
The support team recommended that I do a Force Provision in the controller for the router. That fixed the issue with the wrong IP address being used for the remote logging server.
- Copy Link
- Report Inappropriate Content

Hi @jra11500
Thanks for posting here. Before factory reset the gateway router, would you please share the following information with us?
1. The firmware version of the ER706W;
2. A screenshot of the remote logging config page;
3. Some screenshots of the logs you mentioned, so we could know what kinds of logs are sending duplicates.
4. Is the NAS installed in the same LAN network or remotely?
- Copy Link
- Report Inappropriate Content
Here is the information you asked for:
1. The firmware version of the ER706W is 1.2.2 Build 20250722 Rel.78330(4555).
2. Here is a screenshot of the controller settings for remote logging:
3. Here is a screenshot of the ER706W log as it appears on the NAS:
Here is a screenshot of the OC300 log as it appears on the NAS:
The logs only have a few entries as they were cleared earlier.
4. The NAS is local and is on my main VLAN (20) where my PCs and peripherals reside. The subnet is 192.168.20.0/24. The default VLAN (1) is used only for network devices, such as the gateway and controller. The subnet is 192.168.10.0/24. No clients use the default VLAN.
I do remember having the same problem with my EAP610 when I first installed the controller. The EAP610 was sending logs to the NAS before the controller was configured. To stop the logging, I had to reset the EAP610 and adopt it again.
- Copy Link
- Report Inappropriate Content
Hi @jra11500
Thank you for the info. We will test it locally and see if it's the same.
In the meantime, I had created a support ticket ( ID: TKID250801495). Please send a copy of your controller's configuration file via that email.
This is in case that we are unable to reproduce this issue locally, or if the problem is related to a specific configuration, we will import your configuration file to ensure identical testing conditions.
- Copy Link
- Report Inappropriate Content
I have responded to the support ticket with the file.
I just finished resetting the ER706W and adopting it again in the controller. Only the user account info and the LAN IP address were changed before adopting. The remote logging option was disabled. The gateway is still sending logs to the remote server.
- Copy Link
- Report Inappropriate Content
I have managed to stop the duplicate DHCP log entries coming from the controller. Under Site Logs, Notifications, Event, Device, I disabled the Gateway DHCP Server Module Information option. I now only receive the DHCP assignments in the ER706W log.
- Copy Link
- Report Inappropriate Content

Hi @jra11500
Thanks for the feedback. It's much appreciated.
We will explore more about this feature.
To confirm: is the received log coming from the router's IP 192.168.20.1 ?
- Copy Link
- Report Inappropriate Content
Yes, the log is coming from the gateway IP address (which is its VLAN 20 interface address on the same subnet as the NAS).
- Copy Link
- Report Inappropriate Content
Something new has occurred! Late last night, I changed the IP address of the NAS which runs the remote logging server. I then updated the controller with the new IP setting and the controller logs are being received OK. What is strange is that the ER706W logs have stopped and I am no longer receiving logs directly from the gateway. Thinking that perhaps the gateway might be sending logs to the old IP address, this morning I configured another log server on a different NAS and configured this server with the old IP address. Initially, there were no logs and I went to lunch.
Afternoon Update: The secondary remote logging server on the old IP address has been running some 6 hours now and the ER706W has sent 39 log entries. Somehow the old remote logging server's IP address is "stuck" in the gateway and does not follow the controller's setiings. Comments?
- Copy Link
- Report Inappropriate Content
It appears the controller's configuration failed to override the remote log settings in standalone mode.
I've escalated this to the relevant team and will provide updates as soon as there's progress.
jra11500 wrote
Something new has occurred! Late last night, I changed the IP address of the NAS which runs the remote logging server. I then updated the controller with the new IP setting and the controller logs are being received OK. What is strange is that the ER706W logs have stopped and I am no longer receiving logs directly from the gateway. Thinking that perhaps the gateway might be sending logs to the old IP address, this morning I configured another log server on a different NAS and configured this server with the old IP address. Initially, there were no logs and I went to lunch.
Afternoon Update: The secondary remote logging server on the old IP address has been running some 6 hours now and the ER706W has sent 39 log entries. Somehow the old remote logging server's IP address is "stuck" in the gateway and does not follow the controller's setiings. Comments?
- Copy Link
- Report Inappropriate Content
The support team recommended that I do a Force Provision in the controller for the router. That fixed the issue with the wrong IP address being used for the remote logging server.
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 323
Replies: 12
Voters 0
No one has voted for it yet.