NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
efc
Jul 27, 2021Aspirant
Attached Devices Javascript Error
I am running firmware V1.0.2.82 and still getting the empty attached devices problem. Today I did a bit of Javascript debugging and learned that the router is chocking on the returned result of its o...
schumaku
Jul 28, 2021Guru - Experienced User
The story is almost as old as the many attempts to derive Attached Devices lists and the like from the DHCP/BOOTP client provied host name.
Root cause: RFC ignorants! When walking the RFC trees for DHCP, BOOTP et all, one does come to RFC 1035, where it says:
The labels must follow the rules for ARPANET host names. They must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphen. There are also some restrictions on the length. Labels must be 63 characters or less.
My Google Pixel phone (Device Name) is named "Pixel 4a (5G)". It's dhcpd does provide the host name as part of the request as "pixel-4a-5g". When I find device like "Cath's iPhone 12" in the same context, you might understand what I'm thinking about that other Californian company.... And then, for some reson my defintion for small devices with Internet access are IoJ.
Second line of defense:
Already the router DHCP server should normalize and validate data provided - before it's stored in some internal table. Otherwise some bad guys might come and inject some 63 (or even more?) chars with JavaScript, or whatever interesting ideas. This table can be read then to generate the JSON ... and magic, it would just work, always.
So of course, I'm fully with you efc .
Regards,
-Kurt