mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #2837] [Feature Request] Please document how lifecycle of a remote port (as well as its traffic) is managed. #2267
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#2267
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @enihcam on GitHub (Mar 13, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2837
Describe the feature request
From the doc i can see the remote port (via frp server) is managed by a local frp client.
If that's true, will this remote port be closed as long as the local port is closed (or frp client terminates)?
Or, if the local port is closed, will there be any traffic taken in place between server and client?
Thanks.
Describe alternatives you've considered
More infra docs maybe?
Affected area
@fatedier commented on GitHub (Mar 14, 2022):
You can find what you want to know by reading source codes.
We haven't enough time to write tutorial and all codes are open source.
@github-actions[bot] commented on GitHub (Apr 14, 2022):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.