NAT Hairpin/Loopback
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi all,
Ok so I thought it was a case of either supporting it or not supporting it. But for some reason the Deco seems to "kind of" support it , when it can be bothered.
To give context of what is happening , I have a bunch of web cameras which I access from my mobile device (phone) on a regular basis. Each one is accessed via a DDNS domain name and NAT'd on my router using port forwarding (ie incoming connections to router IP address on port 8000 is forwarded to 1 camera on port 80, and 8001 is forwarded to a different camera on port 80 etc.
With my old router I used to do this and it worked absolutely fine when accessing these either internally or externally from my home network.
I've now got the Deco as a router and have set up forwarding the same as before, but connectivity to the cameras when I'm inside my network sometimes works, sometimes doesn't, and when it does, it is hideously slow.
I've tried disabling the IPS etc on the Deco to see if it was that, but alas it makes no difference.
Pretty sure I can't be the only person with a Deco that is wanting to do such a basic thing like this.... help?
Does it support it or not?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Kevin_Z this works for me. Thanks.
- Copy Link
- Report Inappropriate Content
I see a lot of future releases and nothing being done
Can you clarify?
Kevin_Z wrote
Hi all users.
For the NAT loopback issue, we found that it is caused by the Trend Micro's interception, and we have negotiated a solution with Trend Micro, we will fix it in the next firmware.
Please keep an eye on the official website/Deco app or contact us for more info.
Good day.
- Copy Link
- Report Inappropriate Content
TP-link any updates on this issue for the decco M9 Plus?
I feel like getting rid of this product due to this issue as my NAS plays an important role on my network for backing up pics and i can't run the high bandwidth access to my NAS from my phone unless i use my phone's cell network at home which is ridiculous!
- Copy Link
- Report Inappropriate Content
I am having the same issues. Deco M9 Plus. Unable to connect with IP or tplink DNS. Tried turning off antivirus and set QoS to standard (and removed all devices from priority). Any updates?
Works fine outside the local network. Please help!
- Copy Link
- Report Inappropriate Content
Hi,
Could you please provide me a picture of the network structure of the Deco system?
--if possible, please also help me mark out where the NAS is connected, and on which device that you need to access the NAS via WAN IP or TP-link DNS?
Would there be any error message when you failed to access the NAS?
Thank you very much and wait for your reply.
- Copy Link
- Report Inappropriate Content
The Main deco is set up right after the my ISP router. DMZ open, so everything goes through to the deco.
After that I have a cable to a switch, and a raspberrypi connected by cable. The port in question is set up in port forwarding. And as I said it works outside of the local network. It is also accessible without the local network, using the local IP of the raspberry pi.
I get the error:
ERR_CONNECTION_REFUSED
When you say picture of the network structure, what are you referring to?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi, Sorry for the delay.
I would like to forward your case to the senior engineers for further assistance and please have a check of your email box.
At the same time, could you please help confirm the following 2 details:
1. is the network topology like ISP router(already enabled DMZ for main M9)----cable----main Deco M9-----switch---cable---raspberry pi?
2.Could you please send me the system log on the Deco on the web Ui http://tplinkdeco.net?
Thank you very much.
- Copy Link
- Report Inappropriate Content
Thank you for picking this up again.
1: Yes, that is correct.
2: Log of a successful, and unsuccessful attempt of connecting to the device in question:
Wed Apr 21 08:21:46 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block Wed Apr 21 08:21:46 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:21:46 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:21:47 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block Wed Apr 21 08:21:48 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:21:48 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Apr 21 08:21:48 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Apr 21 08:21:48 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Apr 21 08:21:49 2021 user.err csrMeshGw[7198]: CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!! Wed Apr 21 08:21:49 2021 authpriv.notice dropbear[1909]: Pubkey auth succeeded for 'root' with key sha1!! 60:b0:9f:8a:7a:5f:b3:64:3e:22:e8:25:4e:c1:f9:cc:09:23:ca:92 from 192.168.68.100:50393 Wed Apr 21 08:21:49 2021 authpriv.info dropbear[1909]: Exit (root): Exited normally Wed Apr 21 08:21:50 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block Wed Apr 21 08:21:53 2021 daemon.err client_mgmt: client(06-2F-79-28-38-26) not found in arp table disconnect_counter=0 Wed Apr 21 08:21:53 2021 daemon.err client_mgmt: client(E4-E4-AB-1E-A6-36) not found in arp table disconnect_counter=0 Wed Apr 21 08:21:54 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:21:56 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:21:58 2021 user.err csrMeshGw[7198]: CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff Wed Apr 21 08:21:58 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Apr 21 08:21:58 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Apr 21 08:21:58 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Apr 21 08:21:59 2021 user.err csrMeshGw[7198]: CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!! Wed Apr 21 08:22:02 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:22:03 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:22:03 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:22:08 2021 user.err csrMeshGw[7198]: CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff Wed Apr 21 08:22:08 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Apr 21 08:22:08 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Apr 21 08:22:08 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Apr 21 08:22:09 2021 user.err csrMeshGw[7198]: CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!! Wed Apr 21 08:22:11 2021 authpriv.notice dropbear[2380]: Pubkey auth succeeded for 'root' with key sha1!! 60:b0:9f:8a:7a:5f:b3:64:3e:22:e8:25:4e:c1:f9:cc:09:23:ca:92 from 192.168.68.102:33744 Wed Apr 21 08:22:12 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:22:13 2021 authpriv.info dropbear[2380]: Exit (root): Exited normally Wed Apr 21 08:22:14 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:22:17 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:22:18 2021 user.err csrMeshGw[7198]: CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff Wed Apr 21 08:22:18 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2 Wed Apr 21 08:22:18 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30 Wed Apr 21 08:22:18 2021 user.err csrMeshGw[7198]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30 Wed Apr 21 08:22:19 2021 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block Wed Apr 21 08:22:19 2021 user.err csrMeshGw[7198]: CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 22527
Replies: 42
Voters 1
