FreeNAS changing MAC Addresses all the time...

[rodofrn]

Hello FreeNAS geeks :)

I have a "major"? problem, this is happening to my FreeNAS box and I have no idea what it is or how to fix it. It is messing with my virtualboxes and such. Any idea?

Code:

May 18 10:27:53 freenas kernel: bridge0: link state changed to UP
May 18 10:27:53 freenas kernel: bridge0: link state changed to UP
May 18 10:27:53 freenas kernel: igb0: promiscuous mode enabled
May 18 10:27:53 freenas epair0a: Ethernet address: 02:ff:20:00:05:0a
May 18 10:27:53 freenas epair0b: Ethernet address: 02:ff:70:00:06:0b
May 18 10:27:53 freenas kernel: epair0a: link state changed to UP
May 18 10:27:53 freenas kernel: epair0a: link state changed to UP
May 18 10:27:53 freenas kernel: epair0b: link state changed to UP
May 18 10:27:53 freenas kernel: epair0b: link state changed to UP
May 18 10:27:53 freenas kernel: igb0: link state changed to DOWN
May 18 10:27:53 freenas kernel: igb0: link state changed to DOWN
May 18 10:27:53 freenas kernel: epair0a: promiscuous mode enabled
May 18 10:27:53 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
May 18 10:27:53 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
May 18 10:27:58 freenas kernel: igb0: link state changed to UP
May 18 10:27:58 freenas kernel: igb0: link state changed to UP
May 18 17:27:58 freenas devd: Executing '/etc/rc.d/dhclient quietstart igb0'
May 18 17:27:59 freenas devd: Executing '/etc/pccard_ether epair1a start'
May 18 17:27:59 freenas devd: Executing '/etc/pccard_ether epair1b start'
May 18 17:27:59 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair1a'
May 18 10:27:59 freenas epair1a: Ethernet address: 02:ff:20:00:06:0a
May 18 10:27:59 freenas epair1b: Ethernet address: 02:ff:70:00:07:0b
May 18 10:27:59 freenas kernel: epair1a: link state changed to UP
May 18 10:27:59 freenas kernel: epair1a: link state changed to UP
May 18 10:27:59 freenas kernel: epair1b: link state changed to UP
May 18 10:27:59 freenas kernel: epair1b: link state changed to UP
May 18 10:27:59 freenas kernel: epair1a: promiscuous mode enabled
May 18 10:27:59 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
May 18 10:27:59 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
May 18 17:28:04 freenas devd: Executing '/etc/pccard_ether epair2a start'
May 18 17:28:04 freenas devd: Executing '/etc/pccard_ether epair2b start'
May 18 17:28:04 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair2a'
May 18 10:28:04 freenas epair2a: Ethernet address: 02:ff:20:00:07:0a
May 18 10:28:04 freenas epair2b: Ethernet address: 02:ff:70:00:08:0b
May 18 10:28:04 freenas kernel: epair2a: link state changed to UP
May 18 10:28:04 freenas kernel: epair2a: link state changed to UP
May 18 10:28:04 freenas kernel: epair2b: link state changed to UP
May 18 10:28:04 freenas kernel: epair2b: link state changed to UP
May 18 10:28:04 freenas kernel: epair2a: promiscuous mode enabled
May 18 10:28:04 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 18 10:28:04 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 18 17:28:10 freenas devd: Executing '/etc/pccard_ether epair3a start'
May 18 17:28:10 freenas devd: Executing '/etc/pccard_ether epair3b start'
May 18 17:28:10 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair3a'
May 18 10:28:10 freenas epair3a: Ethernet address: 02:ff:20:00:08:0a
May 18 10:28:10 freenas epair3b: Ethernet address: 02:ff:70:00:09:0b
May 18 10:28:10 freenas kernel: epair3a: link state changed to UP
May 18 10:28:10 freenas kernel: epair3a: link state changed to UP
May 18 10:28:10 freenas kernel: epair3b: link state changed to UP
May 18 10:28:10 freenas kernel: epair3b: link state changed to UP
May 18 10:28:10 freenas kernel: epair3a: promiscuous mode enabled
May 18 10:28:10 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
May 18 10:28:10 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
May 18 17:28:16 freenas devd: Executing '/etc/pccard_ether epair4a start'
May 18 17:28:16 freenas devd: Executing '/etc/pccard_ether epair4b start'
May 18 17:28:16 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair4a'
May 18 10:28:16 freenas epair4a: Ethernet address: 02:ff:20:00:09:0a
May 18 10:28:16 freenas epair4b: Ethernet address: 02:ff:70:00:0a:0b
May 18 10:28:16 freenas kernel: epair4a: link state changed to UP
May 18 10:28:16 freenas kernel: epair4a: link state changed to UP
May 18 10:28:16 freenas kernel: epair4b: link state changed to UP
May 18 10:28:16 freenas kernel: epair4b: link state changed to UP
May 18 10:28:16 freenas kernel: epair4a: promiscuous mode enabled
May 18 10:28:16 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair4b
May 18 10:28:16 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair4b
May 18 17:28:26 freenas devd: Executing '/etc/pccard_ether epair5a start'
May 18 17:28:26 freenas devd: Executing '/etc/pccard_ether epair5b start'
May 18 17:28:26 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair5a'
May 18 10:28:26 freenas epair5a: Ethernet address: 02:ff:20:00:0a:0a
May 18 10:28:26 freenas epair5b: Ethernet address: 02:ff:70:00:0b:0b
May 18 10:28:26 freenas kernel: epair5a: link state changed to UP
May 18 10:28:26 freenas kernel: epair5a: link state changed to UP
May 18 10:28:26 freenas kernel: epair5b: link state changed to UP
May 18 10:28:26 freenas kernel: epair5b: link state changed to UP
May 18 10:28:26 freenas kernel: epair5a: promiscuous mode enabled
May 18 10:28:26 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
May 18 10:28:26 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
May 18 17:28:31 freenas devd: Executing '/etc/pccard_ether epair6a start'
May 18 17:28:31 freenas devd: Executing '/etc/pccard_ether epair6b start'
May 18 10:28:31 freenas epair6a: Ethernet address: 02:ff:20:00:0b:0a
May 18 10:28:31 freenas epair6b: Ethernet address: 02:ff:70:00:0c:0b
May 18 10:28:31 freenas kernel: epair6a: link state changed to UP
May 18 10:28:31 freenas kernel: epair6a: link state changed to UP
May 18 10:28:31 freenas kernel: epair6b: link state changed to UP
May 18 10:28:31 freenas kernel: epair6b: link state changed to UP
May 18 10:28:31 freenas kernel: epair6a: promiscuous mode enabled
May 18 10:28:31 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair6b
May 18 10:28:31 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair6b
May 18 17:28:31 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair6a'
May 18 17:28:50 freenas devd: Executing '/etc/pccard_ether epair7a start'
May 18 10:28:50 freenas epair7a: Ethernet address: 02:ff:20:00:0c:0a
May 18 10:28:50 freenas epair7b: Ethernet address: 02:ff:70:00:0d:0b
May 18 10:28:50 freenas kernel: epair7a: link state changed to UP
May 18 10:28:50 freenas kernel: epair7a: link state changed to UP
May 18 10:28:50 freenas kernel: epair7b: link state changed to UP
May 18 10:28:50 freenas kernel: epair7b: link state changed to UP
May 18 10:28:50 freenas kernel: epair7a: promiscuous mode enabled
May 18 17:28:50 freenas devd: Executing '/etc/pccard_ether epair7b start'
May 18 17:28:50 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair7a'
May 18 10:28:50 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair7b
May 18 10:28:50 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair7b
May 18 10:29:19 freenas dhclient: New IP Address (igb0): 192.168.0.105
May 18 10:29:19 freenas dhclient: New Subnet Mask (igb0): 255.255.255.0
May 18 10:29:19 freenas dhclient: New Broadcast Address (igb0): 192.168.0.255
May 18 10:29:19 freenas dhclient: New Routers (igb0): 192.168.0.1
May 18 10:29:20 freenas dhclient: New Routers (igb0): 192.168.0.1

