US ZPE Cloud Servers: | |||
Hostname(s) | IPv6 Address | IPv4 address | Usage |
second-tier-ca.zpecloud.com, device-api.zpecloud.com, device-apiv2.zpecloud.com | 2600:1901:0:6091:: | 34.49.235.253 | Required to sign the CSR to connect to Remote Access. Required to Upload/Restore Backups. Required to upload output from executed profiles. |
api.astarte.zpecloud.com | 2600:1901:0:53ce:: | 34.49.39.37 | Required for Pairing API - without it, device is not able to authenticate against PubSub service and consequently connect to Cloud. |
access.zpecloud.com | 2600:1901:0:ab8f:: | 34.49.235.61 | Required for Remote Access - without it, device is not able to connect to Remote Access socket. |
broker.astarte.zpecloud.com | 2600:1901:0:5abb:: | 34.49.26.197 | Required for Broker connection - without it, device is not able to connect to PubSub service and consequently connect to Cloud. |
www.zpecloud.com, api.zpecloud.com, proxy-access.zpecloud.com, zpecloud.com | 2600:1901:0:910b:: | 34.120.236.72 | Required for Enrollment. Required to SSO from Cloud to Nodegrid appliance; also needs to be enabled on the Nodegrid appliance under Security :: Authentication :: SSO. |
proxy-forwarder.zpecloud.com | 2600:1901:0:4792:: | 34.36.157.245 | |
European ZPE Cloud Servers: | |||
Hostname(s) | IPv6 Address | IPv4 Address | Usage |
second-tier-ca.zpecloud.eu, device-api.zpecloud.eu, device-apiv2.zpecloud.eu | 2600:1901:0:b0cb:: | 34.128.171.100 | Required to sign the CSR to connect to Remote Access. Required to Upload/Restore Backups. Required to upload output from executed profiles. |
api.astarte.zpecloud.eu | 2600:1901:0:7123:: | 34.49.228.213 | Required for Pairing API - without it, device is not able to authenticate against PubSub service and consequently connect to Cloud. |
access.zpecloud.eu | 2600:1901:0:e8af:: | 34.128.152.77 | Required for Remote Access - without it, device is not able to connect to Remote Access socket. |
broker.astarte.zpecloud.eu | 2600:1901:0:9065:: | 34.36.11.79 | Required for Broker connection - without it, device is not able to connect to PubSub service and consequently connect to Cloud. |
www.zpecloud.eu, api.zpecloud.eu, proxy-access.zpecloud.eu, zpecloud.eu | 2600:1901:0:ec0d:: | 34.111.34.34 | Required for Enrollment. Required to SSO from Cloud to Nodegrid appliance; also needs to be enabled on the Nodegrid appliance under Security :: Authentication :: SSO. |
proxy-forwarder.zpecloud.eu | 2600:1901:0:598e:: | 34.49.218.26 |
Can I change my firewall whitelists now?
Yes, you can update your firewall whitelists now. You can add the new IPv6 addresses while keeping the existing IPv4 entries intact. This ensures you're prepared ahead of the full IPv6 rollout.
What happens if I don’t update my firewall whitelist?
IPv4 will continue to function as usual, even if you don't update your whitelist. However, if IPv6 infrastructure is in place and a firewall is used, you will need to whitelist the new IPv6 addresses to ensure uninterrupted service.
If I don’t use firewall whitelists, do I need to take any action?
While maintaining a firewall is highly recommended for network security, if you don’t currently use a whitelist, no immediate action is required.
Are the new IPs currently active?
No, the new IPv6 addresses will become active on December 9, 2024 and December 11, 2024. To avoid any service disruptions, we recommend adding the new IP addresses to your whitelist in advance.
Does this change require modification to Nodegrid configuration?
No changes to your Nodegrid configuration are necessary
How to verify if the network connection in Nodegrid has IPv6 support?
You can check if your network connection has IPv6 support by accessing Nodegrid’s WebUI and navigating to Network :: Connections. There, you can see if there is any address in the IPv6 column.
How to enable IPv6 support in Nodegrid?
Access Nodegrid’s WebUI and navigate to Network :: Connections. Click on the desired network connection, and then change the “IPv6 mode” for that connection. Please check with your ISP to confirm if your link has IPv6 support.