Registered · Cross-platform

5667 Nagios NSCA

TCP Unofficial
UDP
SCTP
DCCP

What it is

Nagios passive check submission.

When / why

Passive monitoring results to the Nagios server.

Protocol status detail

TransportStatusMeaning
TCP Unofficial Not assigned by IANA, but 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 5667

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 5667

Allow TCP 5667 (Nagios NSCA). 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="5667" protocol="tcp" accept'

Allow TCP 5667 (Nagios NSCA) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

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

Allow TCP 5667 (Nagios NSCA). Assumes table 'inet filter' with an 'input' chain.

iptables

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

Allow TCP 5667 (Nagios NSCA). Persist with iptables-save/netfilter-persistent.

Azure NSG

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

Inbound rule for 5667 (Nagios NSCA). 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=5667,ToPort=5667,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 5667 (Nagios NSCA). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

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

Ingress rule for 5667 (Nagios NSCA). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow Nagios NSCA 5667/TCP" dir=in action=allow protocol=TCP localport=5667 remoteip=<source>

Inbound TCP 5667 (Nagios NSCA). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow Nagios NSCA 5667/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 5667 -RemoteAddress <source>

Inbound TCP 5667 (Nagios NSCA). 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.