-
- Downloads
Test custom port range in quic hopping integration test.
The test also proofes that reading the appropriate environment variables work as expected on the server side. The obfsvpn client doesn't read environment variables and thus need to be invoked with the corresponding command line flags.
Showing
- .env 6 additions, 1 deletion.env
- .env.1ive.bridge 4 additions, 0 deletions.env.1ive.bridge
- .env.hopping 5 additions, 1 deletion.env.hopping
- .env.hopping.kcp 5 additions, 1 deletion.env.hopping.kcp
- .env.hopping.quic 4 additions, 0 deletions.env.hopping.quic
- .env.hoppingkcp.live.bridge 4 additions, 0 deletions.env.hoppingkcp.live.bridge
- .env.kcp 5 additions, 1 deletion.env.kcp
- .env.kcp.live.bridge 4 additions, 0 deletions.env.kcp.live.bridge
- .env.kcp.live.gw 5 additions, 1 deletion.env.kcp.live.gw
- .env.quic 4 additions, 0 deletions.env.quic
- docker-compose.yml 12 additions, 0 deletionsdocker-compose.yml
- images/obfsvpn-client/start.sh 25 additions, 1 deletionimages/obfsvpn-client/start.sh
Loading
Please register or sign in to comment