LNL Relay / Bridge nodes announcing wrong IP addresses

[bredo228]

Describe the bug?

Occasionally, it appears some of the LNL relay nodes are announcing the wrong IP addresses.

Refreshing https://api.resonite.com/networkNodes occasionally shows incorrect IP addresses to be shown sometimes for some of the relays & bridges

To Reproduce

Look at https://api.resonite.com/networkNodes - occasionally refresh this and you might see the LNL relays / bridges announcing the wrong IP addresses.

Expected behavior

LNL bridges / relays to announce correct IP addresses

Screenshots

Showing usw-1 going back and forth (should have copied text for these, sorry!):

Resonite Version Number

2024.7.20.1115

What Platforms does this occur on?

Windows

What headset if any do you use?

No response

Log Files

Output of https://api.resonite.com/networkNodes with issue occuring (no client logs for this)

[
  {
    "id": "a56939f9a5f1498893a9857953163de0",
    "timestamp": "2024-07-20T21:43:30.322242+00:00",
    "name": "resonite-relay-usw-1",
    "address": "0.0.0.1",
    "port": 53072,
    "nodeType": "LNL_Relay",
    "protocolVersion": 2,
    "userCount": 1,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "a56939f9a5f1498893a9857953163de0",
    "ownerId": "N-NetworkNodes"
  },
  {
    "id": "8a06854c6cec4681b024cd56b650d3e4",
    "timestamp": "2024-07-20T21:43:21.109045+00:00",
    "name": "resonite-bridge-usw-1",
    "address": "5.78.110.95",
    "port": 38842,
    "nodeType": "LNL_NAT",
    "protocolVersion": 2,
    "userCount": 4,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "8a06854c6cec4681b024cd56b650d3e4",
    "ownerId": "N-NetworkNodes"
  },
  {
    "id": "0c7e40e7c2f541fc837abe89085d76f9",
    "timestamp": "2024-07-20T21:43:29.792284+00:00",
    "name": "resonite-bridge-eu-2",
    "address": "0.0.0.2",
    "port": 38974,
    "nodeType": "LNL_NAT",
    "protocolVersion": 2,
    "userCount": 76,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "0c7e40e7c2f541fc837abe89085d76f9",
    "ownerId": "N-NetworkNodes"
  },
  {
    "id": "508b72d1a6b94809b200458c970b8bf8",
    "timestamp": "2024-07-20T21:43:33.385703+00:00",
    "name": "resonite-bridge-eu-1",
    "address": "95.217.33.19",
    "port": 60617,
    "nodeType": "LNL_NAT",
    "protocolVersion": 2,
    "userCount": 8,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "508b72d1a6b94809b200458c970b8bf8",
    "ownerId": "N-NetworkNodes"
  },
  {
    "id": "aa88a3ca2ad84022a67c7d61f47240ca",
    "timestamp": "2024-07-20T21:43:34.405226+00:00",
    "name": "resonite-bridge-jp-1",
    "address": "20.243.107.97",
    "port": 42235,
    "nodeType": "LNL_NAT",
    "protocolVersion": 2,
    "userCount": 39,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "aa88a3ca2ad84022a67c7d61f47240ca",
    "ownerId": "N-NetworkNodes"
  },
  {
    "id": "38c38d330dd04c528139e570df86eec8",
    "timestamp": "2024-07-20T21:43:35.57399+00:00",
    "name": "resonite-relay-eu-2",
    "address": "95.217.33.19",
    "port": 53971,
    "nodeType": "LNL_Relay",
    "protocolVersion": 2,
    "userCount": 0,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "38c38d330dd04c528139e570df86eec8",
    "ownerId": "N-NetworkNodes"
  },
  {
    "id": "7bb52abd7d5c4e91886a24e53cea9594",
    "timestamp": "2024-07-20T21:43:35.650626+00:00",
    "name": "resonite-relay-eu-1",
    "address": "95.217.33.19",
    "port": 51898,
    "nodeType": "LNL_Relay",
    "protocolVersion": 2,
    "userCount": 0,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "7bb52abd7d5c4e91886a24e53cea9594",
    "ownerId": "N-NetworkNodes"
  },
  {
    "id": "8fa91ddb47804634a8bfd0fe23d052ee",
    "timestamp": "2024-07-20T21:43:21.992171+00:00",
    "name": "resonite-bridge-aus-1",
    "address": "20.70.130.78",
    "port": 53234,
    "nodeType": "LNL_NAT",
    "protocolVersion": 2,
    "userCount": 134,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "8fa91ddb47804634a8bfd0fe23d052ee",
    "ownerId": "N-NetworkNodes"
  },
  {
    "id": "ac431dabc4f24b9f86e0bae731785da9",
    "timestamp": "2024-07-20T21:43:26.121973+00:00",
    "name": "resonite-relay-jp-1",
    "address": "20.243.107.97",
    "port": 57538,
    "nodeType": "LNL_Relay",
    "protocolVersion": 2,
    "userCount": 0,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "ac431dabc4f24b9f86e0bae731785da9",
    "ownerId": "N-NetworkNodes"
  },
  {
    "id": "4f9d4978acf54a24a0876d33757887ce",
    "timestamp": "2024-07-20T21:43:41.463965+00:00",
    "name": "resonite-relay-aus-1",
    "address": "20.70.130.78",
    "port": 41275,
    "nodeType": "LNL_Relay",
    "protocolVersion": 2,
    "userCount": 0,
    "capacity": -1,
    "ttl": 120,
    "docDBId": "4f9d4978acf54a24a0876d33757887ce",
    "ownerId": "N-NetworkNodes"
  }
]

