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

udp not working #31

Closed
rudius opened this issue Feb 15, 2021 · 7 comments
Closed

udp not working #31

rudius opened this issue Feb 15, 2021 · 7 comments

Comments

@rudius
Copy link

rudius commented Feb 15, 2021

i m trying v2.1.0 linux amd64 with command ./tun2socks-linux-amd64 -device tun://tun0 -proxy socks5://127.0.0.1:1080

I m routing all traffic from another linux on the network to the tun interface.

Tcp is working great but udp is not working at all.

i ve got this

WARN[7446] [UDP] write to 1.1.1.1:53 error: write udp [::]:40930->127.0.0.1:0: sendto: invalid argument
INFO[7446] [UDP] 192.168.0.35:34418 --> 1.1.1.1:53

@xjasonlyu
Copy link
Owner

Would mind to tell which socks5 server you were using with?

It’s wired that your server sent 127.0.0.1:0 as bind address in UDP.

@rudius
Copy link
Author

rudius commented Feb 15, 2021

it shadowproxy_libev on port 1080.

i just did ip link set dev tun0 up. I didn t attached an ip to it and my routes were going to dev tun0. Maybe it s that? TCP is working though

@xjasonlyu
Copy link
Owner

i just did ip link set dev tun0 up. I didn t attached an ip to it and my routes were going to dev tun0. Maybe it s that? TCP is working though

No, tun doesn’t need a ip address could still work if you have route table to it.

BTW, what is shadowproxy_libev? Do you mean shadowsocks_libev, if it is then which version of it?

@rudius
Copy link
Author

rudius commented Feb 15, 2021

yes it s shadowsocks-libev V3.1.3 on ubuntu 18.04

@xjasonlyu
Copy link
Owner

It seems like a server side issue due to wrong bind-address of UDP. You may need to upgrade ss-libev to latest version (v3.3.5 now) since a lot UDP issues have been resolved.

If this bug still exists, please let me know.

@rudius
Copy link
Author

rudius commented Feb 15, 2021

currently doing the update. I will let you know

@rudius
Copy link
Author

rudius commented Feb 15, 2021

you were right. It s working. Thanks

@rudius rudius closed this as completed Feb 15, 2021
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

2 participants