Vladimir Dubrovin

in this case start few 'proxy' bound to different interfaces proxy -i127.0.0.1 -pport1 -DeINTERFACE1 proxy -i127.0.0.1 -pport2 -DeINTERFACE2 and use parent WEIGHT1 http 127.0.0.1 port1 parent WEIGHT2 http 127.0.0.1 port2...

It probably means either the sequence of commands is wrong (e.g. you have matching allow rule prior to deny) or you have auth none or you did not applied configuration...

@APX403 See https://3proxy.ru/plugins/StringsPlugin/ There is an example for .3ps file in 3proxy distribution.

`parent` is applied to preceeding `allow` command, that is in this configuration ``` allow * * list1 parent 1000 parent1 ... allow * * list2 parent 1000 parent ... allow...

According to this log, 3proxy received control (TCP) connection and accepted UDPASSOC command, but no UDP traffic reached 3proxy. You can add `logdump 1 ` to see every UDP packet...

real IP address is expected instead of 0.0.0.0 here, because proxy reports this IP to client, so it can use it to accept incoming traffic.

Internal is an address you expecting client connection to come to (an address you specify as proxy address), external is an address you expect outgoing connection to go from, probably...

UDPASSOC works in latest versions. Check firewall issues. UDPASSOC requires access to ephemeral UDP ports.

Try to eliminate putty and use sockscap directly with 3proxy (internal interface in this case must be set to real IP address)

you can also check the traffic with tcpdmp on internal interface to see if any UDP packets are received by proxy.