Comment on Do you know a remote NAS backup solution without Tailscale?

• litchralee@sh.itjust.works ⁨10⁩ ⁨hours⁩ ago

  Why would UDP be any more difficult than TCP (or anything else) for troubleshooting? If nothing else, it should be easier because there are no stateful connections and every packet is “fire and forget”. Now, as a tunneling technology, WG might be more difficult than a simple client/server socket-driven application, but that just means some routing tables need to be inspected and you have to understand IP subnets. In any case, you’d still want to obtain packet traces from both ends of the WG tunnel.

  original

  • northertech@fedia.io ⁨9⁩ ⁨hours⁩ ago

    With TCP there are built in listeners on OSs which you can use to test. Also TCP will work before UDP. For whatever reason firewalls and such do weird things with UDP traffic. I always use a cli tool that I can't remember the name of for testing.

    original

    • litchralee@sh.itjust.works ⁨7⁩ ⁨hours⁩ ago

      What are these “built in listeners” that you speak of, and which OS’s can I find this on?

      Also TCP will work before UDP. For whatever reason firewalls and such do weird things with UDP traffic.

      This doesn’t really explain why troubleshooting is more difficult, but rather that firewalls often cause trouble for UDP. My question was “why would diagnosing a UDP problem be harder than anything else?”, not “why is UDP more problematic?”. I’m fully aware that some firewalls are configured with absurd parameters, like blocking ICMP, QUIC, or even TLS in some bizarre situations. But my tools for debugging network troubles have always been the same: tcpdump for passive tracing, nc to coerce an active response, and icmp/icmp6 ping for basic connectivity and MTU verification.

      Whether it’s UDP or anything other protocol, those tools have proven sufficient for me. Do you use something else?

      original