Quagga Routing Suite

Quagga Routing Software Suite, GPL licensed IPv4/IPv6 routing software.
Mirrors: at au bg ca ch de dk es fr hu ie it jp nl ro2 ru uk us us2 | set
Latest releases: stable: 0.98.6 unstable: 0.99.10

Route Server

We run an experimental, public route-server, to:

To that end we need as many sessions to as many diverse implementations, as possible, sending as many routes as possible. So if you have some unusual BGP speakers (rare, oddball, very old or very new release, etc..), or if you have lots of routes (real internet, or private, or generated) or non-IPv4 AFI/SAFIs (IPv6, VPN, multicast) then please peer with us! If you don't meet those criteria, then please peer with us!

The Route-server runs on an 8-core, 32-thread Sun T1000 server, provided by Sun, running Solaris (snv95 as of this writing), hosted by IT-SS. It has many GBs of RAM that need to be filled up with routing data!. It's accessible via a looking-glass and telnet on port 2605.

BGP configuration on our route-server is as follows:

Note that non-4byte-ASN BGP speakers should use AS23456, in place of AS196614. If your speaker is 4byte-ASN capable, but doesn't seem to accept 196614, try as-dot notation instead (i.e. "3.6"). Please configure a high hold-time, to avoid any unneeded BGP resets due to connectivity problems.

Peers are divided between two views:

To help out, just email the following details to rs-peering@quagga.net (please be sure to Cc'ed rs-peering Cc'ed on all emails regarding route-server operations):

Note that peering is at your own risk - it is quite possible that we will make configuration mistakes, and you should configure your own router to filter as desired. Also please ensure that you are authorised to configure any session. Finally, details like peering IP, ASN and even contact details may still be accessible, even if we do not publish those details on our website.

Example 'bgpd' configuration snippet to peer with the routeserver (modify AS and IP to suit, change 23456 to 196614 if using a 4-byte-BGP speaker):

router bgp 65600
 bgp router-id 192.168.1.1
 neighbor 195.28.164.125 remote-as 23456
 neighbor 195.28.164.125 ebgp-multihop 255
 neighbor 195.28.164.125 timers 120 3600
 neighbor 195.28.164.125 prefix-list pl-block in
 !
 address family ipv6
  neighbor 195.28.164.125 activate
  neighbor 195.28.164.125 prefix-list pl6-block in
 exit-address-family

The route-server's configuration looks something like:

bgp multiple-instance
!
router bgp 196614 view global
 bgp router-id 195.28.164.125
 bgp dampening 45
 neighbor default peer-group
 neighbor default description default configuration
 neighbor default ebgp-multihop 255
 neighbor default disable-connected-check
 neighbor default timers 90 1800
 neighbor default capability dynamic
 neighbor default capability orf prefix-list receive
 neighbor default remove-private-AS
 neighbor default soft-reconfiguration inbound
 neighbor default prefix-list pl-block out
 neighbor .... remote-as ....
 neighbor .... peer-group default
 neighbor .... description
!
 address-family ipv6
 neighbor default activate
 neighbor default capability orf prefix-list receive
 neighbor default remove-private-AS
 neighbor default soft-reconfiguration inbound
 neighbor default prefix-list pl6-block out
 neighbor .... peer-group default
 exit-address-family
!
router bgp 196614 view test
 bgp router-id 195.28.164.125
 ....
!
ip prefix-list pl-block seq 5 deny any
ipv6 prefix-list pl6-block seq 5 deny any

Route Server Peers

We're very grateful to those who help by peering. They include:

Valid XHTML 1.0! Valid CSS!

last modified Wed, 27 Aug 2008 12:25:16 GMT

webmaster@quagga.net