Your message dated Sat, 15 Nov 2014 16:50:08 +0100
with message-id <[email protected]>
and subject line Re: networkd: please support bridge mac cloning
has caused the Debian Bug report #768908,
regarding networkd: please support bridge mac cloning
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
768908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768908
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-5+b1
Severity: wishlist
Dear systemd Maintainers,
while trying out networkd with a bridge setup, I've been unable to
find how to set a static MAC address for the setup bridge.
Ideally I'd like to just clone the MAC of the physical device, but
setting a static address using a string would do fine as well.
The typical use case for the cloning stuff is a bridge attached to
a single ethX device, and other devices joining the bridges that
are configured through libvirt or any other of virtualization tool.
Why is the MAC even important? Because desktops tend to use DHCP
and they may have "static" IP or other assignments that are bound
to the MAC address.
Thanks,
Christian
-- Package-specific info:
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-57
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1
ii libblkid1 2.25.2-2
ii libc6 2.19-12
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-3
ii libgcrypt20 1.6.2-4
ii libkmod2 18-3
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-5+b1
ii sysv-rc 2.88dsf-57
ii udev 215-5+b1
ii util-linux 2.25.2-2
Versions of packages systemd recommends:
ii dbus 1.8.8-2
ii libpam-systemd 215-5+b1
Versions of packages systemd suggests:
ii systemd-ui 3-2
-- Configuration Files:
/etc/systemd/journald.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Stefan,
* Stefan Lippers-Hollmann <[email protected]> [141110 18:41]:
> Hi
>
> This, in my case using the device's real hardware MAC address, works
> fine with the following configuration (well, only 50-br0.netdev
> matters):
>
> $ cat /etc/systemd/network/50-br0.netdev
> [NetDev]
> Name=br0
> Kind=bridge
> MACAddress=01:23:45:67:89:AB
[..]
thank you for that example, I have tried this now and it works
nicely.
Thanks again,
Christian
--
,''`. Christian Hofstaedtler <[email protected]>
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
pgpvqQ_15nBkk.pgp
Description: PGP signature
--- End Message ---
