Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
You can use the 'route add src_range gw' command to direct your traffic from src subnet to a gateway. check the man pages of route command for the correct syntax. But I don't think you can do the actual NATing with route. Is what you are intending to do?
Iptables also work in the kernel space itself, its just the interface works on the userspace. So I don't think you can get any performance advantage by using route.
Because iptables is a software, route happens on the kernel level thus it's better.
Incorrect on so many levels. Shoe horning a software into doing something it wasn't really intended to do regardless of if it occurs natively in the kernel or through a module is less desirable even when possible. Both route and iptables have userspace interfaces... nee: /sbin/route & /sbin/iptables.