-
Notifications
You must be signed in to change notification settings - Fork 4
tunnelservers: ipv6 config #75
Comments
https://tools.ietf.org/html/rfc6177 How many end sites aka nodes do we have per server? |
according to http://monitor.berlin.freifunk.net/host.php?h=tunnel-clients&p=exec there are 53 clients per server |
I suggest we plan for growth and assume 128 clients per sever. We have 6 servers. In the worst case we have 6 * 128 on one server. That's 768 clients on one server. We round to 1024. So we need 1024 * /56 for each server to be on the save side. So we need 2**10 subnets. 56 - 10 is /46. We should request /46 per server. |
https://tools.ietf.org/html/rfc7421 section 3 describes using prefixes longer than /64 |
Freifunk Rheinland can assign us a /48 but we need a RIPE handle to get the IPs. |
@pmelange Do we have a maximum number of clients configured for the tunneldigger setup? |
Yes we do. Just under 4000. https://github.com/freifunk-berlin/puppet-communitytunnel/blob/4c34b78c85d2f58efc1fb8ae060a799cec8f2c25/manifests/init.pp#L8 |
In considering setting up ipv6 for the tunnels, we need to first gather some information about the current ipv6 settings.
a.tunnel (vm02.roellig-it.de)
b.tunnel (freifunk-gw01.in-berlin.de)
c.tunnel (vpn03d)
d.tunnel (vpn03f)
e.tunnel (vpn03g)
f.tunnel (vpn03h)
The text was updated successfully, but these errors were encountered: