quaqqa is one of the routing software support dynamic protocol like OSPF,RIP and BGP. quaqqa is fork of GNU zebra. in fact name of zebra more familiar than quagga, but quagga more powerfull,both of name take from name of animals…it seem great. (about guagga).
1. QUAGGA DAEMONS:
You have to activate the Quagga daemons matching the routing protocols you want to set on your router.
zebra:
bgpd:
ospfd:
ospf6d:
ripd:
ripngd: Interface declaration and static routing
BGP routing protocol
OSPF routing protocol
OSPF IPv6 routing protocol
RIP v2 routing protocol
RIP Ipv6 routing protocol
In the example below, the zebra and IPv4 OSPF daemon have been activated.
#vim /etc/quagga/daemons
zebra=yes
bgpd=no
ospfd=yes
ospf6d=no
ripd=no
ripngd=no
Restart the Quagga service:
#/etc/init.d/quagga restart
Stopping Quagga daemons (prio:0): ospfd zebra (bgpd) (ripd) (ripngd) (ospf6d) (isisd).
Removing all routes made by zebra.
Nothing to flush.
Loading capability module if not yet done.
Starting Quagga daemons (prio:10): zebra ospfd.
You can check the Quagga daemons status:
#ps -ef | grep quagga
UID PID PPID C STIME TTY TIME CMD
quagga 4632 1 0 22:25 ? 00:00:00 /usr/lib/quagga/ospfd --daemon
quagga 4636 1 0 22:25 ? 00:00:00 /usr/lib/quagga/zebra --daemon
If a Quagga daemon doesn't stop properly, you can kill it manually and start the quagga service:
#kill -9 "UID number"
#/etc/init.d/quagga start
2. CONFIGURATION FILES: (/etc/quagga/*.conf files)
You must create a configuration file (even if it is empty) each time you activate a Quagga daemon.
Each daemon is associated with a specific file name:
zebra:
bgpd:
ospfd:
ospf6d:
ripd:
ripngd: zebra.conf
bgpd.conf
ospfd.conf
ospf6d.conf
ripd.conf
ripngd.conf
To create the config files, copy the sample config files as follows:
In our example, as we activated the zebra and ospfd daemons; we need to create the zebra.conf and ospfd.conf files.
#cp /usr/share/doc/quagga/examples/zebra.conf.sample /etc/quagga/zebra.conf
#cp /usr/share/doc/quagga/examples/ospfd.conf.sample /etc/quagga/ospfd.conf
Another way to do it is to create two empty files called /etc/quagga/ospfd.conf and /etc/quagga/zebra.conf. But in this case you cannot telnet a daemon, you need to configure the telnet permissions with vtsh (see below).
Finally, give user and group ownership to respectively quagga and quaggavty to the files inside the /etc/quagga directory:
#chown quagga.quaggavty /etc/quagga/*.conf
#chmod 640 /etc/quagga/*.conf
Restart the Quagga service:
#/etc/init.d/quagga restart
3. DEBIAN.CONF FILE
By default, the Quagga daemons are listening only to the loopback interface 127.0.0.1. It means that you can telnet a daemon only on its loopback address 127.0.0.1 and thus cannot access it remotely.
If you want to telnet a Quagga daemon remotely you can, in the /etc/quagga/debian.conf file. Either indicate one or several IP addresses or remove the -A option meaning that you can telnet a daemon on any of its IP addresses.
Here are two examples:
The ospfd daemon is listening to the 127.0.0.1 and 192.168.1.104 IP addresses.
ospfd_options=" --daemon -A 127.0.0.1 192.168.1.104"
The zebra daemon is listening to all the Linux interfaces IP addresses. We recommend using this setting. If you want to filter who can access to your router, configure access lists on the router software.
zebra_options=" --daemon "
Here is the recommended debian.conf file:
#vim /etc/quagga/debian.conf
# If this option is set the /etc/init.d/quagga script automatically loads
# the config via "vtysh -b" when the servers are started.
# Check /etc/pam.d/quagga if you intend to use "vtysh"!
#
vtysh_enable=yes
zebra_options=" --daemon -A "
bgpd_options=" --daemon -A "
ospfd_options=" --daemon -A "
ospf6d_options="--daemon -A "
ripd_options=" --daemon -A "
ripngd_options="--daemon -A "
isisd_options=" --daemon -A "
The "vtysh_enable=yes" setting is required to access the Quaggga router via vtysh. (see vtysh section).
Restart the Quagga service
#/etc/init.d/quagga restart
4. VTYSH
As indicated in the Quagga introduction, you can access the daemons by telnetting their port number because each daemon has its own configuration file and terminal interface.
zebra:
ripd:
ripng:
ospfd:
bgpd:
ospf6d: 2601
2602
2603
2604
2605
2606
By instance, to access the ospfd daemon:
#telnet localhost 2604
As it's not very practical to configure your router by telnetting its daemons separately, vtysh has been created to configure everything in one single interface.
To use vtysh, you must first create its configuration file as follows:
#cp /usr/share/doc/quagga/examples/vtysh.conf.sample /etc/quagga/vtysh.conf
/etc/quagga/vtysh.conf
!
! Sample
!
! service integrated-vtysh-config
hostname quagga-router
username root nopassword
!
Apply correct permissions and restart Quagga:
#chown quagga.quaggavty /etc/quagga/*.conf
#chmod 640 /etc/quagga/*.conf
#/etc/init.d/quagga restart
In the example above the "service integrated-vtysh-config" setting has been disabled (recommended). In this case, when you save the config under vtysh, it will be stored in separate files depending on the protocols you activated.
Below, an example where the Quagga configuration is saved under vtysh. (The zebra and ospfd daemons have been enabled.)
#vtysh
quagga-router#write
Configuration saved to /etc/quagga/zebra.conf
Configuration saved to /etc/quagga/ospfd.conf
If you activate "service integrated-vtysh-config", the configuration under vtysh will be saved in one file called Quagga.conf in the /etc/quagga/ directory.
With this setting, when you access a daemon via telnet, the daemon will look first to the Quagga.conf file before looking for its own file. This means that, when you telnet a device, there can be a difference between what you see after the "show run" command and the content of the associated file, for example zebra.conf.
#vtysh
quagga-router#write
Configuration saved to /etc/quagga/Quagga.conf
It is recommended to disable "service integrated-vtysh-config" because if this setting is enabled and in case of a syntax error in the Quagga.conf file, this can lead to all your daemons being unable to start up. This will not be case when "service integrated-vtysh-config" is disabled because the configurations are stored in separate files.
Check that the default "vtysh_enable=yes" setting are configured in your /etc/quagga/debian.conf file. You can read the previous paragraph about the debian.conf file to get more information.
Then it's useful to add the "VTYSH_PAGER=more" setting in your /etc/environment file, otherwise you will see an unfriendly "(END)" blinking in the left-down corner of the screen each time your enter a command and will need to press the "q" key to continue.
#echo VTYSH_PAGER=more > /etc/environnement
Log off and log on to enable the environment setting. You can now access the Quagga router with the vtysh command:
#vtysh
Hello, this is Quagga (version 0.99.6).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
quagga-router#
If you want to run a Quagga command from the Linux shell:
#vtysh -c "command"
For instance, vtysh -c "show ip route" will display the Quagga routing table.
You can use ping and traceroute to perform connectivity checks from the vtysh prompt. Of course, these two programs need to be installed on the Linux machine. Ping is generally installed by default but traceroute often not.
To install traceroute:
#apt-get install traceroute
5. IP FORWARDING:
IP forwarding is required to transfer packets between the network interfaces of a Linux system.
See a picture of the Linux kernel routing.
#echo "1" > /proc/sys/net/ipv4/ip_forward
The command above will add the "1" value inside the /proc/sys/net/ipv4/ip_forward file and thus activate the IP forwarding.
If you want to keep the IP forwarding after a Linux reboot:
#echo "net.ipv4.ip_forward = 1" >> /etc/sysctl.conf
It is possible to check the ip_forwarding status under the Quagga router:
#show ip forwarding
IP forwarding is on
In this case the IP forwarding is activated.
How to install Quagga on Debian linux
configuring bandwidth management netenforcer via hyperterminal
NetEnforcer is a network policy enforcement device that enables you to monitor, categorize and optimize network traffic by assigning Quality of Service (QoS) to specified classes of traffic. QoS is the ability to define a level of performance in a data communications system.
you can use a standard terminal /PC running terminal emulation software connected to the Console port, or Telnet via the internet to configure a NetEnforcer. If you choose to connect via the Console port, most standard windows-based PC systems have a terminal emulation program called HyperTerminal that can be used for this purpose. Configure the terminal to run VT100 terminal emulation with the following parameters:
· Baud rate 19200
· 8 bits
· Stop bits 1
· No flow control
· No parity
CISCO CATALYST stp BLOCKING
Today, i had problem wtih my trunking cisco catalyst c2950. one of my access port to fibre optic interconnection was problem. after one hour i try to find solution for this matter.
this is log problem show:
%SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk FastEthernet0/1 VLAN2.
004964: May 4 00:01:17.302: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking FastEthernet0/1 on VLAN0002. Inconsistent port type.
status of the port show that operational mode change into trunk (before access).
#sh int fa0/1 switchport
Name: Fa0/1
Switchport: Enabled
Administrative Mode: dynamic desirable
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 2 (VLAN0002)
Trunking Native Mode VLAN: 1 (default)
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
After i change to static access it’s running again
#sh int fa0/1 switchport
Name: Fa0/1
Switchport: Enabled
Administrative Mode: static access
Operational Mode: static access
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 2 (VLAN0002)
Trunking Native Mode VLAN: 1 (default)
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
In the majority of cases, the reason for detection of STP inconsistency on the port is apparent:
Access port receives an IEEE 802.1Q-tagged SSTP BPDU.
In this scenario, access port on bridge A receives, from bridge B, a tagged PVST+ BPDU from STP of a VLAN other than 1. The port on A will be put into type-inconsistent state.
Note: The switches need not be connected directly; if they are connected through one or more IEEE 802.1D or IEEE 802.1Q switches—or even hubs—then the effect is the same.
IEEE 802.1Q trunking port receives an untagged SSTP BPDU with a VLAN type, length, value (TLV) that does not match the VLAN where the BPDU was received.
-
In this scenario, the trunk port on A receives a PVST+ BPDU from STP of VLAN 2 with a tag of VLAN 2. This triggers the port on A to be blocked in both VLAN 1 and VLAN 2.
-
The port is configured for IEEE 802.1Q trunking on one side but the other side is access port.
-
IEEE 802.1Q trunks are on both sides, but the Native VLANs are different.
In these cases, fix the configuration mismatch to resolve the STP inconsistency.
If devices on both ends of a point-to-point link are Cisco Catalyst switches, an examination of the local and remote port configuration typically reveals the configuration mismatch:
802.1q vlan interface with mikrotik
Nowadays, Ussually we use Vlan Tagging 802.1q for many connection to one router. And also most of that we using cisco router combine with cisco catalyst 2950(Layer 2 router).
I thinking how about we use Mikrotik router combine with Layer 2 Switch non cisco to build Vlan tagging 802.1q. so I decided to try new improvement for efisien cost
VLAN is an implementation of the 802.1Q VLAN protocol for MikroTik RouterOS 2.7. It allows you to have multiple Virtual LANs on a single ethernet cable, giving the ability to segregate LANs efficiently. It supports up to 4094 vlan interfaces per ethernet device. Many routers, including Cisco and Linux based, and many Layer 2 switches also support it.
A VLAN is a logical grouping that allows end users to communicate as if they were physically connected to a single isolated LAN, independent of the physical configuration of the network. VLAN support adds a new dimension of security and cost savings permitting the sharing of a physical network while logically maintaining separation among unrelated users.
Tagged Port Members
A port is a tagged member of a specific VLAN when it is a member of more than one VLAN. If a port is a tagged member of one VLAN, then the same port is also an untagged member of another VLAN.
Untagged Port Members
A port is an untagged member of a VLAN if the PVID is equal to the VID of that VLAN. A port can be an untagged member of only one VLAN. An example of this is the Default VLAN configuration where all ports are initially configured to be untagged members of VLAN 1 only. A port can also be an untagged member of one VLAN and be a tagged member of one or more VLANS
How do I setup VLAN Tagging Between Mikrotik PC Router and Layer2 Switch : First, We configure 3com switch to define which as port member tagged and untagged.
Menu options: --------------3Com SuperStack 3 Switch 4200-------------
bridge - Administer bridge-wide parameters
gettingStarted - Basic device configuration
logout - Logout of the Command Line Interface
physicalInterface - Administer physical interfaces
protocol - Administer protocols
security - Administer security
system - Administer system-level functions
trafficManagement - Administer traffic management
Type ? for help
-------------------------------------amino, 1 (1)---------------------
Select menu option: bridge vlan
Menu options: --------------3Com SuperStack 3 Switch 4200-------------
create - Create a VLAN
delete - Delete a VLAN
detail - Display detailed information
modify - Modify a VLAN
summary - Display summary information
After that we have to configure Vlan Interface on mikrotik router,
Note :
Ether 1 Direct to Router WAN
Ether 2 To Switch 3com
Next, you just assign ip address per VLAN. Example Company A want to connect to you and you just plug to port 1 switch 3Com which belong to vlan 02 (see configuration switch 3com above).
Next if there’s Company B connect, you just continue to plug to port 2 switch 3Com and assign ip to ether2-vlan03.
php redirect script
You can use a simple PHP script to redirect a user from the page they entered to a different web page. One reason you may want to do this is that the page they are trying to access no longer exists. Using this method, they can be seamlessly transfered to the new page without having to click a link to continue.
To do :
go to web file you want to redirect :
add this source code or change all source with this one for more simple:
<?php header( 'Location: http://www.yoursite.com/new_page.html' ) ?>
You need to replace the URL above with the URL you wish to direct to.
top-10-web-hosting-best-web-hosts-2009
From webhostinggeeks, based on review : Cheap professional web hosting services under $10 a month; all web hosting plans include at least one free domain name registration and 30 day money back guarantee. Review your web host — let other webmasters know the best and the worst!
Rank Web Hosting Provider Features Bonus Features Hosting Review
1 Inmotion web hosting rating - 5 stars
Business Web Hosting Space: Unlimited
Traffic: Unlimited
Price: $8.95 Free Domain Name,
Choice of Data Centers,
Top Technical Support Inmotion Review
Host Rating: 98%
Rate and Review a Host Review Inmotion
2 JustHost web hosting rating - 5 stars
Editor's Choice Hosting Space: Unlimited
Traffic: Unlimited
Price: $4.95 Free Domain Forever,
Host Unlimited Domains,
$75 Marketing Bonus JustHost Review
Host Rating: 97%
Rate and Review a Host Review JustHost
3 WebHostingPad web hosting rating - 5 stars
Cheap Reliable Hosting Space: Unlimited
Traffic: Unlimited
Price: $3.96 Free Domain Forever,
Host Unlimited Domains,
$100 Marketing Bonus WebHostingPad Review
Host Rating: 97%
Rate and Review a Host Review WebHostingPad
4 Bluehost web hosting rating - 4.5 stars
Unlimited Web Hosting Space: Unlimited
Traffic: Unlimited
Price: $4.95 Free Domain Forever,
Host Unlimited Domains,
$75 Marketing Bonus Bluehost Review
Host Rating: 96%
Rate and Review a Host Review Bluehost
5 FatCow web hosting rating - 4.5 stars
Cheap Business Hosting Space: Unlimited
Traffic: Unlimited
Price: $4.83 Free Domain Forever,
Host Unlimited Domains,
$75 Marketing Bonus FatCow Review
Host Rating: 96%
Rate and Review a Host Review FatCow
6 Hostmonster web hosting rating - 4.5 stars
Cheap Unix Hosting Space: Unlimited
Traffic: Unlimited
Price: $4.95 Free Domain Forever,
Host Unlimited Domains,
$75 Marketing Bonus Hostmonster Review
Host Rating: 96%
Rate and Review a Host Review Hostmonster
7 Globat web hosting rating - 4 stars
Cheap Web Hosting Space: Unlimited
Traffic: Unlimited
Price: $4.44 Free Domain Name,
Host Unlimited Domains,
$55 Marketing Bonus Globat Review
Host Rating: 95%
Rate and Review a Host Review Globat
8 Lunarpages web hosting rating - 3.5 stars
Cheap Shared Hosting Space: Unlimited
Traffic: Unlimited
Price: $4.95 Free Domain Forever,
Host Unlimited Domains,
Free $775 in Software Lunarpages Review
Host Rating: 94%
Rate and Review a Host Review Lunarpages
9 GoDaddy web hosting rating - 3.5 stars
Largest Web Hosting Space: Unlimited
Traffic: Unlimited
Price: $12.74 Free Domain Name,
Host Unlimited Domains,
Free SSL Certificate GoDaddy Review
Host Rating: 93%
Rate and Review a Host Review GoDaddy
10 Yahoo web hosting rating - 3.5 stars
Reliable Web Hosting Space: Unlimited
Traffic: Unlimited
Price: $8.96 Free Domain Name,
$100 Yahoo Credit,
$50 Google Credit Yahoo Review
Host Rating: 93%
Rate and Review a Host Review Yahoo
ip policy based routing
Cisco routers running Cisco IOS supports pased based IP Routing which can route packets based on a set IP Policy exiting an Interface.
Policy based routing in Cisco ROuters can be performed by using "route-map" and then applying as a policy to the interface of the IP Packets.
The route-map has a list of "match" and "set" commands where match defines the criteria under which the policy routing is performed (say, match a destination IP or a standard or Extended ACL) and set defines the actions to perform when match criteris met (say, set next hop).
In this example, I change the routing to a particular network only from a particular subnet which is defined in a standard ACL. This ACL is then matched in a route-map and applied as an IP policy for routing change for the change in routing behaviour.
Create Standard ACL
From the global configuration mode, create an ACL to permit source network 10.1.1.0/24
ciscorouter# conf term
ciscorouter(config)# access-list 10 permit 10.1.1.0 0.0.0.255
That creates a new ACL "10" with a permit for 10.1.1.0/24 network.
Create Route-Map
Define a route-map with "match" conditions and "set" actions.
ciscorouter(config)# route-map SetNextHop permit 10
ciscorouter(config-route-map)# match ip address 10
ciscorouter(config-route-map)# set ip next-hop 192.168.0.1
ciscorouter(config-route-map)# exit
That creates a route-map called "SetNextHop" and matches the ACL 10 where the source network for which the route-map should be actioned. I've set the action to be taken when the source network matches to set the next hop router as 192.168.0.1
Apply Policy Route-map to interface
This route-map is now applied to the interface (fa0/0)
ciscorouter(config)# interface fa0/0
ciscorouter(config-if)# ip policy route-map SetNextHop
Test for yourself. For source network 10.1.1.0/24, the nexthop IP is set as 192.168.0.1 (Router B) where every other source networks are router as specified by the static/dynamic routes (in our example through Router A)