Comment on Question about traffic using Cloudflare tunnel

curbstickle@lemmy.dbzer0.com ⁨2⁩ ⁨months⁩ ago

• CameronDev@programming.dev ⁨2⁩ ⁨months⁩ ago

  I dont know that that is true. With cloudflare tunnels, their server.x.y.z will resolve to a cloudlfare IP address, which then tunnels it to their server? The traffic has to hit the cloudflare server, it can’t short circuit that connection? Am I missing something?

  source

  • curbstickle@lemmy.dbzer0.com ⁨2⁩ ⁨months⁩ ago

    Depends on the server obviously, but most will pass off their local once the initial handshake is made.

    Once that is done, DNS isnt relevant anymore.

    source

    • SteveTech@programming.dev ⁨2⁩ ⁨months⁩ ago

      Uhh, this might be true for WebRTC, except not much uses WebRTC other than realtime streaming/calling. Jellyfin for example is just an mp4 stream over http; and http(s) will only use the IP in the DNS record. I’d like to see a packet capture if are certain something is switching IP.

      source
    • CameronDev@programming.dev ⁨2⁩ ⁨months⁩ ago

      How does that work? Do they do something like what tailscale does to negotiate the connection? Can you point me to any doco for how that works?

      source

      • rumba@lemmy.zip ⁨2⁩ ⁨months⁩ ago

        Plex does this on its own. It’s one of the features they provide. The client/service knows when the server is local even though you go outside to make the initial connection. They go through a lot of trouble to do this. You connect externally it brokers the initial connection proxies date of back and forth to see if you can talk to each other directly, your client knows your server is now local and it switches over.

        I don’t know if any other video hosting package that does this. Jellyfin certainly would not. I ‘think’ if you threw a tailscale in the middle, It would be able to do it without hair pinning as long as you were using a local exit node instead of tailnet. They’d still probably go through that local exit node.

        source

        • -> View More Comments
      • curbstickle@lemmy.dbzer0.com ⁨2⁩ ⁨months⁩ ago

        Remember that we’re talking about a server on your local network, and a device on the local network to make the connection for the stream. We aren’t talking about streaming over the internet.

        • Client looks up server via DNS
        • Client connects to public IP
        • Client handshakes to server
        • Server announces to client available connections (public, local)
        • Client continues connections with local address

        There is no need for tailscale or anything, this is a local connection. The only thing the public address is doing is the initial call to the server.

        source

        • -> View More Comments