On Tue, Jul 3, 2018 at 8:12 PM Samuel Holland wrote:
> Right, trying to make it a global setting requires either some sort of
> out-of-band way to pass the information to wg-quick, or rewriting the
> configuration file every time the tunnel is brought up.
>
> Since from netd's point of view, this
On 07/02/18 21:31, Jason A. Donenfeld wrote:
> On Tue, Jul 3, 2018 at 4:27 AM Eric Kuck wrote:
>>
>> I was originally thinking the new fragment would be a per-tunnel thing
>> (set when you create the tunnel or edit it), but you’re right - making it
>> a general setting likely makes a whole lot mo
On 03.07.2018 11:59, Vbook A1 wrote:
WARNING: if you want to use ELrepo kernel - make sure your server does
not have the Matrox G200 series video card! CentOS 6.x with kernel 4.x
will not boot on Matrox GPU.
On Tue, Jun 26, 2018 at 1:10 PM, Lucian Cristian wrote:
On 26.06.2018 05:57, karthik k
WARNING: if you want to use ELrepo kernel - make sure your server does
not have the Matrox G200 series video card! CentOS 6.x with kernel 4.x
will not boot on Matrox GPU.
On Tue, Jun 26, 2018 at 1:10 PM, Lucian Cristian wrote:
> On 26.06.2018 05:57, karthik kumar wrote:
>
> Hi,
> I did see the
I was testing wireguard via a public wifi service (Icomera on-train
wifi) and found that the tunnel MTU wireguard had chosen was too large:
TCP connections got stuck as soon as any large amount of data was sent
(e.g. just running "top")
The MTU of the wifi service itself is 1440:
MacBook-Pro-
