Flooding of DHCP requests from epair0a

[AlunS]

My router log is getting flooded with DHCP requests from the MAC address associated with epair0a. I've allocated a static IP address to it via the GUI but still, they keep flooding in. Any ideas?

23 Jan 6 16:22:10 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
22 Jan 6 16:22:10 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
21 Jan 6 16:22:01 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
20 Jan 6 16:22:01 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
19 Jan 6 16:21:48 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
18 Jan 6 16:21:48 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
17 Jan 6 16:21:32 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
16 Jan 6 16:21:32 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
15 Jan 6 16:21:24 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
14 Jan 6 16:21:24 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
13 Jan 6 16:16:11 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
12 Jan 6 16:16:11 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
11 Jan 6 16:15:57 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
10 Jan 6 16:15:57 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
9 Jan 6 16:15:50 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
8 Jan 6 16:15:50 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
7 Jan 6 16:15:40 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
6 Jan 6 16:15:40 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
5 Jan 6 16:15:31 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
4 Jan 6 16:15:31 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A
3 Jan 6 16:15:24 DHCP INFO DHCPS:Send OFFER with ip 192.168.11.2
2 Jan 6 16:15:24 DHCP INFO DHCPS:Recv DISCOVER from 02:04:A7:00:0A:0A

 

[cyberjock]

Is the jail actually getting that IP address? It sounds to me like the jail might not be receiving the offered IP and so the jail keeps trying to get an IP address over and over in a vicious cycle.

 

[AlunS]

I thought epair0b was the jail, and epair0a the interface on the other side of the virtual bridge, which doesn't have, or need, an IP as far as I know. The jail has a static IP, and that seems to be working fine.

Anyway, it's stopped of it's own accord so it'll remain a mystery for now.