Thanks.

 

[rm-r]

Looks like you have 2 nics in the freenas host - are both connected at the same time to the switch? have you tried changing / replacing the cables?

 

[rodofrn]

Looks like you have 2 nics in the freenas host - are both connected at the same time to the switch? have you tried changing / replacing the cables?

I am guessing when you say "2 nics" you mean like 2 ethernet ports? if so, yeah the freenas box mobo has 2 ethernet ports, although I am using only 1 atm. I would love to use both, but I am afraid of the whole thing collapsing..! I have not tried replacing cables, you mean like new ethernet cables?

 

[Puggs]

We see similar issues in our servers at work until we disable the BMC in the BIOS, worth looking into...

Sent from my Nexus 6P using Tapatalk

 

[pirateghost]

I am guessing when you say "2 nics" you mean like 2 ethernet ports? if so, yeah the freenas box mobo has 2 ethernet ports, although I am using only 1 atm. I would love to use both, but I am afraid of the whole thing collapsing..! I have not tried replacing cables, you mean like new ethernet cables?

Yeah....you shouldn't attempt to use both NICs

 

[rodofrn]

We see similar issues in our servers at work until we disable the BMC in the BIOS, worth looking into...

Sent from my Nexus 6P using Tapatalk

OK, I have no idea what that means, i can look into it though, thanks.

Yeah....you shouldn't attempt to use both NICs

Currently using only 1, I guess it will stay that way :) Thanks.

Anybody else know why this is happening?

 

[Mirfster]

epair

Isn't that pertaining to jails? I don't run them, I have ESXi instead...

Opps, just noticed you mentioned VirtualBox. Are you trying to use two NICs in any jails?

 

[rodofrn]

Isn't that pertaining to jails? I don't run them, I have ESXi instead...

Opps, just noticed you mentioned VirtualBox. Are you trying to use two NICs in any jails?

I am NOT using 2 nics in any jails....

 

[BigDave]

I'm not well versed on internal network stuff, but this log data sounds familiar to me...
https://forums.freenas.org/index.php?threads/intel-nic-driver-issue.43091/
I briefly looked over the logs from both posts, and while not identical, they have a lot of similarities.
iirc the other problem was a corrupted driver issue that was corrected by a re-installation of the OS.
The link to the other post might shed some light on your issue, don't know...
Good luck.