You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has been reported in the forum but I'd like to 'officially' report it here since it's seemingly gone ignored for 3 years, and the problem still exists.
When using Ethernet.maintain(), there are a few bugs that cause the Arduino to constantly spam the network with DHCP broadcast requests - not great for battery powered devices like phones that have to awaken to process all this data (around 50k/sec I was getting).
One bug was reported on the old tracker as issue #985. That's not fixed yet, but the new one was on the forum here: http://forum.arduino.cc/index.php?topic=195422.0 . Essentially half the DHCP reply is missing, and the Library relies on the DHCP server not following the RFC and thus dishing out an existing address. DHCP servers that do follow the RFC hand out a new address, confusing things.
Both are fairly important as not to break people's networks, and fixes have been provided. It'd be a 2 minute job to fix.
I've checked the source for 1.5.x and it's not fixed there, nor in the live 1.0.6 release.
The text was updated successfully, but these errors were encountered:
Elijahg
changed the title
Ethernet Library: DHCP Spam
Ethernet Library: DHCP Broadcast Spam
Jan 23, 2015
This has been reported in the forum but I'd like to 'officially' report it here since it's seemingly gone ignored for 3 years, and the problem still exists.
When using Ethernet.maintain(), there are a few bugs that cause the Arduino to constantly spam the network with DHCP broadcast requests - not great for battery powered devices like phones that have to awaken to process all this data (around 50k/sec I was getting).
One bug was reported on the old tracker as issue #985. That's not fixed yet, but the new one was on the forum here: http://forum.arduino.cc/index.php?topic=195422.0 . Essentially half the DHCP reply is missing, and the Library relies on the DHCP server not following the RFC and thus dishing out an existing address. DHCP servers that do follow the RFC hand out a new address, confusing things.
Both are fairly important as not to break people's networks, and fixes have been provided. It'd be a 2 minute job to fix.
I've checked the source for 1.5.x and it's not fixed there, nor in the live 1.0.6 release.
The text was updated successfully, but these errors were encountered: