We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please answer these questions before submitting your issue. Thanks!
2.5.6
win10
我在windows使用msys编译ssr local,运行访问udp包的时候,报如下错误: 2017-07-28 23:10:45 INFO: [udp] cache hit: 64.37.170.208:20042 <-> 127.0.0.1:56530 2017-07-28 23:10:45 INFO: [udp] cache hit: 64.37.170.208:20042 <-> 127.0.0.1:56530 2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
The text was updated successfully, but these errors were encountered:
Ssr和ss不同的吧,两个协议不同吧,
Sorry, something went wrong.
No branches or pull requests
Please answer these questions before submitting your issue. Thanks!
What version of shadowsocks-libev are you using?
2.5.6
What operating system are you using?
win10
What did you do?
我在windows使用msys编译ssr local,运行访问udp包的时候,报如下错误:
2017-07-28 23:10:45 INFO: [udp] cache hit: 64.37.170.208:20042 <-> 127.0.0.1:56530
2017-07-28 23:10:45 INFO: [udp] cache hit: 64.37.170.208:20042 <-> 127.0.0.1:56530
2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
2017-07-28 23:10:45 ERROR: [udp] remote_recv_sendto: 提供了一个无效的参数。
What did you expect to see?
What did you see instead?
What is your config in detail (with all sensitive info masked)?
The text was updated successfully, but these errors were encountered: