16 Mar
2018
16 Mar
'18
4:41 a.m.
Hi!
On Thu, Mar 15, 2018 at 03:53:37PM -0600, Paul Harmor wrote:
Well damn, Bruno... Horrible and ugly as this may
sound, glad I wasn't the
only one. But why did nobody seem to have any clue of the issue? I've been
struggling with this for weeks now, and chatting about it for over a week,
and nobody seemed to be aware of what you and I experienced with the chef
builds. I was very clear about the fact that I was building from chef, and
nobody said a word about it being a known issue.
I also saw that gateway detection now doesn't work well with bmx7 and
investigated the issue and it's much more simple than you think:
The hook in /etc/watchping/wan-ok.d/bmx7-gw gets called before bmx7 is
even up and running in case the wan interface is being brought up too
quickly during boot.
To work-around that issue, please try the patch below and let me know
if it resolved the issue for you as well
diff --git a/packages/bmx7-auto-gw-mode/files/etc/watchping/wan-fail.d/bmx7-gw
b/packages/bmx7-auto-gw-mode/files/etc/watchping/wan-fail.d/bmx7-gw
index cfb9e2e..988aa3d 100755
--- a/packages/bmx7-auto-gw-mode/files/etc/watchping/wan-fail.d/bmx7-gw
+++ b/packages/bmx7-auto-gw-mode/files/etc/watchping/wan-fail.d/bmx7-gw
@@ -1,4 +1,12 @@
#!/bin/sh
+timeout=60
+while ! bmx7 -c -v 2>&1 >/dev/null ; do
+ logger -t bmx7-auto-gw "waiting for bmx7 to come up..."
+ sleep 1
+ timeout=$((timeout - 1))
+ [ $timeout -lt 1 ] && break
+done
+
logger -t bmx7-auto-gw "Searching Internet access into the mesh"
bmx7 -c tunIn -inet4
bmx7 -c tunOut inet4 /network 0.0.0.0/0 /maxPrefixLen 0
diff --git a/packages/bmx7-auto-gw-mode/files/etc/watchping/wan-ok.d/bmx7-gw
b/packages/bmx7-auto-gw-mode/files/etc/watchping/wan-ok.d/bmx7-gw
index a55f532..592c904 100755
--- a/packages/bmx7-auto-gw-mode/files/etc/watchping/wan-ok.d/bmx7-gw
+++ b/packages/bmx7-auto-gw-mode/files/etc/watchping/wan-ok.d/bmx7-gw
@@ -1,4 +1,12 @@
#!/bin/sh
+timeout=60
+while ! bmx7 -c -v 2>&1 >/dev/null ; do
+ logger -t bmx7-auto-gw "waiting for bmx7 to come up..."
+ sleep 1
+ timeout=$((timeout - 1))
+ [ $timeout -lt 1 ] && break
+done
+
logger -t bmx7-auto-gw "We got Internet access, announcing it to the mesh"
bmx7 -c tunOut -inet4
bmx7 -c tunIn inet4 /n 0.0.0.0/0
---
I VERY much agree, that the chef server should either be taken offline, or
at the VERY LEAST no longer linked from the main page of libremesh.org,
until these issues have been resolved.
Hopefully by experience (and publicizing of it) will get the ball rolling
in the right direction, on that.
On Thu, Mar 15, 2018 at 2:54 PM, bruno vianna <bruno(a)pobox.com> wrote:
>
> In the end, the solution came from installing an image on each directly
>> downloaded from libremesh.org, instead of built on the chef server.
>> Seems the chef server is building them broken.
>>
>>
>
> We had the same experience at the installations we've made. IMHO, the new
> chef should be off-line until these issues are worked out. It's been
> creating a frustrating experience for many users.
>
> On the other hand, the lime-sdk cooker script is working really well.
>
> Bruno
>
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
>
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users