Hi.

> > > It's possible with most NICs, but a few have explicit hardware
> > > protection against it.  The code to do it under Linux exists,
> > > but people are almost always wrong in their desire to do this.
> > It's extremely useful for some types of hot-standy setups.  Some
> > types of channel-bonding might find it useful as well.  Other than
> > that, I can't think of too many reasons either, but I'm sure
> > someone else will :)
> The channel bonding setup program copies the station address, but 
> only the soft copy the kernel keeps.  It doesn't change the EEPROM
> entry.
> Some people might want to restore a corrupted EEPROM, and others need
> to change a replacement adapter to match the previous hardware for
> license cookie reasons.  But pretty much everyone that wants the
> EEPROM setup code is doesn't really understand why they are wrong in
> their desire.

Thanks for all the answers so far.

Donald: Maybe you could tell me why I could be wrong with my desire to
change the NICs MAC? Yes, I know, one MAC should exist only once in the
world, if you mean that.

The problem I have is the following: one of our customers has two
10/100 MBit VG/Anylan-NICs in his Network. Now he has to change these
NICs because lacking drivers for this cards. No problem that far, but
one of his programs (CAD-software) is somehow dongled with the NICs
MAC. I can�t figure completly out why he doesn�t talk to the vendor of
this program in order to change the licence key to work with the MAC
of the new card, but he told me that was not possible. So the idea of
changing the new NICs mac to that of the old NIC came up. This is no
issue of software piracy, even if one could think about that.

> Donald Becker
> Scyld Computing Corporation, [EMAIL PROTECTED]

Bye, Mike

------------------------------------
  Development - Wireless Solutions
  CompuLAN Europe GmbH, Germany
  Tel: ++49-6003-815299
  Fax: ++49-6003-815222
------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to