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

Support multiple connection types #78

Open
WendelHime opened this issue Oct 10, 2024 · 0 comments
Open

Support multiple connection types #78

WendelHime opened this issue Oct 10, 2024 · 0 comments

Comments

@WendelHime
Copy link

WendelHime commented Oct 10, 2024

At lantern listener side (http-proxy), when we make a multiplex listener/wrap listeners, we return a custom connection type (idleConn - there's other custom connections/listeners under the same package, most of them are implementing net.Conn). As an WATER user I want to be able send a custom net.Conn and use this connection to successfully communicate.
Currently when I try to provide an idle connection I got the following error message:

ERROR water_plain_v1: water: PushConn: water: unsupported connection type: *listeners.idleConn 
2024/10/10 13:04:43 dial: v1net.Listener.Accept: errno 8

This message is being triggered here, falling into the default condition, since the custom connection is not supported.

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