You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe that any server-side management logic requires high-level boundary management interfaces to implement it. Manually restarting the service with a new configuration is not the best choice for a high-loaded environment where many users and protocols are handled.
Such interfaces are already implemented in v2fly/v2ray-core, but I find their implementation generally messy, so I prefer to switch to sing-box. Unfortunately, such functionality is not implemented there yet, as far as I understand...
I decided to implement this myself, so check out my contribution. I'm still working on it, but overall it's done and working fine as far as I can verify.
I have some suspicions that this might break something, because some experimental tools like the Clash API can get a pointer to outgoing connections to work with them separately, and during work time these outgoing connections can be removed from the router, but so far I haven't found any problems with this (doesn't means there is no of them).
I believe that any server-side management logic requires high-level boundary management interfaces to implement it. Manually restarting the service with a new configuration is not the best choice for a high-loaded environment where many users and protocols are handled.
Such interfaces are already implemented in
v2fly/v2ray-core
, but I find their implementation generally messy, so I prefer to switch tosing-box
. Unfortunately, such functionality is not implemented there yet, as far as I understand...I decided to implement this myself, so check out my contribution. I'm still working on it, but overall it's done and working fine as far as I can verify.
I have some suspicions that this might break something, because some experimental tools like the Clash API can get a pointer to outgoing connections to work with them separately, and during work time these outgoing connections can be removed from the router, but so far I haven't found any problems with this (doesn't means there is no of them).
Please check my pull request: #2177
The text was updated successfully, but these errors were encountered: