[Touch-packages] [Bug 1791245] Re: bonding 802.3ad with systemd-networkd: duplicate MAC address on 2 different hosts

2019-12-13 Thread Dan Streetman
** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1791245

Title:
  bonding 802.3ad with systemd-networkd: duplicate MAC address on 2
  different hosts

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The problem seems to incriminate systemd-networkd (v229-4ubuntu21.1), not the 
network/bonding configuration.
  When a full bonding configuration is made with systemd in 
/etc/systemd/network, on 2 two differents physical hosts, same hardware and in 
same VLAN:

  - bond0.netdev --
  [NetDev]
  Name=bond0
  Kind=bond

  
  [Bond]
  Mode=802.3ad
  TransmitHashPolicy=layer3+4
  MIIMonitorSec=100ms
  LACPTransmitRate=fast

  - vlan3147.netdev --
  [NetDev]
  Name=vlan3147
  Kind=vlan

  [VLAN]
  Id=3147

  - bond0.network --
  [Match]
  Name=bond0

  [Network]
  VLAN=vlan3147
  BindCarrier=enp1s0f1 enp1s0f0
  LinkLocalAddressing=no

  - enp1s0f0.network --
  [Match]
  Name=enp1s0f0

  [Network]
  Bond=bond0

  - enp1s0f1.network --
  [Match]
  Name=enp1s0f1

  [Network]
  Bond=bond0

  - vlan3147.network --
  [Match]
  Name=vlan3147

  [Address]
  Address=**masked ip***/25

  [Route]
  Destination=10.0.0.0/8
  Gateway=**masked ip***

  [Route]
  Destination=**masked ip***/16
  Gateway=**masked ip***

  
  And in /etc/modprobe.d/bonding.conf
  options bonding max_bonds=0

  .  the two different physicals hosts have the same MAC address on
  bonding:

  on host A:

  32: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 16:d6:b0:24:16:3b brd ff:ff:ff:ff:ff:ff

  on host B:

  32: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 16:d6:b0:24:16:3b brd ff:ff:ff:ff:ff:ff

  
  So strange... how the MAC is generated ? There is no relevant rules in 
/etc/udev/rules.d/70-persistent-net.rules to explain it, and issue occurs only 
with systemd-network, *NOT* with legacy configuration /etc/network/interfaces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1791245/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1791245] Re: bonding 802.3ad with systemd-networkd: duplicate MAC address on 2 different hosts

2018-09-07 Thread lincvz
Problem solved: root cause wa the same id on the 2 machines in /etc
/machine-id

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1791245

Title:
  bonding 802.3ad with systemd-networkd: duplicate MAC address on 2
  different hosts

Status in systemd package in Ubuntu:
  New

Bug description:
  The problem seems to incriminate systemd-networkd (v229-4ubuntu21.1), not the 
network/bonding configuration.
  When a full bonding configuration is made with systemd in 
/etc/systemd/network, on 2 two differents physical hosts, same hardware and in 
same VLAN:

  - bond0.netdev --
  [NetDev]
  Name=bond0
  Kind=bond

  
  [Bond]
  Mode=802.3ad
  TransmitHashPolicy=layer3+4
  MIIMonitorSec=100ms
  LACPTransmitRate=fast

  - vlan3147.netdev --
  [NetDev]
  Name=vlan3147
  Kind=vlan

  [VLAN]
  Id=3147

  - bond0.network --
  [Match]
  Name=bond0

  [Network]
  VLAN=vlan3147
  BindCarrier=enp1s0f1 enp1s0f0
  LinkLocalAddressing=no

  - enp1s0f0.network --
  [Match]
  Name=enp1s0f0

  [Network]
  Bond=bond0

  - enp1s0f1.network --
  [Match]
  Name=enp1s0f1

  [Network]
  Bond=bond0

  - vlan3147.network --
  [Match]
  Name=vlan3147

  [Address]
  Address=**masked ip***/25

  [Route]
  Destination=10.0.0.0/8
  Gateway=**masked ip***

  [Route]
  Destination=**masked ip***/16
  Gateway=**masked ip***

  
  And in /etc/modprobe.d/bonding.conf
  options bonding max_bonds=0

  .  the two different physicals hosts have the same MAC address on
  bonding:

  on host A:

  32: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 16:d6:b0:24:16:3b brd ff:ff:ff:ff:ff:ff

  on host B:

  32: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 16:d6:b0:24:16:3b brd ff:ff:ff:ff:ff:ff

  
  So strange... how the MAC is generated ? There is no relevant rules in 
/etc/udev/rules.d/70-persistent-net.rules to explain it, and issue occurs only 
with systemd-network, *NOT* with legacy configuration /etc/network/interfaces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1791245/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1791245] Re: bonding 802.3ad with systemd-networkd: duplicate MAC address on 2 different hosts

2018-09-07 Thread lincvz
A workaround is to set manually a different MAC address in bond0.netdev:


[NetDev]
Name=bond0
Kind=bond
MACAddress=16:d6:b0:24:16:3c

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1791245

Title:
  bonding 802.3ad with systemd-networkd: duplicate MAC address on 2
  different hosts

Status in systemd package in Ubuntu:
  New

Bug description:
  The problem seems to incriminate systemd-networkd (v229-4ubuntu21.1), not the 
network/bonding configuration.
  When a full bonding configuration is made with systemd in 
/etc/systemd/network, on 2 two differents physical hosts, same hardware and in 
same VLAN:

  - bond0.netdev --
  [NetDev]
  Name=bond0
  Kind=bond

  
  [Bond]
  Mode=802.3ad
  TransmitHashPolicy=layer3+4
  MIIMonitorSec=100ms
  LACPTransmitRate=fast

  - vlan3147.netdev --
  [NetDev]
  Name=vlan3147
  Kind=vlan

  [VLAN]
  Id=3147

  - bond0.network --
  [Match]
  Name=bond0

  [Network]
  VLAN=vlan3147
  BindCarrier=enp1s0f1 enp1s0f0
  LinkLocalAddressing=no

  - enp1s0f0.network --
  [Match]
  Name=enp1s0f0

  [Network]
  Bond=bond0

  - enp1s0f1.network --
  [Match]
  Name=enp1s0f1

  [Network]
  Bond=bond0

  - vlan3147.network --
  [Match]
  Name=vlan3147

  [Address]
  Address=**masked ip***/25

  [Route]
  Destination=10.0.0.0/8
  Gateway=**masked ip***

  [Route]
  Destination=**masked ip***/16
  Gateway=**masked ip***

  
  And in /etc/modprobe.d/bonding.conf
  options bonding max_bonds=0

  .  the two different physicals hosts have the same MAC address on
  bonding:

  on host A:

  32: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 16:d6:b0:24:16:3b brd ff:ff:ff:ff:ff:ff

  on host B:

  32: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 16:d6:b0:24:16:3b brd ff:ff:ff:ff:ff:ff

  
  So strange... how the MAC is generated ? There is no relevant rules in 
/etc/udev/rules.d/70-persistent-net.rules to explain it, and issue occurs only 
with systemd-network, *NOT* with legacy configuration /etc/network/interfaces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1791245/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp