[Commotion-discuss] Send mesh routes to upstream router
Josh King
jking at chambana.net
Wed Jul 13 18:02:13 UTC 2016
Hey Christopher,
That was pretty much what I was going to suggest, you beat me to it :-)
Let me know how that works. If it works out of the box it may be something worth documenting for
other users who want to use auxiliary routing protocols to interconnect networks.
On Mon, 2016-07-11 at 10:20 -0700, Christopher Munz-Michielin wrote:
> Hey Josh,
>
> Just wanted to update you on this as I managed to get Quagga and bgpd
> installed/configured. The trick was to change my repository to the
> vanilla OpenWRT repo
> (http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/routing/),
> and run 'opkg install quagga quagga-bgpd quagga-zebra' After that I was
> able to configure the software as normal and brought up the adjacency
> without issue.
>
> I'll do some testing later to make sure the OSLR routes are being
> advertised (I did enable 'redistribute oslr' in the config) just don't
> have any mother mesh nodes connected right now to verify with.
>
> Cheers!
> Chris
>
>
> On 08/07/2016 06:12, Christopher Munz-Michielin wrote:
> > Hey Josh,
> >
> > I had a chance to test out opkg and was unable to even update the
> > package lists:
> >
> > root at AP-Test-2223136168:~# opkg update
> > Downloading
> > http://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz.
> > wget: not an http or ftp url:
> > https://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz
> > Collected errors:
> > * opkg_download: Failed to download
> > http://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz,
> > wget returned 1.
> >
> > When I manually browse to
> > http://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz
> > it redirects me to the https:// version of the site and looks like the
> > version of wget that is shipped with the commotion firmware doesn't
> > support https. Any idea if I can install a newer version of wget?
> >
> > Chris
> > On 06/07/2016 08:42, Josh King wrote:
> > > Hi Christopher,
> > >
> > > Well, you can see if quagga is available in the repositories currently
> > > configured by running this on the router CLI:
> > >
> > > opkg update
> > > opkg list | grep quagga
> > >
> > > And then install it with 'opkg install' (space permitting). If it's not
> > > in the default Commotion repositories, I can walk you through adding
> > > additional repos.
> > >
> > > On Wed, 2016-07-06 at 08:38 -0700, Christopher Munz-Michielin wrote:
> > > > Hi Josh,
> > > >
> > > > Thanks for the reply. I'd like to run BGP on the commotion router
> > > > and
> > > > have it communicate routing info back to the edge router, but am not
> > > > sure how to get Quagga (or similar) up and running on the commotion
> > > > firmware, any suggestions?
> > > >
> > > > Cheers,
> > > > Chris
> > > >
> > > >
> > > > On 06/07/2016 08:23, Josh King wrote:
> > > > > Hi Christopher,
> > > > >
> > > > > There are a few different ways you could approach this. I can think
> > > > > of
> > > > > three right off the bat, but there may be more. They all have their
> > > > > own
> > > > > advantages and disadvantages:
> > > > >
> > > > > * You could run BGP or similar on the nodes or on the edge router;
> > > > > they
> > > > > would share the kernel routing table with OLSR, but as long as it's
> > > > > set
> > > > > up in such a way that they don't clobber each others' routes it
> > > > > should
> > > > > be fine. I'm not familiar enough though with setting up BIRD,
> > > > > Zebra/Quagga, or similar to know exactly how to configure it to
> > > > > pass
> > > > > along all of the OLSR routes as well.
> > > > >
> > > > > * You could split it up by subnet and configure the routes
> > > > > statically.
> > > > > The problem here is that all Commotion nodes self-select their
> > > > > addresses out of the same private subnet, so you'd need to
> > > > > configure
> > > > > the nodes to select out of separate subnets manually.
> > > > >
> > > > > * Since the nodes already run a dynamic routing protocol (OLSR),
> > > > > you
> > > > > could create a VPN tunnel between the two networks. Then they can
> > > > > dynamically pass their routing traffic themselves between the two
> > > > > networks. This would require setting up a VPN tunnel, and could
> > > > > potentially experience performance issues as the network scales
> > > > > (OLSR
> > > > > is a chatty protocol to be sending over a narrow VPN pipe).
> > > > >
> > > > > Hopefully that helps. Let me know if you have any thoughts.
> > > > >
> > > > > On Mon, 2016-07-04 at 14:45 -0700, Christopher Munz-Michielin
> > > > > wrote:
> > > > > > Hi All,
> > > > > >
> > > > > > Just starting to play around with the Commotion firmware as I'm
> > > > > > part
> > > > > > of
> > > > > > a group of ham radio operators looking at starting a localized
> > > > > > mesh
> > > > > > using ubiquiti M2's. So far I'm impressed by the firmware but
> > > > > > did
> > > > > > have
> > > > > > one question: Is it possible to run a dynamic routing protocol
> > > > > > (such
> > > > > > as
> > > > > > OSPF, BGP or RIP) to send information about the connected mesh
> > > > > > devices
> > > > > > to an upstream router? Our architecture would be something like
> > > > > > this:
> > > > > >
> > > > > > Internet------------Edge Router---------------Mesh
> > > > > > node-------------------Additional mesh nodes-----------local
> > > > > > subnet
> > > > > > |
> > > > > > |
> > > > > > Non mesh network
> > > > > >
> > > > > > I can add static routes to the edge router, but doing so would be
> > > > > > cumbersome and potentially time consuming, especially if we are
> > > > > > adding
> > > > > > new nodes frequently so a dynamic protocol would be preferred.
> > > > > >
> > > > > > Cheers,
> > > > > > Chris
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Commotion-discuss mailing list
> > > > > > Commotion-discuss at lists.chambana.net
> > > > > > https://lists.chambana.net/mailman/listinfo/commotion-discuss
> > > > > -- Josh King
> > > > > PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999
> > > -- Josh King
> > > PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999
> >
>
-- Josh King
PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.chambana.net/pipermail/commotion-discuss/attachments/20160713/e34eef60/attachment.sig>
More information about the Commotion-discuss
mailing list