Entry in node logs at startup - what is the correct interpretation please of relay manager disabled

Support
1

I was looking at the node logs and noticed in the beginning of the logs the message

...:driver 571] Relay manager is disabled for this node.

Does this mean the node will not be providing relay services for home-network nodes?

Or does it mean it is not using a manager to ask other nodes for relay of messages to other nodes?

Without knowing the answer the message does not say if its not acting as a relay for other nodes or not requiring relay nodes to help it.

BTW this is a port forwarded node.

5 Likes
2

I have the same on a 20% of my 20 VPS nodes

[2025-03-15T17:14:25.676559Z INFO ant_networking::driver 571] Relay manager is disabled for this node.

4 Likes
3

I think this means the node could not be persuaded it was on a connection that was connectable from the outside for some reason.

2 Likes
4

These nodes get asked for quotes, so it is odd.

This is a dual network and I have set the default gateway to one of the network ports. But still the logs listen on both network ports.

I tried the option to specify the network port to use but it just could not start the node (usually into lala land), even tried a few ways to specify the network adaptor/port.

1 Like
5

It’s a very active area in dev right now, KAD close group investigations and NAT device detection proper.

6 Likes
6

Be interesting to see the results when they have ironed out the issues.

3 Likes
7

I’m still not convinced it’s solely bugs in the node software but might be connected to some bottleneck on the node runner machines that might be hit (disk I/O / network in some way) and therefore slowing down all network operations … but I guess when KAD and NAT stuff is well investigated and the team doesn’t spot bugs anymore but just slow answering speeds this can be easier debugged/resolved then

one step at a time …

6 Likes