Obfuscation with V2Ray #391
Conversation
Fix build issue
OPT deprecated api `extractnativelibs` instead use ```kotlin
packaging {
jniLibs {
useLegacyPackaging = true
}
}
```
Update dependencies & Fix gradle Scripts
Add swig home brew path
Fix anchor
Remove package from manifest
Fix sdk and libs version
Add obs type
Update Api Models
Add libv2ray
Add config model
Add config construction logic
# Conflicts: # core/src/main/java/com/wireguard/android/backend/GoBackend.java # core/src/main/java/net/ivpn/core/vpn/controller/V2rayController.kt # core/src/main/java/net/ivpn/core/vpn/wireguard/ConfigManager.kt
- Replace manual ServerSocket port checking with libV2ray.GetFreePorts() - Remove unused isPortAvailable method and V2RAY_PORT_RANGE constant - Improve error handling and logging for port allocation - Use kernel-level port allocation for better reliability and performance
Port thumbnail
|
@jurajhilje Please review the pr and check if both VMESS/QUIC and VMESS/TCP + Wireguard Single Hop And Multi Hop working perfectly or not. Also if there are inconsistencies or something missing maybe in UI ? then drop a message in this thread. BTW it partially closes the pr #389, as it updated the dependencies and what just need to be done is update target sdk |
|
@jurajhilje I see the builds are failing. For your information. You need to run the build.sh to build the aar binary for the v2ray core wrapper. The workflow currently is not doing that because of that its failing you can check the logs |
Understood, I will update the workflow, thanks! |
Update workflow.
Anyways updated the workflow also to speedup the process |
|
Build failed. Why are we building aar for the main project ? |
I need to check and update the build Action. Will let you know how it goes. |
Well we cant keep the aar in the core module as it will cause merge conflict of dex when assembling debug builds through gradlew. But you can test it by running the project simply that works. So I need find some solution for that which works |
Fix Build issue
|
Works now |
Add description for obfuscation
SUB ISSUE 3 - FIX PORTS
PR type
What kind of change does this PR introduce?
PR checklist
Please check if your PR fulfills the following requirements:
What is the current behavior?
Currently, WireGuard does not support obfuscation with V2Ray.
Issue number: #295
What is the new behavior?
WireGuard now supports obfuscation with V2Ray, including both VMESS over TCP and QUIC, for both single-hop and multi-hop configurations.
Does this PR introduce a breaking change?
Other information