[GH-ISSUE #2043] Just a quick question if possible, thank you for writing this excellent code. #1626

Closed
opened 2026-05-05 13:02:20 -06:00 by gitea-mirror · 6 comments
Owner

Originally created by @jreiners on GitHub (Oct 30, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2043

Hello, just a quick general question, how is it handled if

OTHERPC-A & ClientB | server

I've got it all working great for localhost ports on ClientB

if I wanted to host OTHERPC-A:8080 over client b's config, is this possible?

I tried setting local_ip = OTHERPC-A's IP and it didn't seem to work for me. I looked at the go source a bit, was just curious if possible without adding a socat on localhost forwarding to OTHERPC-A?

Originally created by @jreiners on GitHub (Oct 30, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2043 Hello, just a quick general question, how is it handled if OTHERPC-A & ClientB | server I've got it all working great for localhost ports on ClientB if I wanted to host OTHERPC-A:8080 over client b's config, is this possible? I tried setting `local_ip = OTHERPC-A's` IP and it didn't seem to work for me. I looked at the go source a bit, was just curious if possible without adding a socat on localhost forwarding to OTHERPC-A?
gitea-mirror 2026-05-05 13:02:20 -06:00
Author
Owner

@kingwilliam commented on GitHub (Oct 31, 2020):

Can you provide more information about what pcA service and port. (Like pcA ftp passive mode)

<!-- gh-comment-id:719851405 --> @kingwilliam commented on GitHub (Oct 31, 2020): Can you provide more information about what pcA service and port. (Like pcA ftp passive mode)
Author
Owner

@fatedier commented on GitHub (Nov 2, 2020):

You should make sure ClientB can connect to OTHERPC-A:8080.

<!-- gh-comment-id:720211272 --> @fatedier commented on GitHub (Nov 2, 2020): You should make sure ClientB can connect to OTHERPC-A:8080.
Author
Owner

@jreiners commented on GitHub (Nov 2, 2020):

@fatedier clientb can access otherpc-a:8080 no problem, they are behind the same firewall at that location, and on the same subnet, I ended up adding a temporary localhost port forward for 127:0.0.1:8080 >> otherpc-a:8080 and it worked, but I'd like to have frp just connect to the other host which would skip a step in setup for a bunch of users, and I could get rid of a bunch of services.

You have a great program, with a really nice interface thank you.

<!-- gh-comment-id:720587365 --> @jreiners commented on GitHub (Nov 2, 2020): @fatedier clientb can access otherpc-a:8080 no problem, they are behind the same firewall at that location, and on the same subnet, I ended up adding a temporary localhost port forward for 127:0.0.1:8080 >> otherpc-a:8080 and it worked, but I'd like to have frp just connect to the other host which would skip a step in setup for a bunch of users, and I could get rid of a bunch of services. You have a great program, with a really nice interface thank you.
Author
Owner

@jreiners commented on GitHub (Nov 2, 2020):

So local_ip can be other-machine-a's ip if it's on the same network?

On Sun, Nov 1, 2020, 9:05 PM fatedier notifications@github.com wrote:

You should make sure ClientB can connect to OTHERPC-A:8080.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fatedier/frp/issues/2043#issuecomment-720211272, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4PG7ER7RMFXAA6TUSTEHTSNYOXXANCNFSM4TFLLRPQ
.

<!-- gh-comment-id:720646330 --> @jreiners commented on GitHub (Nov 2, 2020): So local_ip can be other-machine-a's ip if it's on the same network? On Sun, Nov 1, 2020, 9:05 PM fatedier <notifications@github.com> wrote: > You should make sure ClientB can connect to OTHERPC-A:8080. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/fatedier/frp/issues/2043#issuecomment-720211272>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB4PG7ER7RMFXAA6TUSTEHTSNYOXXANCNFSM4TFLLRPQ> > . >
Author
Owner

@fatedier commented on GitHub (Nov 3, 2020):

Follow the issue template to show more info?

<!-- gh-comment-id:720916340 --> @fatedier commented on GitHub (Nov 3, 2020): Follow the issue template to show more info?
Author
Owner

@github-actions[bot] commented on GitHub (Dec 19, 2020):

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

<!-- gh-comment-id:748397368 --> @github-actions[bot] commented on GitHub (Dec 19, 2020): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#1626
No description provided.