Hi Guus, Thanks for the quick response.
>Try adding TCPOnly = yes to the tinc.conf files. According to docs, TCPOnly applies to Host configs but tried adding to tinc.conf as well, no luck. > check the configuration of the TAP interfaces. Quadruple checked - I can connect tinc inside my lan, no prob. > your DSL and/or 3G provider might do that outside of your control. >From the logs, it appears the 3G network is doing some NAT of it's own. Don't know what impact is on tinc operation? Laptop extract (3G): .. Connected to MainPC (41.242.172.108 port 655) .. Sending ID to MainPC (41.242.172.108 port 655): 0 Laptop 17 .. Got ID from MainPC (41.242.172.108 port 655): 0 MainPC 17 .. Sending CHALLENGE to MainPC (41.242.172.108 port 655): ... .. Bogus data received from MainPC (41.242.172.108 port 655) .. Closing connection with MainPC (41.242.172.108 port 655) MainPC extract (DSL): .. Connection from 41.208.50.180 port 8173 .. Sending ID to <unknown> (41.208.50.180 port 8173): 0 MainPC 17 .. Got ID from <unknown> (41.208.50.180 port 8173): 0 Laptop 17 .. Sending METAKEY to Laptop (41.208.50.180 port 8173): ... .. Got METAKEY from Laptop (41.208.50.180 port 8173): ... .. Sending CHALLENGE to Laptop (41.208.50.180 port 8173): ... .. Sending 259 bytes of metadata to Laptop (41.208.50.180 port 8173) .. Connection closed by Laptop (41.208.50.180 port 8173) Kind regards Graham Smith _______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
