There seems to be a very high rate of MAC address collisions when tap is
running on different machines is there anyway to make the selection of
MAC more random
___
freebsd-virtualization@freebsd.org mailing list
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
Hi Aryeh,
There seems to be a very high rate of MAC address collisions when tap is
running on different machines is there anyway to make the selection of
MAC more random
Do you mean, tap(4) when used with bhyve ? If so, bhyve calculates the
MAC address for adapters based on an md5 hash
In the last episode (Nov 04), Aryeh Friedman said:
There seems to be a very high rate of MAC address collisions when tap is
running on different machines is there anyway to make the selection
of MAC more random
It looks like it's generated based on the number of ticks since boot, plus
the
On 4 November 2013 12:09, Dan Nelson dnel...@allantgroup.com wrote:
In the last episode (Nov 04), Aryeh Friedman said:
There seems to be a very high rate of MAC address collisions when tap is
running on different machines is there anyway to make the selection
of MAC more random
It looks
Hi! I upgraded to 10.0-BETA3 but still see messages like
Tue Nov 5 11:09:05 MSK 2013
calcru: runtime went backwards from 1728 usec to 889 usec for pid 981
(zabbix_server)
calcru: runtime went backwards from 1229 usec to 703 usec for pid 976
(zabbix_server)
calcru: runtime went backwards from
