Comment 16 for bug 1782221

Revision history for this message
Brian Candler (b-candler) wrote :

Is there any indication of how the "random" MAC address is generated, or where it's cached?

I have a prepared VM image, which I've cleaned as carefully as possible, using "virt-sysprep", and inside the image running "cloud-init clean --logs --seed"

However when I start multiple instances of it, the bridges get the same MAC address:

$ sudo arping 192.168.122.10
ARPING 192.168.122.10
42 bytes from 5a:ed:f7:c4:10:14 (192.168.122.10): index=0 time=1.495 msec
42 bytes from 5a:ed:f7:c4:10:14 (192.168.122.10): index=1 time=903.675 usec
^C
--- 192.168.122.10 statistics ---
2 packets transmitted, 2 packets received, 0% unanswered (0 extra)
rtt min/avg/max/std-dev = 0.904/1.200/1.495/0.296 ms

$ sudo arping 192.168.122.20
ARPING 192.168.122.20
42 bytes from 5a:ed:f7:c4:10:14 (192.168.122.20): index=0 time=912.481 usec
42 bytes from 5a:ed:f7:c4:10:14 (192.168.122.20): index=1 time=747.873 usec
^C
--- 192.168.122.20 statistics ---
2 packets transmitted, 2 packets received, 0% unanswered (0 extra)
rtt min/avg/max/std-dev = 0.748/0.830/0.912/0.082 ms

Workaround: separate cloud-init scripts for each one, assigning a MAC address