Dynamic ports cause repeated setup
STUN/P2P can expose the current mapped port, but that port may change. Many clients are not designed for frequent manual port edits.
STUN/P2P dynamic port helper for iSCSI
As public IPv4 access disappears, STUN/P2P hole punching can discover NAT mapped ports and build direct peer-to-peer paths without relay traffic. The problem is that mapped ports can change daily. ZsLink currently focuses on iSCSI: it resolves the latest port and exposes it as a fixed local connection.
Context
STUN/P2P can expose the current mapped port, but that port may change. Many clients are not designed for frequent manual port edits.
It turns the changing remote port into a stable local entry. Clients keep using the local address while ZsLink follows remote changes.
Currently focused on iSCSI. Local browser access and Synology Drive Client have been verified. Other clients should be checked by actual behavior.
How it works
Your iSCSI client, local browser, or Synology Drive Client connects to a fixed local address and port instead of repeatedly editing remote ports.
ZsLink reads the configured dynamic address, gets the current remote port, and shows the current target plus the latest check result.
After closing the main window, ZsLink stays in the menu bar. When the port changes, status and logs help confirm the connection.
Guide
Download the DMG, open it, and drag ZsLink.app to Applications. If macOS blocks the first launch, allow it in System Settings under Privacy & Security.
Enter the local listen port and the dynamic discovery URL in ZsLink. Your iSCSI client, local browser, or Synology Drive Client connects to this local address.
Click Start. When the remote mapped port changes, ZsLink checks and updates so local clients do not need repeated port edits.
Download
Works with macOS 13 and later. Download, drag ZsLink into Applications, and follow the macOS prompt on first launch.
Contact
Please include your macOS version, client type, and local port setup.