Bug#814324: systemd-networkd: networkd setup doesn't seem to work in non-systemd use cases

[Ritesh Raj Sarraf]

On Wed, 2016-02-10 at 17:28 +0530, Ritesh Raj Sarraf wrote:
> I hope I have been able to explain the problem. Or in other words,
> how
> do I achieve a bridge interface status like the following under
> systemd-networkd ?
> 
> 4: sysbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP group default qlen 1000
>     link/ether c6:2b:ef:ba:f2:aa brd ff:ff:ff:ff:ff:ff
>     inet 172.16.20.1/16 brd 172.16.255.255 scope global sysbr0
>        valid_lft forever preferred_lft forever
>     inet6 fe80::c42b:efff:feba:f2aa/64 scope link tentative 
>        valid_lft forever preferred_lft forever


I've filed this as a bug with systemd-networkd because of the odd
behavior of the interface being marked carrier-less, when using tools
like Virtualbox. The oddity is not seen when using a systemd native
add-on tool like nspawn.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160210/72cfdecf/attachment-0002.sig>