Hi,
I have a small box with linux on it as VPN box. This box is headless. So it will be accessed from another computer in the lan. But this box will be used to access the company systems. So the question is, what would be the best solution?
x2go to the box and x2go from there to the systems?
Install a proxy or the like (do not know if this exists) on the box and connect from 1 x2go client routed via the box? Is probably an ssh forward enough?
Thanks and cheers, Matt
Hi,
sry for this dumb question but I am kind of confused. Would be happy if someone would bring me back on track ;-)
Cheers, Matt
Am 09.01.2014 16:22, schrieb Buddy Butterfly:
Hi,
I have a small box with linux on it as VPN box. This box is headless. So it will be accessed from another computer in the lan. But this box will be used to access the company systems. So the question is, what would be the best solution?
x2go to the box and x2go from there to the systems?
Install a proxy or the like (do not know if this exists) on the box and connect from 1 x2go client routed via the box? Is probably an ssh forward enough?
Thanks and cheers, Matt
Am 12.01.2014 18:57, schrieb Buddy Butterfly:
[multi-hop SSH/X2Go]
Is probably an ssh forward enough?
SSH forwarding does the trick.
So, instead of
ssh -p externalsshport externaluser@externalip.or.domain.name
simply do
ssh -L2222:internal.ip.or.name.of.x2gohost:22 -p externalsshport
externaluser@externalip.or.domain.name
Then connect your X2goclient to internaluser@localhost:2222.
If you already use 2222 for something else, change it to anything available in both the ssh and the x2go call.
If you're using any other port than 22 for your internal connection to your x2gohost, change the 22 in the ssh call.
Of course, you could also consider something more elaborate like routing, firewalling and portforwarding, or a VPN connection.
-Stefan
-
Buddy Butterfly -
Stefan Baur