ER7212PC bug with no NAT reflection / hairpinning / loopback
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi @Clive_A , i have the ER7212PC router installed, and attached my web server PC with NAT redirection to IP + port 80, i have the latest firmware installer on the router.
my extern domain name is targeting the router and then translates through NAT perfectly, only when my source computer or phone is not on the local LAN.
at work i call my domain and worked as expected, but on local lan/home it refuses to connect, there are no settings on the ER7212PC to setup/configure reflection/hairpinning/loopback features, this should work out of the box and it is not.
when could ER7212PC reflection/hairpinning/loopback bug can be fixed ? we can't acces local computers by their external name ( => NAT) on the local network.
nb: dont propose me split dns
thx
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I can confirm this bug with the latest firmware. I was unable to use the DNS on my pi-hole naming and had to resort to IP address. I had some result with all items in the same VLAN but between other VLAN's no chance. In the end i downgraded back to 1.0.3 and all started working again. I did place a hint at a problem on the official release thread but had no reply.
- Copy Link
- Report Inappropriate Content
Hi @stephK
Thanks for posting in our business forum.
Need a network diagram. And backup of your settings.
I'll create a case and send it for further diagnostics.
I also need a screenshot of the issue. Please prepare them and send it to the email you receive later.
- Copy Link
- Report Inappropriate Content
@Clive
here is the diagram + settings send me the email pls , help needed !
thank you
- Copy Link
- Report Inappropriate Content
Hi @stephK
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230917231, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
@TazDevilLooney the suggested solution to resolve the issue:
- on your omada web interface, click on the router => right panels => ports
- enable "mirroring" => select the WAN port you want to get mirrored => select mode "ingress and egress"
- apply the setting, you should see a "mirroing icon" on the row of your LAN in the list
solution provided by the TP-Link team
- Copy Link
- Report Inappropriate Content
Hi @stephK
stephK wrote
@TazDevilLooney the suggested solution to resolve the issue:
- on your omada web interface, click on the router => right panels => ports
- enable "mirroring" => select the WAN port you want to get mirrored => select mode "ingress and egress"
- apply the setting, you should see a "mirroing icon" on the row of your LAN in the list
solution provided by the TP-Link team
Hey! I suggest you don't jump to the conclusion. So, the senior engineer built up a network in our lab and tried to reproduce your issue. From the email, he said we can make NAT loopback work. There is no issue with the firmware.
So he suspects that your network is not behaving correctly and asking for you to Wireshark and provide capture so that we can try to locate the reason why.
I would suggest you take it slow and read what was said in the reply. Instead of being sarcastic here.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 872
Replies: 6
Voters 0
No one has voted for it yet.