Showing posts from December, 2011

OSPF Simulation using Quagga

There's a newer version of this article available in my blog.

IP DetailsAll the Routers in the diagram are actually Debian Machines.

Router Alpha:
Router Beta:
eth0: eth1: eth2: Router Gamma:
eth0: eth1: ObjectiveWe would be configuring the Linux boxes with dynamic routing protocol OSPF for total connectivity. This would be done with the help of Quagga.

Router Alpha Configurationroot@alpha:~# apt-get install quagga

First, we have to enable the routing protocols needed.
root@alpha:~# cd /etc/quagga/
root@alpha:~# vim daemons
zebra=yes bgpd=no ospfd=yes ospf6d=no ripd=no ripngd=no isisd=no

Next, we would be configuring the interface parameters. Keep in mind, there are example configuration files stored in /usr/share/doc/quagga/examples.
root@alpha:/etc/quagga# vim zebra.conf
hostname AplhaRouter password zebra enable password zebra ! ! Interface's description. ! interface lo…

RSYNC with Different Port

If SSH is not listening to the default port 22, then naturally we can not use RSYNC without specifying the SSH port. For example, if SSH is listening to port 4321, RSYNC can be used like this -

# rsync -av -e "ssh -p 4321"   source_file   user@IP:/destination

Hope it helps.

Backing up with RSYNC

SSH Login Without Passwords (Alternate SSH Port)

Many people don't use the default SSH port 22 for security purposes. In such case, when sharing the public key with a remote host, the following command can be used -

SSH login without passwords

SSH Private-Public Key Pair Login Everyone would agree with the fact that SSH is the most widely used remote access protocol used in Linux based operating systems. The primary reason behind the popularity of SSH is, it utilizes one way encryption, supports many encryption algorithms as well as pre-shared keys for authentication.
There are a couple of remote file sharing software that rely on SSH for protection like SCP, SFTP, RSYNC. Among them, RSYNC is really popular for taking backups. But because RSYNC to a remote host relies on SSH, and SSH prompts for a password, automating the backup process cannot be done with default settings. Here is where private-public key pair kicks in to save the day. With the help of the key pair, it is possible to utilize SSH to a remote host without using passwords.
The methodology is pretty simple. HostA generates a private and public key pair.While generating the pair, no passphrases are used because the objective is to enable SSH without passwords.…

Adding Persistent Static Routes in Debian

Stumbled upon this just a while ago...

Adding a static Route in Debian can be easily done by using the command

route add -net netmask gw dev eth1
Here, the network is accessible through next hop exit interface eth1. However, the problem is that the system forgets the route if the network service restarts. Here's how the route can be made permanent -

# The primary network interface
auto eth1
allow-hotplug eth1
iface eth1 inet static

up route add -net netmask gw dev eth1
up route add -net netmask gw dev eth1

down route del -net netmask gw dev eth1
down route del -net netmask gw dev eth1

The route is would now be updated every time the network service is restarted. Works like a charm :)