wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: S Bauer <sanderbauer@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: enabling WG0 allows telegram but impedes browsing
Date: Sun, 22 Aug 2021 01:27:53 +0500	[thread overview]
Message-ID: <20210822012753.27447e9f@natsu> (raw)
In-Reply-To: <CA+MSESn8FSHVmOjHQGsNsQqu89ijP3uGiz3ohE3Lbh6LHM3meA@mail.gmail.com>

On Fri, 20 Aug 2021 13:16:34 +0200
S Bauer <sanderbauer@gmail.com> wrote:

> Hello team,
> Hoping you could help me out with a foggy situation.
> The past week I have been struggling to get the Wireguard VPN working
> smoothly. Everything seems to work on paper, except in a specific way
> it doesn't. I am using Pop!_OS 21.04 (Ubuntu Hirsute).
> SitRep;
> I work as a freelance consultant and want to be careful about the
> local networks' peeping tom when accessing sensitive work documents
> from 'out of office', e.g. at a friend's place or at a hotel. So my
> objective is to access my home network via PiHole and then continue
> onward to access my work-related documents on a fileserver.
> I was hoping this could be easily achieved with Wireguard.
> Using the Wireguard VPN wg0 with wg-quick worked perfectly when I
> connected to my brother's phone hotspot (4G). I could access our home
> via VPN as expected and could work on my documents without any
> problems.
> The trouble is that I am now at a different location, working with a
> fixed router from Ziggo NL. For some reason the WG0 still connects
> perfectly, but after that a small mystery occurs. I did not make any
> modifications to WG0.conf, so I remain stumped.
> With WG active, I am no longer able to access any webpage. So no
> access to protonmail\gmail, reddit or anything else. Telegram,
> however, is still working fine. Internal machines on the home's local
> network (IP-camera) can also be accessed directly.
> Disabling the WG gives me full access to any webpage as usual. So
> something is amiss that affects my browser only (Firefox 91.0).

What's your MTU on the wg0 interface? Try reducing that to 1400, or if
that doesn't help, to 1280.

With respect,

  reply	other threads:[~2021-08-21 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 11:16 S Bauer
2021-08-21 20:27 ` Roman Mamedov [this message]
2021-08-23 17:38 ` Chris
     [not found]   ` <CA+MSESmGoAuQJX3rn-a3aucV8YoD+pnrVtTVDaMu9EFuS=-mqg@mail.gmail.com>
2021-08-31 14:46     ` S Bauer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210822012753.27447e9f@natsu \
    --to=rm@romanrm.net \
    --cc=sanderbauer@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    --subject='Re: enabling WG0 allows telegram but impedes browsing' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).