- Fix: On demand monitor could crash
Search found 440 matches
- Wed Jan 25, 2023 12:02 pm
- Forum: VPN Client Pro Announcements
- Topic: New release 1.01.29
- Replies: 0
- Views: 66
New release 1.01.29
- Wed Jan 25, 2023 9:30 am
- Forum: VPN Client Pro Support
- Topic: NAT-T Support for Softether Protocol (Using UDP 53 instead of 443)
- Replies: 5
- Views: 183
Re: NAT-T Support for Softether Protocol (Using UDP 53 instead of 443)
UDP over DNS and NAT-T has been added in the new version 1.01.29.
Please, update the app and check the "Remote servers" section.
Please, update the app and check the "Remote servers" section.
- Wed Jan 25, 2023 9:23 am
- Forum: VPN Client Pro Announcements
- Topic: New release 1.01.28
- Replies: 0
- Views: 24
New release 1.01.28
- (SoftEther) UDP Over DNS / NAT-T
- Fix: crash for KeyPermanentlyInvalidatedException in biometric authentication
- Minor improvements/bug fixes
- Wed Jan 25, 2023 6:26 am
- Forum: VPN Client Pro Support
- Topic: Unable to connect over TUN - TLS error
- Replies: 6
- Views: 77
Re: Unable to connect over TUN - TLS error
2023-01-24 14:24:43 TCP: connect to [AF_INET]73.12.x.x:12973 failed: Connection refused This error means that the connection was rejected by the remote host. This usually happens when the VPN server is not running or listening on another port or a firewall is rejecting TCP-SYN packets. I'm sorry bu...
- Tue Jan 24, 2023 5:42 am
- Forum: VPN Client Pro Support
- Topic: Unable to connect over TUN - TLS error
- Replies: 6
- Views: 77
Re: Unable to connect over TUN - TLS error
Android can use PIA VPN without issue. Probably this VPN uses another port and/or the TCP protocol. Router logs don't show the android trying to connect. This means that packets sent by the client are blocked. I'm thinking an issue with TUN? If the TUN/TAP configuration does not match the VPN conne...
- Mon Jan 23, 2023 4:24 pm
- Forum: VPN Client Pro Support
- Topic: Unable to connect over TUN - TLS error
- Replies: 6
- Views: 77
Re: Unable to connect over TUN - TLS error
2023-01-22 18:45:43 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) This error means that the client receives no response from the server. So sent and/or received packets are lost. This usually happens when there is a firewall between the client an...
- Mon Jan 09, 2023 10:13 am
- Forum: VPN Client Pro Support
- Topic: How to set mssfix setting
- Replies: 1
- Views: 69
Re: How to set mssfix setting
Hello,
here the steps:
here the steps:
- edit the VPN profile
- tap on "Remote servers"
- tap on server's ip/hostname
- select "Limit Maximun Segment Size MSS" and put the wished value
- Mon Jan 09, 2023 10:02 am
- Forum: VPN Client Pro Support
- Topic: auto connect fall over
- Replies: 1
- Views: 56
Re: auto connect fall over
Hello,
you can already handle this situation by editing the VPN profile and adding a new entry in the "Remote servers" section
you can already handle this situation by editing the VPN profile and adding a new entry in the "Remote servers" section
- Thu Dec 29, 2022 10:58 am
- Forum: VPN Client Pro Support
- Topic: Android OpenVPN-TAP - Bonjour/ZeroConf Multicasting Packets Not Sent/Recieved
- Replies: 13
- Views: 485
Re: Android OpenVPN-TAP - Bonjour/ZeroConf Multicasting Packets Not Sent/Recieved
It is not the server that does not send multicast packets but the client that does not send them. In practice, the app that needs to connect to the iTunes server sends mDNS multicast packets, but the Android system on your device doesn't forward them to the VPN interface. I think this problem is due...
- Wed Dec 28, 2022 7:28 pm
- Forum: VPN Client Pro Support
- Topic: Android OpenVPN-TAP - Bonjour/ZeroConf Multicasting Packets Not Sent/Recieved
- Replies: 13
- Views: 485
Re: Android OpenVPN-TAP - Bonjour/ZeroConf Multicasting Packets Not Sent/Recieved
You're welcome. I checked the results of the tcpdumps you sent me and the Android one doesn't have mDNS multicast packets. I've done some testing with the Android emulator and the multicast packets are forwarded just fine, so it seems that the device you are using is not forwarding the multicast pac...