Different address family
-
Hi Guys,
Having a problem here getting the static on the firewall configured for the IPSec interface for AWS VPN with the static routing. I created a phase 1 & 2 entries (the tunnel went up) with 169.254 addressing; then had this tunnel added into the list of interfaces. The interface is up (and I can see it from the console side) with the the routes for in-tunnel addressing. I have gateway is created as well via static routing page, but the moment I am trying to create a static route I am getting "The gateway "169.254.16.x is a different Address Family than network 10.x.x.x", where 10.x.x.x is the network I am trying to add and 169.254.16.x is the address of the AWS-side of the tunnel. Did anyone had this before? I have seen a post from some time ago referring to the address subnetting, but I don't understand how it is relevant here, because the whole purpose of the route is to make hosts of the unknown network accessible via a gateway in the local net?
Cheers