Portnox local RADIUS proxy for redundancy
8.1K
Docker image to run Portnox RADIUS server in a container. The container receives RADIUS messages, communicates with Portnox Cloud services over an encrypted TLS connection, and responds based on policies defined within the Portnox Cloud Portal.
For instructions for running in cloud services and on a docker engine please read our full documentation at Portnox Radius Container Documentation.
Run using Docker Engine
Login to the Clear Portal , go to Settings, and in the SERVICES, click LOCAL RADIUS SERVICE, click a profile and you will be able to copy environment variables required to run the portnox-radius container using the 'export' command. For example
export RADIUS_GATEWAY_ORG_ID=1a23456b-7c89-012d-e345-e67f890a123b
export RADIUS_GATEWAY_PROFILE=0a1234b5-6c67-890d-ef1a-bc234567890d
export RADIUS_GATEWAY_TOKEN=a1bcdef23gh45ijkl6m78nop
Once the environmental variables have been set, copy and paste the docker run command below into your bash terminal to start the portnox-radius container.
sudo docker run -d -p 1812:1812/udp -p 1813:1813/udp --name portnox-radius --restart=on-failure \
--ulimit nproc=65535 \
--ulimit nofile=65535 \
-e RADIUS_GATEWAY_PROFILE=$RADIUS_GATEWAY_PROFILE \
-e RADIUS_GATEWAY_ORG_ID=$RADIUS_GATEWAY_ORG_ID \
-e RADIUS_GATEWAY_TOKEN=$RADIUS_GATEWAY_TOKEN \
portnox/portnox-radius:latest
To place the container in debug mode, add '--debug' to the end of the docker command above. To then view the log output from the container run the following command.
docker logs portnox-radius -f
To verify the container is receiving RADIUS packets from the NAS enter the following commands to install and run tcpdump inside the container. Then attempt to authenticate to the NAS device via 802.1x, MAB, etc.
docker exec -it container-name sh
apk add tcpdump
tcpdump -i eth0 -v port 1812
Content type
Image
Digest
sha256:0d5096d81…
Size
73.5 MB
Last updated
29 days ago
docker pull portnox/portnox-radiusPulls:
241
Last week