Skip to content
Search found 19 matches
- by mark143
- Thu Apr 18, 2019 6:41 pm
- Forum: Viscosity Support (Windows Version)
- Topic: MTU-Disc
- Replies: 1
- Views: 3705
Which OSs are supported?
- by mark143
- Wed Apr 17, 2019 6:51 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Network Cache
- Replies: 1
- Views: 3566
Is there a way to clear any cache in the system that may affect connectivity?
It would be nice a command that is executed prior to establishing connection
It would be nice a command that is executed prior to establishing connection
- by mark143
- Tue Aug 28, 2018 12:41 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Voracle Vulnerability
- Replies: 1
- Views: 3868
Eric, To address this vulnerability, VPN Providers turned off their compression protocol in their respective apps. Subsequently, they have modified their manual config files by adding "comp-lzo no" However, under viscosity app, "Options -> Compression", this needs to be set to &q...
- by mark143
- Sat Aug 11, 2018 10:15 am
- Forum: Viscosity Support (Windows Version)
- Topic: Replay Window
- Replies: 1
- Views: 4423
Eric, I'm getting this message sporadically. It is prevalent during streaming. It usually stops after buffering has stabilized. Any thoughts on addressing this? It comes with different values PID_ERR replay-window backtrack occurred [17] [SSL-3] [0_________________00000000000000000000000000000000000...
- by mark143
- Sat Aug 11, 2018 10:05 am
- Forum: Viscosity Support (Windows Version)
- Topic: ns-cert-type Warning
- Replies: 3
- Views: 7123
Eric, I'm using "--remote-cert-tls server" in my client conf. However, I'm still getting: "WARNING: –ns-cert-type is DEPRECATED. Use --remote-cert-tls instead." I'm using the v1.7.11 Not sure if the server conf has been changed to ""--remote-cert-tls client" since ...
- by mark143
- Sat Jul 21, 2018 9:34 am
- Forum: Viscosity Support (Windows Version)
- Topic: Random Ports
- Replies: 1
- Views: 4057
Hi Eric,
Is it possible to have Viscosity to connect randomly in any of these ports?
TCP Ports: 443, 10288 to 10298
UDP Ports: 1195, 1198, 10088 to 10098, 10188 to 10198
Is it possible to have Viscosity to connect randomly in any of these ports?
TCP Ports: 443, 10288 to 10298
UDP Ports: 1195, 1198, 10088 to 10098, 10188 to 10198
- by mark143
- Thu Jul 19, 2018 4:43 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Dynamic MTU
- Replies: 1
- Views: 4093
Eric,
When I run mtu-test I get different values from time to time. Is this normal? What would be a safe mtu value if everytime you run a test you get between 1200 and 1297
When I run mtu-test I get different values from time to time. Is this normal? What would be a safe mtu value if everytime you run a test you get between 1200 and 1297
- by mark143
- Thu Jul 19, 2018 4:41 pm
- Forum: Viscosity Support (Windows Version)
- Topic: retrieve username/password?
- Replies: 3
- Views: 9731
Eric,
How about integrating the username and password in the client configuration file? Is this possible?
How about integrating the username and password in the client configuration file? Is this possible?
- by mark143
- Thu Jul 12, 2018 3:53 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Header Sizes
- Replies: 1
- Views: 3841
Hi!
Some of the parameters of opevpn carries additional header, such as "fragment" which carries additional 4 bytes. Do you happen to have a listing of how much header is added for the different parameters?
Thanks
Some of the parameters of opevpn carries additional header, such as "fragment" which carries additional 4 bytes. Do you happen to have a listing of how much header is added for the different parameters?
Thanks
- by mark143
- Tue Jul 10, 2018 9:25 am
- Forum: Viscosity Feedback
- Topic: Feature Request
- Replies: 0
- Views: 68366
Is it possible to include:
1. Ping test to multiple VPN Server
2. Download test
3. Best server recommendation
1. Ping test to multiple VPN Server
2. Download test
3. Best server recommendation