Open MrVb0 opened 9 months ago
@MrVb0 i think you want random hosts/snis when get subscribe. hosts can be done. considering add it later snis case some problems.
@wyx2685 Yes, this is one of the things we need, and of course I have explained other things in the update https://github.com/wyx2685/v2board/issues/37#issue-2014542513.
I use Google Translate and some translations may be wrong, I apologize if I did not get my meaning right.
@wyx2685 We can do these things in another style: We give the panel a list of sni, And we have also entered this list in the xrayr sni section (or the automatic panel gives it to xrayr through api) Now, through cronjob, let's order the panel to replace the next sni in the subscription every day at 3 am. And tomorrow the next sni... and tomorrow the next sni... (The same can be done for "ws host header" and "node address" and even other fields) It can also be other commands that are done by Cronjob every day at 3 am, for example: - automatic change of private key / public key / shortid
*** According to rprx, changing sni / private key / public key / shortid every day can help not to be recognized and maybe this method will save us from blocking our IPs a lot.
** Likewise, things like changing the node address and ws host header every day can prevent the creation of additional child nodes (https://github.com/wyx2685/XrayR/issues/16#issuecomment-1824509293).
@MrVb0 xray can support random sni by default. only considering go with that
من تا حالا یک بار ندیدم برنامه نویسش به درخواستها اهمیت بده و فقط هر چیزی رو خودش بخواد طراحی میکنه. ولی بازم دمش گرم . کمک خیلی بزرگی به ما کرده.
Hello, good time, thank you for your good script According to what has been heard and rprx mentioned it , dividing the reality traffic between several SNIs is a very convenient way to avoid IP detection and blocking. As discussed in this topic https://github.com/XTLS/Xray-core/discussions/2450 and other topics, gfw in Iran recently detects reallity and quickly blocks IP. We are looking for ways to make this diagnosis and identification more difficult for gfw.
I would be grateful if a possibility is added to v2board so that we can specify several sni for a node and with each subscription update, the sni of that node will change. (Like something like this: https://github.com/hiddify/Hiddify-Manager/wiki/How-to-use-subdomains-of-a-website-in-Reality)
Also, it will be much better if this method can be used in the remaining sections such as "address" and "ws host header" or "http host header" (for example, enter several addresses in one configuration and change the address with each subscription update) / For example, enter several ws host headers in one config and change ws host header with each subscription update) By doing this, we can spread the traffic to some extent between different servers and prevent the creation of additional nodes.
It would be great if you provide the possibility for the panel to automatically change the public key and private key every few days(for example, change them every 3 days at 3 am) (according to rprx, this directly and greatly helps not to be identified)
It would be good if it is possible to generate more short IDs and change the short ID with each subscription update (according to rprx, changing the short ID may help to avoid detection)
Also, despite the above features, it would be good if xrayr could read "sni" and "dest" as well as "public key" and "private key" and "shortid" through api from the v2board panel.
If there is a feature like spiderx that can help prevent gfw detection, please add it.
Thank you for helping us in this way