[Mesh] WD N600 Router not Meshing

[danarauz at gmail.com]

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
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sudoroom.org/pipermail/mesh/attachments/20191204/60bf32c4/attachment.html>