<br><br><div class="gmail_quote">On Tue, Sep 27, 2011 at 2:29 PM, Eric Malkowski <span dir="ltr"><<a href="mailto:eric@bvwireless.net">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;">
Hi All-<br>
<br>
It's been a while since I've posted here and I'm still using OLSR 0.5.8-r6 (latest stable of that series before 0.6.X came out).<br></blockquote><div>use a newer one,</div><div>(0.6.2 will be released soon) </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I have a basic question about listing networks as HNA in the config and the "Active" interfaces one does OLSR on </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
I usually never list a subnet in the HNA list at the beginning of the config file AND list the interface that the HNA subnet is tied to for "active" OLSR at the end of the file. I have run into a situation where it would be beneficial to do this. Is it OK to do this?<br>
</blockquote><div>the order or config entries makes no difference here,..</div><div>(probably the only config option where order matters in the configfile is the ipversion (ipv4 or ipv6))</div><div><br></div><div>furthermore it does not matter to announce the network the olsrd itnerface is part of, as hna aswell,..</div>
<div><br></div><div>Markus</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
An example could be like this -- two typical mesh + ap nodes out of range of each other but connected with a simple wired interface:<br>
<br>
Outdoor node:<br>
<br>
ath0 AP network listed only as HNA <a href="http://10.23.0.1/16" target="_blank">10.23.0.1/16</a><br>
ath1 Mesh <a href="http://10.5.0.3/24" target="_blank">10.5.0.3/24</a> (does active OLSR, NOT listed as HNA in config)<br>
eth0 Glue network <a href="http://10.0.3.1/24" target="_blank">10.0.3.1/24</a> (does active OLSR NOT listed as HNA in config)<br>
<br>
Other node connected by wired link:<br>
<br>
eth0 Glue network <a href="http://10.0.3.2/24" target="_blank">10.0.3.2/24</a> (does active OLSR NOT listed as HNA in config)<br>
ath1 Mesh <a href="http://10.5.0.5/24" target="_blank">10.5.0.5/24</a> (does active OLSR, NOT listed as HNA in config)<br>
ath0 AP network listed only as HNA <a href="http://10.25.0.1/16" target="_blank">10.25.0.1/16</a><br>
<br>
I've found that even though the two ath1 interfaces (on same subnet) are separated by the wired link, clients on each ath0 networks of either node enjoy connectivity everywhere.<br>
<br>
What I do is have one of the two nodes act as a convenience DHCP server on eth0 so if someone plugs in a wired client, they can get an IP. If internet is available, the default route gets them internet access. However since the eth0 network <a href="http://10.0.3.1/24" target="_blank">10.0.3.1/24</a> is not listed as an HNA by at least ONE of the two nodes, someone on eth0 w/ a DHCP address may not be able to get everywhere since only host routes are listed for 10.0.3.1 and 10.0.3.2.<br>
<br>
I'd like to simply have each node list their eth0 <a href="http://10.0.3.0/24" target="_blank">10.0.3.0/24</a> network as an HNA in the config. Any ideas if this will be a problem? As I said, I normally don't configure an interface for active OLSR AND to be listed as HNA in the config at the same time as it didn't seem like the right thing to do, but I'm thinking to keep everyone to have full connectivity everywhere who might grab an IP from the networks on ath0 or eth0 of each node, it would make make sense that the eth0 <a href="http://10.0.3.0/24" target="_blank">10.0.3.0/24</a> network is listed as HNA in one of the two nodes' config files or both. The more I think about this I would think it should be fine.<br>
<br>
I hope this makes sense.<br>
<br>
Thanks,<br>
<br>
-Eric Malkowski<br><font color="#888888">
<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/<u></u>mailman/listinfo/olsr-users</a><br>
</font></blockquote></div><br>