- Written by
admin
- Posted June 28, 2008 at 12:07 am
This article is next part of recent article
3.Activate daemon
After make zebra configuration. conf and routing protocol (example ospfd. conf), daemon routing protocol necessary activate by:
Router# /etc/init.d/quagga start
And also for restart and stop
Router# /etc/init.d/quagga stop
Router# /etc/init.d/quagga restart
This matter necessary has been done when we have replaced configuration from quagga.
Router# /etc/init.d/quagga restart
Stopping Quagga daemons (prio:0): ospfd zebra (bgpd) (ripd)
(ripngd) (ospf6d).
Removing all routes made by zebra.
Nothing to flush.
Loading capability module if not yet done.
Starting Quagga daemons (prio:10): zebra ospfd.
4.Login to application routing protocol
To login to routing protocol, we can use application TELNET, while to detect port from application routing protocol can be done with command netstat -nlptu
For see zebra port and another routing daemon
Router# netstat -nlptu | grep zebra
tcp 0 0 127.0.0.1:2601 0.0.0.0:*
LISTEN 7567/zebra
Router# netstat -nlptu | grep ospfd
tcp 0 0 127.0.0.1:2604 0.0.0.0:*
LISTEN 7571/ospfd
For zebra uses port 2601 and to ospfd 2604, mean us accessible to application pass ports
Router# telnet localhost 2601
Trying 127.0.0.1…
..
..
Password:
Or to application ospfd in port 2604
Router# telnet localhost 2604
Trying 127.0.0.1…
..
..
Password:
To logging us use password initially “zebra” (without pick two, as according to configuration). so that appear
Router> or ospfd>
Be prompt beginning in quagga. so also when use ripd or another.
5.Do network distribution in pc router
Do network distribution, will mean router (in this case pc) mutual will ask and swap information about network member.
With topology condition on, when do we reside in network a, we only can detect that us has 2 networks 10.252.108.0/24 with 192.168.1.0/24. For certain that us not yet sure know network that present to turned routerb. So also on the contrary.
So that network a can contact network b, in routera must be added table routing that aim to network b. by order of
RouterA# ip route add 192.168.2.0/24 via 10.252.108.15
That can be done when we detect ip network be be turned router b, and when network total that aimed only 1, how when aimed there 1000 router? ? ? ?
So that in quagga we can do distributing by:
-Logging to application routing protocol (example: ospfd with port 2604) with password “zebra”
Router# telnet localhost 2604
Trying 127.0.0.1…
Connected to localhost.localdomain.
Escape character is ‘^]’.
Hello, this is Quagga (version 0.98.3).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
User Access Verification
Password:
ospfd>
-Rise to next privillages by order of “enable”
ospfd> en
-Enter to configuration mode by order of “configure minal”
ospfd# conf t
-Activate type routing
ospfd(config)# router ospf
-Distribute network that has by router
ospfd(config-router)# network 10.252.108.0/24 area 0
ospfd(config-router)# network 192.168.1.0/24 area 0
-Save configuration by order of
CtrlZ
ospfd# wr
IP FORWARDING
Pc router must activate ip forwarding pass terminal by:
Router# echo 1 > /proc/sys/net/ipv4/ip_forward
Or by activate to pass zebra, with password “zebra”
-telnet to port 2601
Router# telnet localhost 2601
Trying 127.0.0.1…
..
..
Password:
-Do “enable” with password “zebra”
Router> en
Password:
-Step into configuration mode by order of “configure minal”
Router# conf t
-Activate ip forwarding
Router(config)# ip forwarding
-Save with return to fashion enable with depress ctrlz, then do command “write memory”
Router(config)#
Router# wr
Configuration saved to /etc/quagga/zebra.conf
Reference:Quagga
