How to set up the firewall for the local RADIUS instance to connect to Portnox Cloud
In this topic, you will learn how to configure your firewall to make sure that the local RADIUS instance can communicate with the cloud RADIUS instances.
You need to open the following ports on your firewall:
FQDN | Protocol | Ports | Direction |
---|---|---|---|
radius.portnox.com | TCP | 443 | Outbound |
rad-events-clear-prod-eastus.servicebus.windows.net | TCP | 443 | Outbound |
rad-events-clear-prod-westeu.servicebus.windows.net | TCP | 443 | Outbound |
devices-ingress-clear-prod-eastus.servicebus.windows.net | TCP | 443 | Outbound |
devices-ingress-clear-prod-westeu.servicebus.windows.net | TCP | 443 | Outbound |
cloudcentraalstoreprodus.blob.core.windows.net | TCP | 443 | Outbound |
cloudcentraalstoreprod.blob.core.windows.net | TCP | 443 | Outbound |
pnxeusprdclrinstallers.blob.core.windows.net | TCP | 443 | Outbound |
pnxweuprdclrinstallers.blob.core.windows.net | TCP | 443 | Outbound |
logs-consolidation-prod-eastus.servicebus.windows.net | TCP | 443 | Outbound |
logs-consolidation-prod-westeu.servicebus.windows.net | TCP | 443 | Outbound |
Additionally, if you want to use the CoA functionality with a local RADIUS Docker container, you must also open the following ports:
FQDN | Protocol | Ports | Direction |
---|---|---|---|
portnox-centraal-prod.servicebus.windows.net | TCP | 80, 443, 5671, 5672 | Outbound |
portnox-centraal-prod-eastus.servicebus.windows.net | TCP | 80, 443, 5671, 5672 | Outbound |
If your firewall software does not support FQDNs or encounters issues, such as failing to recognize some IP addresses resolved from the FQDNs, you can use this official Azure script to retrieve the IP addresses associated with an Azure FQDN. You can then add all these IP addresses to the firewall instead of the FQDNs. However, be sure to regularly monitor connectivity and check for any updates, as Microsoft may add or remove IP addresses over time.