Ip Address Conflict - 0.0.0.0
Posted: Thu Nov 02, 2017 12:47 am
I have been trying to use static IP addresses on my win10 machines so I can assign QOS settings to my PC's. Best I can tell, QOS Assignments only work with Static IPs.
Every few hours (not sure exactly how long). The network adapter on my windows 10 machine stops working. I get this error in the Windows System Event Viewer:
The system detected an address conflict for IP address 0.0.0.0 with the system having network hardware address 04-A1-51-xx-xx-xx. Network operations on this system may be disrupted as a result.
When this happens my win10 machine has no network connectivity. I have to disable the Network adapter on my win10 machine, then enable it and I am back in business (Network on the Win 10 machine starts working again).
Turns out, the conflicting MAC address from the Event Log matches the Wireless MAC Address on the Gargoyle Status page. I think this is pretty weird, but OK.
On the router, I am seeing these messages (LogShow) about the time it breaks my win 10 machine:
Wed Nov 1 19:51:25 2017 daemon.warn dnsmasq-dhcp[1849]: not giving name localhost.lan to the DHCP lease of 192.168.1.214 because the name exists in /etc/hosts with address 127.0.0.1
Wed Nov 1 19:51:25 2017 daemon.warn dnsmasq-dhcp[1849]: not giving name localhost to the DHCP lease of 192.168.1.214 because the name exists in /etc/hosts with address 127.0.0.1
Wed Nov 1 19:52:46 2017 kerninfo kernel: [1139192.680000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is down
Wed Nov 1 19:52:50 2017 kerninfo kernel: [1139196.680000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
For now I have moved back to DHCP assignments ... I dont think I was getting this problem with DHCP, but will report back in a day or so to confirm.
Oh, I am using a WNDR4300 with Version 1.9.2. I updated my Win10 network driver to the latest RealTek PCIe GBE Family Controller (10.23.1003.2017)
1) Is there any way to configure QOS without Static IPs?
2) Is there anyway to stop this horrible breakage of the Win10 network driver?
Thanks!
Greg.
Every few hours (not sure exactly how long). The network adapter on my windows 10 machine stops working. I get this error in the Windows System Event Viewer:
The system detected an address conflict for IP address 0.0.0.0 with the system having network hardware address 04-A1-51-xx-xx-xx. Network operations on this system may be disrupted as a result.
When this happens my win10 machine has no network connectivity. I have to disable the Network adapter on my win10 machine, then enable it and I am back in business (Network on the Win 10 machine starts working again).
Turns out, the conflicting MAC address from the Event Log matches the Wireless MAC Address on the Gargoyle Status page. I think this is pretty weird, but OK.
On the router, I am seeing these messages (LogShow) about the time it breaks my win 10 machine:
Wed Nov 1 19:51:25 2017 daemon.warn dnsmasq-dhcp[1849]: not giving name localhost.lan to the DHCP lease of 192.168.1.214 because the name exists in /etc/hosts with address 127.0.0.1
Wed Nov 1 19:51:25 2017 daemon.warn dnsmasq-dhcp[1849]: not giving name localhost to the DHCP lease of 192.168.1.214 because the name exists in /etc/hosts with address 127.0.0.1
Wed Nov 1 19:52:46 2017 kerninfo kernel: [1139192.680000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is down
Wed Nov 1 19:52:50 2017 kerninfo kernel: [1139196.680000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
For now I have moved back to DHCP assignments ... I dont think I was getting this problem with DHCP, but will report back in a day or so to confirm.
Oh, I am using a WNDR4300 with Version 1.9.2. I updated my Win10 network driver to the latest RealTek PCIe GBE Family Controller (10.23.1003.2017)
1) Is there any way to configure QOS without Static IPs?
2) Is there anyway to stop this horrible breakage of the Win10 network driver?
Thanks!
Greg.