Connection lost after some time of working

[d47081]

I've launched yggstack by systemd from another user on same machine.

It works for some time, but connection lost until I restart service with systemctl yggstack restart

Logs empty, just regular messages, it's my local problem only?
Yggdrasil works well with same public peer.

p.s. I have just changed PK in config to get my previous IP back, nothing else.
p.p.s. found that's happened on active navigation in browser, maybe some threads issue?

[basilgello]

Can reproduce myself on latest available trunk build but havent figured the root cause yet.

[d47081]

Once I have similar problems until replaced old Ethernet wire, not sure same here but who knows ;)

[basilgello]

@d47081 can you check with latest trunk build?

[d47081]

Hi, I'm currently not using yggdrasil but let me install if that fixed, thanks

[d47081]

Looks everything works well, will re-open if issue happen again

Thanks!

[warlomak]

same problem with latest sources, trying to forward UDP 51820 for Wireguard, trying to watch YouTube 4K video, connection lost after 15-20 seconds...
tested on win64:
yggstack.exe -useconffile ./yggdrasil.conf -local-udp 127.0.0.1:51820:[200:14d4:xxx:xxx:xxx:xxx]:51820

[basilgello]

If reliably reproducible, please run yggstack with -log-level trace

[d47081]

After a brief pause, I recently reconnected Twister P2P to Yggstack using this guide. However, after running the node for about a day, I experienced disconnection again. This issue is still unresolved, and I have no idea how to capture the bug since my error logs are empty.

Switched back to the full Yggdrasil node..

[d47081]

I'm not sure if this information could be helpful, but it looks like the remote Yggdrasil node stops accepting connections and bans or ignores future connections from the Yggstack peer node. This is because there are no errors in the logs.

Does the Yggdrasil core have any spam protection? Perhaps the peer, in a P2P case, is sending too many packets or something similar. The same issue can occur with YouTube or any other intensive usage of the connection.