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
Eternal Terminal client fails for me when trying to forward a port. If I remove the port forwarding from the command below, et connects successfully:
$ et --verbose=9 -t "3389:3389" 10.1.2.3
Error binding 10/1/6: 99 Cannot assign requested address
Error establishing port forward: Error binding port 3389: 99 Cannot assign requested address
This error occurs no matter what source port I choose. It is not failing because the port is in use.
Looking at the TcpSocketHandler::listen()source for the error output, it looks like it is failing when trying to bind to an IPv6 interface, as the addrinfo.ai_family value 10 maps to AF_INET6. But given that I've specified an IPv4 host address on the command line, I believe the correct behaviour for et in this scenario should be to skip over IPv6 interfaces. To test this idea, I hard-coded a continue for the case when p->ai_family == AF_INET6 and my et connection with port forwarding subsequently worked (this was just a test, not a proposed solution for the bug).
The text was updated successfully, but these errors were encountered:
gkiessling
changed the title
TcpSocketHandler::listen() does not loop over IPv6 interfaces while connecting with IPv4
TcpSocketHandler::listen() does not loop over IPv6 interfaces while connecting to an IPv4 host
Oct 24, 2024
Eternal Terminal client fails for me when trying to forward a port. If I remove the port forwarding from the command below,
et
connects successfully:This error occurs no matter what source port I choose. It is not failing because the port is in use.
Looking at the
TcpSocketHandler::listen()
source for the error output, it looks like it is failing when trying to bind to an IPv6 interface, as theaddrinfo.ai_family
value 10 maps to AF_INET6. But given that I've specified an IPv4 host address on the command line, I believe the correct behaviour foret
in this scenario should be to skip over IPv6 interfaces. To test this idea, I hard-coded acontinue
for the case whenp->ai_family == AF_INET6
and myet
connection with port forwarding subsequently worked (this was just a test, not a proposed solution for the bug).etclientLogs.tar.gz
The text was updated successfully, but these errors were encountered: