Error: [mux.go:42] mux:unknown conn type, only tcp or kcp at both server and client while use kcp transport

[wellsgz]

Describe the bug
Both server and client sides report error as below:

[W] [mux.go:42]  mux:unknown conn type, only 
[W] [mux.go:448]  bad file descriptor
[W] [mux.go:448]  bad file descriptor
[W] [mux.go:448]  bad file descriptor

To Reproduce
Steps to reproduce the behavior:

1. use kcp as transport

• Server side

##bridge
bridge_type=kcp

• Client side

[common]
conn_type=kcp

Expected behavior
no error msg

Screenshots or logs

[I] [client.go:66]  Successful connection with server 1.2.3.4:567
[W] [mux.go:42]  mux:unknown conn type, only tcp or kcp
[W] [mux.go:448]  bad file descriptor
[W] [mux.go:448]  bad file descriptor
[W] [mux.go:448]  bad file descriptor

Server (please complete the following information):

• OS: Debian
• ARCH: amd64
• Tunnel: kcp
• Version: v0.25.4

Client (please complete the following information):

• OS: Debian
• ARCH: amd64
• Tunnel: kcp
• Version: v0.25.4

Additional context
tcp mode works fine.

[ffdfgdfg]

thx
Kcp package seems like not provides a fd method
xtaci/kcp-go#157
I tried to use unsafe.Pointer to convert kcp.UDPSession to net.UDPConn, wants to get fd, but fails.
So, I set a fixed value to fix this temporary, anyway, I will follow this issue, when it solved, I will update.

[wellsgz]

thx
Kcp package seems like not provides a fd method
xtaci/kcp-go#157
I tried to use unsafe.Pointer to convert kcp.UDPSession to net.UDPConn, wants to get fd, but fails.
So, I set a fixed value to fix this temporary, anyway, I will follow this issue, when it solved, I will update.

Thank you for update, is tcp the only working transport at the moment or I can ignore and error and use kcp as transport?

[ffdfgdfg]

thx
Kcp package seems like not provides a fd method
xtaci/kcp-go#157
I tried to use unsafe.Pointer to convert kcp.UDPSession to net.UDPConn, wants to get fd, but fails.
So, I set a fixed value to fix this temporary, anyway, I will follow this issue, when it solved, I will update.

Thank you for update, is tcp the only working transport at the moment or I can ignore and error and use kcp as transport?

Using tcp for now, I will solve other problems and update later

[ffdfgdfg]

try again

[wellsgz]

try again

Tested and it works like a charm now.