Port 1195: RSF-1 Clustering — The Official Assignment Nobody Uses

Port 1195 lives in the registered port range (1024-49151) and tells the story of how ports actually get used on the Internet—sometimes according to plan, often according to convenience.

What's Officially Assigned

The Internet Assigned Numbers Authority (IANA) officially assigned port 1195 to RSF-1, a high-availability clustering solution that has been providing enterprise failover capabilities since 1995.¹²

RSF-1 uses port 1195 for cluster communication—the heartbeat signals and coordination messages that let multiple servers act as one resilient system. When a primary server fails, RSF-1 detects it and fails over to a standby node, keeping critical services running.³

The protocol operates over both TCP and UDP on port 1195, handling the constant communication required to maintain cluster state and orchestrate failovers.

What Actually Happens

In practice, port 1195 is frequently used for OpenVPN.⁴

OpenVPN officially uses port 1194, but administrators often need to run multiple VPN servers or want to avoid common port scans. Port 1195 sits right next door—close enough to remember, different enough to serve a purpose.

This isn't an accident. When you need an alternative port for OpenVPN, 1195 is the obvious choice. It's unblocked on most networks, falls in a reasonable range, and is easy to remember. The official RSF-1 assignment rarely conflicts because RSF-1 deployments are relatively uncommon compared to the number of OpenVPN installations.

The Registered Port Range

Port 1195 falls in the registered port range—the middle territory between well-known ports (0-1023) that require root privileges and dynamic ports (49152-65535) that get assigned randomly.

Registered ports are assigned by IANA to specific services, but the assignment is more like a reservation than a law. Nothing prevents you from running whatever you want on port 1195. The official assignment just means "if you're running RSF-1, this is the port you should use."

In practice, this range is where official assignments and real-world usage diverge most frequently. A port might be assigned to an enterprise clustering solution used by dozens of companies while simultaneously being used for VPN connections by thousands of individuals.

Security Considerations

If you're running a service on port 1195, know what you're exposing:

For OpenVPN: This is secure by design—OpenVPN uses strong encryption and authentication. But running it on a non-standard port doesn't provide real security through obscurity. Port scanners will find it. The security comes from the protocol itself, not the port number.

For RSF-1: Cluster communication ports should never be exposed to the public Internet. These are internal coordination channels meant for trusted cluster nodes on private networks. Exposing RSF-1 cluster ports to the Internet would allow attackers to potentially disrupt cluster operations or inject false heartbeat signals.

Check what's listening: On any server, verify what's actually using port 1195:

# Linux/macOS
sudo lsof -i :1195
sudo netstat -tulpn | grep 1195

# Windows
netstat -ano | findstr :1195

Why This Port Matters

Port 1195 demonstrates how port assignments work in reality—there's what IANA says the port is for, and there's what people actually use it for.

The official assignment still matters. If you're deploying RSF-1, you know exactly where to configure it. The documentation points to 1195, the defaults work, and clusters communicate without port conflicts.

But the unofficial usage matters too. When thousands of OpenVPN administrators choose 1195 as their alternative port, that becomes part of the port's identity. Network monitoring tools recognize it. Firewall rules account for it. The collective practice shapes what the port means.

This is normal. The Internet is built on protocols and standards, but it's operated by people making practical decisions. Port 1195 serves both roles—official and unofficial—without breaking anything.