Typically you can do port translation on your firewall to map the 28655 port to 655 internally.
Alternatively I believe you can run 2 Tinc instances if 1 Tinc instance will not bind to multiple sockets. It would simply require a 2nd virtual adapter. You would then have 2 public keys or host files. Connecting nodes would need the host file relative to their connecting internally or externally. On Fri, Feb 12, 2010 at 1:49 PM, Rob Townley <[email protected]> wrote: > this node doesnt have two nics, the public address is for those > connecting from the public side of the NAT. As far as that tinc node > knows, it is using 655. i will look elsewhwere for the connection > problem. dynamic dns of port number could help tinc get better meta > knowledge about itself. > > What was the name of the dns library you recommended? Does it work > with dnsmasq? > > Do you use gdb debugger? > > On 2/12/10, Guus Sliepen <[email protected]> wrote: > > On Thu, Feb 11, 2010 at 03:06:17PM -0600, Rob Townley wrote: > > > >> i have a switched and bridged tincd node with two addresses, each > with > >> a > >> different port. > >> Address = 37.70.156.168 28655 > >> Address = 192.168.2.228 655 > > > > Tinc itself will only listen on one port. By default 655, if you want > > another > > port you can use the Port statement. It will also use this port to send > > packets > > from. > > > > -- > > Met vriendelijke groet / with kind regards, > > Guus Sliepen <[email protected]> > > > _______________________________________________ > tinc mailing list > [email protected] > http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
