Tinc/Redux: Difference between revisions
From charlesreid1
(Created page with "Apparently we need to go through a redux. https://linode.com/docs/networking/vpn/how-to-set-up-tinc-peer-to-peer-vpn/ The old configuration that worked for both Mac and Linu...") |
No edit summary |
||
| Line 14: | Line 14: | ||
The confusing part about the broken configuration was that both machines detected each other, and the Mac received packets, it just couldn't send any packets out. We also had a problem with the network interface (kernel problem?) on the Linode. | The confusing part about the broken configuration was that both machines detected each other, and the Mac received packets, it just couldn't send any packets out. We also had a problem with the network interface (kernel problem?) on the Linode. | ||
[[Category:Tinc]] | |||
Latest revision as of 01:35, 16 April 2018
Apparently we need to go through a redux.
https://linode.com/docs/networking/vpn/how-to-set-up-tinc-peer-to-peer-vpn/
The old configuration that worked for both Mac and Linux is now broken.
The above configuration works fine for connecting Linux nodes together (ran an experiment with three AWS nodes and everything went off without a hitch).
However, the difference between the above guide and the prior configuration that no longer works is the network interface - the tinc-up script.
The linux version above uses three ip commands - one to create the device, one to give it an IP address, and one to give it a route.
The prior script on mac and on linux both just used ifconfig up commands to bring up the interface and give it an IP address in one command.
The confusing part about the broken configuration was that both machines detected each other, and the Mac received packets, it just couldn't send any packets out. We also had a problem with the network interface (kernel problem?) on the Linode.