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.
There are a couple ways to do it. If the interfaces are relatively equal in terms of bandwidth, I would recommend using the teql0 qdisc like so:
tc qdisc add dev eth0 root teql0
tc qdisc add dev eth1 root teql0
Then, configure your [public] interfaces. Give teql0 a dummy IP. You don't necessarily have to do the first two commands if your IP addresses [and routes] are already assigned, such as by your PPP client for DSL or DHCP client for cable.
ip addr add dev eth0 220.127.116.11/24
ip addr add dev eth1 18.104.22.168/24
ip addr add dev teql0 10.1.1.1
Finally, set the default route via the teql interface.
ip route add default via 10.1.1.1 dev teql0
Finally, you'll need to turn off an option that controls whether Linux will watch the return path of a packet. Substitute your interface names into these commands:
If you're more interested in doing it with routing tables only, you'll need to have multipath routing enabled in the kernel. If you're using a stock kernel from your distro, you most likely have it. Bring up both interfaces using whatever commands you may use to do so. Once that is done, run:
ip route add default equalize
I personally have not tested it this way, but I have read that this is what works. Feel free to give it a try and let me know how it turns out.