mith <[EMAIL PROTECTED]> wrote:
> From: Mark Smith <[EMAIL PROTECTED]>
> Subject: Re: BCP for Private OUI / address assignments?
> To: [EMAIL PROTECTED]
> Cc: nanog@nanog.org
> Date: Monday, November 24, 2008, 10:01 PM
> Hi,
>
> On Mon, 24 Nov 2008 19:35:07 +0100
&
Realistically, OUI space is pretty large for each L2 domain... Once it
hits an L3 domain, you can repeat OUIs all you want... Pick some prefix
set of bits that include "locally assigned" that is unique to your
organization and you will operationally be fine. Or the last 8 bits of
your host se
Hi,
On Mon, 24 Nov 2008 19:35:07 +0100
Peter Dambier <[EMAIL PROTECTED]> wrote:
> I also found this one helpful
>
> http://www.iana.org/assignments/ethernet-numbers
>
> ===
> The CF Series
>
> RFC 2153 describes a method of usings a "pseudo OUI" for certain
> purposes when there is no appr
I also found this one helpful
http://www.iana.org/assignments/ethernet-numbers
===
The CF Series
RFC 2153 describes a method of usings a "pseudo OUI" for certain
purposes when there is no appropriate regular OUI assigned. These are
listed here.
CF0001 Data Comm for Business
With the increasing use of virtual machines in my environment, I am
needing more and more unique mac addresses to assign to the many virtual
Ethernet devices I have attached and visible to my non-virtual physical
network. The problem of course is that I don't have an IEEE OUI and
therefore
On Nov 24, 2008, at 11:02 AM, mike wrote:
I am needing more and more unique mac addresses
...
it occurs to me that there should be something - ala rfc 1918
You can probably find examples online, but in a nutshell this
does exist.
Set bit b2 to 1, "locally assigned".
Default is 0, "global
6 matches
Mail list logo