Date: Mon, 4 Nov 2013 16:20:45 +0000 From: Michael Berman <michael.berman@tidalscale.com> To: Peter Grehan <grehan@freebsd.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: how is the MAC for tap(4) computed? Message-ID: <89C04F5A-A2E6-4738-AB0C-4DADDE8DCC58@tidalscale.com> In-Reply-To: <5277AE77.8050804@freebsd.org> References: <CAGBxaXn27u3J6iJBoDkW_R2=_kcHzSBU=d0v5eDUvnoAsucSjw@mail.gmail.com>, <5277AE77.8050804@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter, lost the last part of your message ... An alternative would be hashing the vm name with the host name and host MAC= address. Sent from my iPhone > On Nov 4, 2013, at 6:26 AM, "Peter Grehan" <grehan@freebsd.org> wrote: >=20 > Hi Aryeh, >=20 >> 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 >=20 > Do you mean, tap(4) when used with bhyve ? If so, bhyve calculates the MA= C address for adapters based on an md5 hash of the PCI slot/function and VM= name. If you use the same bhyve configuration on a different machine, the = MAC address will be the same. >=20 > If that's the problem, you may want to supply your own MAC address with t= he "mac=3D" parameter on the command line e.g. >=20 > later, >=20 > Peter. >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free= bsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?89C04F5A-A2E6-4738-AB0C-4DADDE8DCC58>