Port 17754 ZEP
Port 17754 is the IANA-assigned zep port for Encap. ZigBee Packets (TCP / UDP).
What is port 17754 used for?
Port 17754 is assigned to zep and uses TCP / UDP. The IANA registry describes the service as “Encap. ZigBee Packets”. It sits above the registered range, where most numbers are transient client ports. A fixed high port is worth documenting precisely because tooling often assumes the default.
Ports are the transport-layer address a service listens on. A client that wants to reach zep connects to port 17754. 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 17754 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.
Browse all IoT and device telemetry ports
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Fred_Fierling].
Check and block port 17754
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 = :17754'
sudo ss -ulpn 'sport = :17754'Check on Windows
Get-NetTCPConnection -LocalPort 17754 -State Listen -ErrorAction SilentlyContinue
Get-NetUDPEndpoint -LocalPort 17754 -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 17754/tcp
sudo ufw deny 17754/udpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 17754 -j DROP
sudo iptables -A INPUT -p udp --dport 17754 -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 17754 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 17754 is usually used
Most traffic on port 17754 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Sensors publishing telemetry to a broker or gateway.
- Home-automation or industrial devices subscribing to commands.
- Testing device connectivity with a protocol client instead of a browser.
Probe the gateway
Confirm the port is reachable before debugging device credentials or topic permissions.
nc -vz 192.168.1.20 17754Common problems with port 17754
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 17754. 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 = :17754' or sudo lsof -i :17754. 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 17754 at a glance
| Port number | 17754 |
|---|---|
| Service name | zep |
| Transport protocol | TCP / UDP |
| Category | IoT and device telemetry |
| Range | High port (10001–65535) |
| Risk level | Standard/Low |
| Registered assignee | [Fred_Fierling] |
| Registry description | Encap. ZigBee Packets |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 17754 used for?
Port 17754 (ZEP) uses TCP / UDP. Encap. ZigBee Packets.
How do I check if port 17754 is open?
On Linux run `sudo ss -tlpn 'sport = :17754'` and `sudo ss -ulpn 'sport = :17754'`. On Windows run `Get-NetTCPConnection -LocalPort 17754 -State Listen -ErrorAction SilentlyContinue` and `Get-NetUDPEndpoint -LocalPort 17754 -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 17754; empty output usually means nothing is bound to it.
How do I block port 17754?
With UFW run `sudo ufw deny 17754/tcp` and `sudo ufw deny 17754/udp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 17754 -j DROP` and `sudo iptables -A INPUT -p udp --dport 17754 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 17754 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 17729 · eaEclipse Aviation
- Port 17755 · zigbee-ipZigBee IP Transport Service
- Port 5684 · coapsConstrained Application Protocol (CoAP)
- Port 5683 · coapConstrained Application Protocol (CoAP)
- Port 17756 · zigbee-ipsZigBee IP Transport Secure Service
- Port 5087 · bioticBIOTIC - Binary Internet of Things Interoperable Communication
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy