<div dir="ltr">Replying to my own email -<div><br></div><div>This latency problem I reported was not Wireguard's fault.</div><div>What happened was that one of the floating IP addresses</div><div>that was assigned to the VM was attached to an OpenStack</div><div>controller that had been provisioned in the wrong data center.</div><div>Amazingly the whole setup did continue to work, but the</div><div>ping times reflected pessimal routing, with the ping from </div><div>New Jersey to New Jersey going via Tokyo.</div><div><br></div><div>No individual component was anywhere near as slow as the</div><div>speed of light under the Pacific Ocean.</div><div><br></div><div>Note to self: if you can't debug the problem within the virtual</div><div>machine, start to look at the physical machines that provide</div><div>the virtual machines, and make sure you know what (and where)</div><div>they are.</div><div><br></div><div>Ed</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Nov 9, 2018 at 11:56 PM Edward Vielmetti <<a href="mailto:edward.vielmetti@gmail.com">edward.vielmetti@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I have a network with several machines in it all running Wireguard. <div><br></div><div>The latest device I've added to this assemblage is a virtual machine</div><div>provisioned under OpenStack. It has 4 ThunderX cores (2 Ghz armv8)</div><div>subdivided off of 96-core machine. What I notice is slow network</div><div>performance through the Wireguard interface - 200 ms round trip VPN ping</div><div>times to a machine in the same data center, compared to 1 ms when</div><div>I don't go through the VPN, and only 45 ms when I use a different</div><div>machine in the same data center to an even slower Raspberry Pi 2 in my attic.</div><div><br></div><div>I don't claim to be an OpenStack expert, and I know there is some</div><div>considerable complexity hiding in its network stack that might not</div><div>be visible within the VM that I'm running. </div><div><br></div><div>I guess the question is, what's the best way to start to make sense of</div><div>network performance within Wireguard (and if anyone knows the answer,</div><div>also within OpenStack?!). </div><div><br></div><div>thanks</div><div><br></div><div>Ed<br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-3700059037923505429m_8796955196307804975gmail_signature" data-smartmail="gmail_signature"><span>Edward Vielmetti <span id="m_-3700059037923505429m_8796955196307804975gc-number-1038" class="m_-3700059037923505429m_8796955196307804975gc-cs-link" title="Call with Google Voice"><span id="m_-3700059037923505429gc-number-1049" class="m_-3700059037923505429gc-cs-link" title="Call with Google Voice">+1 734 330 2465</span></span></span><div><a href="mailto:edward.vielmetti@gmail.com" target="_blank">edward.vielmetti@gmail.com</a></div><div><br></div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Edward Vielmetti +1 734 330 2465<div><a href="mailto:edward.vielmetti@gmail.com" target="_blank">edward.vielmetti@gmail.com</a></div><div><br></div></div>