EG2100-P DHCP problem

Dear all,

Gooday to you all!

I have got an error occur appear with Ruijie EG2100-P. Ialready set up /22 DHCP and /22 router id as following

= DHCP 192.168.0.0/22

= Router id 192.168.0.1

except router id from DHCP assign. client is almost 280.

but problem is found, I saw the syslog message and there is IPconflicts error as following

"%ARP-4-ARPCHANGEMAC: ARP entry 192.168.1.39 onGigabitEthernet 0/2 changed 0056.cdad.257f to 5098.3961.3013." etc ..

I noticed, DHCP is only assign 192.168.0. range and showabove error message at the time. I have no idea please kindly provide me.

Thank you, all brother!

I try to create sub-interface and its OK but new DHCP for sub-interfacewas not working. How should I do?

My job scope is

Client almost 280 including laptop and mobile

My network is

AP and LAN (same DHCP)

Laptop are used both networks.

Best Regards,

K

Hi sir

According to this :

= DHCP 192.168.0.0/22
= Router id 192.168.0.1

The assign ip range is 192.168.0.1/22-192.168.3.254/22
So the user can get the ip address of 192.168.1.39/22

It is possible that this log appears because the user has set an ip address privately, and other users have obtained the same address through DHCP.
Please check if there are any private addresses set by users, and you can statically bound these addresses  to the DHCP address pool.


Best regards.

liuwei8@ruijie. replied at 2021-8-31 20:45
Hi sir

According to this :

Thank for your are kindly help bro

There is no static IP, I already check
"%ARP-4-ARPCHANGEMAC: ARP entry 192.168.1.39 onGigabitEthernet 0/2 changed 0056.cdad.257f to 5098.3961.3013."
this message is just one of the error message. actually I found alot of that kind of message in syslog.

here is some of log bro


*Aug 30 22:50:15: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.187 on GigabitEthernet 0/2 changed fc61.9889.3dfc to e0cc.f82a.1779.
*Aug 30 22:50:17: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.96 on GigabitEthernet 0/2 changed fc61.987a.072a to eea3.9756.407f.
*Aug 30 22:50:19: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.205 on GigabitEthernet 0/2 changed 0811.9610.fbcc to b6d6.4fbf.3f9f.
*Aug 30 22:50:21: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.187 on GigabitEthernet 0/2 changed e0cc.f82a.1779 to fc61.9889.3dfc.
*Aug 30 22:50:23: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.51].
*Aug 30 22:50:23: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.59].
*Aug 30 22:50:24: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.67].
*Aug 30 22:50:24: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.73].
*Aug 30 22:50:24: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.74].

*Aug 30 22:47:50: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.202 on GigabitEthernet 0/2 changed fc61.982e.904d to 1416.9e43.53a1.
*Aug 30 22:47:53: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.96 on GigabitEthernet 0/2 changed eea3.9756.407f to fc61.987a.072a.
*Aug 30 22:48:33: %ARP-4-RATELIMIT: Suppressed message count: 24.
*Aug 30 22:48:33: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.96 on GigabitEthernet 0/2 changed eea3.9756.407f to fc61.987a.072a.
*Aug 30 22:48:34: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.202 on GigabitEthernet 0/2 changed 1416.9e43.53a1 to fc61.982e.904d.
*Aug 30 22:48:35: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.197 on GigabitEthernet 0/2 changed 245a.4c26.02a9 to fc61.9889.226c.
*Aug 30 22:48:38: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.238 on GigabitEthernet 0/2 changed 1041.7f5c.f37e to 9417.00d1.5f2a.

Aug 30 23:49:51: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.202 on GigabitEthernet 0/2 changed fc61.982e.904d to 1416.9e43.53a1.
*Aug 30 23:49:56: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.202 on GigabitEthernet 0/2 changed 1416.9e43.53a1 to fc61.982e.904d.
*Aug 30 23:50:05: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.197 on GigabitEthernet 0/2 changed fc61.9889.226c to 245a.4c26.02a9.
*Aug 30 23:50:26: %ARP-4-RATELIMIT: Suppressed message count: 4.
*Aug 30 23:50:26: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.219 on GigabitEthernet 0/2 changed f01f.af0e.7c29 to f024.75a3.226b.
*Aug 30 23:50:27: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.51].
*Aug 30 23:50:27: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.59].
*Aug 30 23:50:27: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.186].
*Aug 30 23:50:27: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.207].
*Aug 30 23:50:27: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged [192.168.0.209].
*Aug 30 23:50:29: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.218 on GigabitEthernet 0/2 changed 36aa.fd78.bbff to 00e0.0a00.427c.
*Aug 30 23:50:33: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.130 on GigabitEthernet 0/2 changed d4be.d987.f9a4 to e247.fcdb.2eb1.
*Aug 30 23:50:34: %ARP-4-ARPCHANGEMAC: ARP entry 192.168.0.143 on GigabitEthernet 0/2 changed f01f.af67.7fe1 to f0db.e2af.b8b9.

Best Regards,
K