Port 6924 SPLIT-PING
Port 6924 is the IANA-assigned split-ping port for Ping with RX/TX latency/loss split (TCP / UDP).
What is port 6924 used for?
Port 6924 is assigned to split-ping and uses TCP / UDP. The IANA registry describes the service as “Ping with RX/TX latency/loss split”. It sits in the registered range, the block used by databases, application servers and developer tooling. Port conflicts here are common when several local services start at once.
Ports are the transport-layer address a service listens on. A client that wants to reach split-ping connects to port 6924. A TCP connection is refused when nothing is listening, while a UDP request simply goes unanswered. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 6924 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Ben_Cartwright_Cox].
Check and block port 6924
Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.
Check on Linux
sudo ss -tlpn 'sport = :6924'
sudo ss -ulpn 'sport = :6924'Check on Windows
Get-NetTCPConnection -LocalPort 6924 -State Listen -ErrorAction SilentlyContinue
Get-NetUDPEndpoint -LocalPort 6924 -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 6924/tcp
sudo ufw deny 6924/udpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 6924 -j DROP
sudo iptables -A INPUT -p udp --dport 6924 -j DROPThese commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.
Is port 6924 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Where port 6924 is usually used
Most traffic on port 6924 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Application backends and supporting services that use a fixed registered number.
- Containers or local stacks that publish the port on the host.
- Firewall and exposure reviews before the service goes to production.
Probe the port
Confirm something is listening before you debug the client. This checks a TCP handshake on the port.
nc -vz 127.0.0.1 6924Common problems with port 6924
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 6924. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.
Port already in use
Find the process holding the port with sudo ss -tlpn 'sport = :6924' or sudo lsof -i :6924. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.
Firewall rule did not survive a reboot
UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.
The port is blocked but still reachable
A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.
Port 6924 at a glance
| Port number | 6924 |
|---|---|
| Service name | split-ping |
| Transport protocol | TCP / UDP |
| Category | Application services |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [Ben_Cartwright_Cox] |
| Registry description | Ping with RX/TX latency/loss split |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 6924 used for?
Port 6924 (SPLIT-PING) uses TCP / UDP. Ping with RX/TX latency/loss split.
How do I check if port 6924 is open?
On Linux run `sudo ss -tlpn 'sport = :6924'` and `sudo ss -ulpn 'sport = :6924'`. On Windows run `Get-NetTCPConnection -LocalPort 6924 -State Listen -ErrorAction SilentlyContinue` and `Get-NetUDPEndpoint -LocalPort 6924 -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 6924; empty output usually means nothing is bound to it.
How do I block port 6924?
With UFW run `sudo ufw deny 6924/tcp` and `sudo ufw deny 6924/udp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 6924 -j DROP` and `sudo iptables -A INPUT -p udp --dport 6924 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 6924 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Nevertheless, keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Related ports
- Port 6901 · jetstreamNovell Jetstream messaging protocol
- Port 6936 · xsmsvcXenSource Management Service
- Port 6900 · rtimeviewerR*TIME Viewer Data Interface
- Port 6970 · conductorConductor test coordination protocol
- Port 6817 · pentbox-simPenTBox Secure IM Protocol
- Port 6980 · qolyesterQoS-extended OLSR protocol
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy