FreePeer eXchange

FreePeer eXchange is a project aimed at allowing a private network that rides on top of the existing internet for the purpose of learning.

This site is free to use and setup a tunnel on in which you can advertise your prefixes, manipulate BGP, host and access services on the network, etc. The goal is to provide a free means to learn routing protocols, tunneling, and networking in general. Registration is free and configuration aids are available to help kick start your connectivity; Get started today by clicking on register above!

The items used for this project are virtual servers running Gentoo Linux, quagga for BGP/OSPF dynamic routing, and OpenNHRP for dynamic gre tunnels, links are below.



TServ4 Issues - Resolved
Tserv4 has been restored to full service.


Statistics: Posted by rgoode214 - Thu Aug 14, 2014 11:28 pm - Replies 0 - Views 4944

Tserv4 Issues
TServ4 (LON) is having issues with regards to bringing up OSPF adjacency to the other tunnel servers and therefore is preventing BGP from coming up.

I am working on this now to bring to resolution.


Statistics: Posted by rgoode214 - Thu Aug 14, 2014 10:21 pm - Replies 0 - Views 2646

New Server
The site will be transitioning to a new server in the next few days so bear with any issues as they will be fixed as they come up.


Statistics: Posted by rgoode214 - Mon Aug 11, 2014 3:45 am - Replies 0 - Views 4056

Routing Updates
Several routing changes have been made within the core to optimize routing. In addition the first phase of community strings have been implemented and announced with routes. They are listed as follows:

64600:103 - Routes advertised by Tserv3
64600:104 - Routes advertised by Tserv4
64600:105 - Routes advertised by Tserv5
64600:499 - Routes advertised to a tserv from another tserv (internal use only really)
64600:500 - Routes advertised to a Tserv by a legacy client
64600:510 - Routes advertised to a Tserv by a DMVPN client

You can use these to apply filters (more than prefixes) to match routes from individual hosts/tservs.

In addition, routes advertised by a tserv that were originated by a legacy client now set the next hop to that of the tserv that is advertising the route, this will prevent recursive route lookups.


Statistics: Posted by rgoode214 - Fri Apr 18, 2014 10:39 pm - Replies 0 - Views 84041