[Mesh] WD N600 Router not Meshing

[danarauz at gmail.com]

Yes, me too.

About the NetOps seems like a good question, because from the distance I
see it that it is possible to only hard core folks. Which it is good, but
certainly there may be some tasks for lower level folks as well.

Thanks for the update Matt, good info.







On Thu, Dec 5, 2019 at 5:55 PM Matt Senate <mattsenate at gmail.com> wrote:

> More than one person mentioned at the meetup on tuesday that they
> power-cycle their routers up to about once per week in order to ensure it
> continues to properly function. I wonder if there are bugs, and I asked
> folks to check their logs and see if there are any obvious errors.
>
> We also discussed seeing these types of issues as potential usability
> improvements -- how do we make it easier for folks to become network
> operators and for end users to get a consistent and positive experience?
>
> Glad it's working though!
>
> On Thu, Dec 5, 2019 at 1:27 PM danarauz at gmail.com <danarauz at gmail.com>
> wrote:
>
>> I just checked and it seems that the routers and meshes’ e-god may have
>> had mercy on me.
>>  The router is meahing right now. I didn’t do anything to it.
>>
>> A bit confused.
>>
>> D
>>
>> On Monday, December 2, 2019, danarauz at gmail.com <danarauz at gmail.com>
>> wrote:
>>
>>> Mesh-folks,
>>>
>>> I have flashed the WD N600 router twice, and it fails to connect to the
>>> mesh. As far I was able to tell, the second time it connected, but after 1+
>>> hour the fun ended.
>>>
>>>
>>> LOGS:
>>>
>>> *babeld log:*
>>> "<snip>
>>> Interface eth0.1 has no link-local address.
>>>
>>> setsockopt(IPV6_LEAVE_GROUP): Cannot assign requested address
>>>
>>> Interface eth0.2 has no link-local address.
>>>
>>> setsockopt(IPV6_LEAVE_GROUP): Cannot assign requested address
>>> <snip>"
>>>
>>> *messages log:*
>>> "<snip>
>>>
>>> Sun Dec  1 23:47:49 2019 daemon.err td-client: Failed to resolve
>>> hostname 'exit2.sudomesh.org'.
>>>
>>> Sun Dec  1 23:47:49 2019 daemon.err td-client: Failed to resolve
>>> hostname 'exit1.sudomesh.org'.
>>>
>>> <snip>"
>>>
>>>
>>>
>>> *Question:*Is there a script|command to trigger the IP acquisition? Or
>>> is it a DNS issue on the exit node end?
>>>
>>>
>>> Mesh-merize me,
>>>
>>>
>>> Daniel
>>>
>>>
>>>
>>>
>>> _______________________________________________
>> mesh mailing list
>> mesh at lists.sudoroom.org
>> https://sudoroom.org/lists/listinfo/mesh
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sudoroom.org/pipermail/mesh/attachments/20191205/e94911ea/attachment.html>