[6bone] quagga bgpd importing and advertising debian routes on the fly
Dan Reeder
dan@reeder.name
Sun, 23 Nov 2003 23:10:58 +1000
This is a multi-part message in MIME format.
------=_NextPart_000_0014_01C3B217.0E321120
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi guys
Here's the plan: we're in the middle of setting up a tunnel server on a =
debian box that is also running Quagga's bgp daemon that will hopefully =
be able to automatically advertise the newly made tunnel =
interfaces/networks on to its bgp peers.=20
The problem is just how to go about doing this? The process will involve =
the http server (using perl or php) to get the new prefix, create it in =
debian [this works fine so far], then tell bgpd to include it in its =
statements.=20
We'd normally just have a supernet that covers all the tunnels that =
would be created on the box and just advertise that to the peers, but =
the requirement to use just one pool of prefixes across two tunnel pops =
doing the above functions.=20
The simple answer is to just get php to edit the bgpd.conf and restart =
bgpd every time a new tunnel interface is made - but that'd wreak havoc =
with the routing table for the rest of the users.=20
Firstly is there a way to manually get the bgpd include and advertise =
new routes on the fly without interrupting other routes, and secondly =
can this be done automatically by php/perl/some other httpd-based =
function.
thanks
Dan Reeder
------=_NextPart_000_0014_01C3B217.0E321120
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#d9d9d9>
<DIV><FONT face=3DArial size=3D2>Hi guys</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Here's the plan: we're in the middle of =
setting up=20
a tunnel server on a debian box that is also running Quagga's bgp daemon =
that=20
will hopefully be able to automatically advertise the newly made tunnel=20
interfaces/networks on to its bgp peers. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The problem is just how to go about =
doing this? The=20
process will involve the http server (using perl or php) to get the new =
prefix,=20
create it in debian [this works fine so far], then tell bgpd to include =
it in=20
its statements. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We'd normally just have a supernet that =
covers all=20
the tunnels that would be created on the box and just advertise that to =
the=20
peers, but the requirement to use just one pool of prefixes =
across two=20
tunnel pops doing the above functions. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The simple answer is to just get php to =
edit the=20
bgpd.conf and restart bgpd every time a new tunnel interface is =
made - but=20
that'd wreak havoc with the routing table for the rest of the users.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Firstly is there a way to manually get =
the bgpd=20
include and advertise new routes on the fly without interrupting other =
routes,=20
and secondly can this be done automatically by php/perl/some other =
httpd-based=20
function.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Dan Reeder</FONT></DIV></BODY></HTML>
------=_NextPart_000_0014_01C3B217.0E321120--