"Ryan Finnie" <[EMAIL PROTECTED]> writes:
>> Not if it boots off a different host it won't.
>
> You quoted everything in my message except the part where I
> essentially say ", unless it's on a different host".
Apologies. I didn't mean to misrepresent you.
> Besides, the automatic generation
On 10/12/06, Nic James Ferrier <[EMAIL PROTECTED]> wrote:
> > This combines the umid you expect you assign to the instance with the
> > hostname of the host. That way, the mac address will be the same each
> > time it boots,
>
> Not if it boots off a different host it won't.
You quoted everything
"Ryan Finnie" <[EMAIL PROTECTED]> writes:
> I took a simpler route for pseudo-random non-varying mac address
> generation. Here you go:
>
> echo $(hostname)${UMID} | md5sum | \
> awk '{print "00:08:93:"substr($1,1,2)":"substr($1,3,2)":"substr($1,5,2)}'
>
> This combines the umid you expect you as
On 10/12/06, Nic James Ferrier <[EMAIL PROTECTED]> wrote:
> In my quest for the perfect network setup for a VM here is a piece of
> code that will allocate mac addresses from a pool.
I took a simpler route for pseudo-random non-varying mac address
generation. Here you go:
echo $(hostname)${UMID}
In my quest for the perfect network setup for a VM here is a piece of
code that will allocate mac addresses from a pool.
It's not that polished yet. So far you can only allocate based on the
pool:
fe:fd:12:aa:bb:cc
where aa:bb:cc are the pool. However, that is 17 million different mac
addresse
