[mesh-dev] makenode DHCP range

Alexander Papazoglou papazoga at gmail.com
Wed Oct 15 16:37:07 PDT 2014


Just double checked; it is relative to the NETWORK address (which is
10.0.0.0 for us), so what we're
doing makes sense.

Alex

2014-10-15 13:47 GMT-07:00 Max B <maxb.personal at gmail.com>:

>  I agree that the documentation suggests that we should be able to just
> use a standard offset, but I'm fairly certain that in practice that is not
> the case. I remember pretty specifically wasting several hours trying to
> figure out why the hell I was getting incorrect dchp lease addresses.
>
> Worth taking a look at though just to double check....
>
>
> On 10/15/14, 9:35 AM, Alexander Papazoglou wrote:
>
>  I believe we're setting the mesh_dhcp_range_start option incorrectly. The
> wiki (http://wiki.openwrt.org/doc/uci/dhcp) says it should be the offset
> from the network address of the interface. So we should be able to set this
> to, say, 50 for all nodes.
>
>  I can't seem remember how this worked in practice though. None of the
> running nodes I have access to had any dhcp.leases for me to check.
>  Something to test on Thurs.
>
> Alex
>
>
> _______________________________________________
> mesh-dev mailing listmesh-dev at lists.sudoroom.orghttps://lists.sudoroom.org/listinfo/mesh-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sudoroom.org/lists/private/mesh-dev/attachments/20141015/92a050df/attachment.html>


More information about the mesh-dev mailing list