If I implement the md5 on the outside interface, does it set the authentication on all interfaces, or do I need to set each seperately?
MD5 Authentication is per interface, whichever ASA interface is OSPF peering with is where you apply MD5, if your inside interface runs ospf process and peers with an inside router, the MD5 authentication is set in the INSIDE interface
Can I globally set the MD5 authentication on all interfaces at the same time?
As far as I know this cannot be setup globally but per interfaces. Technically you can set the MD5 authetication in all other interfaces on the ASA even if there is no OSPF peering on other interfaces but this will provide another layer of security in preventing unautorized devices from peering to your ASA ospf routing.
you will have routing hiccup when implementing message digest MD5 authenticaion, when you enter this config in ASA ospf will lose peering thus your dynamic routing is disrupted until you enter MD5 authetication config in router peering with ASA , then ospf adjecency will form again, best to do your implementation during non production hours.. this is simple implementation but still have to be carefull.
Richard, yes you could do static routes which will take precedance, did not think of it, as long the inside source is reachable through inside router. When doing static you can always confirm in router by doing show ip route and see the route installed in routing table as (S), the same in ASA.
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...