Displaying 5 results from an estimated 5 matches for "subnet0".
Did you mean:
subnet
2017 Feb 14
4
LocalDiscovery flip flopping and network design tips
...5 open to the world, and all the other servers have 655 open to
internal ips only. With LocalDiscovery (as well as IndirectData = yes on
"non-public" servers) this works work pretty well, as far as I can tell.
But it wouldn't solve the inner-Google traffic between subnets since Google
Subnet0 would talk over public to Google Subnet1. What's the best way of
doing something like this? I was thinking maybe 2 instances of tinc on the
"public" boxes, but Google servers only have a single interface, eth0, that
has the internal IP, so I couldn't listen on the external and int...
2017 Feb 14
2
LocalDiscovery flip flopping and network design tips
...er servers have 655 open to
>> internal ips only. With LocalDiscovery (as well as IndirectData = yes on
>> "non-public" servers) this works work pretty well, as far as I can tell.
>> But it wouldn't solve the inner-Google traffic between subnets since Google
>> Subnet0 would talk over public to Google Subnet1. What's the best way of
>> doing something like this? I was thinking maybe 2 instances of tinc on the
>> "public" boxes, but Google servers only have a single interface, eth0, that
>> has the internal IP, so I couldn't lis...
2017 Feb 14
0
LocalDiscovery flip flopping and network design tips
...and all the other servers have 655 open to
> internal ips only. With LocalDiscovery (as well as IndirectData = yes on
> "non-public" servers) this works work pretty well, as far as I can tell.
> But it wouldn't solve the inner-Google traffic between subnets since Google
> Subnet0 would talk over public to Google Subnet1. What's the best way of
> doing something like this? I was thinking maybe 2 instances of tinc on the
> "public" boxes, but Google servers only have a single interface, eth0, that
> has the internal IP, so I couldn't listen on the e...
2017 Feb 14
1
LocalDiscovery flip flopping and network design tips
...and all the other servers have 655 open to
> internal ips only. With LocalDiscovery (as well as IndirectData = yes on
> "non-public" servers) this works work pretty well, as far as I can tell.
> But it wouldn't solve the inner-Google traffic between subnets since Google
> Subnet0 would talk over public to Google Subnet1. What's the best way of
> doing something like this? I was thinking maybe 2 instances of tinc on the
> "public" boxes, but Google servers only have a single interface, eth0, that
> has the internal IP, so I couldn't listen on the e...
2017 Feb 14
0
LocalDiscovery flip flopping and network design tips
...5 open to the world, and all the other servers have 655 open to internal ips only. With LocalDiscovery (as well as IndirectData = yes on "non-public" servers) this works work pretty well, as far as I can tell. But it wouldn't solve the inner-Google traffic between subnets since Google Subnet0 would talk over public to Google Subnet1. What's the best way of doing something like this? I was thinking maybe 2 instances of tinc on the "public" boxes, but Google servers only have a single interface, eth0, that has the internal IP, so I couldn't listen on the external and int...