Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add config option for tcp keep-alive in intercept.v1, host.v1 and host.v2 #1567

Closed
plorenz opened this issue Dec 7, 2023 · 1 comment
Closed

Comments

@plorenz
Copy link
Member

plorenz commented Dec 7, 2023

Add config option for tcp keep-alive in intercept.v1, host.v1 and host.v2. This should us to detect when a connection goes down, so we can tear down the associated ziti circuit. When there's a clean TCP close, we shouldn't need it, but this will help us in those cases where we have a non-graceful connection termination on the remote side of the connection. Additionally, users may want to be able to enable this behavior.

Intercept.v1 example:

{
    "addresses" : [ "echo.ziti" ],
    "portRanges" : [
        { "low" : 1234, "high" : 1234 }
    ],
    "protocols" : ["tcp"],
    "tcpOptions" : {
        "keepAlivePeriod" : "15s"
    }
}

Host.v1 example

{
    "address" : "localhost",
    "port" : 1234,
    "protocol" : "tcp",
    "tcpOptions" : {
        "keepAlivePeriod" : "15s"
    }
}

Host.v2 will use the same syntax as host.v1

@plorenz
Copy link
Member Author

plorenz commented Dec 8, 2023

For now we're not going to make this configurable.

@plorenz plorenz closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant