That depends on your system configuration. I am not fond of Vagrant. It's a tool we put up for students and new contributors to quickly use OpenWISP. You can use it, but I can't help you much with it.
I don't deploy using vagrant. I deploy using ansible-openwisp2 on VMs hosted on the internet. If I had to deploy on an machine in a LAN, as in your case, I would first make sure the network of the machine is well configured for usage with the rest of the LAN and then deploy on it using ansible-openwisp2. Federico On Thu, Apr 9, 2020 at 1:20 PM Bart Tiemersma <[email protected]> wrote: > My network uses the 192.168.8.* range, while my openwisp controller is > hosted on 192.168.56.5. This host doesn't seem to be reachable, not even by > openwrt. I tried hosting it in the same ip range, but that wasn't allowed > by vagrant. Should this work, or is there something else I can try? > > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/bd342b8f-7be0-4ee7-91e0-06e66f7f2959%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAERYH6U5seBbYYA59a_7At2FOwRVcPpK8cn%3DrReaPfZQZHsg5w%40mail.gmail.com.
