I want to simulate LEACH protocol in wsn, I use inet 3.2.4 and omnet++ 4.6 both working fine. I execute tutorials with inet. I use StandrdHost module to build my wsn,how a node is declared as a cluster head and other surrounding nodes know it, and how packet is forwarded through a specific nodes, i.e. where i should write my routing protocol and then configure in the network.
Related
I have created a bridge( br-physnet1) on 2 interfaces( eno2 and eno3) using packstack answer file and created vlan interfaces on that. What I see is when both ports are up on host, ping from VM to GW doesnt work and it works when one of the interface is up. So I created a bond and added both interface on them and ping worked in all cases.
Now my issue is bond is created using ovs and we want to deliver everything using heat template. I am not finding any bonding support in openstack heat ( whatever doc I saw were redhat director). Is there a way I can create ovs bond using heat template ?
I am quite new to DDS. I am using ROS2 which is built on DDS. I want to run a ROS2 based publisher and subscribe to a RTI Connext based Simulink model both located on different PC's.
I want communication between 2 different PC's.
Questions :
Should both PC's be located in the same network.
Should multicasting be enabled ? Multicasting is blocked in my company's network. Is there an alternative to this ?
Yes, both PC must be under the same network.
Multicasting is used for the discovery of the nodes in ROS2.
If your company does not provide the necessary networking support, you can always try to build your own. For example you can use a switch and connect both PC to it.
Or you can use your phone. I created a hotspot with my phone with 4 devices connected to it and communicating using ROS2.
However, if you need to have access to the company network, ask your IT department if they can set you up with a switch connected to the network that has multicast :)
Edit: As specified in another answer, it is possible to do a static discovery. However, this would imply modifying the ROS2 configuration of the RTI Connext RMW> https://github.com/ros2/rmw_connext
If the computers are on the same network, and multicast is enabled, and the multicast TTL is high enough, and the computers are publishing/subscribing on the same topic on the same domain, and their Types and QoS are compatible, then they should automatically discover each other.
If multicast is disabled, you can tell the DDS participant to use a specific address to peer to (see the docs for "initial peers"). This can be done in different ways. Here's a good reference: Initial Peers
I wanted to setup a 3-node ring network, each connects to the other 2 using 2 Ethernet ports directly without a switch/router.
The interface configurations looks like this:
I've used ifconfig on each node to configure each port, and made sure I can ssh from each node to the other 2 nodes.
But a simple ring_c example doesn't work... So I turn on --mca btl_base_verbose 30, I could see that node1 was trying to use 23.0.0.2 (linke between node2 and 3) to get to node2 though there is a direct link to node 2.
The output log is like:
[node1:01828] btl: tcp: attempting to connect() to [[19529,1],1]
address 23.0.0.2 on port 1024
[[19529,1],0][btl_tcp_endpoint.c:606:mca_btl_tcp_endpoint_start_connect]
from node1 to: node2 Unable to connect to the peer 23.0.0.2 on port
4: Network is unreachable
I've read the following posts and FAQs but still couldn't understand this kind of behavior.
How does Open MPI know which IP addresses are routable to each other in Open MPI 1.3 (and beyond)?
How do I tell Open MPI which IP interfaces / networks to use?
Open MPI User's Mailing List Archives
Any pointers would be appreciated! Thanks in advance!
My open-mpi info:
Open MPI: 1.0.0.22
Open RTE: 1.0.0.22
OPAL: 1.0.0.22
MPI API: 2.1
Best,
Shang
I have xmobar running in xmonad displaying network traffic summary via the dynnetwork monitor. It works fine with eth0 and wlan0, as wired and wireless network are identified on this machine, but the usb0 interface is not picked up when in use. bmon sees and reports traffic on usb0. Is there some way to have dynnetwork pick up usb0 traffic when it is in use or is it just not designed to do so?
Thanks to the author for identifying the problem. The usb0 interface was being raised after xmobar was run and the Net plugin only identifies active interfaces at initial runtime. By raising the usb0 interface before xmobar (or restarting xmabar after the interface is raised) it will be detected and reported normally. Hopefully a fix on the way.
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.