Development discussion of WireGuard
 help / color / mirror / Atom feed
* VXLAN
@ 2017-02-12 21:07 info
  2017-02-13 10:43 ` VXLAN Jason A. Donenfeld
  2017-02-16 18:05 ` VXLAN jens
  0 siblings, 2 replies; 3+ messages in thread
From: info @ 2017-02-12 21:07 UTC (permalink / raw)
  To: wireguard

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-02-16 18:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-12 21:07 VXLAN info
2017-02-13 10:43 ` VXLAN Jason A. Donenfeld
2017-02-16 18:05 ` VXLAN jens

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).