Classic VPN client - could I fix conflicting addresses this way?
We have servers in 192.168.0.0 and 192.168.1.0. Most (99.99%) home networks are in one of these subnets. The PC at home then tries to route to the server via the local subnet. Our NAT termination device is a PIX running version 7.
Could I setup a policy NAT for these connections? Have the VPN IP pool accessing the servers see the servers as 172.30.0.0 and 172.30.1.0 instead. The clients use a DNS server that is in one of the server subnets, so DNS lookups could also be fixed-up. But has anyone ever got this to work?
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...