<br><br><div class="gmail_quote">On Fri, Feb 10, 2012 at 11:54 PM, Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@guardianproject.info">hans@guardianproject.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
It sounds like then the the IP addresses in OLSR networks must be<br>
manually set on each computer on order to work. Basically, you need to<br>
know the ip range and netmask of the nearest neighbors, correct?<br></blockquote><div>if u manually set the olsrd broadcast address in configfile, you only have to know this,..</div><div>(and it can be 255.255.255.255) if you do this u can use a /32.</div>
<div><br></div><div>if not setting the address manually olsrd uses the one from the interface, and than yes u have to configure the interfaces correctly on the nodes</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>
My goal is to make a "zeroconf" test network for the Debian package, so<br>
newbies can just "apt-get install olsrd" then "/etc/init.d/olsrd start"<br>
and have some kind of basic mesh working. Therefore, it seems that<br>
ahcpd is essential for that goal.<br>
<br>
.hc<br>
<div><div class="h5"><br>
On 02/10/2012 03:09 PM, Markus Kittenberger wrote:<br>
> in a mesh network, neither .. /16 or /17 or /18 ... /30 or /32 is<br>
> correct, but usually anything (which is not too big) works.. (if the<br>
> mesh routing software (e.g. olsrd) does work)<br>
><br>
> e.g. with a netmask of /32 you infact define that a node has no<br>
> neighbours! (as its alone in its own network, and there is no<br>
> network-route to anyone)<br>
> and u need a mesh routing software to add known neighbours,.. (and host<br>
> routes to them)<br>
><br>
> while e.g. if u use a /24, the node has a network route to this /24, and<br>
> thinks it has up to 255 neighbours (in its subnet) which are one hop<br>
> away (which is usually wrong!)<br>
> so you need to add a mesh routing software to add routes (via correct<br>
> direct neighbours) to the nodes that are multiple hops away (else this<br>
> node will try and (most often) fail to communicate directly with all<br>
> neighbours within the subnet)<br>
><br>
> main difference (regarding unwanted side effects), in the latter case<br>
> you have unwanted packets (e.g. many/repeated stupid arp-requests),<br>
> while in the first u have no change to communicate from one hop to its<br>
> direct neighbour if the mesh routing software e.g. crashed<br>
><br>
> i hope this clarified things, if not:<br>
><br>
> yes u are overthinking,... (-;<br>
><br>
> Markus<br>
><br>
> (btw did u mange to ping between 2 nodes (without olsrd) via adhoc already?)<br>
><br>
> On Fri, Feb 10, 2012 at 8:52 PM, Hans-Christoph Steiner<br>
</div></div><div class="im">> <<a href="mailto:hans@guardianproject.info">hans@guardianproject.info</a> <mailto:<a href="mailto:hans@guardianproject.info">hans@guardianproject.info</a>>> wrote:<br>
><br>
><br>
> Maybe I'm overthinking this, but I can't seem to wrap my head around<br>
> what each computer should have set for its netmask. It seems to me<br>
> that each node on the network should have a netmask of<br>
> 255.255.255.255 since each node has an entry individually. But then<br>
> I see that mesh networks use a defined set, like <a href="http://10.10.0.0/16" target="_blank">10.10.0.0/16</a><br>
</div>> <<a href="http://10.10.0.0/16" target="_blank">http://10.10.0.0/16</a>>. Is that just to define an IP for a given<br>
<div class="im">> mesh? Or should each computer also have a netmask of 255.255.0.0?<br>
><br>
> .hc<br>
><br>
> ----------------------------------------------------------------------------<br>
><br>
> "It is convenient to imagine a power beyond us because that means we<br>
> don't have to examine our own lives.", from "The Idols of<br>
> Environmentalism", by Curtis White<br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> Olsr-users mailing list<br>
</div>> <a href="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</a> <mailto:<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>
><br>
><br>
</blockquote></div><br>