VirtualBox with Networking
Martin Stein
martin.stein at ...1...
Mon Sep 25 13:57:11 CEST 2017
Hi Chris,
If you intercept the NIC connections between your bridge and the vbox's with the NIC dump
component, you can compare the packets for your two usecases.
A good example of how to use the nic_dump can be found in libports/run/nic_dump.run.
There it intercepts the NIC connection between the bridge (server/uplink) and the router
(client/downlink). Of cause you can put also only one nic_dump between nic_drv and
nic_bridge.
I hope this helped?
Martin
Am 24.09.2017 um 19:16 schrieb Chris Rothrock:
> I have been able to make a working environment with Genode/NOVA/VirtualBox a single VM running TinyCore with networking enabled and can communicate across the network. So far, only on VirtualBox 4, 5 still has issues that I am still trying to work out that I will get into at a later time but my goal is multiple VMs with networking.
>
> With VirtualBox 4, I have successfully made two VM environments and both VMs see eth0, I can assign an IP address to each but neither VM can communicate outside their own VM. Unlike with the single VM, I was unsuccessful to get an IP via DHCP (hence why I used a static IP), they could not ping the other VM, they could not ping anything on the network to which they were attached. Is there a setting in the test.vbox file different than for a single VM mode that I need to make to make the bridge work for this?
>
> --
>
>
> Thank You,
>
> Chris Rothrock
> Senior System Administrator
> (315) 308-1637
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> genode-main mailing list
> genode-main at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>
More information about the users
mailing list