[cisco-voip] uc500 ssh help

Syed Khalid Ali syed.khalid.khursheed at gmail.com
Sun Oct 18 12:09:37 EDT 2009


Andrew,
I don't know a lot about PIX 6.x releases. But with 7.x or higher you can do
this really easy.

static (inside,outside) tcp <public-ip-address> telnet <private-ip-address>
telnet netmask 255.255.255.255

You can also refer to an public IP address interface instead of an static IP
address with interface keyword. Refer to command reference:
http://www.cisco.com/en/US/docs/security/asa/asa70/command/reference/s.html#wp1540284

I also find a document on Cisco Website. It might be helpful
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a00804708b4.shtml#t10

Another resource at:
http://www.tech-recipes.com/rx/711/port-redirect-to-inside-host-on-a-cisco-pix-firewall/


I hope this helps!

Regards,
Khalid

On Sun, Oct 18, 2009 at 7:28 PM, Andrew Waddle <anacomm at gmail.com> wrote:

> Hello everyone!
>  I have a pix 501 at the front of my network at home, with my uc500
> directly behind it, I use port 22 to ssh into my pix from the outside, but I
> also what to ssh into my uc500 that's behind my pix, I only have one public
> IP address so i think i need to use some form of port forwarding or
> redirection of some sort. my thoughts were to redirect port 2222 from my pix
> to the outside interface of my uc500, that way whenever I try to ssh using
> port 2222 my pix will redirect that port to the uc500...
>
> another question is once port 2222 is redirect to the uc500, i need some
> way of the uc500 knowing that port 2222 should be used for an ssh connection
>
> any help would be greatly appreciated
>
> --
> Andrew Waddle
> Anacomm at Gmail.com
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091018/3a8b3426/attachment.html>


More information about the cisco-voip mailing list