You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does OVT have any authentication at all? I find it weird that someone sending random garbage to this port can cause a critical error, and that it takes 10 seconds (!) until that socket gets disconnected.
As you can see the ManagedQueue getting stuck happens exactly at this moment.
For now, I'll try to firewall the port for all IPs that aren't my edges.
I think it should be looked at how the OVT code can quickly check if something is a valid client, and close the socket if not, and not making it part of any queue before it's clear it's a valid client.
The text was updated successfully, but these errors were encountered:
In #1583 I had reported that the OVT stream worker can get stuck.
I have just seen the issue again, and this time was able to pin-point it in the log.
I now believe the issue is caused by exploit scanners hitting the OVT port:
192.241.196.124 is not one of my edges, but an exploit scanner:
https://www.abuseipdb.com/check/192.241.196.124
Does OVT have any authentication at all? I find it weird that someone sending random garbage to this port can cause a critical error, and that it takes 10 seconds (!) until that socket gets disconnected.
As you can see the ManagedQueue getting stuck happens exactly at this moment.
For now, I'll try to firewall the port for all IPs that aren't my edges.
I think it should be looked at how the OVT code can quickly check if something is a valid client, and close the socket if not, and not making it part of any queue before it's clear it's a valid client.
The text was updated successfully, but these errors were encountered: