> On 31 Mar 2019, at 19:56, roberto battistoni <[email protected]> wrote: > > Sorry but the DHCP offers the IP both in the NAT and BRIDGE configuration. I > think that the "forward" does not work in the bridge configuration.
Why would it be forwarding in ‘bridge’ mode? I think you’re slightly confused. In bridge mode, you wouldn’t use a port forward as you could talk directly to the device. Perhaps you can look at how QEMU is actually invoked but the two different options? > For example: > > capstan run -n "nat" -f "8000:8000" -e "--verbose /cli/cli.so" uni ==> THIS > WORKS and "curl http://localhost:8000/os/version"; returns correctly the > version "0.53" I’m not sure what capstan does, but I think for NAT it installs a port forward to the QEMU options. Thus port 8000 on localhost is forwarded to OSv port 8000. > capstan run -n "bridge" -f "8000:8000" -e "--verbose /cli/cli.so" uni ==> > THIS DOES NOT WORK and "curl http://localhost:8000/os/version"; returns "(7) > Failed to connect to localhost port 8000: Connection refused" I believe in bridge mode it does not - you should be using http://<ip-address-of-OSv>:8000/ (which I think was 192.168.122.168 in your example). Rick -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
