epair0a consumes DHCP leases with changing MAC addresses

[bal0an]

For a while now I observe my DHCP server giving out DHCP IPv4 leases to a freenas resource (the listing is from my router, a avm fritz box 7270):

The cause for the ever changing IP addresses is a randomized MAC address of the epair0a device in freenas. The MAC address seems to be randomized at system startup which my freenas does on a daily basis (it is a backup server and does not need to run 24/7 - saves me money on my electricity bill)

Is there any way make epair0a use the same MAC address and prevent DHCP lease space pollution?

Regards, baloan

 

[Dusan]

Are you using jails (or plugins)? How is the jail network configured (VIMAGE, NAT, ...)?
Could you please post the output of ifconfig?

 

[bal0an]

Are you using jails (or plugins)? How is the jail network configured (VIMAGE, NAT, ...)?
Could you please post the output of ifconfig?

re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>​

ether 00:25:22:b3:18:f2​

inet 192.168.178.25 netmask 0xffffff00 broadcast 192.168.178.255​

nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>​

media: Ethernet autoselect (1000baseT <full-duplex>)​

status: active​

ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536

nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>​

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>​

inet6 ::1 prefixlen 128​

inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6​

inet 127.0.0.1 netmask 0xff000000​

nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>​

bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

ether 02:fe:4a:c8:9c:00​

nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>​

id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15​

maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200​

root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0​

member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>​

ifmaxaddr 0 port 8 priority 128 path cost 2000​

member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>​

ifmaxaddr 0 port 3 priority 128 path cost 20000​

epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

options=8<VLAN_MTU>​

ether 02:81:e0:00:08:0a​

inet6 fe80::81:e0ff:fe00:80a%epair0a prefixlen 64 scopeid 0x8​

inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255​

nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>​

media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)​

status: active​

 

[Dusan]

The jail should be using a fixed IP address (the one configured in your screenshot). Are you sure it's the epair / FreeNAS doing those DHCP requests?
You may want to create a bug report here: https://bugs.freenas.org/projects/freenas/issues

 

[bal0an]

The jail should be using a fixed IP address (the one configured in your screenshot). Are you sure it's the epair / FreeNAS doing those DHCP requests?
You may want to create a bug report here: https://bugs.freenas.org/projects/freenas/issues

Well, pretty sure. The MAC address marked in my router as active matches the epair0a MAC address. Doesn't match with the screenshot as I happened to switch routers just yesterday to adress connectivity problems. Apologies for the confusion.

 

[Lukas]

Coincidentally, I just started seeing this exact problem in my router I installed yesterday. Any news on that?

 

[bal0an]

I have migrated to freenas 9.2.1. The problem has disappeared.