I have asked another question here, but have since narrowed down my issue to be using the "host-only" network adapter, versus a bridge network (with DHCP).
I have created two Ubuntu virtuals, and have installed Cassandra (from DataStax) the same way.
The first box is using a host-only adapter...
dev.vm.network :private_network, ip: "192.168.10.200"
And the second is bridged using DHCP...
dev.vm.network :public_network
The box using a "host-only" private network doesn't allow me remote access, even though the Cassandra configuration is the same. The box using a public network has remote access working just fine.
I am using Windows 10, and I am not sure if this was working on Windows 8.
Related
We are building a proof of concept piece that uses ONOS to update the flow tables on an OVS switch to either block or allow traffic connected to the OVS switch. We have got a piece working on a local machine using using virtual machines on virtual box. We're trying to see if we can get it working using virtual machines in Azure. Here's the setup:
I have three Linux virtual machines running in Azure.
One virtual machine has ONOS installed on it. Ley's call this ONOS-1.
The second virtual machine has OVS installed on it. Let's call this OVS-1.
And the third virtual machine is just a standard Linux virtual machine that is being used by a user. Let's call this HOST-1.
The OVS-1 has two network interface cards, one for management access and another used by OVS for bridging. In OVS there are multiple vPorts configured on the single NIC that is on the data network.
The idea is that ONOS-1 is connected to OVS-1, and the OVS-1 is connected to HOST-1via one of the OVS vPorts. ONOS-1 should be able to control OVS-1. Currently, ONOS-1 can see OVS-1, but any vPorts created on OVS-1 show as enabled=False in ONOS-1. What is the problem or what are we missing? Any help, guidance, or direction would be greatly appreciated.
Network diagram
We've tried adding additional NIC for each OVS vPort. This did not work either.
I have 2 PC (with Windows as default OS), let's say PC_master and PC_slave. Since it is recommended to work with Linux to manage a spark Cluster i created one Virtual Machines with Linux on each of theses PC: VM_master on PC_master and VM_slave on PC_slave.
I would like to setup a Standalone Spark Cluster, so which Networking configuration should i use (NAT, Bridge, HostOnly?) for theses 2VM in order that they own their private IP adress letting me ssh from one to another without the need of port forwarding ?
Edit: My two laptop are linked to the same box, so they have private IP and supposed to be linked to the same router.
Finally it seems that if i want to give each VM its own Ip adress to create a private Network i have to choose Bridge Network which will assign a unique Ip for each VM!
I have a Windows7 as host and Debian as guest via VirtualBox. everything worked just fine until I did apt-get update on my guest machine and I think it scrambled some settings (not sure though...).
My current VB network settings are:
Adapter 1: Bridged Adapter
Adapter 2: Host-only adapter
My guest machine works fine, has internet connection and I can access it files via My Computer > Network, yet I cannot ping the guest machine nor access its apache webserver, any ideas?
Glad to hear it dude. :)
1 network adapter usually enough for 'normal' purpose. I use more than 1 network adapter when I want to simulate more complicated computer network plan, like I want to have experiment with proxy, router, dns etc. Just make sure you understand the networking mode that you want to use.
Thanks to #yogipriyo, removed the second adapter and selected only 1 bridged adapter and it works.
I'm trying to access the Cassandra browser terminal but the reported IP is unreachable.
I'm following the instructions to install Cassandra on VirtualBox here, and have the following configuration:
And Cassandra appears to start up appropriately:
But I'm unable to hit the provided IP (10.0.0.2)
Any idea what's wrong?
Ok, so I went to Install Cassandra OVA on VirtualBox and followed the instructions (like you did). And it didn't work for me, either.
What did work, was messing with the network settings and ultimately switching to a "Bridged" network adapter:
This put the CassandraVM on my internal network, and I was then able to reach everything from an internal IP (192.168.0.103, in my case).
Also, not sure if it made a difference, but I set Promiscuous Mode to "Allow All."
Had the same issue. Here's what worked for me (the solution came from this VirtualBox forum post).
In Host-only Network Details select the Adapter tab and change the ipv4 address into something inside the 10.0.0.x range. I think you should avoid conflicts with settings in the DHCP Server tab, thus a suitable choice would be 10.0.0.254, for example.
Also, I think you should configure your virtual machine's network settings this way:
Attach to: select Host-only Adapter
Name: select vboxnet0
I've also set Allow All for Promiscous Mode, but I don't know if it's strictly required.
I am new to embedded linux development.I have inherited a particular way of Embedded linux development from the previous developer.
I was just wondering if there is a more industry standard way of working.
This is how he was working,
There is an ARM embedded linux board which is not on the corporate network and has a fixed IP address of 192.168.0.52.I have a virtualbox based linux host which is connected directly to this linux board via an Ethernet cable.This host has an NFS shared with the target for running the cross compiled binaries.I have to set a fixed IP address for the host of 192.168.0.50.Then I can telnet with the target to run the compiled binaries on the NFS folder. Also as the VM host is not connected to the corporate network.I cannot use the company issued SVN for version control.So what I do is have a shared folder via virtual box between Windows and Linux host and I manually keep transferring the files which I have to commit/test.
What I would I ideally like, is both networks connected to the corporate network,so that I can update the OS,use version control.Is there way by which the VM on Windows access the corporate network and also be connected to the target.IT is not willing to give a static IP to the target.If we connect the target via DHCP what is the best way to discover it on the network.Also IT is concerned about the traffic it will generate.Can I use a switch to create a subnetwork,so that the target can have a fixed address?
Another question is they are open to a linux based host as well.Is a VM based linux any worse off than a Linux PC.The only problem I have been having are networking based issues,not really Virtualbox issues.But I am curious to know if there are any limitations at all.
In order to have the VM connected to the corporate network, you can setup the VM network adapter in bridge mode.
In order to discover the embedded device, you can use the arp command (for instance: arm -i eth0 -a).
If you have got two network interfaces you could also connect the remote device directly through this interface and setup a dhcp server in your VM.
Personally, I think that with the VM you can do everything that you need (cross-compiling the Kernel and bootloader and creating the remote File System). I have been using a VM for embedded linux development on a AT91SAM board without problems at all.