How can we help you today?
Start a new topic

Windows DHCP ipv4_conflict_detection BAD Address

Hello,


I got a Problem with the Snom D315 & D375 telephones which are running by default the ipv4 conflict detection (Firmware-Version:    snomD375-SIP 8.9.3.40). We are running Windows DHCP Server and don't use any vlan, so a very simple network installation.

On every reboot of the phones we get marked the last IP address that was used for the phone as BAD Address. On the Phone logs we can see that the conflict detects its own mac address for that IP and try to get a new one from the DHCP Server. Sometime it works on the second time but sometimes on 5th time. Here is an Output of the Phone Log:


Aug 23 08:28:11.756 [INFO ] PHN: IPv4: Init Device eth0 with mac 00:04:13:91:aa:88
Aug 23 08:28:11.756 [DEBUG1] PHN: IPv4Monitor: Device eth0, IP , State device init
Aug 23 08:28:11.756 [WARN ] PHN: Already Initialised eth0
Aug 23 08:28:11.756 [DEBUG0] PHN: IPv4: Start Detection on eth0, IP 10.0.0.158
Aug 23 08:28:11.757 [DEBUG1] PHN: IPv4Monitor: Device eth0, IP 10.0.0.158, State detecting
Aug 23 08:28:11.757 [WARN ] PHN: IPv4Monitor: Device eth0, IP 10.0.0.158, State detect conflict, Remote 0:04:13:91:aa:88
Aug 23 08:28:11.757 [DEBUG1] PHN: IPv4Monitor: Device eth0, IP 10.0.0.158, State device none
Aug 23 08:28:11.757 [NOTICE] PHN: DHCP: Received NAK, retry 1
Aug 23 08:28:11.757 [DEBUG2] PHN: DHCP: Received answer for ip allocation
Aug 23 08:28:11.757 [NOTICE] PHN: DHCP: Received IP address 10.0.0.151
Aug 23 08:28:11.757 [NOTICE] PHN: DHCP: Parsing answer of type 2
Aug 23 08:28:11.758 [DEBUG1] PHN: DHCP: Received Lease 3600
Aug 23 08:28:11.758 [DEBUG2] PHN: DHCP: Received answer for ip allocation
Aug 23 08:28:11.758 [NOTICE] PHN: DHCP: Parsing answer of type 5
Aug 23 08:28:11.758 [DEBUG1] PHN: DHCP: Received Lease 3600
Aug 23 08:28:11.758 [INFO ] PHN: DHCP option 81 ignored
Aug 23 08:28:11.758 [INFO ] PHN: IPv4: Init Device eth0 with mac 00:04:13:91:aa:88
Aug 23 08:28:11.758 [DEBUG1] PHN: IPv4Monitor: Device eth0, IP , State device init
Aug 23 08:28:11.759 [WARN ] PHN: Already Initialised eth0
Aug 23 08:28:11.759 [DEBUG0] PHN: IPv4: Start Detection on eth0, IP 10.0.0.151
Aug 23 08:28:11.759 [DEBUG1] PHN: IPv4Monitor: Device eth0, IP 10.0.0.151, State detecting
Aug 23 08:28:11.759 [DEBUG1] PHN: IPv4Monitor: Device eth0, IP 10.0.0.151, State detect no conflict
Aug 23 08:28:11.759 [DEBUG0] PHN: IPv4: Start Defending on eth0, IP 10.0.0.151
Aug 23 08:28:11.759 [DEBUG1] PHN: IPv4Monitor: Device eth0, IP 10.0.0.151, State defend no conflict
Aug 23 08:28:11.759 [INFO ] PHN: DHCP: t1 1800
Aug 23 08:28:11.759 [INFO ] PHN: DHCP: t2 3150
Aug 23 08:28:11.760 [NOTICE] PHN: Finished waiting for DHCP 4; d4.state = dhcp_finished





THe DHCP Config is also very simple with Options: 3,6,15,42,66,67










Hi Berk,


If you upgrade to version 8.9.3.80 is the issue still there?

http://wiki.snom.com/Firmware/V8_9_3_80


Please factory reset the phone after the upgrade (and if possible clear the DHCP configuration for it) .


Thanks

Catalina


Hi Catalina,

I iwll try and let you know. Thanks


Does anybody has exprience with the combination of snom phones and Windows DHCP server?

Login or Signup to post a comment