09-18-2012 08:52 AM
Here is the setup:
Outside Interface : 50.50.50.5
Inside Interface: 192.168.1.5
Wireless Interface: 192.168.2.5
The wireless interface is used for guest access to the internet and it cannot get to any internal servers or workstations. For offiste employees we are using Cisco VPN to remote in through the firewall.
Now here is the question, a traveling person comes into the office, connects to the wireless network (no LAN ports available) and then wants to VPN in to do work. Can that be allowed through ACL's to allow traffic like that or would we be looking at using Cisco AnyConnect? I would not want to enable "globally" the ability for the Wireless range to speak to the Inside interface, but only allow VPN access. At first blush I would imagine the ASA to not allow this, but trying to get some clarification, thanks!
And if it can be done, I can see security implications so I am also looking for best practice info as well.
Solved! Go to Solution.
09-18-2012 10:12 AM
Hello Mrjwilson,
5 stars to you
Thank you for sharing the solution, now please mark the question as answered so future users can learn from your problem.
09-18-2012 09:51 AM
Ok, so what we did is enable IPSEC (IKEv1) connection profiles on both the wireless interface and the outside interface. That seems to have taken care of the vpn needs.
If anyone out there still sees an issue with best practice, let me know.
09-18-2012 10:12 AM
Hello Mrjwilson,
5 stars to you
Thank you for sharing the solution, now please mark the question as answered so future users can learn from your problem.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide