Aug/23/2014 20:47:42 dhcp,warning dhcp1 offering lease 172.16.43.255 for 18:34:51:00:29:97 without success
Aug/23/2014 21:01:28 dhcp,warning dhcp1 offering lease 172.16.46.163 for 40:A6:D9:34:0F:D6 without success
Aug/23/2014 21:06:49 dhcp,warning dhcp1 offering lease 172.16.44.63 for BC:3B:AF:4C:FD:02 without success
Aug/23/2014 21:06:54 dhcp,warning dhcp1 offering lease 172.16.43.32 for F4:F1:5A:BB:1E:68 without success
Aug/23/2014 21:07:01 dhcp,warning dhcp1 offering lease 172.16.43.32 for F4:F1:5A:BB:1E:68 without success
Aug/23/2014 21:07:01 dhcp,warning dhcp1 offering lease 172.16.43.32 for F4:F1:5A:BB:1E:68 without success
Aug/23/2014 21:09:33 dhcp,warning dhcp1 offering lease 172.16.42.50 for BC:3B:AF:11:6A:3A without success
Aug/23/2014 21:11:30 dhcp,warning dhcp1 offering lease 172.16.50.99 for 18:00:2D:2B:BD:B6 without success
Aug/23/2014 21:15:40 dhcp,warning dhcp1 offering lease 172.16.42.61 for 28:E1:4C:3B:75:AA without success
Aug/23/2014 21:17:18 dhcp,warning dhcp1 offering lease 172.16.47.119 for 88:1F:A1:94:F1:CA without success
Aug/23/2014 21:17:23 dhcp,warning dhcp1 offering lease 172.16.47.119 for 88:1F:A1:94:F1:CA without success
Aug/23/2014 21:26:36 dhcp,warning dhcp1 offering lease 172.16.42.174 for 54:EA:A8:BE:7E:ED without success
Aug/23/2014 21:39:12 dhcp,warning dhcp1 offering lease 172.16.43.182 for 38:AA:3C:68:7A:99 without success
Aug/23/2014 21:48:16 dhcp,warning dhcp1 offering lease 172.16.48.165 for 00:73:E0:79:81:C2 without success
Aug/23/2014 22:24:56 dhcp,warning dhcp1 offering lease 172.16.44.0 for BC:3B:AF:02:C0:83 without success
8月/ 23/2014 22:27:25 dhcp,警告dhcp1提供lease 172.16.44.45 for 50:EA:D6:40:CA:05 without success
Aug/23/2014 22:34:54 dhcp,warning dhcp1 offering lease 172.16.49.50 for A8:86:DD:13:51:D5 without success
Aug/23/2014 22:36:43 dhcp,warning dhcp1 offering lease 172.16.44.98 for 8C:00:6D:08:EF:5D without success
Aug/23/2014 22:41:16 dhcp,warning dhcp1 offering lease 172.16.49.231 for 0C:3E:9F:59:E4:3C without success
Aug/23/2014 22:41:40 dhcp,warning dhcp1 offering lease 172.16.50.146 for B4:62:93:C2:21:E6 without success
Aug/23/2014 22:41:54 dhcp,warning dhcp1 offering lease 172.16.41.96 for 48:74:6E:62:D7:35 without success
Aug/23/2014 22:43:01 dhcp,warning dhcp1 offering lease 172.16.46.173 for D0:22:BE:7C:B1:93 without success
Aug/23/2014 22:45:49 dhcp,warning dhcp1 offering lease 172.16.42.248 for 94:EB:CD:57:B5:09 without success
Aug/23/2014 22:46:10 dhcp,warning dhcp1 offering lease 172.16.50.111 for 88:30:8A:D7:82:FF without success
Aug/23/2014 22:47:37 dhcp,warning dhcp1 offering lease 172.16.48.115 for CC:78:5F:28:31:DE without success
Aug/23/2014 22:52:00 dhcp,warning dhcp1 offering lease 172.16.46.156 for F0:25:B7:BC:C6:F0 without success
Aug/23/2014 23:00:07 dhcp,warning dhcp1 offering lease 172.16.43.42 for 34:C0:59:A6:F3:A8 without success
Aug/23/2014 23:02:14 dhcp,warning dhcp1 offering lease 172.16.48.144 for FC:25:3F:86:B7:15 without success


any solutions ?

Do you have this on bridge interface ?

ether5

Hi,

You can try checking if you enabled admin MAC on bridge; if it's enabled you must put some MAC that no cause conflit on all devices on bridge.

Regards.

David L.

Umm, can you explain the admin mac on the Bridge? When I setup a bridge it automatically enables the mac and applies a mac address from? And, if the admin mac is one address how can it effect the list of addresses that are listed? Thanks for the info.

I would suggest moving the DHCP server to the bridge rather than a member port

The mac address of the bridge tends to be the first interfaces mac address thats added to the bridge.

我理解管理macis to specify a mac address fixed to the bridge and as pointed out you want to use a mac address that will never otherwise appear on the network as if it should collide then odd things can happen.

Regards
Alexander