search for: any_ip_in_the_tincnet_subnet

I have a three tinc server setup, similar to "4.3 How Connections Work" using the configuration mostly likehttp://ostolc.org/site-to-site-vpn-with-tinc.html The clients (Ubuntus, Debians and Windows 10s) can all ping (and SSH) to each other remotely. As far as that is concerned it's working great - thanks so much for some great software. However, on each of the Tinc servers (A and

...ed this via telnet ipaddressx 700 and watched via tcpdump what happened on hostb and hostc. A weird thing is when I try the add route with any ip in the tincnet subnet the route gets added even if that ip is not in use and all traffic still goes via the ip of hostb. ie: ip route add default via any_ip_in_the_tincnet_subnet dev tincnet table hostc Does any one know what is happening here? Is it tincd at hostb that intercepts the traffic actually meant for hostc and thinks it's meant for hostb and rewrites stuff automaticaly?  Or am I missing something in the ip route / ip rules part? I am using tinc a lot bu...

...ipaddressx port 700 to hostc, they will not be forwarded the way you want. > A weird thing is when I try the add route with any ip in the tincnet subnet > the route gets added even if that ip is not in use and all traffic still > goes via the ip of hostb. > ie: ip route add default via any_ip_in_the_tincnet_subnet dev tincnet table > hostc Again, in router mode, the "via ..." option has no effect at all. > Is it tincd at hostb that intercepts the traffic actually meant for hostc > and thinks it's meant for hostb and rewrites stuff automaticaly?  Or am I > missing something in the...

...to hostc, they will not be forwarded the way you want. > >> A weird thing is when I try the add route with any ip in the tincnet subnet >> the route gets added even if that ip is not in use and all traffic still >> goes via the ip of hostb. >> ie: ip route add default via any_ip_in_the_tincnet_subnet dev tincnet table >> hostc > Again, in router mode, the "via ..." option has no effect at all. > >> Is it tincd at hostb that intercepts the traffic actually meant for hostc >> and thinks it's meant for hostb and rewrites stuff automaticaly?  Or am I >> m...

...t > 700 to hostc, they will not be forwarded the way you want. > > > A weird thing is when I try the add route with any ip in the tincnet subnet > the route gets added even if that ip is not in use and all traffic still > goes via the ip of hostb. > ie: ip route add default via any_ip_in_the_tincnet_subnet dev tincnet table > hostc > > Again, in router mode, the "via ..." option has no effect at all. > > > Is it tincd at hostb that intercepts the traffic actually meant for hostc > and thinks it's meant for hostb and rewrites stuff automaticaly? Or am I > missing...