Shawn Carey

unable to rebase due to unsigned commits in release-next. recreating PR as #1919.

Perhaps the most obvious solution would be to create a server socket using the operating system's sockets API to listen on spoofed IPs. Indeed this could work, but would be...

https://github.com/netfoundry/zfw can be used to work around this limitation.

do you know if this behavior was introduced with 0.19.10?

Hi @aidan-casey. Thanks for your interest! Logs certainly wouldn't hurt. Without those it's hard to know what you're running into, so please attach (or DM) when you can. It would...

added build configuration for windows/arm64 to dependencies: - ziti-sdk-c (https://github.com/openziti/ziti-sdk-c/pull/499) - ziti-tunnel-sdk-c (https://github.com/openziti/ziti-tunnel-sdk-c/pull/623)

I don't recall which version of zet was in use when this occurred. Based on commits to [smoketest.go](https://github.com/openziti/ziti/blob/release-next/zititest/models/smoke/smoketest.go) it could have been either [zet 0.22.25](https://github.com/openziti/ziti-tunnel-sdk-c/releases/tag/v0.22.25) ([csdk 0.36.7](https://github.com/openziti/ziti-sdk-c/releases/tag/0.36.7), which did _not_...

Hmm. The only zet version that used csdk 0.36.9 was zet 0.22.26 (and .27, which was only pre-release). Perhaps the smoketest was using a custom kit when this issue came...

I think the tunnel status message needs two indicators: `canBind` and `canDial` (or something in that spirit), because an identity may have permission for either or both operations.

possibly specify/enable this with an identity attribute e.g. `secureTunneler`