@Tim2 thanks for the feedback, we certainly can understand the cost sensitivities involved for many WISPs, this is to a large degree why we’ve given ISPs the choice for a lower cost router+PoE or a simple PoE. I realize this may make more sense for ISPs buying more in scale and picking preferred accessories.
Regarding the concerns you raise about routing, hopefully you’ll have noticed that in the 2.0.2 release we’ve introduced all functions within the A5 to prevent network outages from improperly connected home routers (rogue DHCP server, broadcast traffic flood prevention, etc.). So it should not be required to have a router at the A5 location, and of course other neighboring C5 clients on the same A5 are isolated from each other as well. This was also done to make it easy to leverage an existing router for cost reasons, and over time we’ll add capabilities to auto-provision the right IP addresses as I think you noticed in the Option 82 feature.
For IP addresses on the C5, most use a private management VLAN. In actuality, the A5 in the background also does contact the C5 autonomously if IP addresses are not setup to monitor health, and displays each C5 basic within the A5 user interface as normal, although it is not possible to use the Web UI function to access the C5 the UI in this fashion currently, so it’s mainly for aggregate monitoring.
Hope this helps, let me know if I can answer any more concerns/questions.