Difference between standalone socks5 and client socks5

[terrytw]

Dear Dev,

Thanks for this great project! Benefited a lot from it!

I recently run into a problem: I am trying to route traffic of qbittorrent through brook.

However if I run

brook server -l="0.0.0.0:8000" -p="password"
brook client --socks5="192.168.1.1:5555" -s="server ip:8000" -p="password"

And access 192.168.1.1:5555, all UDP trackers do not work, meaning that UDP over socks5 is not working for 192.168.1.1:5555

But if I run brook socks5 -l="server ip:5555"

And access server ip:5555, it works flawlessly.

Testing using brook testsocks5 -s shows that both 192.168.1.1:5555 and server ip:5555 is working.

I am banging my head against it for a couple of days now, it would be much appreciated if you can point me towards the right direction. Thank you!

A few additional notes: I don't want to use socks5 proxy directly because

1. socks5 is not a safe protocol that should be used on the internet.
2. I want to use udpovertcp function of brook.

[terrytw]

Update:

I have tried relayoverbrook, still no luck:

brook socks5 -l 127.0.0.1:10086
brook server -l server ip:8000 -p password
brook replayoverbrook -l 192.168.1.1:5555 s server ip:8000 -p password -t 127.0.0.1:10086

[txthinking]

GUI tun? CLI tun2brook?

On Sun, Nov 27, 2022 at 10:05 AM terrytw @.***> wrote:

Update:

I have tried relayoverbrook, still no luck:

brook socks5 -l 127.0.0.1:10086 brook server -l server ip:8000 -p password brook replayoverbrook -l 192.168.1.1:5555 s server ip:8000 -p password -t 127.0.0.1:10086

— Reply to this email directly, view it on GitHub https://github.com/txthinking/brook/issues/1057#issuecomment-1328152341, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJPFTYYFZ7O7OSFIRIE4X3WKK6W7ANCNFSM6AAAAAASMAVWV4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[terrytw]

GUI tun? CLI tun2brook? … On Sun, Nov 27, 2022 at 10:05 AM terrytw @.> wrote: Update: I have tried relayoverbrook, still no luck: brook socks5 -l 127.0.0.1:10086 brook server -l server ip:8000 -p password brook replayoverbrook -l 192.168.1.1:5555 s server ip:8000 -p password -t 127.0.0.1:10086 — Reply to this email directly, view it on GitHub <#1057 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJPFTYYFZ7O7OSFIRIE4X3WKK6W7ANCNFSM6AAAAAASMAVWV4 . You are receiving this because you are subscribed to this thread.Message ID: @.>

Hi, tun2brook does not seem to support udpovertcp which beats one of the main goals that I am trying to achieve.

[terrytw]

Besides, I don't intend to route all traffic on my system through brook.

[txthinking]

keyword: socks5 on /talks and /youtube

On Sun, Nov 27, 2022 at 11:28 AM terrytw @.***> wrote:

Besides, I don't intend to route all traffic on my system through brook.

— Reply to this email directly, view it on GitHub https://github.com/txthinking/brook/issues/1057#issuecomment-1328162278, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJPFT7QVA3CDLY24ZPQQMTWKLIOLANCNFSM6AAAAAASMAVWV4 . You are receiving this because you commented.Message ID: @.***>

[terrytw]

Hi thanks for the info I have actually read these before hand.

I just don't understand why socks5 proxy provided by brook client does not support UDP over socks5. Is it impossible to implement the same function from brook socks5?

[txthinking-bot]

it supports by unknown