<div dir="ltr">I can confirm that the ath5k and ath9k (and presumably ath10k) drivers do not support ahdemo, by design. Ahdemo was intentionally left out, even though it still works with madwifi, since it was not considered 802.11-compliant.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 11, 2014 at 9:38 AM, Eric Malkowski <span dir="ltr"><<a href="mailto:eric@bvwireless.net" target="_blank">eric@bvwireless.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>We avoid the problem Ben describes (I'm quite sure) with multiple ad hoc radios with olsr all on same ssid by using madwifi's ahdemo mode which will never have cell splits like ad hoc proper can. Ahdemo just sends data and no beacons etc. and olsr is great to build a mesh through this. We just do 2 radios on different channels with same ssid and same subnet and it works very well for us. Feels like one big distributed subnet of host ip addrs and we put hnas off of some of these (one ap and one ahdemo setup) that works well. If the latest ath5k or ath9k etc driver did an equivalent for ahdemo we would like to know so we could use it in our setup. Good luck.</div>
<div><br></div><div>-Eric</div><div><br></div><div><br></div><div><i><font style="color:#333333">Sent from my Verizon Wireless 4G LTE DROID</font></i></div></div><br><br><a href="mailto:olsr-users-request@lists.olsr.org" target="_blank">olsr-users-request@lists.olsr.org</a> wrote:<br>
<br>Send Olsr-users mailing list submissions to<br> <a href="mailto:olsr-users@lists.olsr.org" target="_blank">olsr-users@lists.olsr.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br>
or, via email, send a message with subject or body 'help' to<br> <a href="mailto:olsr-users-request@lists.olsr.org" target="_blank">olsr-users-request@lists.olsr.org</a><br><br>You can reach the person managing the list at<br>
<a href="mailto:olsr-users-owner@lists.olsr.org" target="_blank">olsr-users-owner@lists.olsr.org</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Olsr-users digest..."<br>
<br><br>Today's Topics:<br><br> 1. OLSR Across Multiple Channel Ad-hoc Networks? (Duncan Eastoe)<br> 2. Re: OLSR Across Multiple Channel Ad-hoc Networks? (Henning Rogge)<br> 3. Re: OLSR Across Multiple Channel Ad-hoc Networks? (Duncan Eastoe)<br>
4. Re: OLSR Across Multiple Channel Ad-hoc Networks? (Ben West)<br> 5. Re: OLSR Across Multiple Channel Ad-hoc Networks? (Duncan Eastoe)<br> 6. Re: OLSR Across Multiple Channel Ad-hoc Networks? (Kim Hawtin)<br> 7. Re: OLSR Across Multiple Channel Ad-hoc Networks? (Ben West)<br>
<br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 10 Feb 2014 20:50:29 +0000<br>From: Duncan Eastoe <<a href="mailto:duncaneastoe@gmail.com" target="_blank">duncaneastoe@gmail.com</a>><br>
To: <a href="mailto:olsr-users@lists.olsr.org" target="_blank">olsr-users@lists.olsr.org</a><br>Subject: [Olsr-users] OLSR Across Multiple Channel Ad-hoc Networks?<br>Message-ID:<br> <<a href="mailto:CAECcapiRn0D6GOtM5RA1ReJHEyL8AymZ3w6j-gyUQpdi8PJpMA@mail.gmail.com" target="_blank">CAECcapiRn0D6GOtM5RA1ReJHEyL8AymZ3w6j-gyUQpdi8PJpMA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<div class=""><br><br>Hello,<br><br>For my undergraduate dissertation I am running tests on a mesh<br>network. I have a network consisting of 6 nodes running OpenWrt. I<br>wish for OLSR to manage the routing between them.<br>
<br>All of the nodes are in range of each other, however I need to emulate<br>an environment where the nodes communicate via directed antennas and<br>where they are not in a full mesh. To do this I'm planning to use<br>
several ad-hoc networks running on different channels.<br><br>I'm not sure whether OLSR is able to handle the routing across<br>multiple ad-hoc networks, each of which is running on a different<br>channel.<br><br>Please could someone clarify this and/or point me to any resources for<br>
configuration in such an environment?<br><br>Thank you,<br>Duncan<br><br><br><br></div>------------------------------<br><br>Message: 2<br>Date: Mon, 10 Feb 2014 22:02:18 +0100<br>From: Henning Rogge <<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>><br>
To: Duncan Eastoe <<a href="mailto:duncaneastoe@gmail.com" target="_blank">duncaneastoe@gmail.com</a>><br>Cc: olsr ysers mailing list <<a href="mailto:olsr-users@lists.olsr.org" target="_blank">olsr-users@lists.olsr.org</a>><br>
Subject: Re: [Olsr-users] OLSR Across Multiple Channel Ad-hoc<br> Networks?<br>Message-ID:<br> <<a href="mailto:CAGnRvurC4_%2BV-D3w9GHm2jWKOS7NmAUUmm3Z1-ir0RgMtziJNw@mail.gmail.com" target="_blank">CAGnRvurC4_+V-D3w9GHm2jWKOS7NmAUUmm3Z1-ir0RgMtziJNw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<div class=""><br><br>OLSRd easily works with multiple interfaces, being ethernet,<br>wifi-networks or any other broadcast capable interface.<br><br>Using it in a multi-channel adhoc network is also common procedure in<br>
lots of Community Networks.<br><br>Henning Rogge<br><br>On Mon, Feb 10, 2014 at 9:50 PM, Duncan Eastoe <<a href="mailto:duncaneastoe@gmail.com" target="_blank">duncaneastoe@gmail.com</a>> wrote:<br>> Hello,<br>><br>
> For my undergraduate dissertation I am running tests on a mesh<br>> network. I have a network consisting of 6 nodes running OpenWrt. I<br>> wish for OLSR to manage the routing between them.<br>><br>> All of the nodes are in range of each other, however I need to emulate<br>
> an environment where the nodes communicate via directed antennas and<br>> where they are not in a full mesh. To do this I'm planning to use<br>> several ad-hoc networks running on different channels.<br>><br>
> I'm not sure whether OLSR is able to handle the routing across<br>> multiple ad-hoc networks, each of which is running on a different<br>> channel.<br>><br>> Please could someone clarify this and/or point me to any resources for<br>
> configuration in such an environment?<br>><br>> Thank you,<br>> Duncan<br>><br></div><div class="">> --<br>> Olsr-users mailing list<br>> <a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>
> <a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br><br><br><br></div>------------------------------<br><br>Message: 3<br>Date: Mon, 10 Feb 2014 21:12:35 +0000<br>
From: Duncan Eastoe <<a href="mailto:duncaneastoe@gmail.com" target="_blank">duncaneastoe@gmail.com</a>><br>To: Henning Rogge <<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>><br>Cc: olsr ysers mailing list <<a href="mailto:olsr-users@lists.olsr.org" target="_blank">olsr-users@lists.olsr.org</a>><br>
Subject: Re: [Olsr-users] OLSR Across Multiple Channel Ad-hoc<br> Networks?<br>Message-ID:<br> <<a href="mailto:CAECcaphH9Z9AB1_ucybac5nT97-Q-TJgN-Cv2zvgPHJtD1ub0A@mail.gmail.com" target="_blank">CAECcaphH9Z9AB1_ucybac5nT97-Q-TJgN-Cv2zvgPHJtD1ub0A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<div class=""><br><br>Thank you for clarifying Henning.<br><br></div>Duncan<div class=""><br><br>On 10 February 2014 21:02, Henning Rogge <<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>> wrote:<br>
> OLSRd easily works with multiple interfaces, being ethernet,<br>> wifi-networks or any other broadcast capable interface.<br>><br>> Using it in a multi-channel adhoc network is also common procedure in<br>> lots of Community Networks.<br>
><br>> Henning Rogge<br>><br>> On Mon, Feb 10, 2014 at 9:50 PM, Duncan Eastoe <<a href="mailto:duncaneastoe@gmail.com" target="_blank">duncaneastoe@gmail.com</a>> wrote:<br>>> Hello,<br>>><br>
>> For my undergraduate dissertation I am running tests on a mesh<br>>> network. I have a network consisting of 6 nodes running OpenWrt. I<br>>> wish for OLSR to manage the routing between them.<br>>><br>
>> All of the nodes are in range of each other, however I need to emulate<br>>> an environment where the nodes communicate via directed antennas and<br>>> where they are not in a full mesh. To do this I'm planning to use<br>
>> several ad-hoc networks running on different channels.<br>>><br>>> I'm not sure whether OLSR is able to handle the routing across<br>>> multiple ad-hoc networks, each of which is running on a different<br>
>> channel.<br>>><br>>> Please could someone clarify this and/or point me to any resources for<br>>> configuration in such an environment?<br>>><br>>> Thank you,<br>>> Duncan<br>
>><br>
</div><div class="">>> --<br>>> Olsr-users mailing list<br>>> <a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>>> <a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br>
<br><br><br>-- <br></div><div class="">PGP public key -<br><a href="http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA3B79B579009DCA2" target="_blank">http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA3B79B579009DCA2</a><br>
<br><br><br></div>------------------------------<br><br>Message: 4<br>Date: Mon, 10 Feb 2014 15:16:51 -0600<br>From: Ben West <<a href="mailto:me@benwest.name" target="_blank">me@benwest.name</a>><br>To: Henning Rogge <<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>><br>
Cc: olsr ysers mailing list <<a href="mailto:olsr-users@lists.olsr.org" target="_blank">olsr-users@lists.olsr.org</a>><br>Subject: Re: [Olsr-users] OLSR Across Multiple Channel Ad-hoc<br> Networks?<br>Message-ID:<br>
<CADSh-SPzUgXc56Heeu_hY0bOG-ksVAbRhfs22=<a href="mailto:etUKi4cQA55g@mail.gmail.com" target="_blank">etUKi4cQA55g@mail.gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"<div class=""><br><br>
A possibly non-trivial, operational detail that may arise from testing<br>OLSRd across multiple interfaces, i.e. wired + wireless interface(s), is<br>that the popular OpenWRT firmware used by most community networks does not<br>
support directly bridging adhoc wireless interface with wired interfaces.<br></div>The recommended approach (I think) is to use the *trelay* package in<div><div class="h5"><br>OpenWRT to have the kernel basically forward packets b/w any such<br>
interfaces that don't otherwise support conventional bridging. I believe<br>by creating a named VLAN for the purpose.<br><br><br>On Mon, Feb 10, 2014 at 3:02 PM, Henning Rogge <<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>> wrote:<br>
<br>> OLSRd easily works with multiple interfaces, being ethernet,<br>> wifi-networks or any other broadcast capable interface.<br>><br>> Using it in a multi-channel adhoc network is also common procedure in<br>
> lots of Community Networks.<br>><br>> Henning Rogge<br>><br>> On Mon, Feb 10, 2014 at 9:50 PM, Duncan Eastoe <<a href="mailto:duncaneastoe@gmail.com" target="_blank">duncaneastoe@gmail.com</a>><br>
> wrote:<br>
> > Hello,<br>> ><br>> > For my undergraduate dissertation I am running tests on a mesh<br>> > network. I have a network consisting of 6 nodes running OpenWrt. I<br>> > wish for OLSR to manage the routing between them.<br>
> ><br>> > All of the nodes are in range of each other, however I need to emulate<br>> > an environment where the nodes communicate via directed antennas and<br>> > where they are not in a full mesh. To do this I'm planning to use<br>
> > several ad-hoc networks running on different channels.<br>> ><br>> > I'm not sure whether OLSR is able to handle the routing across<br>> > multiple ad-hoc networks, each of which is running on a different<br>
> > channel.<br>> ><br>> > Please could someone clarify this and/or point me to any resources for<br>> > configuration in such an environment?<br>> ><br>> > Thank you,<br>> > Duncan<br>
> ><br></div></div><div class="">> > --<br>> > Olsr-users mailing list<br>> > <a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>> > <a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br>
><br>> --<br>> Olsr-users mailing list<br>> <a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>> <a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br>
><br><br><br><br>-- <br>Ben West<br></div><a href="mailto:me@benwest.name" target="_blank">me@benwest.name</a><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.olsr.org/pipermail/olsr-users/attachments/20140210/b8ab1c0b/attachment-0001.html" target="_blank">http://lists.olsr.org/pipermail/olsr-users/attachments/20140210/b8ab1c0b/attachment-0001.html</a>><br>
<br>------------------------------<br><br>Message: 5<br>Date: Mon, 10 Feb 2014 22:22:17 +0000<br>From: Duncan Eastoe <<a href="mailto:duncaneastoe@gmail.com" target="_blank">duncaneastoe@gmail.com</a>><br>To: <a href="mailto:me@benwest.name" target="_blank">me@benwest.name</a><br>
Cc: olsr ysers mailing list <<a href="mailto:olsr-users@lists.olsr.org" target="_blank">olsr-users@lists.olsr.org</a>><br>Subject: Re: [Olsr-users] OLSR Across Multiple Channel Ad-hoc<br> Networks?<br>Message-ID:<br>
<<a href="mailto:CAECcapghQ8zzPsbM6x8NkEzRXVf6pC_uyYxJKHN4E-mo9RQHqQ@mail.gmail.com" target="_blank">CAECcapghQ8zzPsbM6x8NkEzRXVf6pC_uyYxJKHN4E-mo9RQHqQ@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<div class="">
<br><br>I'm only interested in multiple wireless interfaces per node so<br>shouldn't be a problem?<br><br></div><div><div class="h5">Thanks,<br>Duncan<br><br>On 10 February 2014 21:16, Ben West <<a href="mailto:me@benwest.name" target="_blank">me@benwest.name</a>> wrote:<br>
> A possibly non-trivial, operational detail that may arise from testing OLSRd<br>> across multiple interfaces, i.e. wired + wireless interface(s), is that the<br>> popular OpenWRT firmware used by most community networks does not support<br>
> directly bridging adhoc wireless interface with wired interfaces. The<br>> recommended approach (I think) is to use the trelay package in OpenWRT to<br>> have the kernel basically forward packets b/w any such interfaces that don't<br>
> otherwise support conventional bridging. I believe by creating a named VLAN<br>> for the purpose.<br>><br>><br>> On Mon, Feb 10, 2014 at 3:02 PM, Henning Rogge <<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>> wrote:<br>
>><br>>> OLSRd easily works with multiple interfaces, being ethernet,<br>>> wifi-networks or any other broadcast capable interface.<br>>><br>>> Using it in a multi-channel adhoc network is also common procedure in<br>
>> lots of Community Networks.<br>>><br>>> Henning Rogge<br>>><br>>> On Mon, Feb 10, 2014 at 9:50 PM, Duncan Eastoe <<a href="mailto:duncaneastoe@gmail.com" target="_blank">duncaneastoe@gmail.com</a>><br>
>> wrote:<br>>> > Hello,<br>>> ><br>>> > For my undergraduate dissertation I am running tests on a mesh<br>>> > network. I have a network consisting of 6 nodes running OpenWrt. I<br>
>> > wish for OLSR to manage the routing between them.<br>>> ><br>>> > All of the nodes are in range of each other, however I need to emulate<br>>> > an environment where the nodes communicate via directed antennas and<br>
>> > where they are not in a full mesh. To do this I'm planning to use<br>>> > several ad-hoc networks running on different channels.<br>>> ><br>>> > I'm not sure whether OLSR is able to handle the routing across<br>
>> > multiple ad-hoc networks, each of which is running on a different<br>>> > channel.<br>>> ><br>>> > Please could someone clarify this and/or point me to any resources for<br>>> > configuration in such an environment?<br>
>> ><br>>> > Thank you,<br>>> > Duncan<br>>> ><br></div></div><div class="">>> > --<br>>> > Olsr-users mailing list<br>>> > <a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>
>> > <a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br>>><br>>> --<br>>> Olsr-users mailing list<br>>> <a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>
>> <a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br>><br>><br>><br>><br>> --<br>> Ben West<br></div><div class="">
> <a href="mailto:me@benwest.name" target="_blank">me@benwest.name</a><br><br><br><br>-- <br>PGP public key -<br><a href="http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA3B79B579009DCA2" target="_blank">http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA3B79B579009DCA2</a><br>
<br><br><br></div>------------------------------<br><br>Message: 6<br>Date: Tue, 11 Feb 2014 11:13:44 +1030<br>From: Kim Hawtin <<a href="mailto:kim@hawtin.net.au" target="_blank">kim@hawtin.net.au</a>><br>To: <a href="mailto:olsr-users@lists.olsr.org" target="_blank">olsr-users@lists.olsr.org</a><br>
Subject: Re: [Olsr-users] OLSR Across Multiple Channel Ad-hoc<br> Networks?<br>Message-ID: <<a href="mailto:52F97240.1060907@hawtin.net.au" target="_blank">52F97240.1060907@hawtin.net.au</a>><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<div class="">
<br><br>Hi Duncan,<br><br>On 11/02/14 08:52, Duncan Eastoe wrote:<br>> I'm only interested in multiple wireless interfaces per node so<br>> shouldn't be a problem?<br><br>I've done this in the past with multiple wifi interfaces with the same <br>
ssids on different channels. I ran into problems where the chipset would <br>jump channels to be on the same ssid as an existing adhoc mesh.<br><br>So initially I would suggest naming your channels with different ssids.<br>
<br>Also would be interesting to see if this bug is in modern wifi chipsets.<br><br>regards,<br><br>Kim VK5FJ<br><br><br><br></div>------------------------------<br><br>Message: 7<br>Date: Mon, 10 Feb 2014 23:29:18 -0600<br>
From: Ben West <<a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a>><br>To: <a href="mailto:kim@hawtin.net.au" target="_blank">kim@hawtin.net.au</a><br>Cc: olsr-users <<a href="mailto:olsr-users@lists.olsr.org" target="_blank">olsr-users@lists.olsr.org</a>><br>
Subject: Re: [Olsr-users] OLSR Across Multiple Channel Ad-hoc<br> Networks?<br>Message-ID:<br> <CADSh-SOFPO43n3+r7VTOFQ5H9XE0DTiBf1dZmNCn8Bvk68=<a href="mailto:Ong@mail.gmail.com" target="_blank">Ong@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<div><div class="h5"><br><br>I believe OpenWRT's restriction on not letting adhoc wireless interfaces<br>join bridges would also mean multiple wireless adhoc interface could not be<br>
bridged together directly to share the same IP address, if that is<br>desired. Traffic between such interfaces would have be routed explicitly<br>(i.e. each radio sits on its own IP subnet, OLSRd computes routes between<br>
them), or you could create a VLAN and bridge the interfaces indirectly with<br>trelay.<br><a href="https://dev.openwrt.org/ticket/10108" target="_blank">https://dev.openwrt.org/ticket/10108</a><br><br>As for Duncan's experience with broadcasting the same SSID on multiple<br>
channels, that may have conflicted with the roaming function implemented in<br>whichever 802.11 chipsets were being used. Clients seeing the same SSID<br>on different channels may try to roam freely between each AP, and the<br>
behavior Duncan observed could have been those clients' roaming behavior as<br>implemented for adhoc.<br><br><br><br>On Mon, Feb 10, 2014 at 6:43 PM, Kim Hawtin <<a href="mailto:kim@hawtin.net.au" target="_blank">kim@hawtin.net.au</a>> wrote:<br>
<br>> Hi Duncan,<br>><br>><br>> On 11/02/14 08:52, Duncan Eastoe wrote:<br>><br>>> I'm only interested in multiple wireless interfaces per node so<br>>> shouldn't be a problem?<br>>><br>
><br>> I've done this in the past with multiple wifi interfaces with the same<br>> ssids on different channels. I ran into problems where the chipset would<br>> jump channels to be on the same ssid as an existing adhoc mesh.<br>
><br>> So initially I would suggest naming your channels with different ssids.<br>><br>> Also would be interesting to see if this bug is in modern wifi chipsets.<br>><br>> regards,<br>><br>> Kim VK5FJ<br>
><br>><br>> --<br>> Olsr-users mailing list<br>> <a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>> <a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br>
><br><br><br><br>-- <br>Ben West<br><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br><a href="tel:314-246-9434" value="+13142469434" target="_blank">314-246-9434</a><br>
</div></div>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.olsr.org/pipermail/olsr-users/attachments/20140210/d8f7d8fc/attachment.html" target="_blank">http://lists.olsr.org/pipermail/olsr-users/attachments/20140210/d8f7d8fc/attachment.html</a>><br>
<br>------------------------------<br><br>Subject: Digest Footer<div class=""><br><br>-- <br>Olsr-users mailing list<br><a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br><a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br>
<br></div>------------------------------<br><br>End of Olsr-users Digest, Vol 80, Issue 5<br>*****************************************<br><br>--<br>
Olsr-users mailing list<br>
<a href="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</a><br>
<a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/mailman/listinfo/olsr-users</a><br></blockquote></div><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br>
<a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>314-246-9434<br></div>
</div>