- 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 4379: CTDB
Port 4379 is assigned by IANA to ctdb (CTDB).
How ctdb works
Other servicesThe client sends a request to port 4379 and the ctdb 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
- Registered (1024-49151)
- Category
- Other services
Is port 4379 dangerous?
We have no specific security note for port 4379. Its risk depends on the program actually listening on it. General advice for other services services:
IANA registry entries for port 4379
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| ctdb | 4379 | TCP, UDP | CTDB | - | 2007-07-05 |
// source: IANA service name and port number registry
Which program uses port 4379, and is it reachable?
Linux
sudo ss -ltnup 'sport = :4379' # process listening on 4379
sudo lsof -nP -i :4379macOS
sudo lsof -nP -i :4379
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 4379 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 4379 netstat -ano | findstr :4379
From another machine
nmap -p 4379 -sV <host> sudo nmap -sU -p 4379 <host> nc -zv <host> 4379
Block it in the firewall
sudo ufw deny 4379/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 4379" -Direction Inbound -LocalPort 4379 -Protocol TCP -Action Block # Windows
What is port 4379 used for?
Port 4379 is assigned by IANA to ctdb (CTDB).
Is port 4379 TCP or UDP?
Port 4379 is registered for TCP and UDP.
Is it safe to open port 4379?
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 4379 is open?
On Linux run "ss -ltnup 'sport = :4379'", on macOS "lsof -nP -i :4379", and on Windows "netstat -ano | findstr :4379" to see the local process. From another machine, "nmap -p 4379 <host>" shows whether it is reachable.