From: jens <jens@viisauksena.de>
To: wireguard@lists.zx2c4.com
Subject: Re: VXLAN
Date: Thu, 16 Feb 2017 19:05:32 +0100 [thread overview]
Message-ID: <b3ec4bcb-e867-7e24-0d10-74746240c3f5@viisauksena.de> (raw)
In-Reply-To: <d6qpul2kg1fyp0sdshfmv137.1486933562582@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 1875 bytes --]
i also understand it like you want to use vxlan0 to connect each other,
surprisingly we are playing with this actually also - but run in
difficulties with v6 and vxlan
doing somethings like on each endpoint (both have wg0 , and this is
working fine with v6 wg internal adresses)
|ip link add vxlan0 type vxlan id 42 local <local_wg_v6>dstport 4789
nolearning bridge fdb add to <remote_mac>dst <remote_wg_v6> dev vxlan0
so fyi: (german only)
https://forum.freifunk.net/t/wireguard-0-0-20161230-linuxkernel-3-18-gluon-v2016-2-2/14122/16
|
you may consider gretap tunnel - which already is working,
but i am also interested in workling vxlan setups
On 12.02.2017 22:07, info wrote:
> Hello,
>
> I would love to use VXLANs for my network to separate stuff, although
> I'm a bit struggling. My topology looks like this:
>
> VM A --> AMSTERDAM -> FRANKFURT -> VIENNA --> VM B
>
> '->' indicates a Wireguard tunnel
> '-->' is a physical link
>
> Actually I'm configuring a VXLAN Interface in AMSTERDAM and VIENNA,
> with the tunnel IPs as remote/local.
>
> Anyway, somehow I'm facing a strange issue here. VM A and VM B can
> ping each other already, although nothing else works. I cannot do
> curl/wget between the VMs nor iperf, etc.
>
> Do you know if my topology above should work? VM A can reach VM B
> without VXLAN just fine over the other hops, as well AMSTERDAM and
> VIENNA can reach each other fully.
>
> No firewall enabled nor anything else. Allowed-IPs is 0.0.0.0/0,::/0
> on all tunnels.
>
> My guess was that this is somewhat MTU related, tried 1200 on the
> VXLAN interfaces - no difference.
>
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
--
make the world nicer, please use PGP encryption
[-- Attachment #2: Type: text/html, Size: 4762 bytes --]
prev parent reply other threads:[~2017-02-16 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 21:07 VXLAN info
2017-02-13 10:43 ` VXLAN Jason A. Donenfeld
2017-02-16 18:05 ` jens [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=b3ec4bcb-e867-7e24-0d10-74746240c3f5@viisauksena.de \
--to=jens@viisauksena.de \
--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).