11 Mar
2017
11 Mar
'17
12:15 a.m.
On 11/03/17 01:03, Daniel Golle wrote:
Actually I think it has been recently fixed by UFO (the luci-mod-status
bug).
I'll open a new mailing thread to discuss about this issue.
--
./p4u
On Sat, Mar 11, 2017 at 12:08:48AM +0100, Pau wrote:
I've to confirm the bug. I only tested it once. After trying all
possibilities of dnsmasq -F option, the only thing that worked for me
was rolling back dnsmasq. But I've to try again with a new build and
find the way to reproduce it.
On 10/03/17 23:38, Daniel Golle wrote:
Is there a bug filed for that upstream or east for LEDE?
I guess it'd be nice to see this getting fixed... On Fri, Mar 10, 2017 at 11:22:29PM +0100, Pau
wrote:
I add libremesh 17.02 testing pre-release which is based on LEDE 17.01
and LiMe/develop in the automatic building system. It will be soon
available for testing.
So once it is compiled we will make a call for testing. For the moment I
found two possible bugs that must be handled before releasing:
- dnsmasq 2.76 does not work properly with the IPv6 range. Downgrade to
2.75 works. We managed to make the DNS change. So that should
be fixed now.
Amazing. Thanks for the prompt reaction.
Now at least the 16.07 build is available again.
It'd be great to have up-to-date develop builds for ar71xx-mini as
well, seems like the last build is from October, which is too long
ago and obviously before the LEDE 17.01 release... -
luci-mod-status and batman-adv LuCi interface does not work properly
Ok, that we have to deal with ourselves and see what's wrong here...
Probably more will come...
@Daniel would be nice to include your contributions on bmx6-autogw and
IPv6 for the next release. So let me kindly push you to solve the
current issues that are blocking the current pull request
Do we have a consensus with regarding minPrefixLen, maxPrefixLen and
using whether watchping should add/remove a route to 2000::/3 or ::/0?
To me it looked like we concluded to make the naming consistent with
the rest of lime ('publicv6') and use 2000::/3. But the prefix length
was still an ongoing debate and I'm also less flexible there, simply
because I cannot test things with maxPrefixLen >= 64 because all
ARPAnet gateways I have access to only got a single /64 and hence
should not delegate anything shorter than a /72 (ie. max 255 clouds
using that gateway). Thus it's impossible for me to actually test any
setup which involves shorter prefixes.
Also note that the counterpart, the needed changes on the client-side
to make bmx6/7 automatically choose the right prefix and address is
still missing afaik and I don't have time to implement that right now.
Anyway. Let me know what to do, I'll do it, so we can move on :)
Cheers.
--
./p4u
On 10/03/17 23:16, Pau wrote:
>
> On 10/03/17 21:59, Daniel Golle wrote:
>> Hi!
>>
>> All download and snapshot build sites are down:
>> chef.altermundi.net doesn't offer downloads without registering first
>> builds.libremesh.org and downloads.libremesh.org both point to some
>> parking site rather than allowing to download anything.
>>
>> lime-build fails due to chaoscalmer not building due to unavailable
>> openwrt.org resources.
>>
>> It's kinda hard to promote the use of libremesh in this situation.
>>
>> How can we improve this situation?
>
> Not depending on third parties...
> We are using a server from the qmp.cat project for building the firmware
> and storing the binaries. The name downloads.libremesh.org is a CNAME of
> fw.qmp.cat which used to point to the IP 84.88.85.55 (not anymore due a
> domain expiration problem).
>
> I don't have access to the libremesh.org DNS administration, but
> changing the entry from CNAME to A (84.88.85.55) would solve the problem.
>
> Meanwhile this would also partially solve the problem on a local machine:
>
> sudo echo "84.88.85.55 downloads.libremesh.org builds.libremesh.org"
>>
> /etc/hosts
>
> Cheers.
>
>> Cheers
>>
>> Daniel
>> _______________________________________________
>> lime-dev mailing list
>> lime-dev(a)lists.libremesh.org
>> https://lists.libremesh.org/mailman/listinfo/lime-dev
>>
>
>
>
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
>
--
./p4u
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev