home nodes depend on static exit node ips

[jhpoelen]

currently, home nodes have configuration that is tied to specific exit node ip (mesh+internet) in addition to the required list of brokers for tunneldigger client in /etc/config/tunneldigger.

suggest to remove dependencies on exit node ip (mesh+internet) outside of the configuration in /etc/config/tunneldigger.

Why now? We setting up a second (ed. third actually...) exit node and would like to be able to bridge the mesh between the two. This means that the exit nodes have to have distinct mesh ips. Right now, home nodes are hardcoded to expect a exit node at 100.65.0.42 .

[jhpoelen]

This issue has been resolve in latest version of makenode. Also, a patch is available at https://github.com/sudomesh/patches/tree/master/bug0023 .

[bennlich]

I notice on my home node I have a file called /etc/resolv.conf.dnsmasq that also contains the exit node mesh ip:

root@pattyspuddles:~# cat /etc/resolv.conf.dnsmasq
# These are the upstream DNS servers used by dnsmasq

nameserver 100.64.0.42 # sudomesh exit server
nameserver 209.244.0.3 # Level3 primary DNS
nameserver 209.244.0.4 # Level3 secondary DNS
nameserver 84.200.69.80 # dns.watch primary DNS
nameserver 84.200.70.40 # dns.watch secondary DNS
nameserver 2001:1608:10:25::1c04:b12f # dns.watch primary IPv6 DNS
nameserver 2001:1608:10:25::9249:d69b # dns.watch secondary IPV6 DNS

See https://github.com/sudomesh/makenode/blob/master/configs/templates/files/etc/resolv.conf.dnsmasq#L3.

[bennlich]

Looks like you addressed this in the patch, but maybe not in the makenode commit?

[jhpoelen]

@bennlich nice catch!

[bennlich]

I think this patch might need to include this change too:
sudomesh/makenode@f23342d

(because the patch deletes the $INETEXITIP variable)

[bennlich]

I was able to apply, revert, and reapply this patch without issues besides the above! The above issue is non-catastrophic. Just results in the following error getting logged:

Thu Mar 22 22:42:04 2018 user.emerg syslog: Error: an inet prefix is expected rather than "/32".

[jhpoelen]

@bennlich great to hear that you were able successfully apply patch https://github.com/sudomesh/patches/tree/master/bug0023 ! Thanks for testing it. I made the changes you suggested to fix the (non-breaking) patch omission to remove the routing rule from /etc/init.d/meshrouting .