Bug 18885

Summary:	Cannot connect to Internet with SystemD
Product:	Mageia	Reporter:	Muhammad Tailounie <mageia>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	bittwister2
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Muhammad Tailounie 2016-07-07 07:59:14 CEST

Configuring a bridge connection using based on systemd does create the bridge and connect apparently, but I cannot even ping the router. Firewall is disabled to check. Apparently it's related to routing: No idea really..

6sta1, systemd 230


How reproducible:
Stop network service, disable it, then create the necessary configuration files under /etc/systemd/network. Now enable and start systemd-networkd and make sure systemd-resolved is enabled and started too.


Steps to Reproduce:
1. stop systemd-networkd
2. start systemd-networkd

or reboot

Comment 1 Bit Twister 2016-07-09 03:46:39 CEST

(In reply to Muhammad Tailounie from comment #0)


> Stop network service, disable it, then create the necessary configuration
> files under /etc/systemd/network.

You might want to consider placing your files in /usr/lib/systemd/network/.
That way you can link /etc/systemd/network/same_name to /dev/null which allows you to disable the same named file in /usr/lib/systemd/network/

For example I have
     $ locate /usr/lib/systemd/network/*_my_*
     /usr/lib/systemd/network/10_my__enp3s0.network
     /usr/lib/systemd/network/11_my__enp4s0.network
     /usr/lib/systemd/network/12_my__wlp2s0.network
and for disabling second nic and wireless I have

     $ locate /etc/systemd/network/*_my_*
     /etc/systemd/network/11_my__enp4s0.network
     /etc/systemd/network/12_my__wlp2s0.network


> Now enable and start systemd-networkd and
> make sure systemd-resolved is enabled and started too.

I think the suggestion is to link resolv.conf to systemd/resolve/resolv.conf
Example:
$ ll /etc/resolv.conf
lrwxrwxrwx 1 root root 32 Sep 17  2015 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

Stock/normal configuration file from my setup:

$ cat /usr/lib/systemd/network/10_my__enp3s0.network
#*********************************************************************
# /usr/lib/systemd/network/10_my__enp3s0.network
# Created by /local/bin/install_net_nic Mon 01 Feb 23:00 2016
# 
# man systemd.network
# http://www.freedesktop.org/software/systemd/man/systemd.network.html
# 
# If you change this file, make the same change in
# /local/bin/install_net_nic and run
#   systemctl restart systemd-networkd
# 
#*********************************************************************

[Match]
Name=enp3s0

[Network]
Description=LAN_NIC
DNS=127.0.0.1
DNS=8.8.8.8
Domains=home.test


[Address]
Address=192.168.11.132/24

[Route]
Gateway=192.168.11.1
# Metric=5
#****** end /usr/lib/systemd/network/10_my__enp3s0.network ****

CC: (none) => bittwister2

Comment 2 Muhammad Tailounie 2016-07-11 08:08:43 CEST

Thank you Bit Twister,

Actually I had everything well configured. I found out, though, that the firewall rules were messed up for the bridge interface. Now everything is ok. :)

Comment 3 Muhammad Tailounie 2016-07-11 08:09:09 CEST

Firewall rules messed up!

Status: NEW => RESOLVED
Resolution: (none) => FIXED