Open wwessel opened 1 year ago
Do you know if the remote device running the assistant is ipv6 only or is it dual ipv4/ipv6?
Hi,
It’s dual ipv4/ipv6.
Regards
Wolfgang
Von: Simon Smith @.> Gesendet: Dienstag, 20. Februar 2024 00:54 An: Ylianst/MeshCentral @.> Cc: wwessel @.>; Author @.> Betreff: Re: [Ylianst/MeshCentral] MeshCentral Assistant can't connect to IP6 only server. (Issue #5076)
Do you know if the remote device running the assistant is ipv6 only or is it dual ipv4/ipv6?
— Reply to this email directly, view it on GitHub https://github.com/Ylianst/MeshCentral/issues/5076#issuecomment-1953288263 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBM23DMBYFQ6ADOZF4UQOLYUPQYNAVCNFSM6AAAAAAWZ5OR2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGI4DQMRWGM . You are receiving this because you authored the thread.Message ID: @.***>
I set up a MeshCentral server with ip6 only. All is working fine (server/web interface & agent on client device), but assistant can't connect. So I assume it has to do with IP6 only?
Server Software (please complete the following information):
Client Device (please complete the following information):
This is from the debug.log:
15:57:.2374: WebSocket: Websocket TCP failed to connect: System.ArgumentException: Keine der ermittelten oder angegebenen Adressen entspricht der Socketadressfamilie. (None of the addresses determined or specified match the socket address family.) Parametername: context bei System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult) bei System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) bei System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult) bei MeshAssistant.webSocketClient.OnConnectSink(IAsyncResult ar)