Great! I will try it Guus. thanks
El vie., 30 dic. 2016 a las 12:43, Guus Sliepen (<[email protected]>) escribió: > On Fri, Dec 30, 2016 at 11:38:51AM +0100, Etienne Dechamps wrote: > > > I believe the reason why you're experiencing this problem is because tinc > > does not use the connection TCP port to determine which port to send UDP > > packets to. Instead, it uses the port that is *advertised* by the other > > node. > > That's correct, at least for the initial PMTU probes. If it receives > packets from a peer with a different UDP source port, it will switch to > that one instead. > > But, to announce a different UDP port than what tinc is actually > listening on, you can use the following trick in tinc.conf: > > Port = 25 > ListenAddress = * 655 > > -- > Met vriendelijke groet / with kind regards, > Guus Sliepen <[email protected]> > _______________________________________________ > tinc mailing list > [email protected] > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > -- *Ing. Guillermo Bisheimer* *B&S Sistemas de Control y Equipamientos* Av. de los Constituyentes 1172 (E3116CIX) Crespo, Entre Ríos Tel/Fax: (0343) 407-8990 (Nuevo número) Cel: (0343) 154679052 WEB: www.bys-control.com.ar e-mail: [email protected] skype: guillermo.bisheimer
_______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
