1
General Discussion / Re: Translate outgoing request for external IP to internal IP?
« on: March 19, 2020, 05:46:07 pm »
Wow, thanks so much for the speedy response!!!
Unfortunately I am used to configuring consumer-grade routers, not professional ones like OPNsense. Thus my experience with NAT is roughly that everything is automatically configured, except for port forwards where I simply provide a list of internal IPs and ports. All the new options are wonderful but overwhelming.
In this specific case, my confusion is about which packet headers are getting rewritten by which rule. If I correctly understand your explanation, when I send a packet from 192.168.1.50 to 10.0.0.100, the "Port Forward" rule rewrites "Destination" from 10.0.0.100 to 192.168.1.100, but it leaves "From" as 192.168.1.50. So then the "Outbound" rule would somehow rewrite "Source" from 192.168.1.50 to 192.168.1.1. But I don't understand how the given rule makes this happen.
Is it a pipeline where Port Forward comes first, changing the destination? And next the Outbound rule is applied, and it matches since we just changed the destination to 192.168.1.100?
Unfortunately I am used to configuring consumer-grade routers, not professional ones like OPNsense. Thus my experience with NAT is roughly that everything is automatically configured, except for port forwards where I simply provide a list of internal IPs and ports. All the new options are wonderful but overwhelming.
In this specific case, my confusion is about which packet headers are getting rewritten by which rule. If I correctly understand your explanation, when I send a packet from 192.168.1.50 to 10.0.0.100, the "Port Forward" rule rewrites "Destination" from 10.0.0.100 to 192.168.1.100, but it leaves "From" as 192.168.1.50. So then the "Outbound" rule would somehow rewrite "Source" from 192.168.1.50 to 192.168.1.1. But I don't understand how the given rule makes this happen.
Is it a pipeline where Port Forward comes first, changing the destination? And next the Outbound rule is applied, and it matches since we just changed the destination to 192.168.1.100?