Archer C6 hairpin / loopback
Archer C6 hairpin / loopback
Hi,
Is it possible to configure loopback / hairpining in Archer C6? I'm trying to access my home server using my public IP adress and domain name assigned to that IP. I'm able to access my server from outside of my lan/wifi network, but when I'm connected to lan/wifi the only possibility to connect is to use my internal IP adress adres of the server (192.168.0.x).
There is nextcloud host running on my server and nextcloud mobile client won't allow two ip adresses/domains for single server.
Kind Regards,
P.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi,
the Archer C6 supports NAT loopback and it is enabled by default.
Can you access the server with WAN IP address when your device connected to the router?
Besides, what do you mean " here is nextcloud host running on my server and nextcloud mobile client won't allow two ip adresses/domains for single server.” please provide more details.
Good day.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Same problem here. The strange thing in my case is that NAT loopback used to work in the beginning, and stopped working after a while. Not sure what caused it to stop working. I've tried deactivating QoS and NAT boost as suggested in other threads, but no luck.
I have an entry in virtual servers mapping the 8080 port of my NAS web management to the local NAS IP. I can access the web management from WAN without problems, and from LAN through local IP of the NAS. When accessing the web management from LAN I get a timeout. I assume this is due to hairpinning not working properly (any more).
Firmware version: 1.2.1 Build 20200110 rel.60119 (4555)
Hardware version: Archer C6 v2.0
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
This is obviously an old thread but this issue remains...
1.3.1 - Loopback works but wifi bug
1.3.6 - Loopback doesn't work but wifi seems better...
Don't suppose anyone has figured out how to turn loopback on in 1.3.6?
- Copy Link
- Report Inappropriate Content
Hello, are you with the latest 1.3.6 version on the Archer C6, or you are with some special build beta version? Can we have the detailed version info? You may check it on its web interface page.
Are you able to access the local server from WAN, but failed to access it locally? Was there any error message? Please provide the detailed network scratch, is there any switch or extender in the network?
- Copy Link
- Report Inappropriate Content
I was on 1.3.1 with everything working well. I then upgraded to 1.3.6 (20201030-rel60104) downloaded from this forum. Straight after upgrading I lost access to my local server from within the network but still had WAN access. Fiddled around checking settings and the server but couldn't find a solution to rolled back to the 1.3.1 firmware and everything was working again. There wasn't a specific error message that I can recall - I think it just wouldn't connect. I'm accessing a local Home Assistant server.
I have an Archer C6 as my main router and DHCP server. It connects to fibre via a Ubiquiti LOCO ONT. I extend that network with a wired connection to an Archer C20 in AP mode.
I'm considering trying other firmware options, but thought I should check if anyone knew which versions had working loopback.
- Copy Link
- Report Inappropriate Content
Thank you very much for all the details.
So can you please confirm if there is only a firmware upgrade on the Archer C6, no other changes or modifications in the network? If it is not too troublesome, we hope you could try to reset the Archer C6 to factory defaults, then reconfigure it from scratch to confirm this.
Do you mean you cannot roll back to the latest official version? Can you please confirm again? As we are informed that this version can be rolled back. You may find the latest official firmware here:
https://www.tp-link.com/support/download/archer-c6/#Firmware
BTW, we will soon test and confirm this, we will update you once this is confirmed.
- Copy Link
- Report Inappropriate Content
I can confirm the only change is the firmware on the network.
I was using 1.3.1 even though the official is 1.3.5 - I'd read that there were still 2.4ghz wifi issues with 1.3.5. I'd tried 1.3.6 beta as it seemed from comments on the forum that it was better for 2.4ghz wifi.
I can reset to factory defaults and try again this evening - don't want to spend too much time now while I'm working.
- Copy Link
- Report Inappropriate Content
Thank you very much for your quick reply and cooperation on this. Do that at your convenience, and we will soon check this as well.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5959
Replies: 17
Voters 0
No one has voted for it yet.