From: HadetTheUndying <HadetTheUndying@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openvpn build with libressl-3.1.3 does not connect
Date: Mon, 17 Aug 2020 17:07:19 +0200 [thread overview]
Message-ID: <20200817150719.1xkeswP5x5zeVieTQzZve0XJImZ6PUisOnpB4FGgRY8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23413@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
New comment by HadetTheUndying on void-packages repository
https://github.com/void-linux/void-packages/issues/23413#issuecomment-674936953
Comment:
I just wanted to update that ProtonVPN does connect now, i'm not sure when it started working. It does take awhile to complete the connection, I'm not sure what causes the slowdown but it took over a minute.
```
hadet@endurance ~ protonvpn c --fastest
Connecting to US-IL#34 via UDP...
Connected!
hadet@endurance ~ ping google.com
PING google.com (172.217.8.206) 56(84) bytes of data.
64 bytes from ord37s09-in-f14.1e100.net (172.217.8.206): icmp_seq=1 ttl=117 time=58.3 ms
64 bytes from ord37s09-in-f14.1e100.net (172.217.8.206): icmp_seq=2 ttl=117 time=52.4 ms
64 bytes from ord37s09-in-f14.1e100.net (172.217.8.206): icmp_seq=3 ttl=117 time=81.5 ms
64 bytes from ord37s09-in-f14.1e100.net (172.217.8.206): icmp_seq=4 ttl=117 time=75.2 ms
64 bytes from ord37s09-in-f14.1e100.net (172.217.8.206): icmp_seq=5 ttl=117 time=78.1 ms
64 bytes from ord37s09-in-f14.1e100.net (172.217.8.206): icmp_seq=6 ttl=117 time=56.9 ms
```
If anyone else can confirm i think it might be safe to close the issue.
next prev parent reply other threads:[~2020-08-17 15:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 11:39 [ISSUE] " jkoderu-git
2020-07-06 13:03 ` Johnnynator
2020-07-06 13:26 ` TinCanTech
2020-07-06 16:15 ` jkoderu-git
2020-07-06 18:13 ` TinCanTech
2020-07-06 18:27 ` ericonr
2020-07-06 18:58 ` jkoderu-git
2020-07-08 14:43 ` Johnnynator
2020-07-08 15:06 ` TinCanTech
2020-07-08 17:44 ` jkoderu-git
2020-07-10 13:40 ` HadetTheUndying
2020-07-10 15:55 ` TinCanTech
2020-07-10 15:57 ` TinCanTech
2020-07-10 15:57 ` TinCanTech
2020-07-10 15:58 ` Johnnynator
2020-07-10 16:02 ` TinCanTech
2020-07-10 16:04 ` HadetTheUndying
2020-07-10 16:07 ` Johnnynator
2020-07-10 16:09 ` Johnnynator
2020-07-10 16:29 ` TinCanTech
2020-07-11 13:25 ` mvf
2020-07-12 10:54 ` jkoderu-git
2020-07-12 11:38 ` jkoderu-git
2020-07-12 17:03 ` HadetTheUndying
2020-07-12 17:26 ` jkoderu-git
2020-08-17 15:06 ` HadetTheUndying
2020-08-17 15:07 ` HadetTheUndying [this message]
2020-08-22 12:45 ` jkoderu-git
2020-08-22 13:33 ` jkoderu-git
2020-08-22 13:33 ` jkoderu-git
2021-01-21 17:54 ` ericonr
2021-01-22 9:46 ` travankor
2021-01-22 9:47 ` travankor
2021-01-22 13:12 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200817150719.1xkeswP5x5zeVieTQzZve0XJImZ6PUisOnpB4FGgRY8@z \
--to=hadettheundying@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).