Closed mazzz1y closed 1 year ago
Routing rule with auth_user field sometimes not working and traffic goes to the next chain rule. It cause connection leak.
auth_user
Type of connection: BitTorrent client(qBittorrent) over socks proxy with authorization.
I debugged a bit and some connections doesn't have metadata.User field. I think that it is the reason.
metadata.User
Please pay attention to these lines:
inbound/mixed[mixed-in]: inbound packet connection to 0.0.0.0:0 router: match[2] inbound=[trojan-in mixed-in] => 1-trojan-out outbound/trojan[1-trojan-out]: outbound multiplex packet connection to 0.0.0.0:0
As workaround I added rule to block all mixed-in connections with non-matching auth_user field
mixed-in
Try 9e67f3b4a59f6310f1a7df452e6659b148915848
Can't reproduce now. Thank you
Welcome
Description of the problem
Routing rule with
auth_user
field sometimes not working and traffic goes to the next chain rule. It cause connection leak.Type of connection: BitTorrent client(qBittorrent) over socks proxy with authorization.
I debugged a bit and some connections doesn't have
metadata.User
field. I think that it is the reason.Version of sing-box
Server and client configuration file
Server and client log file
Please pay attention to these lines:
Additional info
As workaround I added rule to block all
mixed-in
connections with non-matchingauth_user
field