Hi ... In regards to the DDNS question .. I don't think the PIX can do that as it would have to refer to a FQDN as the peer for a VPN tunnel which is not supported. As long as I am aware you can only refer to an IP address or hostname ( previously defined with the name command on the PIX ).
The second question:
The access-list defines the traffic that will be encrypted when it traverses the interface to which the crypto map has been applied to. If the traffic does not traverse the interface to which the map has been aplied then that traffic will not be encrypted.
Does this answer your question ..? If you want to exempt traffic for this host from encryption then I suggest you to exclude that from the access-list using the deny option.
My initial thought was that the 'hostname' parameter of an ACL could be a FQDN, but found out that it is only hosts defined with 'name'. I guess we will have to come up with another idea or wait and see if it is going to be implemented some time.
Doesn't the crypto maps also (help to) determine where the traffic must be sent (which will be the peer)? I guess my question is if this conflics with a route in the routing table, which one takes preference?
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...