In a DHCP situation, there absolutely must be a DHCP server to ping. I suspect it doesn't have to be a ping, but any traffic whatsoever such as a bogus ARP request. I want to be clear here in that I don't think this is some kind of fault in the pixel stick, but one in the actual device that it is associated with through wifi. That said, I wouldn't hold my breath waiting for "the other guy" to solve this problem. I was just suggesting a possible way to avoid the issue that is within reach of the pixel stick firmware guys that carries a lot less weight than a DHCP renegotiation every 4 minutes. My personal experience was with a particular cable modem that seemed to be the root of the issue since the customer had multiple devices that suffered from it. That makes me believe that the modem was the problem, not the end device, especially after a firmware upgrade to the modem "solved" their problems. I admit that I'm not an expert on all the ins and outs of TCP/IP over wifi, but I do have some knowledge of how this all works, especially on the TCP/IP end of it. I presume that the end client's state machine is left hanging "thinking" that it's just not getting through due to radio conditions, not that it's being completely ignored by the host device.
Notifications
Clear all
Nov 28, 2016 6:05 pm
Page 3 / 3
Prev
