As an example: some people might be using the offerings from Microsoft or Amazon, whilst other people might be running a VM with a VPS somewhere and hosting their apps like Homeassistant, OpenHAB, Node-Red etc there.

I wanted to know if you do something like this, and what might be the downsides to doing something like this.

Thanks!

  • @chaospatterns
    link
    English
    21 year ago

    Tailnet appears to be Tailscale which is Wireguard underneath. This means it operates at layer 3 (IP). However a bunch of smart home stuff (mDNS, WoL, etc) all depend on layer 2 connectivity (same subnet).

    That means some stuff won’t work correctly.

    • @MigratingtoLemmyOP
      link
      11 year ago

      I see. Could you give me a few more examples on what could break if I go forward with this? Will I still need to consider multicast DNS if my DNS server is on-prem (Pi-Hole + Unbound)?

      I remember that it was not possible to route multicast traffic through IPSec earlier, which is why people used to opt for GRE-over-IPSec. But just as IPSec supports multicast traffic now, doesn’t Wireguard too? Or am I missing something important as to why this is not supported?

      • @chaospatterns
        link
        English
        11 year ago

        Will I still need to consider multicast DNS if my DNS server is on-prem (Pi-Hole + Unbound)

        Multicast DNS is separate from DNS, so even if you have Pi-Hole, you’d still have devices using mDNS. It’s possible to route mDNS across separate IP networks seeing as how there’s mDNS relays across VLANs which would suggest Wireguard could support Multicast. Other things use Broadcast (e.g. WoL) which is a bit more challenging to forward across IP networks.

        I’m not familiar with GRE so I couldn’t comment on whether it’s possible or not. I guess it all depends on how confident you are with your networking skills. If you get it working, you should definitely document it and share with others.

        I didn’t quite do what you did, but I ran HA in a Kubernetes cluster which was logically a separate IP network. I had to setup the container with multiple network interfaces and specially craft the route table to forward broadcasts + multicast traffic to the correct network.

        • @MigratingtoLemmyOP
          link
          11 year ago

          Thank you for your reply.

          It seems I need to study mDNS more. I haven’t had the opportunity to play with IOT much, but this is something I never considered.

          I will not be working with GRE over Wireguard though, I’d like to keep it simpler.

          Thanks again, I’ll have a look. Thanks for the tip with k8s