Well-known · Network

323 RPKI-Router

TCP Yes
UDP
SCTP
DCCP

What it is

Resource Public Key Infrastructure to Router.

When / why

BGP route-origin validation.

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

Well-known (0–1023). System port for a core service. On Unix-like systems, binding it requires superuser privileges.

Browse all ports →

Firewall rules for port 323

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 323

Allow TCP 323 (RPKI-Router). 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="323" protocol="tcp" accept'

Allow TCP 323 (RPKI-Router) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

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

Allow TCP 323 (RPKI-Router). Assumes table 'inet filter' with an 'input' chain.

iptables

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

Allow TCP 323 (RPKI-Router). Persist with iptables-save/netfilter-persistent.

Azure NSG

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

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

Inbound TCP 323 (RPKI-Router). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

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

Ingress rule for 323 (RPKI-Router). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow RPKI-Router 323/TCP" dir=in action=allow protocol=TCP localport=323 remoteip=<source>

Inbound TCP 323 (RPKI-Router). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow RPKI-Router 323/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 323 -RemoteAddress <source>

Inbound TCP 323 (RPKI-Router). 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.