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
Ran into all our OSC failing after updating to 1.7.4 from 1.7.2. Turns out that because of the newly added ipv6 support, our client with address 'localhost' is now only putting out messages on ipv6. Our corresponding server (OSCUDPServer) is hosting on 'localhost' which still defaults to ipv4. In fast when we try to give it an ipv6 address ('::1') it fails because the underlying socketserver uses the socket.AF_INET address family, which doesn't understand ipv6 addresses.
def server_bind(self):
"""Called by constructor to bind the socket.
May be overridden.
"""
if self.allow_reuse_address:
self.socket.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
> self.socket.bind(self.server_address)
E socket.gaierror: [Errno 11001] getaddrinfo failed
..\..\..\Anaconda3\envs\narupa-dev\lib\socketserver.py:466: gaierror
I am able to work around this with the following subclass, but it was certainly very confusing that server and client behave in different ways given the same localhost address, and also that the underlying socket errors are so esoteric.
class ThreadingOSCUDPServerV6(ThreadingOSCUDPServer):
address_family = socket.AF_INET6
As far as I can tell socket.AF_INET6 doesn't understand ipv4 address so I'm not sure if there's any easy way to support both seamlessly.
The text was updated successfully, but these errors were encountered:
Ran into all our OSC failing after updating to 1.7.4 from 1.7.2. Turns out that because of the newly added ipv6 support, our client with address
'localhost'
is now only putting out messages on ipv6. Our corresponding server (OSCUDPServer) is hosting on'localhost'
which still defaults to ipv4. In fast when we try to give it an ipv6 address ('::1'
) it fails because the underlying socketserver uses thesocket.AF_INET
address family, which doesn't understand ipv6 addresses.I am able to work around this with the following subclass, but it was certainly very confusing that server and client behave in different ways given the same
localhost
address, and also that the underlying socket errors are so esoteric.As far as I can tell
socket.AF_INET6
doesn't understand ipv4 address so I'm not sure if there's any easy way to support both seamlessly.The text was updated successfully, but these errors were encountered: