Registered · Cross-platform

19999 DNP3 Secure / Netdata

TCP Yes
UDP
SCTP
DCCP

What it is

Secure DNP3 (SCADA); also the Netdata monitoring dashboard.

When / why

Utility SCADA or real-time host metrics.

Protocol status detail

TransportStatusMeaning
TCP Yes Assigned by IANA and standardized, specified, or widely used on this port.
UDP Not applicable for this transport.
SCTP Not applicable for this transport.
DCCP Not applicable for this transport.

Port range

Registered (1024–49151). Assigned by IANA on request; usable without elevated privileges on most systems.

Browse all ports →

Firewall rules for port 19999

Copy-ready inbound rules for the active transports. Replace every <source> placeholder with the specific host, subnet, or CIDR that should reach this port.

ufw

sudo ufw allow proto tcp from <source> to any port 19999

Allow TCP 19999 (DNP3 Secure / Netdata). Replace <source> with the network/host that should reach it.

firewalld

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<source>" port port="19999" protocol="tcp" accept'

Allow TCP 19999 (DNP3 Secure / Netdata) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

nft add rule inet filter input ip saddr <source> tcp dport 19999 accept

Allow TCP 19999 (DNP3 Secure / Netdata). Assumes table 'inet filter' with an 'input' chain.

iptables

sudo iptables -A INPUT -p tcp -s <source> --dport 19999 -j ACCEPT

Allow TCP 19999 (DNP3 Secure / Netdata). Persist with iptables-save/netfilter-persistent.

Azure NSG

az network nsg rule create -g <resource-group> --nsg-name <nsg> -n Allow-dnp3securenetdata-19999 --priority 1000 --access Allow --direction Inbound --protocol TCP --source-address-prefixes <source> --destination-port-ranges 19999

Inbound rule for 19999 (DNP3 Secure / Netdata). Set <source> to a CIDR; lower priority number = higher precedence.

AWS Security Group

aws ec2 authorize-security-group-ingress --group-id <sg-id> --ip-permissions IpProtocol=tcp,FromPort=19999,ToPort=19999,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 19999 (DNP3 Secure / Netdata). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

gcloud compute firewall-rules create allow-dnp3securenetdata-19999 --direction=INGRESS --action=ALLOW --rules=tcp:19999 --source-ranges=<source-cidr> --network=<network>

Ingress rule for 19999 (DNP3 Secure / Netdata). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow DNP3 Secure / Netdata 19999/TCP" dir=in action=allow protocol=TCP localport=19999 remoteip=<source>

Inbound TCP 19999 (DNP3 Secure / Netdata). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow DNP3 Secure / Netdata 19999/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 19999 -RemoteAddress <source>

Inbound TCP 19999 (DNP3 Secure / Netdata). Replace <source> with a host or subnet.

Rules are generated only for transports marked active for this port. They default to an inbound allow with an explicit source placeholder — never any. Review direction, scope, and rule precedence before applying in production.