Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Frank Carmickle <frank@carmickle.com>
To: Franck MESSAOUDI <frank.messaoudi@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Getting some troubles when setting up the VPN
Date: Tue, 17 Dec 2019 10:32:23 -0500	[thread overview]
Message-ID: <25228A87-3310-44DB-A00A-2536C7C0CEF5@carmickle.com> (raw)
In-Reply-To: <CAHC_4XPNXxVHD02qDXFpgOdYN0ojpmUWyq4t==DuTSwe6s7fUg@mail.gmail.com>

Hello Franck,

> On Dec 17, 2019, at 10:14 AM, Franck MESSAOUDI <frank.messaoudi@gmail.com> wrote:
> 
> Dear members, 
> 
> I am using the wireguard to create VPN in order to access my VMs in openstack.
> The thing is that I am getting some troubles when I chage the network or the access point.
> Indeed, I have two wifi networks and one via ethernet. the VPN is working only for one wifi access network, for the two others it does not work. I do not understand why this behaviour? is it due the routing tables?

Almost certainly it is do to missing routes, but we don't have enough information to really know. Remember you need a route to the network of openstack systems, as well as a route from the openstack systems back to the networks you are trying to access the systems from.

HTH
--FC

> 
> You will be very kind if some of you could reply with an answer.
> 
> In advance, thank you.
> 
> Best regards, 
> 
> Franck
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

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

      reply	other threads:[~2019-12-19  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 15:14 Franck MESSAOUDI
2019-12-17 15:32 ` Frank Carmickle [this message]

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=25228A87-3310-44DB-A00A-2536C7C0CEF5@carmickle.com \
    --to=frank@carmickle.com \
    --cc=frank.messaoudi@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).