Development discussion of WireGuard
 help / color / mirror / Atom feed
From: <cristian.c@istream.today>
To: <wireguard@lists.zx2c4.com>
Subject: After I start the Wireguard service, VMs from same network are not reachable via local IP
Date: Sun, 4 Aug 2019 15:16:07 +0300	[thread overview]
Message-ID: <06fc01d54abe$653f3320$2fbd9960$@istream.today> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3242 bytes --]

Hi Guys,

 

    I have a very strange issue,  and I do not understand why is working
like this..

 

   I have 3 ( A,B ) VMs, 2 in the same network and 1( C ) outside of this
network.

 

 

   A:  Just a VM in the same network with B, not able to ping VM B when
Wireguard is UP on B..

 

3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000

    link/ether 00:50:56:80:2d:e3 brd ff:ff:ff:ff:ff:ff

    inet 10.100.21.3/16 brd 10.100.21.255 scope global noprefixroute ens192

       valid_lft forever preferred_lft forever

    inet 10.100.20.3/16 brd 10.100.20.255 scope global noprefixroute ens192

       valid_lft forever preferred_lft forever

    inet6 fe80::8700:5c89:fbc7:3473/64 scope link noprefixroute

       valid_lft forever preferred_lft forever

 

 

   B : Where Wireguard is installed and connected to C, reachable from both
side over wireguard interface but not other interface, like : 10.100.21.4/16

 

3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000

    link/ether 00:50:56:80:50:e5 brd ff:ff:ff:ff:ff:ff

    inet 10.100.21.4/16 brd 10.100.21.255 scope global noprefixroute ens192

       valid_lft forever preferred_lft forever

    inet 10.100.20.4/16 brd 10.100.20.255 scope global noprefixroute ens192

       valid_lft forever preferred_lft forever

    inet 172.11.0.251/24 brd 172.11.0.255 scope global noprefixroute ens192

       valid_lft forever preferred_lft forever

    inet6 fe80::1003:1bdb:46ee:e16f/64 scope link noprefixroute

       valid_lft forever preferred_lft forever

7: wg1: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN
group default qlen 1000

    link/none

    inet 10.100.20.1/16 scope global wg1

       valid_lft forever preferred_lft forever

    inet6 fe80::d4cf:f1cb:3e3a:dc19/64 scope link flags 800

       valid_lft forever preferred_lft forever

[root@usa-dns ~]#

 

 

C: The VM outside of network where A and B are located, this VM communicate
with B: over wireguard.

 

3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000

    link/ether 00:50:56:80:00:71 brd ff:ff:ff:ff:ff:ff

    inet 172.11.0.3/24 brd 172.11.0.255 scope global noprefixroute ens192

       valid_lft forever preferred_lft forever

    inet 10.100.21.251/16 brd 10.100.21.255 scope global noprefixroute
ens192

       valid_lft forever preferred_lft forever

    inet6 fe80::250:56ff:fe80:71/64 scope link noprefixroute

       valid_lft forever preferred_lft forever

7: wg1: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN
group default qlen 1000

    link/none

    inet 10.100.20.5/16 scope global wg1

       valid_lft forever preferred_lft forever

    inet6 fe80::cdc3:f783:5066:eb5e/64 scope link flags 800

       valid_lft forever preferred_lft forever

[root@canada-dns ~]#

 

 

 

  Question A: Why the VM A and B are not reachable anymore  via local IP
when Wireguard is turned on.?

 

  Question B: Is there a way to make B and C reachable over any other
interface when the wireguard is enabled? I do not want only via Wireguard
interface 10.100.0.0/16

 

 

Thank you.

Cristian

 

 


[-- Attachment #1.2: Type: text/html, Size: 7940 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

                 reply	other threads:[~2019-08-05 18:57 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='06fc01d54abe$653f3320$2fbd9960$@istream.today' \
    --to=cristian.c@istream.today \
    --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).