Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 1717 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSH Tunneling, SSH and Up2Date 4.009

nicklassa
I noticed an immediate change in the ability to tunnel the TCP/3389 protocol via SSH after applying the latest update to ASL.  I am using SecureCRT.  Typically I connect to ASL using SecureCRT (SSH2), automaticaly login as loginuser, and then I pull up the MS Remote Desktop Console, connect to the loopback address of the PC I am using.  Then, I get the login prompt for the Windows box and I am on my way.  This no longer works.  Nothing has changed in the application's configuration.  

Also, I lost the ability to outbound SSH to a Cisco router (SSH 1.5) which is connected via a virtual interface connection on the external interface of the firewall.  I was able to do this before in the previous release of ASL.

Any ideas?

Thanks  


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to techno.kid
    Hey thanks, yeah I saw drops.  I found that explicit rules are now  required in 4.009 to allow the firewall to SSH outbound.  I also had to add an explicit rule to allow the internal firewall interface to communicate with my Teminal Services server when attempting to tunnel RDP through an SSH connection from an external network.  I guess this is a good thing; its more secure.