[GH-ISSUE #3197] can work if install on a private ip host and set port map in a router which have a public ip?

gitea-mirror commented

2026-05-05 13:39:07 -06:00

Owner

Copy link

Originally created by @lygn128 on GitHub (Dec 4, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3197

Describe the feature request

client A：private ip host;
client B: private ip host;
Server A: private ip host under a public ip router R;
i want ssh to client A from client B, if i install frp in Server A, and config port map in route R,
do the config can work? thank you very much.

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 @lygn128 on GitHub (Dec 4, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3197 ### Describe the feature request client A：private ip host; client B: private ip host; Server A: private ip host under a public ip router R; i want ssh to client A from client B, if i install frp in Server A, and config port map in route R, do the config can work? thank you very much. ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:39:07 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:39:10 -06:00

Author

Owner

Copy link

@Becods commented on GitHub (Dec 5, 2022):

Yes, the odds are that this will work.

Practice makes perfect.

@Becods commented on GitHub (Dec 5, 2022): Yes, the odds are that this will work. Practice makes perfect.

gitea-mirror commented

2026-05-05 13:39:11 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jan 5, 2023):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jan 5, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified