* WG IPV6 problem
@ 2022-03-23 20:07 Barry Cisna
0 siblings, 0 replies; only message in thread
From: Barry Cisna @ 2022-03-23 20:07 UTC (permalink / raw)
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?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-04-21 23:48 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-23 20:07 WG IPV6 problem Barry Cisna
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).