Registered · Cross-platform

38412 5G NGAP

TCP Yes
UDP
SCTP
DCCP

What it is

NG Application Protocol between gNB and AMF in 5G core (over SCTP).

When / why

5G radio-to-core signaling.

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 38412

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 38412

Allow TCP 38412 (5G NGAP). 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="38412" protocol="tcp" accept'

Allow TCP 38412 (5G NGAP) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

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

Allow TCP 38412 (5G NGAP). Assumes table 'inet filter' with an 'input' chain.

iptables

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

Allow TCP 38412 (5G NGAP). Persist with iptables-save/netfilter-persistent.

Azure NSG

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

Inbound rule for 38412 (5G NGAP). 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=38412,ToPort=38412,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 38412 (5G NGAP). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

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

Ingress rule for 38412 (5G NGAP). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow 5G NGAP 38412/TCP" dir=in action=allow protocol=TCP localport=38412 remoteip=<source>

Inbound TCP 38412 (5G NGAP). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow 5G NGAP 38412/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 38412 -RemoteAddress <source>

Inbound TCP 38412 (5G NGAP). 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.