WireGuard Archive on lore.kernel.org
 help / color / 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
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 --]

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi Guys,<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; I have a very strange issue, &nbsp;and I do not understand why is working like this&#8230;.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>&nbsp;&nbsp; I have 3 ( A,B ) VMs, 2 in the same network and 1( C ) outside of this network.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>&nbsp;&nbsp; A:&nbsp; Just a VM in the same network with B, not able to ping VM B when Wireguard is UP on B..<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>3: ens192: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc pfifo_fast state UP group default qlen 1000<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; link/ether 00:50:56:80:2d:e3 brd ff:ff:ff:ff:ff:ff<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet 10.100.21.3/16 brd 10.100.21.255 scope global noprefixroute ens192<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet 10.100.20.3/16 brd 10.100.20.255 scope global noprefixroute ens192<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet6 fe80::8700:5c89:fbc7:3473/64 scope link noprefixroute<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>&nbsp;&nbsp; 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<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>3: ens192: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc pfifo_fast state UP group default qlen 1000<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; link/ether 00:50:56:80:50:e5 brd ff:ff:ff:ff:ff:ff<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet 10.100.21.4/16 brd 10.100.21.255 scope global noprefixroute ens192<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet 10.100.20.4/16 brd 10.100.20.255 scope global noprefixroute ens192<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet 172.11.0.251/24 brd 172.11.0.255 scope global noprefixroute ens192<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet6 fe80::1003:1bdb:46ee:e16f/64 scope link noprefixroute<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>7: wg1: &lt;POINTOPOINT,NOARP,UP,LOWER_UP&gt; mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; link/none<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet 10.100.20.1/16 scope global wg1<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet6 fe80::d4cf:f1cb:3e3a:dc19/64 scope link flags 800<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>[root@usa-dns ~]#<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>C: The VM outside of network where A and B are located, this VM communicate with B: over wireguard.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>3: ens192: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc mq state UP group default qlen 1000<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; link/ether 00:50:56:80:00:71 brd ff:ff:ff:ff:ff:ff<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet 172.11.0.3/24 brd 172.11.0.255 scope global noprefixroute ens192<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet 10.100.21.251/16 brd 10.100.21.255 scope global noprefixroute ens192<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet6 fe80::250:56ff:fe80:71/64 scope link noprefixroute<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>7: wg1: &lt;POINTOPOINT,NOARP,UP,LOWER_UP&gt; mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; link/none<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet 10.100.20.5/16 scope global wg1<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp; inet6 fe80::cdc3:f783:5066:eb5e/64 scope link flags 800<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; valid_lft forever preferred_lft forever<o:p></o:p></p><p class=MsoNormal>[root@canada-dns ~]#<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>&nbsp; Question A: Why the VM A and B are not reachable anymore &nbsp;via local IP when Wireguard is turned on.?<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>&nbsp; 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<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Thank you.<o:p></o:p></p><p class=MsoNormal>Cristian<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

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

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

                 reply index

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

Reply instructions:

You may reply publically 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

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/ public-inbox