ASA SSL clientless VPN

I have an outside interface IP address on the ASA with a 255.255.255.248 subnet allowing 6 IP addresses. I have setup clientless SSl vpn enabled on the outside interface and when i try to access it to the IP address within the subnet that is actually configured on the outside interface it works fine.
However if i try and set it up so the tunnel-group group-url points to one of the other IP's in the subnet it won't work.
Can anyone confirm whether it only works on the actual configured IP or should i be able to connect on any of the IPs in the subnet.

ie if IP was as shown below the address 1.1.1.1 would work but 1.1.1.2 - 1.1.1.6 would not.

 interface GigabitEthernet0/1
 nameif outside
 security-level 0
 ip address 1.1.1.1 255.255.255.248
nappyshockAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Erik BjersPrincipal Systems AdministratorCommented:
You will need to connect to the actual interface IP on the ASA for the VPN to work.  

If you want to use an IP other than the one you have assigned to the physical interface you will need to create a sub-interface and assign a different public IP to it (ability to do this depends on the ASA and license you have).  For more information see http://www.cisco-tips.com/tag/asa-subinterfaces/

However there is really no need to use a different IP for your VPN so I would suggest using the one you have assigned to the public interface.

eb
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nappyshockAuthor Commented:
Thanks for quick response.
0
nappyshockAuthor Commented:
Thanks ebjers for the quick response!
I reason i was going to put the clientless SSL VPN on a seperate IP was because port 80/443 on the actual interface IP is being used by the SSL anyconnect client.
I suppose i could use a different port for the clientless SSL VPN.
0
Erik BjersPrincipal Systems AdministratorCommented:
in that case if your license allows it create a sub-interface
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.