Additional Context

No response

Reporters

bredo

[ProbablePrime]

Il run around and statically allocate all their announce addresses at some point today

[ikanimew]

DISPLACER - 2024.7.20.1115 - 2024-07-20 22_27_00.log
From testing a bit here, if I force use relays, the connection fails, so likely this issue. Have a log if it's of use for this. ^^

[XDelta]

Yeah, we experienced this today with Blood on the Clocktower, our temporary solution was making sure players turned off the Always use relay to connect setting for the few that had it set or otherwise picked another relay.

5:35:45 PM.833 (143 FPS)  NetworkInitStart
5:35:45 PM.833 (143 FPS)  Network manager: FrooxEngine.LNL_Manager - priority: 0
5:35:45 PM.833 (143 FPS)  Network manager: FrooxEngine.SteamNetworkManager - priority: -100
5:35:45 PM.833 (143 FPS)  Network manager: FrooxEngine.TCP_Manager - priority: -1000
5:35:45 PM.835 (143 FPS)  LNL Connection for Address: lnl-nat://0c7e40e7c2f541fc837abe89085d76f9/S-6d4d08b3-b080-4b6a-b129-f6e96236770c, World  (Handle: 30. Focus: Background, State: Initializing, InitState: InitializingNetwork, FailState: None, FailReason: , IsDestroyed: False, IsAuthority: False, SyncTick: 1, StateVersion: 1, Time: 0, TimeSinceLastUpdate: 0.0030008 on port 55971. LocalBindIP: 0.0.0.0
5:35:45 PM.835 (143 FPS)  Connecting to: lnl-nat://0c7e40e7c2f541fc837abe89085d76f9/S-6d4d08b3-b080-4b6a-b129-f6e96236770c
5:35:45 PM.835 (143 FPS)  Punchthrough attempt for lnl-nat://0c7e40e7c2f541fc837abe89085d76f9/S-6d4d08b3-b080-4b6a-b129-f6e96236770c: 0
5:35:45 PM.843 (143 FPS)  OnNetworkError, endpoint: 0.0.0.2:38974, socketError: NetworkUnreachable, connection state: Direct, client running: True
5:35:45 PM.843 (143 FPS)  Connection to lnl-nat://0c7e40e7c2f541fc837abe89085d76f9/S-6d4d08b3-b080-4b6a-b129-f6e96236770c closed: World.Error.NetworkError
5:35:45 PM.843 (143 FPS)  Connection lnl-nat://0c7e40e7c2f541fc837abe89085d76f9/S-6d4d08b3-b080-4b6a-b129-f6e96236770c was unsuccessful, trying next available option
5:35:45 PM.843 (143 FPS)  All protocols failed to establish connection

[ProbablePrime]

Slowly fixing this now.

[ProbablePrime]

Ok i've statically assigned all network nodes their valid IPs.

We'll have to see why the default behavior wasn't working but it doesn't really matter now they are statically allocated.