dns resolution behind proxy

Uwe Werler
Tue, 27 Oct 2015 13:45:28 -0000

Hello Guus,

thanks for Your fast reply.

Does it mean only socks is affected and http proxy should work? If this is the
case then this may be a temp. solution.

Thanks and regards!

Uwe

Am 27.10.2015 14:08:36, schrieb Guus Sliepen:
> On Tue, Oct 27, 2015 at 12:33:35PM +0000, Uwe Werler wrote:
>
> > I wonder why tinc tries to resolve host names before connection even
> > with configured (socks5) proxy which fails behind restrictive
firewalls.

> You are right that it shouldn't be necessary to do this with SOCKS5.
> With SOCKS4, it needs to know the exact address, and then I just used
> that for SOCKS5 as well.
>
> > Is there any "workaround"?

> The workaround is to do resolve the hostnames yourself and replace the
> hostnames in the Address statements with numeric addresses. I'll try to
> change tinc so it will allow connections via SOCKS5 even if it cannot
> resolve the hostname itself.
>
> --
> Met vriendelijke groet / with kind regards,
>      Guus Sliepen <> guus at tinc-vpn.org> >
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc




--
Sent with love from the Tine 2.0 email client ...
Please visit http://www.tine20.com
-------------- n?chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20151027/935a7cf0/attachment.html>