Defining a derp server (and removing default ones) disables direct connection #254

Closed
opened 2025-12-29 01:25:06 +01:00 by adam · 1 comment
Owner

Originally created by @Patralos on GitHub (Apr 11, 2022).

Hi,

I have the problem, that as long as I keep the default derp configuration, I am using direct mode between nodes, visible in tailscale status.

As soon as I remove the official derp servers by removing the setting urls:
urls: []

All connections go over my relay, none of them is direct anymore.

My derp file looks like this:

regions:
  900:
    regionid: 900
    regioncode: Name
    regionname: Name
    nodes:
      - name: 900a
        regionid: 900
        hostname: url

Is this intended behavior? Is it possible to use direct connections while running a private relay?

Originally created by @Patralos on GitHub (Apr 11, 2022). Hi, I have the problem, that as long as I keep the default derp configuration, I am using direct mode between nodes, visible in tailscale status. As soon as I remove the official derp servers by removing the setting urls: `urls: []` All connections go over my relay, none of them is direct anymore. My derp file looks like this: ``` regions: 900: regionid: 900 regioncode: Name regionname: Name nodes: - name: 900a regionid: 900 hostname: url ``` Is this intended behavior? Is it possible to use direct connections while running a private relay?
adam added the bug label 2025-12-29 01:25:06 +01:00
adam closed this issue 2025-12-29 01:25:06 +01:00
Author
Owner

@Patralos commented on GitHub (Apr 11, 2022):

Nevermind, when adding the relay, I changed a nat rule

@Patralos commented on GitHub (Apr 11, 2022): Nevermind, when adding the relay, I changed a nat rule
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#254