[systemd-devel] The Bridge on the River PID EINS

Tom Gundersen teg at jklm.no
Sun Mar 16 05:20:04 PDT 2014


On Sun, Mar 9, 2014 at 5:58 AM, poma <pomidorabelisima at gmail.com> wrote:
>
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>
> STATIC OK!
>
> $ ll /etc/systemd/network/
> ... enp3s0.network
>
> $ cat /etc/systemd/network/enp3s0.network
> [Match]
> Name=enp3s0
>
> [Network]
> Address=192.168.2.2/24
> Gateway=192.168.2.1
> DNS=192.168.2.1
>
> # journalctl -b -u systemd-networkd
> -- Logs begin at ...
> ... systemd-networkd[630]: enp3s0: carrier on
> ... systemd-networkd[630]: enp3s0: link configured
>
> $ ifconfig enp3s0
> enp3s0: flags=...
>         inet 192.168.2.2  netmask 255.255.255.0  broadcast 192.168.2.255
>         inet6 ...
>         ether ...
>         ...
>
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>
> BRIDGED !?
>
> $ ll /etc/systemd/network/
> ... bridge0.netdev
> ... enp3s0.network
>
> $ cat /etc/systemd/network/enp3s0.network
> [Match]
> Name=enp3s0
>
> [Network]
> Address=192.168.2.2/24
> Gateway=192.168.2.1
> DNS=192.168.2.1
> Bridge=bridge0
>
> $ cat /etc/systemd/network/bridge0.netdev
> [NetDev]
> Name=bridge0
> Kind=bridge
>
> # journalctl -b -u systemd-networkd.service
> -- Logs begin at ...
>
> $ ifconfig enp3s0
> enp3s0: flags=...
>         ether ...
>         ...
>
> $ brctl show
> bridge name     bridge id               STP enabled     interfaces
> bridge0         8000.000000000000       no

Thanks for the report, this should be fixed in git now.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>
> /var/log/messages

[...]

> Mar  9 05:05:15 localhost systemd-udevd[396]: Could not apply link
> config to bridge0
> Mar  9 05:11:14 localhost systemd-udevd: Could not apply link config to
> bridge0
> Mar  9 05:14:26 localhost systemd-udevd: Could not apply link config to
> bridge0
>
> What "link config"!? :)

This is a separate and harmless warning. It is refering to
systemd.link(8). We should find a way to avoid these warnings
(assuming it is just the default .link and not your own custom one?).

Cheers,

Tom


More information about the systemd-devel mailing list