[MLB-WIRELESS] Routing protocols

Thu Oct 16 09:11:44 EST 2008

G'day!

Yes, I have done that already - my questions was really just a reply to your
statement that "there was a reason for them" and I guess I was just curious
as to what that reason might be ;-)

You are right about the production network, of course, but I still like the
idea of advertising some of my live subnets into the MW net.

What I'm considering at the moment is a scheme that can do this reliably and
efficiently:

I am going to create a border bewteen my production network and the MW net
in general.

The border will be essentially a link between the client (I call it KBN-JEE)
currently connected to JEE and another router I use as a gateway between my
home network and my live network. I'll run BGP on that gateway, and set up
KBN-JEE as a BGP peer. 

Something like this:

          -------+        +--------+          +---------+          +--------
 DuxTel/VBRN Net +--OSPF--+ BORDER +----BGP---+ KBN-JEE +--OSPF----+
JEE--MelbWireless  
          -------+        +--------+          +---------+          +--------

That essentially uses BGP as a mechanism to filter the routes learned by
KBN-JEE from MW so that I do not risk letting junk come into the live
network.  At the same time, this scheme will let me preferentially present
selected live subnets into MW and then advertise through OSPF by KBN-JEE.

I think that this may be a useful model for other MW nodes that border on
independent networks, and perhaps even between clusters of MW nodes.
Exactly where those borders can be entirely determined by the independent
node operators, and should be dynamic enough to permit relatively ad-hoc
implementation.

It's kinda like federation in reverse ;-)

The big question now, is what AS numbers to use?  I could just pull one off
the list of private allocations, but it would be a better idea to try to
adhere to any existing allocation schemes already out there in the world of
community networks.

Anyone know of existing AS allocation schemes that we can buy in to?  I
suspect Kim Hawtin will have a suggestion or two (?) :)

Comments anyone?

> -----Original Message-----
> From: Peter Buncle [mailto:peter at nmc.net.au] 
> Sent: Thursday, 16 October 2008 7:45 AM
> To: mike at viewbankrise.net.au
> Subject: RE: [MLB-WIRELESS] Routing protocols
> 
> 
> If you put in 
> 
> ip route 0.0.0.0/1 your-gw
> ip route 128.0.0.0/1 your-gw
> 
> Into zebra.conf 
> 
> It should override the other routes.
> 
> 
> There shouldn't be any other routes coming through But due to 
> it's dynamic nature and the prossibility Of newbie mistakes , 
> it should be separate to a production system.
> 
> The easy fix is to make important routes static.
> 
> Cheers
> 
> Peter
> 
> 
> 
> -----Original Message-----
> From: Mike Everest [mailto:mike at viewbankrise.net.au]
> Sent: Wednesday, 15 October 2008 8:19 PM
> To: Peter Buncle
> Subject: RE: [MLB-WIRELESS] Routing protocols
> 
> G'day,
> 
> Ok, I've managed to weed out those two duds.  It would be 
> good if you managed to figure out where they came from....  
> But it would probably be better if we used BGP in here 
> somewhere.  Perhaps I need to make that device one step 
> removed from the rest of my network in case some more of 
> those nasties get through! ;-)
> 
> Cheers. 
> 
> > -----Original Message-----
> > From: Peter Buncle [mailto:peter at nmc.net.au]
> > Sent: Wednesday, 15 October 2008 5:53 PM
> > To: mike at viewbankrise.net.au
> > Subject: RE: [MLB-WIRELESS] Routing protocols
> > 
> > I've cleaned it up a bit , see if it's better now.
> > 
> > Peter
> > 
> >  
> > 
> > -----Original Message-----
> > From: Mike Everest [mailto:mike at viewbankrise.net.au]
> > Sent: Wednesday, 15 October 2008 3:15 PM
> > To: Peter Buncle
> > Subject: RE: [MLB-WIRELESS] Routing protocols
> > 
> > Leave it with me for a bit.  I'll turn on debugging at this end and 
> > see if I can figure out what is going on.
> > 
> > Cheers! 
> > 
> > > -----Original Message-----
> > > From: Peter Buncle [mailto:peter at nmc.net.au]
> > > Sent: Wednesday, 15 October 2008 2:42 PM
> > > To: mike at viewbankrise.net.au
> > > Subject: RE: [MLB-WIRELESS] Routing protocols
> > > 
> > > Hmmm , I check the router and the condfig is correct.
> > > 
> > > 
> > > It's also picking up the entire route table from the 
> larger network
> > > 
> > > 
> > > I've rebooted , so how is it now
> > > 
> > > 
> > > 
> > > Peter
> > > 
> > >  
> > > 
> > > -----Original Message-----
> > > From: Mike Everest [mailto:mike at viewbankrise.net.au]
> > > Sent: Wednesday, 15 October 2008 1:26 PM
> > > To: Peter Buncle
> > > Subject: RE: [MLB-WIRELESS] Routing protocols
> > > 
> > > Hi Peter,
> > > 
> > > I have ospf enabled, and it is receiving routes from jee, 
> but it is 
> > > only receiving the local jee subnet (10.10.65.0/29) - it
> > seems as if
> > > jee is not advertising any other routes to this end.
> > > 
> > > Cheers!
> > > 
> > > > -----Original Message-----
> > > > From: Peter Buncle [mailto:peter at nmc.net.au]
> > > > Sent: Wednesday, 15 October 2008 12:50 PM
> > > > To: mike at viewbankrise.net.au
> > > > Subject: RE: [MLB-WIRELESS] Routing protocols
> > > > 
> > > > Hi Mike,
> > > > 
> > > > You've been busy !
> > > > 
> > > > We use OSPF on the mw network for now , and node jee is
> > > broadcasting
> > > > it You must just have some config issues at your end.
> > > > 
> > > > Make sure you use area 0.0.0.0
> > > > 
> > > > There's config examples at
> > > > 
> > > > http://www.melbourne.wireless.org.au/wiki/?ConfigsFPYOspf
> > > > 
> > > > And zebra at
> > > > 
> > > > http://www.melbourne.wireless.org.au/wiki/?ConfigsGDWZebra
> > > > 
> > > > 
> > > > Naturally you have to modify both for your interfaces 
> and subnets.
> > > > 
> > > > 
> > > > Cheers
> > > > 
> > > > Peter
> > > > 
> > > > --
> > > > Message  protected by MailGuard: e-mail anti-virus, 
> anti-spam and 
> > > > content filtering.
> > > > http://www.mailguard.com.au/mg
> > > > 
> > > > 
> > > 
> > 
> 