XBOX 1 requesting dhcp constantly

[edsyl]

Just wondering if anyone else has seen their xbox1 constantly banging away at the DHCP serice?

Here is an excerpt:
May 17 21:36:56 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:38:03 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:38:03 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:39:05 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:39:05 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:39:16 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:39:16 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:39:25 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:39:25 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:39:35 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:39:35 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:39:46 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:39:46 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:39:54 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:39:54 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:40:04 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:40:04 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:40:15 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:40:15 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:40:26 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:40:26 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:40:48 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:40:48 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:40:59 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:40:59 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:41:08 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:41:08 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:41:16 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:41:16 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:42:04 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:42:04 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:42:15 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:42:15 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:42:23 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:42:23 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:42:32 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:42:32 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:42:40 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:42:40 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:42:50 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:42:50 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:42:58 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:42:58 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:43:08 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:43:08 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1
May 17 21:43:29 dnsmasq-dhcp[871]: DHCPREQUEST(br0) 192.168.1.33 50:1a:c5:a2:b1:91
May 17 21:43:29 dnsmasq-dhcp[871]: DHCPACK(br0) 192.168.1.33 50:1a:c5:a2:b1:91 BORGXBOX1


Any ideas as to what this is?
THanks
Ed

 

[L&LD]

What router? What firmware version (be specific)? Was a reset to factory defaults performed after flashing the current firmware and followed by a minimal and manual configuration of the router to secure it and connect to your ISP?

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573


I would also suggest at least testing with new ssid's too (you can keep the old password). Even if just temporarily (while testing).

 

[edsyl]

What router? What firmware version (be specific)? Was a reset to factory defaults performed after flashing the current firmware and followed by a minimal and manual configuration of the router to secure it and connect to your ISP?

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573


I would also suggest at least testing with new ssid's too (you can keep the old password). Even if just temporarily (while testing).

AC68U, 380.59.
Yes I reset everything and set everything manually.
Regards
Ed

 

[L&LD]

Thanks. Does having an new ssid help?

 

[MXM]

I had a similar problem but with a different WiFi device.... After much testing, I determined the issue was tied to the router WiFi channel.

I forced the router to run on Ch 11 (but 1 or 6 worked too) and the problem went away. Never really determined the underlying cause but the problem went away.

Try that and see if it works for you too..

 

[netwrks]

I see the same thing from a wired XBOX ONE, on a Tomato router, running DHCP Services. Google shows lots of the same reports. XBOX sites are totally useless, in trying to find a resolution. I just disabled DHCP logging. If you find a resolution, let us know!

 

[Kronyx]

I have the same issue with a wired Xbox one ...

 

[mstombs]

Consoles and some Windows versions do this when they cannot get out to something on the internet - are you adblocking by domain or hosts? Due to the ancient dhcp protocol there is no way for a dhcp server to tell the client to renew, so the devices try to refresh the IP and wake up the connection inc case the old IP is no longer valid. Shame the router doesn't do this in my experience - my ISP gives a 7 day lease and the router waits for 3.5 days even if ISP do some reconfiguration - so I have a ping script that tries a renew or eventually reboots the router.

 

[Gitsum]

Same with my Xbox 1 and an ASUS AC-88U with Merlin firmware. I tried manually assigning an IP address from the router to it but that didn't help. I suppose I could manually go into the Xbox and set it's IP there and see if that helps. But for the mean time I just disabled DHCP logging.

 

[jeff288]

Go to LAN --> DHCP Server --> Hide DHCP/RA queries. This was discussed in another thread. I also had the same issues with a wired Xbox 1 doing this every 15 minutes but this solved it. It hid the message, anyway, still not sure why it was doing this.

The other thread: http://www.snbforums.com/threads/rt-ac68u-dhcprequest-br0-dhcpack-br0.30573/