And also 4433 which is used by DTLS
https://wiki.wireshark.org/DTLS
--dad
On 20/11/18 9:53 AM, Lonnie Abelbeck wrote:
On Nov 19, 2018, at 2:33 PM, John wrote:
Should I stick with the "standard" udp service ports for my
trial-and-error based approach? Wikipedia has an article that lists
> On 19.11.2018, at 21:04, nico...@eisfunke.com wrote:
>
> Hello,
>
>> I’v installed wireguard-app from play store on android 8.1.
>> If using the userspace version i get a "key-icon" in the status-bar when a
>> tunnel is active.
>> Switching to the kernel version the icon is not working any
Nope,
Wireguard should work with multiple clients by default. You just have to
manually add the public key and assign an IP for each one.
Whether any specific configuration is “recommended” really depends on your
exact use-case and assessment of the other options that are available to you.
Are you certain that the dkms rebuild was triggered? Seems like like it
was not. Perhaps manually trigger it and reboot.
On Monday, November 19, 2018, Tosh wrote:
> Hello,
>
> I'm using Wireguard on ArchLinux since a long time, and today I have
> some troubles to start my VPN. Here is the log
Finally, something I can actually help with.
Yes, Verizon is actively blocking data through port 53.
Back in 2015 I discovered by accident that VPN traffic through port 53 on
Verizon was not monitored by whatever they use to calculate data usage.
Even better, it worked on deactivated sim cards
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
A new snapshot, `0.0.20181119`, has been tagged in the git repository.
Please note that this snapshot is, like the rest of the project at this point
in time, experimental, and does not consitute a real release that would be
considered
OK! Firstly, thank you to everyone who took the time to reply. I
think it's a safe assumption that WG is functioning as it should and
that I need to identify another port on which to run. I will post a
new thread on this topic.
On Mon, Nov 19, 2018 at 10:28 AM Jacob Schooley
wrote:
>
>
Hi Jordan,
On Mon, Nov 19, 2018 at 7:04 PM Jordan Glover
wrote:
>
> It fails to build for me (doing in-kernel build with Linux 4.20rc3 and
> WireGuard/contrib/kernel-tree/create-patch.sh) with below message:
>
>
> make[2]: *** No rule to make target
>
Hello,
If I were to set up a WireGuard server and have multiple clients
connecting to it, is there anything I need to be aware of? Specifically,
I am looking to understand if this is recommended as I already see
commercial offering of WireGuard - but not by all providers - so I was
wondering if
Hello!
I’v installed wireguard-app from play store on android 8.1.
If using the userspace version i get a "key-icon" in the status-bar when a
tunnel is active.
Switching to the kernel version the icon is not working any more.
Any sugestions?
Robert
Hello there!
I'm using WireGuard about a year and really happy with it. It's
easy-to-use, fast and stable. Great thanks for this precious software.
Sometimes I use servers from providers which do not have any internal
network. So I tried to setup Docker Swarm and route it's ingress network
over
On Monday, November 19, 2018 6:27 PM, Jason A. Donenfeld
wrote:
> Hello,
>
> A new snapshot, `0.0.20181119`, has been tagged in the git repository.
>
> Please note that this snapshot is, like the rest of the project at this point
> in time, experimental, and does not consitute a real release
Have you tried 1701/udp? That's the standard L2TP port - it's unlikely to
be particularly useful on networks which deliberate block VPN access, but
I've encountered a number of networks on which that port was usable, and
not much else.
Cheers,
Steve
On Tue, 20 Nov 2018 at 09:38 John wrote:
>
On Monday, November 19, 2018 8:02 PM, Jason A. Donenfeld
wrote:
> Hi Jordan,
> On Mon, Nov 19, 2018 at 7:04 PM Jordan Glover
> golden_mille...@protonmail.ch wrote:
>
> > It fails to build for me (doing in-kernel build with Linux 4.20rc3 and
> > WireGuard/contrib/kernel-tree/create-patch.sh)
14 matches
Mail list logo
