Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Barry Cisna <brcisna@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: one subnet not pingable
Date: Fri, 25 Mar 2022 18:11:47 -0500	[thread overview]
Message-ID: <CAL0AYvdc7Pm5b=MGXnQo3-yNmbBRQ8kF_oW75W8J0MGdh1J4VA@mail.gmail.com> (raw)

Hello All,

Peer2   (client) - Debian Bullseye
wwan0  = 100.64.2.161/30   # cellular modem CGNAT
bridge0 = ethernet & wifi interfaces   192.168.67.1
wg0client2  = 192.168.67.2

Peer 1 (server)
Google Cloud Instance Debian Bullseye static IPV4 address
ens4 = 10.128.0.2
wg0 +  192.168.69.1

PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A
POSTROUTING -o ens4 -j MASQUERADE
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D
POSTROUTING -o ens4 -j MASQUERADE

Peer2, Clients connected to LAN/bridge0 both wired and wireless can
webbrowse but is delayed. DNS not exactly right,,

Peer2 can ping Peer1 fine responds both interface addresses

If Peer1 pings Peer2 at 192.168.67.1 returns "no message,,,something"
and returns 192.168.69.1
if Peer1 pings Peer2 at wwan0 it gets a response
So..it seems the wwan0 can not hop to the bridge0 interface for some reason,
I have tried for hours to make static routes what i think may work,and
always get "route already exists'. tried a few iptables guesses on
client,,,no go..

Thanks

                 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='CAL0AYvdc7Pm5b=MGXnQo3-yNmbBRQ8kF_oW75W8J0MGdh1J4VA@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).