On 01/12/2016 08:43 AM, Peter Steele wrote:
On 01/12/2016 06:35 AM, brian mullan wrote:
Peter
On AWS unless you are using VPC I don't think
you can use secondary addresses because AWS won't
route any of that traffic. Also with your
addresses routing would be affected by the
split-horizon
All I did was install/configure PeerVPN on say server1 and server2 and make
sure they
connected.
While logged into each of your servers you should then be able to ping
10.x.x.x IP address of the other PeerVPN member server(s) ... assuming you
are using PeerVPN as an L2 VPN and not a L3 VPN.
The
Peter
On AWS unless you are using VPC I don't think you can use secondary
addresses because AWS won't route any of that traffic. Also with your
addresses routing would be affected by the split-horizon problem with the
same network on 2 sides.
You probably know this ... but on AWS each instance
On 01/12/2016 01:34 PM, brian mullan wrote:
All I did was install/configure PeerVPN on say server1 and server2 and
make sure they
connected.
While logged into each of your servers you should then be able to ping
10.x.x.x IP address of the other PeerVPN member server(s) ... assuming
you are
re: I *can* ping a container in host 2 but not host 2 itself
welcome to networking... its a layer 2 network and each host itself is the
tunnel end point.
I had kept something that explained some of it and if I can find it send it
to you tomorrow.
Your br0 interfaces on the 2 servers you assign
On 01/12/2016 04:24 PM, brian mullan wrote:
re: I *can* ping a container in host 2 but not host 2 itself
welcome to networking... its a layer 2 network and each host itself is
the tunnel end point.
I had kept something that explained some of it and if I can find it send
it to you tomorrow.
On 01/12/2016 06:35 AM, brian mullan wrote:
Peter
On AWS unless you are using VPC I don't think you can use secondary
addresses because AWS won't route any of that traffic. Also with your
addresses routing would be affected by the split-horizon problem with
the same network on 2 sides.
