I use 'sslh' demultiplexer in these types of scenarios.
Reconfigure httpd to listen on localhost:80, then configure sslh to listen
on 10.1.1.10:80 and point http traffic to localhost:80, and to point tinc
traffic to whatever port tinc is bound.
On Apr 24, 2015 2:36 AM, "Guus Sliepen" <guus at tinc-vpn.org>
wrote:
> On Wed, Apr 15, 2015 at 10:28:36PM +0900, Benda Xu wrote:
>
> > I am behind a firewall which only let UDP 80 go through. In order to
> > connect to an outside public node by UDP, I can set
> >
> > ...
> > Port = 80
> > ...
> >
> > However, an httpd is running on the public node, occupying TCP 80.
> >
> > How can I configure tinc to bind on TCP 8080 but listen to UDP 80?
> >
> > Redirecting UDP 80 to UDP 8080 on the public node is one method. Is
> > there a more elegant way to achieve this?
>
> At the moment, tinc only wants to bind to both TCP and UDP
> simultaneously, so you cannot tell it to bind to port 80 for UDP only.
> Redirecting with firewall rules is the easiest option in this scenario.
>
> --
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20150426/95c8c566/attachment.html>