Well-known · Cross-platform

320 PTP general

TCP
UDP Yes
SCTP
DCCP

What it is

Precision Time Protocol general messages.

When / why

PTP management/announce traffic.

Protocol status detail

TransportStatusMeaning
TCP Not applicable for this transport.
UDP Yes Assigned by IANA and standardized, specified, or widely used on this port.
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 320

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 udp from <source> to any port 320

Allow UDP 320 (PTP general). 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="320" protocol="udp" accept'

Allow UDP 320 (PTP general) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

nft add rule inet filter input ip saddr <source> udp dport 320 accept

Allow UDP 320 (PTP general). Assumes table 'inet filter' with an 'input' chain.

iptables

sudo iptables -A INPUT -p udp -s <source> --dport 320 -j ACCEPT

Allow UDP 320 (PTP general). Persist with iptables-save/netfilter-persistent.

Azure NSG

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

Inbound rule for 320 (PTP general). 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=udp,FromPort=320,ToPort=320,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound UDP 320 (PTP general). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

gcloud compute firewall-rules create allow-ptpgeneral-320 --direction=INGRESS --action=ALLOW --rules=udp:320 --source-ranges=<source-cidr> --network=<network>

Ingress rule for 320 (PTP general). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow PTP general 320/UDP" dir=in action=allow protocol=UDP localport=320 remoteip=<source>

Inbound UDP 320 (PTP general). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow PTP general 320/UDP" -Direction Inbound -Action Allow -Protocol UDP -LocalPort 320 -RemoteAddress <source>

Inbound UDP 320 (PTP general). 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.