Posts

Showing posts with the label ipv6

How to set up IPv6 BGP peering and filtering in Quagga BGP router

Image
I had originally written this article for xmodulo . In the previous tutorials, we demonstrated how we can set up a  full-fledged BGP router  and configure  prefix filtering  with Quagga. In this tutorial, we are going to show you how we can set up IPv6 BGP peering and advertise IPv6 prefixes through BGP. We will also demonstrate how we can filter IPv6 prefixes advertised or received by using  prefix - list  and  route - map  features. Topology For this tutorial, we will be considering the following topology. Service providers A and B want to establish an IPv6 BGP peering between them. Their IPv6 and AS information is as follows. Peering IP block: 2001:DB8:3::/64 Service provider A: AS 100, 2001:DB8:1::/48 Service provider B: AS 200, 2001:DB8:2::/48 Installing Quagga on CentOS/RHEL If Quagga has not already been installed, we can install it using  yum . # yum install quagga On CentOS/RHEL 7, the default SELinux policy, ...

Nagios Ping Problem

I'm using Nagios3 in my Debian 6 box for monitoring my network. My system pings www.google.com periodically to check whether the Internet connection is okay or not. The weird thing happened is that, when Nagios checks whether www.google.com is reachable or not, it says "Network not found". However, I can ping www.google.com manually. root@dragonfly:~# /usr/lib/nagios/plugins/check_ping -H www.google.com -c 100,90% -w 100,90% CRITICAL - Network Unreachable (www.google.com) root@dragonfly:~# ping www.google.com PING www.l.google.com (74.125.236.208) 56(84) bytes of data. 64 bytes from maa03s17-in-f16.1e100.net (74.125.236.208): icmp_req=1 ttl=53 time=210 ms 64 bytes from maa03s17-in-f16.1e100.net (74.125.236.208): icmp_req=2 ttl=53 time=229 ms ^C --- www.l.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 210.611/219.867/229.124/9.268 ms After a bit of googling, here's what I found. 8-Jun w...