Open SonProCode opened 3 weeks ago
Hi @SonProCode, The message from the QUIC stack is not the cause. If you don't receive beacons from the attachment point, there could be several causes:
tcpdump
)Both the border router and the control service have an HTTP API that you can query from the machine, where it will tell you their metrics. That is useful for instance to check the BR has BFD packets back and forth, etc.
Thanks @juagargi for your response!
By the way, this is the latest picture that i took concerning the SCIONLab Health Check.
I am trying to set up an AS in SCION Lab by running it on a VM. Everything was going well until I checked whether the beacons had been registered ( I followed the instructions in https://docs.scionlab.org/content/config/check.html), and the returned list was empty. I have included the log from the border router (attached in the image), and I noticed a line stating:
*Nov 01 11:09:13 scionlab-ffaa-1-1184 scion-control-service[14364]: 2024/11/01 11:09:13 connection doesn't allow setting of receive buffer size. Not a net.UDPConn?. See https://[github.com/quic-go/quic-go/wiki/](http://github.com/quic-go/quic-go/wiki/)**
Could this be the reason for the issue? I have attempted to follow the troubleshooting section to fix the problem but to no avail. I also tried resolving the issue according to the instructions on https://github.com/quic-go/quic-go/wiki/, but after all, I still cannot find the beacon.