Thanks Mark.

On 29/07/19 5:37 pm, Mark Birss wrote:
David

I noticed a while back that I lost the ability to access my connected wifi ap with 10.13.0.1, but used dnsmasq-lease-share and my arp cache to find my connected noted and the other by viewing /tmp/dhcp.x.remote

but this was actually lime-proto-anygw that was missing because i was including dnsmasq-lease-share

but all still was fine since mesh nodes could still access the internet via the 1 mesh node that had internet access

I have now removed dnsmasq-lease-share and included shared-state-dnsmasq_leases that has brought back lime-proto-anygw that allows local connected mesh ap access via 10.13.0.1

Hope that helps you also

Regards

On Mon, Jul 22, 2019 at 8:41 AM David Medland-Slater <david.medlandslater@gmail.com> wrote:

Very, very useful information Mark and thanks very much for those, especially the metamesh info


On 22/07/19 6:06 pm, Mark Birss wrote:
David

I have been using a mix of LibreRouter config and what was the old notes, and actually was not including lime-proto-anygw 

I was including dnsmasq-lease-share. 

I will now check with your response from SAn about using shared-state-dnsmasq_leases instead and what effect it has

What might be usefull is to understand about how these packages actually work or at lease what files it generates


Other OLSR based resources you can look at if you are interested

 
Regards



On Sun, Jul 21, 2019 at 10:39 AM David Medland-Slater <david.medlandslater@gmail.com> wrote:
Very much appreciated!  I'll give that a go....

On 21/07/19 8:31 pm, SAn wrote:
> Hi David!
>
> I think the problem is that the documentation is not in sync with the last developments we have been doing moving away from alfred to maintain shared state and using a new development called shared-state do do it. So now lime-proto-anygw depends on shared-state-dnsmasq_leases instead of dnsmasq-lease-share. Sorry about this! We will fix the docs.
>
> Here you can find the config that we are using for the LibreRouter firmware: https://github.com/LibreRouterOrg/openwrt/blob/librerouter-18.06/configs/default_config . We have been keeping this config in sync with libremesh-development.
>
> Best!
> SAn
>
> On 7/21/19 2:28 AM, David Medland-Slater wrote:
>> Well at least I'm not going mad then!  Could I perhaps ask for some
>> general advice Mark on building a more up to date libremesh.  I'm
>> running the released version but on another project I've found plain
>> vanilla openwrt 18 is considerably better than 17.  Is there a sensible
>> path to get a libremesh 18?  This is for a home lab, nothing fancy
>> running only 3 nodes, so it doesn't need to be production quality.  I
>> had hoped the development.html web page would be enough to give me
>> working build options, but as you have seen, I'm not making much progress.
>>
>> With v17, I make use of the distributed DHCP, although I could live
>> without that if it was problematic.
>>
>> Thanks in advance ...
>>
>> On 21/07/19 8:49 am, Mark Birss wrote:
>>> yes, lime-proto-anygw disappear when selecting dnsmasq-lease-share.
>>>
>>> but seems i dont use it for my builds. I use BATMAN-adv gw mode
>>>
>>>
>>> On Sat, Jul 20, 2019 at 10:25 PM David Medland-Slater
>>> <david.medlandslater@gmail.com <mailto:david.medlandslater@gmail.com>>
>>> wrote:
>>>
>>>       Yes that gives me the same result Mark.  For me then, at the point of
>>>       running menuconfig, lime-proto-anygw is visible.  Enable
>>>       dnsmasq-lease-share and it disappears.  As from the docs both need
>>>       to be
>>>       selected, I appear to be stuck.
>>>
>>>       Do you get the same effect; selecting dnsmasq-lease-share makes
>>>       lime-proto-anygw disappear and if you search, it has been deselected?
>>>
>>>
>>>       On 21/07/19 6:58 am, Mark Birss wrote:
>>>       > echo "CONFIG_PACKAGE_dnsmasq=n" >> .config
>>>       > echo "CONFIG_PACKAGE_dnsmasq-dhcpv6=y" >> .config
>>>       > echo "CONFIG_PACKAGE_odhcpd=n" >> .config
>>>       > make defconfig
>>>       _______________________________________________
>>>       lime-dev mailing list
>>>       lime-dev@lists.libremesh.org <mailto:lime-dev@lists.libremesh.org>
>>>       https://lists.libremesh.org/mailman/listinfo/lime-dev
>>>
>>>
>>> _______________________________________________
>>> lime-dev mailing list
>>> lime-dev@lists.libremesh.org
>>> https://lists.libremesh.org/mailman/listinfo/lime-dev
>> _______________________________________________
>> lime-dev mailing list
>> lime-dev@lists.libremesh.org
>> https://lists.libremesh.org/mailman/listinfo/lime-dev
>>
_______________________________________________
lime-dev mailing list
lime-dev@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev

_______________________________________________
lime-dev mailing list
lime-dev@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
_______________________________________________
lime-dev mailing list
lime-dev@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev

_______________________________________________
lime-dev mailing list
lime-dev@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev