Relay server low bars w/ prerouting redirect

Support
1

I have my Syncthing relay server set up, and my download/upload speeds are good. However, my connection bars are always at the lowest setting when connected through the relay. I saw an old post where someone fixed this by not redirecting the port using prerouting. My question is, why don’t we just run the service on port 443 from the start? What is the purpose of prerouting? Does it provide any security features? I have a cheap VPS currently running only my relay.

Here is my service start command for systemd

ExecStart=/usr/bin/strelaysrv \
    -keys=/etc/strelaysrv \
    -listen ":22067" \ # change to -listen ":443"
    -ext-address ":443" \
    -pools "" \
    -status-srv="" \
    -token="MY_TOKEN" \
    -protocol="tcp"
2

The rating doesn’t take connection metrics into account. It only grades by connection type:

Relay < WAN < LAN

443 is a priviliged port. That means you’d need to run the relay server with more permissions just for the sake of being able to bind to that port. Following good security hygiene, we avoid that by using redirection.

2 Likes
3

Okay, thank you. I will sometimes get a connection that will say the IP of my relay, then sometimes it will say Relay WAN, then LAN. Relay WAN and the IP have equal signal strength. I’ll disregard the signal strength.

5

According to syncthingController.js, it’s actually:

Relay WAN (1 bar) < Relay LAN (2 bars) < (TCP,QUIC) WAN (3 bars) < (TCP,QUIC) LAN (4 bars).

Basically what you said except there’s such a thing as LAN relays, and they’re better than WAN relays, but worse than direct connections.

6

6b5
6b5680×680 77.5 KB

(sorry, couldn’t resist the urge :smiley: )

1 Like