Direct and relay
Why the dot goes amber, and how to get a direct link back.
Every session tries to go straight between your two computers. When a network blocks that, it goes through a relay instead, and the toolbar says On relay in amber.
Both work. The difference is speed and how much data can flow.
What changes
| Direct | Relay | |
|---|---|---|
| Path | Computer to computer | Through a middle server |
| Delay | Just the network | The network, plus a detour |
| Data rate | What your links can carry | Capped on purpose |
| What the middle sees | Nothing is in the middle | Locked data it cannot open |
The picture is softer on a relay because less data gets through. Small text goes first.
Why it happens
- Mobile networks and some home broadband share one address between many customers. This is the most common cause.
- Strict office firewalls block the direct path.
- No IPv6 on one side, on networks where the older trick fails.
The app cannot talk its way out of these. The relay is there so you still get a session.
Getting back to direct
Use a network with IPv6
Most home internet has it now. It skips the whole problem.
Try a different network on your side
Phone tethering, or getting off a guest network, often flips it straight away.
Look at the other end
A computer behind an office firewall stays on relay no matter what you do. Ask for outgoing UDP to be allowed. Nothing incoming is needed.
Making relay comfortable
Lower the shared computer's resolution. At 1080p or 720p, the same data covers fewer pixels, so text gets readable again. See picture quality.
RealFrame never changes the far computer's resolution on its own.
Relay speed depends on your plan
Free is best-effort. Paid plans get priority. If most of your sessions are relayed, that is the difference you would feel. See plans.