Jouni Hartikainen

I seem to have this same problem. Instead of having ZT traffic going over itself using IPv4 address of the remote LAN my problem seems to caused by IPv6 address...

It seems that I was able to fix my problem by adding the bridge interface on the remote LAN end to `interfacePrefixBlacklist` on `local.conf`. Now the IPv6 address still propagates...

Here's some information about the `local.conf` file: https://github.com/zerotier/ZeroTierOne/tree/master/service On Debian it should be placed to `/var/lib/zerotier/local.conf` (assuming you have installed ZeroTier from prebuilt .deb package).

Don't know about your specific setup, but for me blacklisting using IP address helped. My `local.conf` (with IP address obfuscated): ``` { "physical": { "2001:2003:xxxx:xxxx::/56": { "blacklist": true } }...

I poked around with the code and came up with a solution that - albeit a bit hackily - adds support for the `-nv` style input transparently to all PGNs....

Added a small helper for constructing -nv style input fields for test JSON as I noticed that its quite error prone to write JSON strings by hand: https://github.com/chacal/n2k-signalk/commit/00b6f056200a23170b11251eea9df190ca7de560