search for: test_tinc_1

Displaying 4 results from an estimated 4 matches for "test_tinc_1".

Did you mean: test_find_1
2017 Feb 14
2
LocalDiscovery flip flopping and network design tips
Hang on a second. I've just re-read your original message and I believe you are confused about what the "Subnet" option does. Again, it deals with addresses *inside* the VPN. In the configuration you posted you seem to be using 10.240.0.4 and 10.240.0.5 as internal addresses, but then your other statements (and especially your dump edges output) seem to indicate that 10.240.0.4 and
2017 May 11
2
LocalDiscovery flip flopping and network design tips
...N > > addresses and physical addresses, your problems should go away. > > That's kind of intentional. I want tinc to be able to receive traffic > destined the local network over the tinc tunnel. I might be doing this > wrong and obviously I'm open to suggestions. > > test_tinc_1 has an internal IP of 10.240.0.4/16 > test_tinc_1 config is: > Subnet = 10.240.0.0/16 > Subnet = 10.240.0.4/32 > Address = 104.154.59.151 > > I want other nodes being able to talk to test_tinc_1 to be able to > talk to the network that test_tinc_1 is on. I might not need "...
2017 Feb 14
0
LocalDiscovery flip flopping and network design tips
...o use different IP subnets for VPN > addresses and physical addresses, your problems should go away. That's kind of intentional. I want tinc to be able to receive traffic destined the local network over the tinc tunnel. I might be doing this wrong and obviously I'm open to suggestions. test_tinc_1 has an internal IP of 10.240.0.4/16 test_tinc_1 config is: Subnet = 10.240.0.0/16 Subnet = 10.240.0.4/32 Address = 104.154.59.151 I want other nodes being able to talk to test_tinc_1 to be able to talk to the network that test_tinc_1 is on. I might not need "Subnet = 10.240.0.0/16" if I...
2017 May 11
0
LocalDiscovery flip flopping and network design tips
...d physical addresses, your problems should go away. >> >> That's kind of intentional. I want tinc to be able to receive traffic >> destined the local network over the tinc tunnel. I might be doing this >> wrong and obviously I'm open to suggestions. >> >> test_tinc_1 has an internal IP of 10.240.0.4/16 >> test_tinc_1 config is: >> Subnet = 10.240.0.0/16 >> Subnet = 10.240.0.4/32 >> Address = 104.154.59.151 >> >> I want other nodes being able to talk to test_tinc_1 to be able to >> talk to the network that test_tinc_1 is...