Yahoo Messenger

I'm installing a firewall, and discover that users need to treat Yahoo Messenger differently for a specified group. Therefore I need to know which ports are being used by YM.

Here are list of the ports:

- Messages: 5050, 80, 23 and any port

- Voice: 5000 and 5001

- Webcam: 5100

MPLS VPN

MPLS VPN is a solution to solve duplicate customer address range in the provider routing table. By having this solution, a service provider will be able to provide a connectivity for several customers which are connected each other with privete IP(s).

Data plane on this solution is a bit different with MPLS unicast. The PE (provider edge) has another table called VRF (Virtual Routing and Forwarding). The PE also add two labels (instead of one label) into the header. The outer label is being used to deliver the packet to the next router, while the inner label is being used to identify which VRF is related to the packet.

One of the challange to implement VPN is overlapping IP address. This problem is solved by using RD (route distinguisher) by taking advantage of MP-BGP. The RD will add 64-bit RD to the 32-bit IP-v4  prefix. Then MPLS will your RT (route target) to decide which packet is correlated to which VRF.

MPLS Unicast IP

MPLS is a protocol that forward packet based on Label instead of IP address. There are several MPLS application, and one of them is MPLS Unicast IP. A router with MPLS Unicast IP is actually forwarding a packet to the same path as a router with IP routing. The difference is only that the MPLS router forwards the packet based on Label. Then why it is important to know what MPLS Unicast IP is? It is important since many of the application is using MPLS unicast IP forwarding as part of the MPLS network.

MPLS has something called Control Plane and Data Plane. The Data Plane are the data structured used by the MPLS in operation.  FIB, LFIB, LIB are the tables that we are talking about. FIB contains information to map IP address and network interface of where a packet destined to an IP address will be forwarded. LFIB contains information to map label and network interface of where a packet with a label will be forwarded. And the LIB is actualy a library of LFIB, which map all labels and ports including the ones which are not currently being used to forward packet. LIB contains only the best map, so that there is only network interface mapped to a label on it. 

Now, how the LIB feeds the LFIB and FIB? 

In simple words, the MPLS routers distribute routing information using EIGRP, OSPF or other routing procotol. From this protocol, the MPLS router will know where is the best route to delivere a packet. The router will pick up the best route, find the related label on the LIB and then update the LFIB.

How-To Change Time Zone in Linux

I was looking for how-to change time-zone in my linux box.

Fortunately, I found the website below:

http://www.wikihow.com/Change-the-Timezone-in-Linux

Steps

1. Logged in as root, check which timezone your machine is currently using by executing `date`. You'll see something like Mon 17 Jan 2005 12:15:08 PM PST, PST in this case is the current timezone.
2. Change to the directory /usr/share/zoneinfo here you will find a list of time zone regions. Choose the most appropriate region, if you live in Canada or the US this directory is the "America" directory.
3. If you wish, backup the previous timezone configuration by copying it to a different location. Such as

   mv /etc/localtime  /etc/localtime-old 

4. Create a symbolic link from the appropiate timezone to /etc/localtime. Example:

   ln -sf /usr/share/zoneinfo/Europe/Amsterdam /etc/localtime 

5. If you have the utility rdate, update the current system time by executing

   /usr/bin/rdate -s time-a.nist.gov 

6. Set the ZONE entry in the file /etc/sysconfig/clock file (e.g. "America/Los_Angeles")
7. Set the hardware clock by executing:

   /sbin/hwclock --systohc

Line is up, Protocol is Down

I've got several questions from some friends of what it means by the status when it shows "Line is up, Protocol is Down". From google, I found two websites explaining about the meaning of the statis, i,e:

• Troubleshooting Line Protocol is Down, from Cisco
  
• Cisco Show Interface
  

Basically, this status will be appear when one of the conditions below met:

• Local or remote router misconfigured
  
• Keep-alives not being sent by remote router
  
• Leased-line or other carrier service problems, such as noisy lines or faulty switch
  
• Timing problem on cable, possibly caused by the CSU/DSU not being set correctly.
  
• Failed local or remote CSU/DSU.
  
• Router failure.
  

Install Exim with DKIM and Domainkeys on DirectAdmin

Installing Exim on DirectAdmin makes my day today. I have to dig several sites in order to finish the installation. I think It will be better to document it here. I may need it again in the future, or perhaps you may need this when you need to compile Exim with DKIM and domainkeys on Centos.

First, compile and install the DKIM:

wget http://duncanthrax.net/exim-experimental/libdkim-1.0.16-tk.tar.gz

tar zxvf libdkim-1.0.16-tk.tar.gz

cd libdkim-1.0.16-tk

cd src

make

make install

cd ..

cp lib/libdkim.a /usr/lib

cp include/dkim.h /usr/include/

Compline and Install Domainkeys:

tar zxvf libdomainkeys-0.69.tar.gz

cd libdomainkeys-0.69

make

echo -lresolv > dns.lib

make

make install

cp *.h /usr/local/include/

cp *.a /usr/local/lib

Download Exim:

wget http://files.directadmin.com/services/all/exim/exim-4.69.tar.gz

tar xvzf exim-4.69.tar.gz

cd exim-4.69/Local

wget http://www.directadmin.com/Makefile

perl -pi -e 's/^EXTRALIBS/#EXTRALIBS/' Makefile

Edit the Makefile:

EXPERIMENTAL_DKIM=yes

CFLAGS  += -I/usr/include

LDFLAGS += -ldkim -lssl -lstdc++ -L/usr/lib

EXPERIMENTAL_DOMAINKEYS=yes

CFLAGS  += -I/usr/local/include

LDFLAGS += -ldomainkeys -L/usr/local/lib

#added April 9, 2008

HAVE_ICONV=yes

CFLAGS=-O -I/usr/local/include

EXTRALIBS_EXIM=-L/usr/local/lib -liconv

#end add

Compile and Install it:

cd ..

make

make install

Last job, you need to rename the compiled exim and restart:

cp -f /usr/sbin/exim-4.69-12 /usr/sbin/exim

/sbin/service restart exim

That's it, you have exim with domainkeys on DirectAdmin now.

How to determine the root port

The root port will be determined based on the algorithm below.
1. Lowest port cost
2. Lowest value of the forwarding switch's ID
3. Lowest port priority
4. Lowest internal port number