I also found this thread where another community member points out the bug/limitation.
The interesting thing is that the network stack still works with the larger subnet; at least when using DHCP to assign the mask. In this setup, the hub has no issues communicating with local, remote, or internet systems. The only issue is that it will treat some devices in its local subnet as remote because they are not in the same /24 (255.255.255.0) subnet. The reason for my feature request is to add support for a user selected subnet mask so the hub knows what is in its local security zone.
