Hi,
Why don't you make a test with OpenVSwitch?
You can setup an SDN with it.
TIA,
Ruzsi
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
Maybe a VPN container that peers with the other VPN containers and runs a
dynamic routing protocol? Then just setup a route on the lxd host to the
VPN guest. Make it config driven so you just push a new peer list to
update. Or not and just push the updated container?
On Sep 18, 2016 4:21 AM, "To
I got a response back from Tobias Volk (the PeerVPN author)
He changed the bullet on the main web page to help clarify that there is no
automatic tunnel through firewalls..
text was...
*Automatically builds tunnels through firewalls and NATs without any
further setup (for example, port forwarding
Serge,
>
>
>
> *> Automatically builds tunnels through firewalls and NATs without any
> further> setup (for example, port forwarding).I would not appreciate
> something which "automatically" (whatever itmeans) traverse my firewalls,
> to be honest. We should treat our dataseriously, Brian.*
Fir
On 2016-09-19 05:12, Tilak Waelde wrote:
Hope this helps. Happy to share my LXD configurations with anyone...
Please do! I'd really love to see a description of a production lxd /
lxc setup with proper networking and multiple hosts!
I haven't played around with it yet, but is it possible to i
On Mon, Sep 19, 2016 at 8:48 PM, brian mullan wrote:
> Automatically builds tunnels through firewalls and NATs without any further
> setup (for example, port forwarding).
I would not appreciate something which "automatically" (whatever it
means) traverse my firewalls, to be honest. We should tre
Tomasz
After experimenting with TINC, OpenVPN & others I found and have used
PeerVPN to do this:
https://peervpn.net/
PeerVPN is a full-mesh VPN and is auto-learning..
- Ethernet tunneling support using TAP devices.
- IPv6 support.
- Full mesh network topology.
- Automatically build
Hope this helps. Happy to share my LXD configurations with anyone...
-Ron
Please do! I'd really love to see a description of a production lxd /
lxc setup with proper networking and multiple hosts!
I haven't played around with it yet, but is it possible to include some
sort of VRF-lite[0] i
On Sun, Sep 18, 2016 at 7:11 PM, Tomasz Chmielewski wrote:
> On 2016-09-18 21:05, Sergiusz Pawlowicz wrote:
>>
>> On Sun, Sep 18, 2016 at 4:16 PM, Tomasz Chmielewski
>> wrote:
>>
>>> While I can imagine setting up many OpenVPN tunnels between all LXD
>>> servers
>>
>>
>> I cannot imagine that :-)
So, just for clarity, you are saying each LXD server will have no separate
network connection for the containers. Thus, all containers are private to the
LXD server, and any outbound traffic must traverse the container server
interface. Is this correct? If so, sorry, I must have missed this r
On 2016-09-18 22:14, Ron Kelley wrote:
(Long reply follows…)
Personally, I think you need to look at the big picture for such
deployments. From what I read below, you are asking, “how do I extend
my layer-2 subnets between data centers such that container1 in Europe
can talk with container6 in
(Long reply follows…)
Personally, I think you need to look at the big picture for such deployments.
From what I read below, you are asking, “how do I extend my layer-2 subnets
between data centers such that container1 in Europe can talk with container6 in
Asia, etc”. If this is true, I think
On 2016-09-18 21:05, Sergiusz Pawlowicz wrote:
On Sun, Sep 18, 2016 at 4:16 PM, Tomasz Chmielewski
wrote:
While I can imagine setting up many OpenVPN tunnels between all LXD
servers
I cannot imagine that :-) :-)
Use tinc, mate. Your life begins :-)
https://www.tinc-vpn.org/
I did some r
On Sun, Sep 18, 2016 at 4:16 PM, Tomasz Chmielewski wrote:
> While I can imagine setting up many OpenVPN tunnels between all LXD servers
I cannot imagine that :-) :-)
Use tinc, mate. Your life begins :-)
https://www.tinc-vpn.org/
cheers,
Serge
___
l
Tomasz Chmielewski writes:
> While I can imagine setting up many OpenVPN tunnels between all LXD
> servers (LXD1-LXD2, LXD1-LXD3, LXD2-LXD3) and constantly adjusting the
> routes as containers are stopped/started/migrated, it's a bit of a
> management nightmare. And even more so if the number of
It's easy to create a "LAN" for LXD containers on a single LXD server -
just attach them to the same bridge, use the same subnet (i.e.
10.10.10.0/24) - done. Containers can communicate with each other using
their private IP address.
However, with more then one LXD server *not* in the same LAN
16 matches
Mail list logo
