[arch-general] Network-Issues after last updates

Ruben Kelevra cyrond at gmail.com
Wed Mar 5 07:17:59 EST 2014

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

Best Regards,


2014-03-05 13:14 GMT+01:00 arnaud gaboury <arnaud.gaboury at gmail.com>:
> On Wed, Mar 5, 2014 at 12:36 PM, Thomas Bächler <thomas at archlinux.org> 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.

More information about the arch-general mailing list