Hi Jared - fast response! Am I right to assume “remote” = spoke and “local” = hub?
Can you discuss this with Ron Case? Ron and I have traded a few e-mails and there are two different variations here:
- Spoke units get an IP from the Hub DHCP pool; this can support spoke LAN initiated traffic to the Hub but not always hub side initiated traffic to unique hosts in the spoke LAN. In some implementations, hub lan to spoke lan is supported via Port Forwarding at the spoke which will work for some applications, but I understood Ron to mean even this was only in development and not available today.
- If you refer to my diagrams, you’ll see hub LAN devices can actually initiate comms to individual devices by IP in the spoke LAN - the key is they have to target virtual IPs that eventually get NATed to the real IPs. This scenarios is more comprehensive than scenario 1 as it allows full hub lan to spoke lan comms with no port forwarding.
Can you talk to Ron, re-review my attachments, and provide feedback as to which of the above scenarios is supported and which are on roadmap? You can PM me or get my full contact info from Ron if its easier to discuss on a call.