I'm working to a project which is about creating a simple 2 router and 2 virtual pc configuration on GNS3. I created it (look for the link of the screenshot below) but now i have to simulate a modbus traffic in this net. Is this possible? How can i do that?
here you have the screenshot of what i've done until now
https://mega.nz/#!GvhD2CbJ!cPIrwTXdE-L_cyqdo2Ac8XkUhEaiUMfeJ0BdHXNsOao
I'm trying to setup an OpenFlow enabled topology using Raspberry Pi3 as switches, and an external POX controller running on my PC. The topology is as follows.
Now the continuous lines are data paths which are basically RJ45 cables.
The dashed lines are the control lines which receive OpenFlow messages from the controller.
My question is how should I connect all the switches to the controller. Is it by
Direct connnection (a network inside a network). In my case, there needs to be 1 LAN cable from each switch to the controller. Total 4 LAN wires to the controller
Use the existing PiSwitch network. 1 extra LAN cable between the controller and any one of the switch.
The problem with (1) is that it's not scalable with increasing number of switches
The problem with (2) is that the network needs some pre-information regarding the controller's location during startup. One switch will become too much loaded in this case.
How is it done in real life when the number of switches is very high?
Suppose I've got SR-IOV passthrough enabled on the host with 2 Virtual Functions, I'm running two QEMU/KVM VM's with libvirt, each connected to a VF respectively, is there any way to see the VF counters on the host (such as rx/tx pkts)?
I've tried to use ethtool -S to see stats but I can only see the global counters of the physical function.
I found an SR-IOV counters plugin for OpenStack Ceilometer but it's a Mellanox plugin and uses a proprietary drivers on the Guest VM's.
Any help would be appreciated.
When you enable VFs on a host, the VFs are initially bound to a host kernel network driver module, so will appear as ethNN letting you query stats. When you then attach the VF to a guest using PCI device assignment the VF is unbound from the host kernel driver, so the ethNNN device goes away in the host. It is thus impossible to query network stats for that VF in the host.
The only way to achieve that is to not use PCI device assignment, and instead associate the VF with the guest using MACVTAP in direct mode. This is not quite as high performance as using PCI assignment, but is still pretty decent due to virtio-net design and lets you see the NIC in the host to monitor traffic.
I start my USB 3G Modem by:
# wvdial
And then I must do, in order to acquire internet access:
# route add default ppp0
Note that ppp0 is the new virtual interface name.
I would like to automate this:
#!/bin/bash
wvdial
route add default ppp0
But sometimes there is some previous ppp connection established (i.e: VPN), so the correct adapter must have another number (it is created as ppp1, ppp2... etc).
How could I guess/specify the name of the newly created ppp interface?
P.S: I am sure that there should be another more practical method to establish such PPP connection. So I opened this other question.
You can force the system to use a specific interface name with option unit.
Just add unit 1 to your pppd-options file (usually /etc/ppp/options).
That works if you always have only one ppp-device.
My issue is nearly identical to this question. I tried those solution and none worked. But I am using a different Android x86 image. I'm using the ICS (4.0-RC1) asus_laptop image. (I tried a different image previously and couldn't get it to install.)
I installed VirtualBox 4.1.12 on Kubuntu 12.04. I followed these steps and installed the android-x86-4.0-RC1-asus_laptop.iso image in my VM. It boots up and works correctly except for networking.
Alt-F1 netcfg shows no interfaces up except the lo (127.0.0.1). eth0, which should be available, is not shown. That prevents me from trying the solution here.
New references I'm checking out:
Android ICS x86 on VirtualBox with Internet Connection
http://groups.google.com/group/android-x86/browse_thread/thread/30fa23d81cddfab1/2e480f6b9cbf773d
How to setup network for Android Honeycomb in VirtualBox?
The following works very good for me
sudo vi /etc/init.sh
add 4 lines below to init.sh
netcfg eth0 dhcp
echo nameserver <ip> > /etc/resolv.conf
dnsmasq
setprop net.dns1 8.8.8.8
on virtualbox set the network interface to bridged (PCnet Fast III) and that's all.
Update: If Android x86 does not work well for you, you might want to look at AndroVM. I run it in VirtualBox and have had no hardware related issues.
Real Answer:
Somewhat of a follow-up answer since I can't add comments yet. I think getting this setup is highly dependent on your host hardware. I am not using hardware that perfectly fits any of the current ISOs. So I tested all of them with all Ethernet settings to see what would work.
On a Dell Latitude D820 here is what I got:
eeepc - Bridged Adapter with PCnet-PCI II
tegav2 - NAT adapter with PCnet-PCI III
amd_brazos - No CPU support
asus_laptop - No eth0 option for any Ethernet adapter setting
s104t - Would not boot
For the two ISOs that would work for me (eeepc and tegav2), I added the following two lines to /etc/init.sh (as per the other answer)
netcfg eth0 dhcp
setprop net.dns1 8.8.8.8
For me the solution of user1330614 worked very well.
Another nice writeup for the problem can be found here:
http://davematthew.blogspot.de/2012/04/android-x86-ics-on-virtualbox.html
try this one
VBoxManage modifyvm "Your Android VB name" --natpf1 adb,tcp,*,5555,*,5555
If you can't edit /etc/init.sh or /etc/init.androVM.sh and the error is the read-only file (despite being su) you can just write the following as superuser on the commandline:
setprop net.dns1 10.0.0.138
or any other IP, this is often the local router (capable of DNS). Check your network connection details for getting this IP.
The drawback is, that you have to do this every time, but it is not very time-consuming.
I had to enable WiFi in the Android settings and select the virtual network created by VirtualBox. In my case it was called "VirtWifi", which is a fake WiFi network using my computer network.
Some sources in the net says you should use the PCnet-Fast III either in bridged mode or NAT in your VBox Machine settings. Just give it a try.
This is a guide i found, but to be sincere, i am new to Android on VBox (and to Android at all) and i didn't test it myself.