Solved

ssh through vpn on asa5505

Posted on 2011-09-14
11
1,060 Views
Last Modified: 2012-05-12
I have an asa5505 configured to allow ssh from select hosts on the internet to specific hosts on the LAN. That works well. The firewall is also configured to allow client based VPN connections, and that works well, also. The appliance is also configured to allow ssh connections to itself from inside. It works.

I can't figure it out how to allow ssh connections to the appliance from the VPN clients.

To summarize:
LAN: 192.168.2.0
VPN pool: 192.168.30.1 - 192.168.30.10
port 22 on the outside interface is mapped to a (*nix) host on the LAN
on ASA, I have: ssh 192.168.2.0 255.255.255.0 inside

I can successfully ssh from the internal (*nix) host to ASA
I can successfully ssh from outside through ASA to the internal (*nix) host
I can successfully establish a VPN connection to the ASA

Keeping all the above in place, I want to be able to ssh into ASA from a specific host outside, through the VPN or not (doesn't matter). In other words, my only way to ssh into the appliance at the moment from outside is to ssh first into the internal host and from there back to ASA. I'm worried that if the internal host is unavailable I'm cut out from the appliance.

tx,
0
Comment
Question by:sgiurgeu
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 4
11 Comments
 
LVL 35

Expert Comment

by:Ernie Beek
ID: 36536327
Do you have something like: ssh source_IP_address mask source_interface in the config (shoulde be atleast one). The second should have source_IP_address mask as the address where you're coming from on the outside (the VPN ip) and source_interface should be the outside interface.
0
 
LVL 35

Expert Comment

by:Ernie Beek
ID: 36536339
So something like: ssh 192.168.30.0 255.255.255.240 outside
0
 

Author Comment

by:sgiurgeu
ID: 36536343
in my posting, i mentioned that i have:

ssh 192.168.2.0 255.255.255.0 inside

I cannot add a similar statement for the outside interface since port 22 is mapped to an internal host. This is also document in my original posting.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 35

Expert Comment

by:Ernie Beek
ID: 36536358
Reading too fast :-~

So port 22 is mapped using the public address on the outside interface and you only have one public ip?
0
 

Author Comment

by:sgiurgeu
ID: 36536384
that is correct.

i guess my only way around this would be to map an arbitrary port, say 2222 from outside. Would that work?
0
 
LVL 35

Expert Comment

by:Ernie Beek
ID: 36536402
That could be an option.

I'm trying to remember something. If you are connected through the vpn and then try to ssh to the inside ip of the ASA, does that work?
0
 
LVL 35

Expert Comment

by:Ernie Beek
ID: 36536409
You might want to add: ssh 192.168.30.0 255.255.255.240 inside though.
0
 

Author Comment

by:sgiurgeu
ID: 36536518
I've already tried that (ssh-ing through vpn). adding ssh 192.168.30.0 255.255.255.240 inside doesn't work (I tried it) for the obvious reason that the vpn clients are considered (by asa) as belonging to the outside interface.
0
 
LVL 35

Accepted Solution

by:
Ernie Beek earned 500 total points
ID: 36536569
I know, it isn't very logical but that should work normally (ssh through the vpn to the inside interface).

Do you have management-access inside somewhere in your config? If not, try adding that.
0
 

Author Comment

by:sgiurgeu
ID: 36536700
That worked!!

I put:

asa(config)# ssh 192.168.30.0 255.255.255.0 inside
asa(config)# management-access inside

and now i can shh into the appliance after establishing the vpn connection.

Case closed. Thank you for your help.
0
 
LVL 35

Expert Comment

by:Ernie Beek
ID: 36536712
You're welcome :) Glad I could help.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This past year has been one of great growth and performance for OnPage. We have added many features and integrations to the product, making 2016 an awesome year. We see these steps forward as the basis for future growth.
Many of the companies I’ve worked with have embraced cloud solutions due to their desire to “get out of the datacenter business.” The ability to achieve better security and availability, and the speed with which they are able to deploy, is far grea…
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…
Both in life and business – not all partnerships are created equal. Spend 30 short minutes with us to learn:   • Key questions to ask when considering a partnership to accelerate your business into the cloud • Pitfalls and mistakes other partners…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question