A node's location is now taken from its real connection address

SecurityEdge Node

A node could report an address other than the one it connected from, and so choose the city and metro it was listed under. The control plane now uses the address the connection actually came from, which is what leaderboards, badges and placement rely on.

A node’s city and metro are worked out from the IP address it checks in from. That location decides which metro leaderboard it competes on, which badges it can earn, and which sites can be placed on it by region.

Until now, the control plane would accept an address the node supplied itself in place of the one it actually connected from. A node that had been changed to do so could pick the address it was recorded under, and with it the city and metro it appeared in.

The control plane now uses only the address the connection really came from, and ignores anything the node says about its own address. Each node’s next check-in records its real address, and every node was located again on 2 October.

One limit. For a node with no public address of its own, we also record an address that browsers use to reach it directly. One that was already recorded isn’t rechecked. Only new check-ins use the trusted address.

What you need to do

Nothing. A node running our software always reported its real address, so nothing changes for it.

← All changes · More Edge Node changes · Subscribe to Edge Node