Skip to content

Add Eytak - #236

Merged
Kas-tle merged 2 commits into
GeyserMC:masterfrom
OyuNet:add-eytak
Nov 15, 2026
Merged

Kas-tle merged 2 commits into
GeyserMC:masterfrom
OyuNet:add-eytak

Conversation

@OyuNet

@OyuNet OyuNet commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Adds Eytak to the setup guide.

Eytak runs Geyser for its customers at the node edge (Geyser 2.12.1 Standalone, transport=both: RakNet on UDP 19132, NetherNet with built-in signaling on TCP 19132 and WebRTC on UDP 19133). Customers turn on "Bedrock support" in the panel, which installs Floodgate on their server; Bedrock players then join with the server's own address on port 19132. Only Paper, Purpur and Spigot servers are supported, so the proxy guides are hidden.

Tested: a real phone joined over NetherNet with these steps, and NetherNet traffic from players is live on our nodes, so the entry is not marked confirmed: false.

@OyuNet
OyuNet requested review from a team as code owners November 12, 2026 14:14

@hasankayra04 hasankayra04 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RakNet is deprecated, other then that LGTM.

@rtm516

rtm516 commented Nov 12, 2026

Copy link
Copy Markdown
Member

@OyuNet You should not share a floodgate key between customers as anyone with that key can trick floodgate into spoofing any player.

@OyuNet

OyuNet commented Nov 12, 2026

Copy link
Copy Markdown
Contributor Author

@rtm516 Thanks for flagging this. It’s exactly the risk we designed around, and I should have said so in the description.

The key isn’t shared. Every customer server gets its own randomly generated Floodgate key (16 random bytes, set once per server), and the Geyser key never leaves the node. Geyser hands its logins to our edge proxy over loopback; the edge decrypts the Floodgate data with Geyser’s node-local key and encrypts the same bytes again under the destination server’s own key. Only connections from Geyser’s loopback address are re-keyed. Floodgate data arriving from anywhere else is passed through untouched, so the server’s Floodgate checks it against its own key, which nobody on another server has. A customer can read their own server’s key, but it only works on that server.

We checked production before replying: 176 servers with a key, 176 distinct keys; on one node, all 19 key files on disk are distinct and none matches Geyser’s key.

@hasankayra04 thanks. NetherNet is the main path; we run transport=both only so clients still joining over RakNet aren’t cut off, and will drop it once that’s no longer needed.

@Kas-tle
Kas-tle merged commit f660380 into GeyserMC:master Nov 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants