Port 4152 (idig-mux, idig_mux)

IANA assigns port 4152 to idig-mux, idig_mux: iDigTech Multiplex IANA assigned this well-formed service name as a replacement for "idig_mux"..

Registered (user) port, 1024-49151 TCPUDP

IANA assignment

Service nameProtoDescriptionAssigneeReference

idig-mux TCP iDigTech Multiplex IANA assigned this well-formed service name as a replacement for "idig_mux". Robin Findley -

idig_mux TCP iDigTech Multiplex
This entry is an alias to "idig-mux". This entry is now historic, not usable for use with many common service discovery mechanisms. Robin Findley -

idig-mux UDP iDigTech Multiplex IANA assigned this well-formed service name as a replacement for "idig_mux". Robin Findley -

idig_mux UDP iDigTech Multiplex
This entry is an alias to "idig-mux". This entry is now historic, not usable for use with many common service discovery mechanisms. Robin Findley -

Registry dates for this port: registered 2007-05.

Check what is listening on port 4152

Linux: is anything listening on TCP 4152?

sudo ss -tlnp 'sport = :4152'

Linux: UDP 4152

sudo ss -ulnp 'sport = :4152'

Linux / macOS: which process owns the port

sudo lsof -nP -i :4152

Older Linux / BSD (net-tools)

sudo netstat -tlnp | grep ':4152 '

Windows (Command Prompt)

netstat -ano | findstr :4152

Windows (PowerShell)

Get-NetTCPConnection -LocalPort 4152 -State Listen | Select LocalAddress,OwningProcess

Test it from outside

From another machine

nc -vz -w 5 HOST 4152

From Windows

Test-NetConnection HOST -Port 4152

UDP probe (no reply does not prove it is closed)

nc -vzu -w 5 HOST 4152

Block port 4152 in the firewall

ufw

sudo ufw deny 4152/tcp

iptables

sudo iptables -A INPUT -p tcp --dport 4152 -j DROP

nftables

sudo nft add rule inet filter input tcp dport 4152 drop

Windows Firewall

New-NetFirewallRule -DisplayName 'Block TCP 4152' -Direction Inbound -Protocol TCP -LocalPort 4152 -Action Block

ufw

sudo ufw deny 4152/udp