Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Stunnel, netcat, socat, but they are more useful for specific ports, I don't think any have an option for using tap/tun. Ssh can do either, portforwarding or using tap/tun interfaces. I have to admit I'm really curious why any of the other ones wouldn't work for you. If its a matter of a protocol inspecting firewall between the two then I'd go with ssh over https.
ssh can setup a vpn using the tap/tun interface with the -w option and the Tunnel config option. I usually set the Tunnel config option to ethernet so it creates a tap interface which is the equivalent of a normal ethernet interface. Then you just ssh -w any user@remote_machine (might want to add -f -N -n)
It results in a pair of interfaces, one on each machine that are connected to one another like the two machines were on the same lan. If you use the tap interface option then just set up your ips and routes or bridge the interface.