<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 01/12/2016 08:43 AM, Peter Steele wrote:<br>
<blockquote cite="mid:56952D46.2060900@gmail.com" type="cite"><br>
<tt>On 01/12/2016 06:35 AM, brian mullan wrote:</tt><tt><br>
</tt><br>
<blockquote
cite="mid:CAFX-c4s7rXHuCvW4XuMiE1wNoztHkStGDLJMeDexGkTHefu6pw@mail.gmail.com"
type="cite"><tt>Peter</tt><br>
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div><tt><br>
</tt></div>
<tt>On AWS unless you are using VPC I don't think<br>
you can use secondary addresses because AWS
won't<br>
route any of that traffic. Also with your<br>
addresses routing would be affected by the<br>
split-horizon problem with the same network on 2<br>
sides.</tt><tt><br>
</tt><tt><br>
</tt></div>
<tt>...</tt><br>
</div>
</div>
</div>
<tt><br>
I install PeerVPN (</tt><tt><a moz-do-not-send="true"
href="http://www.peervpn.net">www.peervpn.net</a></tt><tt>)<br>
on my AWS servers to support inter-server LXC<br>
communications. Its dead simple to setup, its<br>
auto-learning & full mesh vpn and you can then<br>
interconnect not only LXC on multiple AWS servers but on<br>
different Clouds like AWS & Digital Ocean and/or
your<br>
own servers at home/office.</tt><tt><br>
</tt><tt><br>
</tt></div>
<tt>It also doesn't require firewall changes beyond what you<br>
already use.</tt><tt><br>
</tt><br>
</div>
<tt>Flockport did a </tt><tt><a moz-do-not-send="true"
href="https://www.flockport.com/build-layer2-and-layer-3-overlay-networks-with-peervpn/">nice<br>
writeup on how to install/use PeerVPN</a></tt><tt> also. <br>
Maybe that will help.</tt><br>
</div>
<br>
</blockquote>
<tt> </tt><tt>Brian, thanks for this pointer. It looks like this
is what<br>
we'll need to solve our networking issues. However, I followed<br>
through </tt><tt>F</tt><tt>lockport's L2 example and configured<br>
peervpn on my two EC2 hosts but I still cannot ping containers<br>
across hosts. If I could indulge on your expertise I'd
appreciate<br>
some pointers.</tt><tt><br>
...</tt><tt><br>
</tt><tt>The output from peervpn on host 2 also shows that one
peer<br>
has connected, so it appears that my configuration is correct.
Is<br>
there something else that's needed on the containers? The<br>
container IPs are all statically assigned and I don't need DHCP/</tt><tt>dnsmasq<br>
support. </tt><tt><br>
<br>
</tt><tt>Any advice would be appreciated.</tt><br>
</blockquote>
<br>
I believe I solved the issue. I executed the command<br>
<br>
ip link set dev peervpn0 master br0<br>
<br>
on each host and I can now ping across my containers. <br>
<br>
Thanks very much for pointing me to this tool. It never came up in
any of the searches I did about networking between containers in
EC2.<br>
<br>
Peter<br>
<br>
</body>
</html>