Unable to Port Forward SSH in NAT Network

Discussions related to using VirtualBox on Windows hosts.
Post Reply
naisanza
Posts: 9
Joined: 1. Jan 2011, 06:50
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: FreeBSD, Arch, BackTrack, WeakNet, CentOS

Unable to Port Forward SSH in NAT Network

Post by naisanza »

This was probably three versions of VirtualBox ago, but I just wanted to bring this to the attention of anyone running an SSH jumpbox or proxy and using the NAT Network feature.

Port forwarding to the SSH VM "works," but you end up getting disconnections or connection drops.

I tested this in this scenario
+ All authentication is using PKI
+ NAT Network port forward 222 => SSH-vm:22
+ Client => SSH-a => SSH-b => SSH-vm
+ SSH-a flags: -L 22:SSH-b:222
+ SSH-b flags: -L 222:localhost:222

I did this about three months ago, so details on the errors and messages are fuzzy, but essentially it didn't work, and I reverted it to Bridged Network.

I'll try to recall some errors I would see

Code: Select all

Unable to create pseudo-term pty-0
The errors were somewhere along those lines. I believe you had a full shell that you could navigate, but if you tried to drop it into the background with '-N', for say as a SOCKS5 proxy it wouldn't work.

That's all I wanted to say, in-case anyone else is thinking about trying something like this with their setup.
Post Reply