batch-fragment-test 3.3

Fixes regarding Issues

• #6 #11 Handling space characters in xray core and config file paths.

Changes

• Duplicated selection of random set of fragment values is no longer allowed.
• Maximum possible instances of random sets is calculated and prompted again if the input exceeds the max.

batch-fragment-test 3.2

Fixes regarding Issues

#7 as suggested by @GFW-knocker:

• Set the number of requests (how many times a fragment value set should be tested) per instance at the beginning of the run.
• Drop the value of first ping request to achieve more accurate results.

batch-fragment-test 3.1

Fixes regarding issues

• #4 Execution policy bypass should work on Windows 11 as well.
• #6 Xraylogs.txt keeps logs for all instances during the entire run for debugging.
• #7 Added suggested fragment values.

Notice

• If you still encounter issues with bypassing Execution Policy, until we find a better fix, first open powershell:
  On Windows 10, try:
  Set-ExecutionPolicy Bypass -Scope Process
  On Windows 11, try:
  Set-ExecutionPolicy RemoteSigned -Scope Process

Then navigate to your script folder cd C:\ExampleFolder and run the script .\batch-fragment-test.ps1

batch-fragment-test 3.0

Changelog

Script revamped for a neat output.

• Script output is now shown as Tables (Thanks to @ircfspace)
• Xray core logs are saved separately at xraylogs.txt, to keep the console output clean.
• #1 Changed test URL to Cloudflare to achieve better ping results.

Contributors

• Big thanks to @ircfspace for reviewing, testing and contributing to the code.

batch-fragment-test 2.1

• Reduced allowed delay time between each test.
• Better handling of invalid ping tests.

Provided config.json in batch-fragment-test-with-core is just an example and might not work. Suggest that you should use your own config for better results, refer to the manual.

batch-fragment-test 2.0

PowerShell script revamped for ease of use.

• Bypassing execution policy, instances, timeout and proxy port are prompted in the beginning of the run.
• Running PowerShell as admin is no longer necessary, can open the script directly with PowerShell.
• The script no longer needs Curl for requests, HttpWebRequest is used instead.
• Absolute paths are removed. Ensure Xray Core xray.exe and Fragment v2ray config config.json are in the same folder as the PowerShell script.

batch-fragment-test 1.3

• Ping requests are now in HTTPS.
• Implementing Curl request directly instead of using Invoke-WebRequest command.

batch-fragment-test 1.2

• The script now runs the test using Curl on socks5://127.0.0.1:10808
• Setting Timeout for pings is conveniently changeable, as $TimeoutSec variable.
• Xray core version provided here is at 1.8.11, you could get latest version from here.

batch-fragment-scanner 1.1

• Now after the end of the test, the console displays the top three (best) pings with their fragment values.
• Changing Instances (number of fragment tests) is conveniently changeable, as $Instances variable.
• Added more default fragment values.
• Xray core version here is at 1.8.11, so use the latest version from here.

batch-fragment-test

• Version 1.0 with the ability to batch test various fragment values for Cloudflare-based configs.
• For detailed instructions: https://github.com/Surfboardv2ray/batch-fragment-test/blob/main/README.md