Nighthawk RAX30 - DHCP Client Issues

Wonderful job documenting the situation:

• The ISP fails to respond to a DHCP discover with SECS value of 0.
  While annoying (and probably inefficient), this may be a typical behavior in certain networking environments.
  There being nothing a customer can do to get the ISP to modify their practices (or even get a ticket escalated to someone who actually understands the issue), this is "not good".
• The RAX30 does not increase the SECS value on subsequent DHCP requests.  Thus, it will never trigger the ISP to respond.
  While one would hope that escalating this issue through Netgear support might (eventually) result in updated firmware that functions correctly, there is no guarantee that the problem will ever reach "someone who cares and can DO something".

THANK YOU for investing the time and effort to document this.  It seems to me that

• There is little incentive to keep the RAX30. (a) the ISP not likely to change their practice to enable it to connect. (b) there is no way to predict if Netgear will recognize the problem and fix it or how long that might take.
• You have hit a DEAD END.
• There might be some value in publicizing this issue so that others to not make the same mistake.  i.e.
  o Post on the ISP user forum "Do not attempt to connect a Netgear RAX30 because it will not work"
  o When returning the RAX30 for a refund, explain, "it would NOT WORK with ISP xxxx"
  o etc. etc.