Hi,
Thank you for evaluating SOCKS64. Kristof> I got this kind of errors when I tried runsocks ssh, or runsocks w3m, ... Kristof> Apr 25 21:10:40 abraham Socks5[14211]: UDP Proxy Termination: Kristof> (157.193.28.16:1904) for user ; 0 bytes out 0 bytes in You are using the runsocks (libsocks5_sh.so) of SOCKS64 or socks5-v1.0r10, right? These lack support of substituting getaddrinfo() function to SOCKS version. In other words, you can't correctly SOCKSify the application using getaddrinfo() by these (socks5-v1.0r10 or socks64 based on socks5-v1.0r10) implementations. I don't know if the latest SOCKS5 reference implementation (socks5-v1.0r11) supports SOCKSifying getaddinfo(), but if it does, or if you could get or write some patches to enable SOCKSifying getaddrinfo(), you should be able to use SOCKS64 with that runsocks (libsocks5_sh.so). Please note that SOCKS64 does not support UDP relay. Many applications such as ssh or w3m uses UDP only for DNS queries, which will be eliminated if the application is correctly SOCKSified. However, if you need UDP communications other than DNS queries, SOCKS64 can't relay them. You might try NEC's implementation (http://www.socks.nec.com/reference/translator.html) for such purpose. Kristof> With rftp everything went fine, but listing on the kame ftp server Kristof> didn't work. I'm afraid our 6bone connection is temporary down, so I can't test it right now. It might be a bug of SOCKS64. Kobayashi Shinji [EMAIL PROTECTED] --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
