Use Loopback to access the WAN IP of an upper router.
Use Loopback to access the WAN IP of an upper router.
The issue involves a network setup where the local IP address isn't signed directly. When trying to reach the NAS over WAN, packets go through an upper NAT and then back. The diagram shows the basic flow: office router → b.b.b.b (upper NAT) → c.c.c.c (global). I don’t understand how the ISP configures these components, especially since DMZ is connected to b.b.b.b. I’m using pfSense as the router.
It's referred to as Haripinning and should be set up on the device managing NAT. Does it seem like you don't manage that device?
I lack authority over the higher-level NAT unit. However, I manage the office LAN which includes the local NAT device (PFSense). Routers typically loop back their WAN IP address by default. But here, I need to redirect the upper-level NAT's WAN IP into the local NAT.
Not activated by default on most systems. No information about pfsense provided. You need access to the underlying hardware to proceed.
You won't require connection to the upstream device. Just set up a destination NAT rule; if pfSense detects traffic going to c.c.c.c, it will translate to a NAS IP address. This approach is still viewed as hairpinning or Nat loopback, based on the vendor or your specific setup. Create a Nat rule, assign it to your internal/lan interface, input source and destination networks, then apply the redirect target IP for the NAS internal address.
He seems focused solely on getting to the NAS, so why not just use the private IP?
Of course, office colleagues often mix up private and public IP addresses. I’m trying to reduce data usage when accessing large files through the NAS webUI using a public IP. LOL
Great! I'm here to help you figure out what this page is about. Let me know if you need a clearer explanation. 😊