From: info <info@florianb.space>
To: wireguard@lists.zx2c4.com
Subject: VXLAN
Date: Sun, 12 Feb 2017 21:07:36 +0000 [thread overview]
Message-ID: <d6qpul2kg1fyp0sdshfmv137.1486933562582@email.android.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1851 bytes --]
next reply other threads:[~2017-02-12 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 21:07 info [this message]
2017-02-13 10:43 ` VXLAN Jason A. Donenfeld
2017-02-16 18:05 ` VXLAN jens
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=d6qpul2kg1fyp0sdshfmv137.1486933562582@email.android.com \
--to=info@florianb.space \
--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).