I am attempting to create a dnat to the far side of a s2s vpn tunnel and this isnt' working
from the webadmin i can ping the far side host I am trying to get to 192.168.102.200
I want 10.10.1.3 to "spoof" per say being the 192.168.102.200 addy.
What I have done.
Setup an additional IP address on the internal interface 10.10.1.3 (As I want all services to be able to get to the remote host.)
created dnat rule
from internal network -> any service -> to additional ip 10.10.1.3
change the destination to 192.168.102.200.
Auto firewall rule
this is not working ... my understanding is if setting up a dnat rule to access an internal server from the internet would be
from internet -> port 80 (http) -> to external IP
change destination to: internal web server.
auto firewall.
what am i missing?:confused:
from the webadmin i can ping the far side host I am trying to get to 192.168.102.200
I want 10.10.1.3 to "spoof" per say being the 192.168.102.200 addy.
What I have done.
Setup an additional IP address on the internal interface 10.10.1.3 (As I want all services to be able to get to the remote host.)
created dnat rule
from internal network -> any service -> to additional ip 10.10.1.3
change the destination to 192.168.102.200.
Auto firewall rule
this is not working ... my understanding is if setting up a dnat rule to access an internal server from the internet would be
from internet -> port 80 (http) -> to external IP
change destination to: internal web server.
auto firewall.
what am i missing?:confused: