Hairpin NAT


#1

I’d like the ability to create a hairpin NAT. For example: allow internal clients to access an internal server using the public address (very useful for customers not running split DNS). Other vendors (sonicwall, juniper, etc) support this.


#2

We have already supported this feature. Once you have configured Inbound Access/Port Mappings/NAT Mappings rules, the internal clients can access the internal server using the public IP address.


#3

I opened a support case for this yesterday (Ticket# 744765). I was told that Peplink does not support this feature and was directed to this forum to suggest it. I’ve also tested it and it does not appear to work so I must be missing something. I’ve verified the port forwarding is working; external computers can access my internal servers via the port forward yet the internal computers still cannot access using the public IP. What should I be checking?


#4

I am requesting the Diagnostic Report of your unit, please check my response through email.


#5

Is there any documentation or KB articles that explain how to set up hairpining with Inbound Access/Port Mappings/NAT Mappings rules? I would like to set this up on our Balance 305 to allow our Guest lan to access our OWA server.


#6

@ban
There is no special feature to activate it, you will just need to ensure the portforwarding is setup along with being on current firmware:
http://www.peplink.com/support/downloads/balance-firmware-and-user-manual-6-2/