Keepalive timers for disconnected chisel client
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hello guys! Looks like you are doing a great things! Thank you for that!
One question pls:
I used chisel server / client with option "R" for forwarding traffic from server side to client.
But found the things like if to disconnect the client (for example unplug the cable ) from internet - the server side will still listening the port that client used before disconnect ( in forwarding option mode) . And of course once client will connect again in two-three minutes - it can't to do that as port is busy.
The server will disable this port after around 10 minutes. This is so long....
Is there some ways to fix that? may be add the keepalive timer on server side or something like that...
server v1.9.1
client v1.9.1
thank you for you job....
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the disconnected-client case using server-side R forwarding, then trace how the server handles a client that loses its network connection. Done means the forwarded port is released promptly after disconnection and a client reconnecting a few minutes later can bind it again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100