- Close the port if nothing on the host needs it.
- Identify the process that listens on it (commands below) before opening it in a firewall.
- Expose a service only to the networks that use it.
Port 122: SMAKYNET
Port 122 is assigned by IANA to smakynet (SMAKYNET).
How smakynet works
Other servicesThe client sends a request to port 122 and the smakynet service answers.
- Transport
- TCP · UDP
- Exposure risk
- not rated depends on the program listening
- Encryption
- Unknownnot stated by the registry
- IANA status
- Assigned1 registered service
- Range
- Well-known (0-1023)
- Category
- Other services
Is port 122 dangerous?
We have no specific security note for port 122. Its risk depends on the program actually listening on it. General advice for other services services:
IANA registry entries for port 122
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| smakynet | 122 | TCP, UDP | SMAKYNET | - | - |
// source: IANA service name and port number registry
Which program uses port 122, and is it reachable?
Linux
sudo ss -ltnup 'sport = :122' # process listening on 122
sudo lsof -nP -i :122macOS
sudo lsof -nP -i :122
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 122 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 122 netstat -ano | findstr :122
From another machine
nmap -p 122 -sV <host> sudo nmap -sU -p 122 <host> nc -zv <host> 122
Block it in the firewall
sudo ufw deny 122/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 122" -Direction Inbound -LocalPort 122 -Protocol TCP -Action Block # Windows
What is port 122 used for?
Port 122 is assigned by IANA to smakynet (SMAKYNET).
Is port 122 TCP or UDP?
Port 122 is registered for TCP and UDP.
Is it safe to open port 122?
It depends on the program that listens on it. Open it only for a service you know and only to the networks that need it. Close the port if nothing on the host needs it.
How do I check if port 122 is open?
On Linux run "ss -ltnup 'sport = :122'", on macOS "lsof -nP -i :122", and on Windows "netstat -ano | findstr :122" to see the local process. From another machine, "nmap -p 122 <host>" shows whether it is reachable.