Port 2349 (redstorm-diag, redstorm_diag)

IANA assigns port 2349 to redstorm-diag, redstorm_diag: Diagnostics Port IANA assigned this well-formed service name as a replacement for "redstorm_diag"..

Registered (user) port, 1024-49151 TCPUDP

IANA assignment

Service nameProtoDescriptionAssigneeReference

redstorm-diag TCP Diagnostics Port IANA assigned this well-formed service name as a replacement for "redstorm_diag". David Weinstein -

redstorm_diag TCP Diagnostics Port
This entry is an alias to "redstorm-diag". This entry is now historic, not usable for use with many common service discovery mechanisms. David Weinstein -

redstorm-diag UDP Diagnostics Port IANA assigned this well-formed service name as a replacement for "redstorm_diag". David Weinstein -

redstorm_diag UDP Diagnostics Port
This entry is an alias to "redstorm-diag". This entry is now historic, not usable for use with many common service discovery mechanisms. David Weinstein -

Check what is listening on port 2349

Linux: is anything listening on TCP 2349?

sudo ss -tlnp 'sport = :2349'

Linux: UDP 2349

sudo ss -ulnp 'sport = :2349'

Linux / macOS: which process owns the port

sudo lsof -nP -i :2349

Older Linux / BSD (net-tools)

sudo netstat -tlnp | grep ':2349 '

Windows (Command Prompt)

netstat -ano | findstr :2349

Windows (PowerShell)

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

Test it from outside

From another machine

nc -vz -w 5 HOST 2349

From Windows

Test-NetConnection HOST -Port 2349

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

nc -vzu -w 5 HOST 2349

Block port 2349 in the firewall

ufw

sudo ufw deny 2349/tcp

iptables

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

nftables

sudo nft add rule inet filter input tcp dport 2349 drop

Windows Firewall

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

ufw

sudo ufw deny 2349/udp