Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Barry Cisna <brcisna@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: WG IPV6 problem
Date: Wed, 23 Mar 2022 15:07:50 -0500	[thread overview]
Message-ID: <CAL0AYvfw6EoUJy21pOcH9NOA1zh4zttrpZhiLsQar32VuNoEiA@mail.gmail.com> (raw)

Hello All,

Have Wireguard setup as PEER1 on an Debian Bullseye machine residing
on Google Cloud instance. IPV4 only,,
PEER2 is the home Debian Bullseye server  behind cgnat cellular provider
After a learning curve these connect fine and PEER2 does get the PEER
1 public ipv4 address,,,with a US Cellular hotspot connected to PEER2.
BUT on the same PEER2 if i use a T-Mobile hotspot ,,,again
CGNAT,,internet does still work fine and can ping PEER1,,,BUT does not
get PEER1 public ip address.
Only thing i see different is the T-Mobile hot spot is set to IPV6
only in the GUi settings of  the hotspot. I did not in the Network
manager gui setting of PEER2 the IPV6 is set to 'IGNORE' I havent yet
tried changing that to 'automatic'.
What would i change in the PEER2 Network Manager config to make this
work with IPV6?

Thank You

                 reply	other threads:[~2022-04-21 23:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAL0AYvfw6EoUJy21pOcH9NOA1zh4zttrpZhiLsQar32VuNoEiA@mail.gmail.com \
    --to=brcisna@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /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).