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?
Hello,
On 24.09.2017 19:16, Chris Rothrock wrote:
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
just a guess:
If you using the nic_bridge, make sure that the MAC addresses generated by and assigned by the nic_bridge to the VMs (repos/os/src/server/nic_bridge/README) actually are not ignored/are permitted by your DHCP server.
In the single VM use-case (running without the nic_bridge), the MAC address of the network card is assigned to your VM, which is probably permitted/white-listed by your DHCP server in your network, I guess.
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?
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Alexander,
As a second part to thatm I took the DHCP part completely out of the equation and set a static IP on both VMs and I was unable to ping between the two VMs thereby taking the outside network completely out of the picture. In this case, the ping should have gone from one VM to the NIC bridge then back to the second VM but that didn't occur either. I will also try Martin's suggestion with the NIC dump but there is certainly something not routing properly with the bridge.
Chris
On Mon, Sep 25, 2017 at 7:48 AM, Alexander Boettcher < alexander.boettcher@...1...> wrote:
Hello,
On 24.09.2017 19:16, Chris Rothrock wrote:
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
just a guess:
If you using the nic_bridge, make sure that the MAC addresses generated by and assigned by the nic_bridge to the VMs (repos/os/src/server/nic_bridge/README) actually are not ignored/are permitted by your DHCP server.
In the single VM use-case (running without the nic_bridge), the MAC address of the network card is assigned to your VM, which is probably permitted/white-listed by your DHCP server in your network, I guess.
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?
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
-- Alexander Boettcher Genode Labs
http://www.genode-labs.com - http://www.genode.org
Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Chris,
please have a look at [0]. There are already some information about Virtualbox and nic_router and nic_bridge. Static IP addresses seem to not work with nic_bridge and VBox.
[0] https://github.com/genodelabs/genode/issues/2373
Alex.
On 25.09.2017 14:09, Chris Rothrock wrote:
Alexander,
As a second part to thatm I took the DHCP part completely out of the equation and set a static IP on both VMs and I was unable to ping between the two VMs thereby taking the outside network completely out of the picture. In this case, the ping should have gone from one VM to the NIC bridge then back to the second VM but that didn't occur either. I will also try Martin's suggestion with the NIC dump but there is certainly something not routing properly with the bridge.
Chris
On Mon, Sep 25, 2017 at 7:48 AM, Alexander Boettcher < alexander.boettcher@...1...> wrote:
Hello,
On 24.09.2017 19:16, Chris Rothrock wrote:
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
just a guess:
If you using the nic_bridge, make sure that the MAC addresses generated by and assigned by the nic_bridge to the VMs (repos/os/src/server/nic_bridge/README) actually are not ignored/are permitted by your DHCP server.
In the single VM use-case (running without the nic_bridge), the MAC address of the network card is assigned to your VM, which is probably permitted/white-listed by your DHCP server in your network, I guess.
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?
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
-- Alexander Boettcher Genode Labs
http://www.genode-labs.com - http://www.genode.org
Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Chris,
I would stay debugging the DHCP problem instead of switching to static IPs. I assume that there is no problem with the bridge or the VMs. Maybe you can send the NIC dump output so we can see more clearly what is going on. If you use my branch merge_to_staging [1], you can also configure the output by adding something like:
log_cfg.dhcp = Packet_log_config::COMPREHENSIVE; /* print all header information */ log_cfg.udp = Packet_log_config::COMPACT; /* print most important information only */ log_cfg.ipv4 = Packet_log_config::SHORT; /* print protocol name only */ log_cfg.eth = Packet_log_config::NONE; /* print nothing for this protocol */
after this line in Interface::_handle_eth [2]:
Packet_log_config log_cfg;
Cheers, Martin
[1] https://github.com/m-stein/genode/tree/merge_to_staging [2] https://github.com/m-stein/genode/blob/merge_to_staging/repos/os/src/server/...
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
-
Alexander Boettcher -
Chris Rothrock -
Martin Stein