I want tinc to listen locally on loopback, so that port 655 is not exposed on any system interfaces. Can't tinc make outbound connections when listening on loopback? I can't see any reason why it should. This system will never have other tinc daemons connect to it, it will only ever connect to other tinc daemons in order to establish a VPN connection.
-- Jonny Tyers On Sat, 17 Nov 2018 at 22:03, Clemens Schrimpe <[email protected]> wrote: > > The only thing „localhost“ can talk to is „localhost“ - by definition & > independently of tinc. > > What are you trying to accomplish with that choice? > > Clemens > > Von meinem iPad gesendet > > > Am 17.11.2018 um 21:58 schrieb Jonny Tyers <[email protected]>: > > > > Hi there, > > > > Thanks for tinc, firstly. It's awesome. Now, I've found that if I specify: > > > > BindAddress = 127.0.0.1 655 > > > > Then my tincd cannot make outbound connections (on attempting to > > connect to another tinc daemon is receives 'Invalid argument'). > > Removing BindAddress fixes the issue. Unless I've misunderstood the > > purpose of this option, is this a bug? > > > > I'm running v1.0.35 on Arch Linux > > _______________________________________________ > > tinc mailing list > > [email protected] > > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > _______________________________________________ > tinc mailing list > [email protected] > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc _______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
