Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
So, I've set up Anyconnect client access to an ASA-5510.I've got a handful of interfaces, which contain hosts that should be accesible to anyconnect clients. I'm unable to reach addresses on a specific network, due to what packet-tracer claims is an...
Greetings, I'm configuring up aa ASA-5510, and I have several interfaces, some of which include:interface Ethernet0/0.200 vlan 200 nameif SITECORP security-level 90 ip address 10.1.4.1 255.255.254.0 !interface Ethernet0/0.207 vlan 207 nameif SI...
Ok, so the problem was accessing 10.1.24.10 (nameif SECURE) from 10.1.6.* (Anyconnect client coming inbound from nameif INTERNET).Your suggestion, while not applicable to the right named interface, definitely put me on the right track.I configured a ...
Alright, I've got authorization to share the config. Pleaes find it below. Thanks so much for your assistance.Regards, --philfw1# show run: Saved:ASA Version 8.0(3)6 !hostname fw1enable password REDACTED encryptedpasswd REDACTED encryptednamesname...
It's no problem for me to share smaller pieces of the configuration, but to post the whole thing, I'll need to get some approval.In the mean time, is there anything else I might look for, or any smaller parts of the configuration that might help?Rega...
Thanks, Julio.I did implement the same-security-traffic permit inter-interface, and it absolutely worked. The ASA has a dozen other vlan interfaces, and it made sense to re-visit the security-level.You've certainly thoroughly answered the question, ...
Julio, Thanks for the reply. So traffic between interfaces with the same security-level is not treated the same as traffic to an interface with a higher security-level? I.e., an access-policy permitting the traffic will be insufficient?In any case...
