Skip to main content

Linux Advanced Routing And Traffic Control (LARTC)

Introduction

Networking in Linux is one of essential part for the success of this operating system. The flexibility and robustness are the key point for the success. However, the user-friendliness, at the very early stage, was not good which resembles the old Unix. Nowadays, many modern Linux distros come with good interface on setting up many aspects of networking stuff and many things can be configured automatically when the hardwares detected.

Many organizations need to have an advanced routing for their network infrastructure. Basic network infra cannot cope with certain conditions. This is when the advanced routing comes into play. In Linux, we have iproute2 package to work hand-in-hand with iptables and recent kernel for advanced routing. This topic is thoroughly covered on LARTC home page at http://www.lartc.org. My article here just covers basic things.

Make it work

Let's take a look at this scenario :

Scenario 1

We want to route packets that come from local network(s) to two different or two same ISPs. Say the two ISPs are tm1 and tm2 with the associated IP respectively (see above diagram --deleted. Will update soon! - 16/11/2005).

Our work is in the router box. Login as root and set two tables:

echo 1 tm1 >> /etc/iproute2/rt_tables echo 2 tm2 >> /etc/iproute2/rt_tables

These commands will put 2 new table entries in file rt_tables. The content of the file after previous commands :

255 local
254 main
253 default
0 unspec
1 tm1
2 tm2

Now we have 3 routing tables :
main
tm1
tm2

The next step is to populate the routing rules to the tables:

tm1 table

~# ip route add default via 10.1.1.1 dev eth1 table tm1
~#ip rule add from 192.168.0.0/24 table tm1

**Explaination
The packets that come from 192.168.0.0/24 will go to tm1 routing table and then will be passed to the tm1 gateway (default route) which is 10.1.1.1 on device eth1

tm2 table

~#ip route add default via 10.8.8.1 dev eth2 table tm2
~#ip rule add from 192.168.1.0/24 table tm2

**Explaination
The packets that come from 192.168.1.0/24 will go to tm2 routing table and then will be passed to the tm2 gateway (default route) which is 10.8.8.1 on device eth2

To see the routing tables after previous commands :

To see tm1 table:

~#ip route show table tm1

To see tm2 table:

~#ip route show table tm2

To see main table:

~#ip route show table main

Please note that this kind of routing can't be done without iproute2 package.Please make sure that this package is installed first with your distro utility.On Mandrake, this can be done with urmpi as simple as urpmi -v iproute2.


let say that you want to route packets based on their destination ports. You can do this with the help of iptables. To mark the packets that have the 22 and 80 as destination port, we will use the mangle table as below :

~#iptables -t mangle -A PREROUTING -i eth0 -p tcp --dport 80 -j MARK --set-mark 1
~#iptables -t mangle -A PREROUTING -i eth0 -p tcp --dport 22 -j MARK --set-mark 2

Let say you want to separate their route based on the destination port:

All packets with destination port 80 will go out via table tm1

~#ip route add default via 10.1.1.1 dev eth1 table tm1
~#ip rule add from all fwmark 1 table tm1


All packets with destination port 22 will go out via table tm2

~#ip route add default via 10.8.8.1 dev eth2 table tm2
~#ip rule add from all fwmark 2 table tm2

All packets with destination port 22 will go out via table tm2

Happy experimenting!

Comments

Popular posts from this blog

mplayer-gui error : Error in skin config file

After installing mplayer-gui package, I can't start it.

$ gmplayer MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Error in skin config file on line 6: PNG read error in /usr/share/mplayer/skins/default/main Config file processing error with skin 'default'
After googling a bit, I found out that it was due to the png files in dir /usr/share/mplayer/skins/default. This is the default skin directory. To fix this error, I have to install ImageMagick package because I want to use the convert program to convert all of the png files to format png24. Thus, cd /usr/share/mplayer/skins/default; for FILE in *.png ; do sudo convert $FILE -define png:format=png24 $FILE ; done
Rerun gmplayer and all should be fine.
Have fun!
UPDATE (02-10-2017)

It doesn't work on Ubuntu 16.04 (xenial) but there's a workaround here.

You can update your syst…

Moving your mysql database to another hard disk

Recently, my server's only hard disk was almost full. I bought a new hard disk with bigger size and I decided to just add it as a second hard disk. Since I need to move it to the 2nd hard disk, I need to find a proper way to move the db with minimum downtime. So I googled around and found a solution.
First, I needed to format the 2nd hard disk and I chose xfs as the filesystem. I created 2 partitions using Linux's fdisk for this task. First partition is 10 GB and 2nd one is around 900 GB. That's approximately added up to 1 TB. Then I mounted the 2nd partition in current partition eg /media/hd2 as follows:
mount -t xfs /dev/sdb5 /media/hd2
where /dev/sdb5 is the partition and /media/hd2 is the mounting dir.
Stop mysql db before doing anything:
service mysql stop
Afterthat, I copied the entire db to newly mounted hard disk:
cp -rv /var/lib/mysql /media/hd2
It will take a while if you have huge databases.
Then, change the ownership of the dir to user and group of mysql:
chown -R mysql:…

Transparent proxy with squid 2.6

I have upgraded my squid from 2.5 STABLE13 to 2.6 STABLE18. Transparent proxy is setup differently in this version. You need this directives in squid.conf (usually in /etc or /usr/local/etc or /usr/local/squid/etc, check with your distro).

acl our_networks src 192.168.2.0/24 127.0.0.1
http_access allow our_networks
http_port 192.168.2.1:3128 transparent
always_direct allow all

where 192.168.2.1 is your proxy server IP address.


If you have flushed your iptables, create new rule:

iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

where 3128 is the port where squid is running.
References:
http://www.deckle.co.za/squid-users-guide/Transparent_Caching/Proxy