MAC address changes on every boot

[Randy Wyatt]

I am running a fully patched Fedora 21 system.  We are trying to give it a
long term lease in the DHCP server,  but the MAC address sent changes on
every boot.  The MAC address seen at the DHCP server is not actually valid.

The DHCP server is like Win2008 Server R2.

Any ideas?

Regards,
Randy

[Robert Moskowitz]

On 04/30/2015 12:24 PM, Randy Wyatt wrote:
>  I am running a fully patched Fedora 21 system.  We are trying to give 
>  it a long term lease in the DHCP server,  but the MAC address sent 
>  changes on every boot.  The MAC address seen at the DHCP server is not 
>  actually valid. 
If you have a NIC that can't (or maybe does not) have a stable MAC 
address you can:

vi /etc/udev/rules.d/70-persistent-net.rules

# net device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="02:8b:02:81:f4:4a", ATTR{type}=="1",
KERNEL=="eth*", 
NAME="eth0"

Or whatever you want for the MACaddr.

[Boris Epstein]

What hardware do you have in your machine?

I've seen some NIC's with bad firmware that lose their MAC address
assignment.

Boris.

On Thu, Apr 30, 2015 at 12:24 PM, Randy Wyatt <rwwyatt01(a)gmail.com&gt; wrote:

>  I am running a fully patched Fedora 21 system.  We are trying to give it a
>  long term lease in the DHCP server,  but the MAC address sent changes on
>  every boot.  The MAC address seen at the DHCP server is not actually valid.
>
>  The DHCP server is like Win2008 Server R2.
>
>  Any ideas?
>
>  Regards,
>  Randy
>
>
>  --
>  users mailing list
>  users(a)lists.fedoraproject.org
>  To unsubscribe or change subscription options:
>  https://admin.fedoraproject.org/mailman/listinfo/users
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>  Have a question? Ask away: http://ask.fedoraproject.org
>
>

[Rick Stevens]

On 04/30/2015 09:24 AM, Randy Wyatt wrote:
>  I am running a fully patched Fedora 21 system.  We are trying to give it
>  a long term lease in the DHCP server,  but the MAC address sent changes
>  on every boot.  The MAC address seen at the DHCP server is not actually
>  valid.
>
>  The DHCP server is like Win2008 Server R2. 
I don't see that as possible unless the F21 machine has multiple NICs
and the software is reassigning names on each boot. Not likely, but if
it does, you could tell udev to always assign one of the NICs as a fixed
name (em1, eth0, whatever) via a udev rule, then make sure that's the
NIC which the dhclient runs on.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks(a)alldigital.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-            The gene pool could use a little chlorine.              -
----------------------------------------------------------------------

[William Oliver]

On Thu, 30 Apr 2015, Tom Horsley wrote:

>  On Thu, 30 Apr 2015 09:24:32 -0700
>  Randy Wyatt wrote:
>
> > Any ideas?
>
>  I've had at least two separate linksys NIC cards die like this. The
>  MAC would be randomly different on each power cycle. I chucked
>  those cards in the recycle bin :-).
>
>  If these are built in ethernet ports, perhaps the motherboard
>  battery is going dead and causing a similar problem?
>  
You could set the MAC address on each bootup so that it's consistent.

See, for instance:

http://www.billoblog.com/?p=1252

The above is for fedora 19, but the method is about the same for F21.

Obviously, you'd set it to a number rather than randomizing it...

billo

[Tom Horsley]

On Thu, 30 Apr 2015 09:24:32 -0700
Randy Wyatt wrote:

>  Any ideas? 
I've had at least two separate linksys NIC cards die like this. The
MAC would be randomly different on each power cycle. I chucked
those cards in the recycle bin :-).

If these are built in ethernet ports, perhaps the motherboard
battery is going dead and causing a similar problem?