The fact of the matter is many consumer routers with a built in DHCP service automatically create a 10.0.0.0 address for the private network so that is what many folks end up using anyway. …and that is a Class A network by default. Lots of folks have more than 255 hosts on their home networks given all the “intelligent” crap we buy so more and more routers are now just issuing 10 dot addresses. Less and less people are running Class C networks anymore…
Yes, I know lots of ways around this (like sticking a $50 router onto the side of the laser to create a private class C network under my primary network just for it alone). But the proper solution is for Ruida to fix their code to allow us to specify the mask we want to use. That is the way it should have been done in the first place and it should be a fairly simple fix.
…and yes, I have programmed FPGA hardware, using both Verilog and VHDL.
Anyway, despite all the axes everyone seems to have to grind, it appears Ruida has not updated their firmware so I’ll take my leave at this point.
This was simply a follow up on another thread (1-1/2 years ago) where it was said that Ruida recognized the issue and would be fixing it at some point: https://forum.lightburnsoftware.com/t/how-do-i-connect-a-ruida-controller-with-ethernet-cont/90889/7?u=evanevery
So I guess I got my answer: NO
Thanks