[GH-ISSUE #3281] Method to forward through a client to an internal device?

gitea-mirror commented

2026-05-05 13:41:56 -06:00

Owner

Copy link

Originally created by @ylluminate on GitHub (Feb 1, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3281

Describe the feature request

In a scenario where one needs to access another device on a LAN that is incapable of running frpc, is it possible to have an frpc client on a system forward access to another internal IP+port?

So, as an example, if I need to directly access a network device at LAN IP:port 192.168.0.15:2345, could another frpc.ini be setup to facilitate accessing that device through itself and creating the tunnel back out to the frps server?

If this can be done, is there an example config for the frpc.ini to do this?

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @ylluminate on GitHub (Feb 1, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3281 ### Describe the feature request In a scenario where one needs to access another device on a LAN that is incapable of running `frpc`, is it possible to have an `frpc` client on a system forward access to another internal IP+port? So, as an example, if I need to directly access a network device at LAN IP:port 192.168.0.15:2345, could another `frpc.ini` be setup to facilitate accessing that device through itself and creating the tunnel back out to the `frps` server? If this can be done, is there an example config for the `frpc.ini` to do this? ### Describe alternatives you've considered _No response_ ### Affected area - [X] Docs - [X] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror closed this issue

2026-05-05 13:41:57 -06:00

gitea-mirror commented

2026-05-05 13:41:59 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Feb 1, 2023):

https://github.com/fatedier/frp/blob/dev/conf/frpc_full.ini#L153

@fatedier commented on GitHub (Feb 1, 2023): https://github.com/fatedier/frp/blob/dev/conf/frpc_full.ini#L153

gitea-mirror commented

2026-05-05 13:41:59 -06:00

Author

Owner

Copy link

@ylluminate commented on GitHub (Feb 1, 2023):

Thank you, this helps. It does appear that simply forwarding an IP + port to another device actually works perfectly. This leads me to believe that one could simply run frpc on a single system on a LAN and then forward all ports to any and all devices desired through this singular client.

@ylluminate commented on GitHub (Feb 1, 2023): Thank you, this helps. It does appear that simply forwarding an IP + port to another device actually works perfectly. This leads me to believe that one could simply run `frpc` on a single system on a LAN and then forward all ports to any and all devices desired through this singular client.

No Branch/Tag specified