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.
I have a linux (ubuntu) router, it is setup and works great as a basic router. I'm wanting to setup a VPN back to my work and forward the following traffic through it:
Everything directed at the 10.0.0.0/16 network
All traffic from 192.168.200.125
I have gotten all the 10.0.0.0/16 traffic to work like I want with the following:
But I have no idea how to get all the traffic from 192.168.200.125 to pass through VPN instead of the WAN... I just have no idea where to start. The REDIRECT in iptables looks interesting, but I'm thinking thats only for ports
You can use the magic of iproute2 to create a separate routing table to handle that.
ip ro add 10.0.0.0/16 dev ppp0 table 4
ip ro add 192.168.200.125 dev eth1 table 4
ip ro add default dev ppp0 table 4
ip ru add from 192.168.200.125 lookup 4
ip ru add from 10.0.0.0/16 to 192.168.200.125 lookup 4
ip ro fl cache