Custom TCP & LAN Targets
FRP Auto Deploy is not limited to SSH/web. The stable core can publish arbitrary TCP targets reachable from an enrolled client.
Local custom TCP examples
LAN gateway pattern
The target does not have to run on the FRP client itself.
The only FRP-specific requirement for the target path is that the FRP client can make a normal TCP connection to the configured target-host:target-port.
Before publishing a LAN target
Stable Service ID
Use a descriptive stable Service ID, for example:
Changing the display name or target later should not require changing the Service ID.
Security responsibility
Publishing a database, appliance, or API makes that TCP endpoint reachable through the public FRP entry point. FRP Auto Deploy does not automatically configure:
- database users or ACLs
- application authentication
- target host firewalls
- network segmentation
- source-IP allow lists
Keep the target application’s own authentication and authorization enabled.
Be especially cautious when publishing databases or administrative appliance ports. A reachable port is not the same thing as an appropriately secured service.
Port lifecycle
Normal target edits and disable/enable operations are designed to preserve the public-port reservation. Use release service only when you intend to return the port to the pool.