IPv6 ranges in use: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
2a03:9da0:0010::/48 - [https://billing.gigatux.com/nimdb/clientsservices.php?userid=1789&id=3605 analyticsseo-vps2] | 2a03:9da0:0010::/48 - [https://billing.gigatux.com/nimdb/clientsservices.php?userid=1789&id=3605 analyticsseo-vps2] | ||
==node00006== | |||
2a03:9da0:0011::/48 - [https://billing.gigatux.com/nimdb/clientsservices.php?userid=3225&id=3860 hagen] | 2a03:9da0:0011::/48 - [https://billing.gigatux.com/nimdb/clientsservices.php?userid=3225&id=3860 hagen] | ||
Latest revision as of 17:40, 31 January 2025
We have to keep track of IPv6 ranges manually because OpenNebula doesn't support automatic assignment/firewall rules for these.
node00005
2a03:9da0:0010::/48 - analyticsseo-vps2
node00006
2a03:9da0:0011::/48 - hagen