Previously, when "ether tun" configuration was used on a Linux host,
packets were sent with Ethernet/MAC address 00:00:00:00:00:00. Under
CentOS 7 at least, this did not appear to cause any issues where the
tun interface on the host was configured with an IP address, but when
an attempt was made to bridge the tun interface, it was no longer
possible to establish IP communication between the emulated machine
and either the Linux host or a Windows NT Server 4 VM.
This fix causes an Ethernet/MAC address to be generated in the same
way when using TUN/TAP as is done for ethertap.
Previously, when "ether tun" configuration was used on a Linux host, packets were sent with Ethernet/MAC address 00:00:00:00:00:00. Under CentOS 7 at least, this did not appear to cause any issues where the tun interface on the host was configured with an IP address, but when an attempt was made to bridge the tun interface, it was no longer possible to establish IP communication between the emulated machine and either the Linux host or a Windows NT Server 4 VM.
This fix causes an Ethernet/MAC address to be generated in the same way when using TUN/TAP as is done for ethertap.