<div dir="ltr">That's great! As Josh mentioned -- if you want to document what you did we could add it to the website so others can follow your example.<div><br></div><div>Thanks for sharing Chris!</div><div><br></div><div>-Georgia</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 14, 2016 at 10:45 AM, Christopher Munz-Michielin <span dir="ltr"><<a href="mailto:christopher@ve7alb.ca" target="_blank">christopher@ve7alb.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Josh,<br>
<br>
We did some testing last night and I just wanted to update you that the BGP routing was successful! I was able to see the OSLR routes populate in the BGP routing table, and, after adding the upstream subnet to the HNA announcements I was able to access the upstream network from mesh clients with no NAT.<br>
<br>
Cheers!<br>
Chris<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On 13/07/2016 11:02, Josh King wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Christopher,<br>
<br>
That was pretty much what I was going to suggest, you beat me to it :-)<br>
<br>
Let me know how that works. If it works out of the box it may be something worth documenting for<br>
other users who want to use auxiliary routing protocols to interconnect networks.<br>
<br>
On Mon, 2016-07-11 at 10:20 -0700, Christopher Munz-Michielin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Josh,<br>
<br>
Just wanted to update you on this as I managed to get Quagga and bgpd<br>
installed/configured. The trick was to change my repository to the<br>
vanilla OpenWRT repo<br>
(<a href="http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/routing/" rel="noreferrer" target="_blank">http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/packages/routing/</a>),<br>
and run 'opkg install quagga quagga-bgpd quagga-zebra' After that I was<br>
able to configure the software as normal and brought up the adjacency<br>
without issue.<br>
<br>
I'll do some testing later to make sure the OSLR routes are being<br>
advertised (I did enable 'redistribute oslr' in the config) just don't<br>
have any mother mesh nodes connected right now to verify with.<br>
<br>
Cheers!<br>
Chris<br>
<br>
<br>
On 08/07/2016 06:12, Christopher Munz-Michielin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Josh,<br>
<br>
I had a chance to test out opkg and was unable to even update the<br>
package lists:<br>
<br>
root@AP-Test-2223136168:~# opkg update<br>
Downloading<br>
<a href="http://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz" rel="noreferrer" target="_blank">http://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz</a>.<br>
wget: not an http or ftp url:<br>
<a href="https://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz" rel="noreferrer" target="_blank">https://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz</a><br>
Collected errors:<br>
* opkg_download: Failed to download<br>
<a href="http://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz" rel="noreferrer" target="_blank">http://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz</a>,<br>
wget returned 1.<br>
<br>
When I manually browse to<br>
<a href="http://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz" rel="noreferrer" target="_blank">http://downloads.commotionwireless.net/router/1.1/ar71xx/generic/packages/Packages.gz</a><br>
it redirects me to the https:// version of the site and looks like the<br>
version of wget that is shipped with the commotion firmware doesn't<br>
support https. Any idea if I can install a newer version of wget?<br>
<br>
Chris<br>
On 06/07/2016 08:42, Josh King wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Christopher,<br>
<br>
Well, you can see if quagga is available in the repositories currently<br>
configured by running this on the router CLI:<br>
<br>
opkg update<br>
opkg list | grep quagga<br>
<br>
And then install it with 'opkg install' (space permitting). If it's not<br>
in the default Commotion repositories, I can walk you through adding<br>
additional repos.<br>
<br>
On Wed, 2016-07-06 at 08:38 -0700, Christopher Munz-Michielin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Josh,<br>
<br>
Thanks for the reply. I'd like to run BGP on the commotion router<br>
and<br>
have it communicate routing info back to the edge router, but am not<br>
sure how to get Quagga (or similar) up and running on the commotion<br>
firmware, any suggestions?<br>
<br>
Cheers,<br>
Chris<br>
<br>
<br>
On 06/07/2016 08:23, Josh King wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Christopher,<br>
<br>
There are a few different ways you could approach this. I can think<br>
of<br>
three right off the bat, but there may be more. They all have their<br>
own<br>
advantages and disadvantages:<br>
<br>
* You could run BGP or similar on the nodes or on the edge router;<br>
they<br>
would share the kernel routing table with OLSR, but as long as it's<br>
set<br>
up in such a way that they don't clobber each others' routes it<br>
should<br>
be fine. I'm not familiar enough though with setting up BIRD,<br>
Zebra/Quagga, or similar to know exactly how to configure it to<br>
pass<br>
along all of the OLSR routes as well.<br>
<br>
* You could split it up by subnet and configure the routes<br>
statically.<br>
The problem here is that all Commotion nodes self-select their<br>
addresses out of the same private subnet, so you'd need to<br>
configure<br>
the nodes to select out of separate subnets manually.<br>
<br>
* Since the nodes already run a dynamic routing protocol (OLSR),<br>
you<br>
could create a VPN tunnel between the two networks. Then they can<br>
dynamically pass their routing traffic themselves between the two<br>
networks. This would require setting up a VPN tunnel, and could<br>
potentially experience performance issues as the network scales<br>
(OLSR<br>
is a chatty protocol to be sending over a narrow VPN pipe).<br>
<br>
Hopefully that helps. Let me know if you have any thoughts.<br>
<br>
On Mon, 2016-07-04 at 14:45 -0700, Christopher Munz-Michielin<br>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi All,<br>
<br>
Just starting to play around with the Commotion firmware as I'm<br>
part<br>
of<br>
a group of ham radio operators looking at starting a localized<br>
mesh<br>
using ubiquiti M2's. So far I'm impressed by the firmware but<br>
did<br>
have<br>
one question: Is it possible to run a dynamic routing protocol<br>
(such<br>
as<br>
OSPF, BGP or RIP) to send information about the connected mesh<br>
devices<br>
to an upstream router? Our architecture would be something like<br>
this:<br>
<br>
Internet------------Edge Router---------------Mesh<br>
node-------------------Additional mesh nodes-----------local<br>
subnet<br>
|<br>
|<br>
Non mesh network<br>
<br>
I can add static routes to the edge router, but doing so would be<br>
cumbersome and potentially time consuming, especially if we are<br>
adding<br>
new nodes frequently so a dynamic protocol would be preferred.<br>
<br>
Cheers,<br>
Chris<br>
<br>
<br>
_______________________________________________<br>
Commotion-discuss mailing list<br>
<a href="mailto:Commotion-discuss@lists.chambana.net" target="_blank">Commotion-discuss@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
</blockquote>
-- Josh King<br>
PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999<br>
</blockquote></blockquote>
-- Josh King<br>
PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999<br>
</blockquote></blockquote></blockquote>
-- Josh King<br>
PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999<br>
</blockquote>
<br>
_______________________________________________<br>
Commotion-discuss mailing list<br>
<a href="mailto:Commotion-discuss@lists.chambana.net" target="_blank">Commotion-discuss@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr">Georgia Bullen</div><div dir="ltr">Director of Technology Projects<br><div><a href="http://newamerica.org/oti/" target="_blank">Open Technology Institute</a> @ <a href="http://newamerica.org" target="_blank">New America</a></div><div><span style="font-size:small">740 15th Street NW, Suite 900, Washington DC, 20005</span><br></div><div><a href="http://twitter.com/georgiamoon" target="_blank">@georgiamoon</a></div></div></div></div></div></div></div></div></div>
</div></div>