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