Source: network-manager Version: jessie Severity: normal When creating bridges it is not possible to specify the bridge MAC address and sometimes on boot (actually a reboot rather than fresh boot) network-manager assigns some random MAC adress to the bridge device instead of the MAC address of the first slave.
This breaks DHCP static leases as well as MAC-based ACLs (e.g. on enterprise-grade switch you can limit what MAC address combined with VLAN ID are allow to come in on a certain port on the switch, but this breaks if the MAC address is not known because it is some randomly assign MAC address that is in the ethernet frame). Regards, Daniel -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
