how can I debug discovery?

I’ve setup a discovery and relay server in my LAN because i have more than one subnet.

I have one client on each. They both connect to the central gateway which is running both discovery and relay server.

i’ve setup both clients to listen on: tcp://0.0.0.0:22000,quic://0.0.0.0:22000,relay://10.0.0.1/?id=MYLONGID

Both clients show on logs “joining relay…” and on the GUI they do show 3 listeners always:

quic://0.0.0.0:22000
relay://10.0.0.1....
tcp://0.0.0.0:22000

they also both show always 2 discoveries:

IPv4 local
global@https://10.0.0.1.....

At this point, clicking add new devices doesn’t show the IDs as if they were on local discovery. And adding the IDs manually just keep them always “disconnected” even though they are all hooked up to the same discovery and same relay.

Already triple checked IDs and logs. On the logs, there’s nothing ever from discovery… either on client logs or the stdicosrv daemon!

After I restarted the client where I tried to add manually, I immediately got the pairing request on the other client. So i believe everything is working, even though even with everything work trhu the discovery I got zero logs :slight_smile: should i have seen logs?

Also, after adding the fixed discovery/relay settings, every web GUI action shows a “saving settings” dialog that last for 30+seconds, for everything: saving setting, accepting new peer, sharing/accepting new folder.

The proposal of not-yet-added device IDs in the Web GUI only works for local discovery. The discovery server protocol simply has not way to request a list of all encountered device IDs (for good reasons).

1 Like