Well I gonna try to move the three Server to networkd, but with this complex network-setup this is a hugh pain. :/ Best Regards, Ruben 2014-03-05 13:14 GMT+01:00 arnaud gaboury :

On Wed, Mar 5, 2014 at 12:36 PM, Thomas Bächler wrote:

...

Am 05.03.2014 12:26, schrieb Ruben Kelevra:

...

I still using netcfg to statically configure my cards, the only hw-card was eth0 and now named ens3, which was the first problem on that upgrade ... changing eth0 to ens3 in configuration still wont fix the problem...

I suspect your problem comes more from the netctl/systemd-networkd side. I have been trying since many days now to setup a simple bridge for a visualised machine with netctl/systemd-networkd, and my container still cna't reach the network. I have tried all kinds of configurations, but all left me with a broken network on container. I suspect that in the near future, systemd will take care of the overall network setup (like more and more services on our machines). So the correct question is about the necessity to keep netctl along with networkd. I feel like at some point some conflicting configurations will arise.

The Problem is that I got ~25 Interfaces on any Server ... Bridges, Mesh, Tunnel Interfaces ... Best Regards Ruben 2014-03-05 13:22 GMT+01:00 arnaud gaboury :

On Wed, Mar 5, 2014 at 1:17 PM, Ruben Kelevra wrote:

...

Well I gonna try to move the three Server to networkd, but with this complex network-setup this is a hugh pain. :/

I confirm. There is a clear lack of solid documentation and this service is quite new. I have set up many bridges in the past very easily, and it is the first time I found myself like a total n00b trying to set up a bridge ! Do not hesitate to post on systemd-devel mailing list. Only a few people here will answer (Lenart being the most active), but if you are lucky, you will find solutions.