Cem, Have you verified that the emane process is still running in your container? Running emane with log level 3, have you checked to see if there are any relevant log messages?
-- Steven Galgano Adjacent Link LLC www.adjacentlink.com On 02/05/2018 09:04 AM, Karan, Cem F CIV USARMY RDECOM ARL (US) wrote: > Thanks for the reply Steven. In that case, I suspect that I'm truly and > seriously confused by what I'm supposed to be doing. I was expecting that > within each LXC container I would see two different interfaces, one for the > EMANE-controlled network (which would provide emulation for the wireless > communications), and one for a control interface that I could always SSH in > to > whenever I needed to check how a particular node was operating. In my tests, > I only see the control node network (as eth1), but I never see emane0. Would > it be possible for me to send you my configuration files to check and see > what > I'm doing? If so, what would be the best way for me to send them to you? > > Thanks, > Cem Karan > > --- > Other than quoted laws, regulations or officially published policies, the > views expressed herein are not intended to be used as an authoritative state > of the law nor do they reflect official positions of the U.S. Army, > Department > of Defense or U.S. Government. > >> -----Original Message----- >> From: Steven Galgano [mailto:[email protected]] >> Sent: Saturday, February 03, 2018 1:46 PM >> To: Karan, Cem F CIV USARMY RDECOM ARL (US) <[email protected]> >> Cc: [email protected] >> Subject: [Non-DoD Source] Re: [emane-users] Help understanding >> 'platformendpoint' and 'transportendpoint' >> >> Cem, >> >> You only need to configure external transports if you are planning on >> running the transports (also referred to as application/emulation >> boundaries) outside of the emulator instances (i.e., externally). >> >> For example, if you are running the emulator configured to use the virtual >> transport (which creates the vif emane0) and you want that vif >> in the same container (or vm or physical system) as the emulator, you don't >> need external transports. If however you want the emulator >> to run in container (or vm or physical system) 'A' and you want the vif >> emane0 to be in a different container (or vm or physical system) 'B', >> you need to tell the emulator to make an external connection between the >> parts of the NEM running in the emulator and the parts >> running externally via an emanetransportd instance. You also need to run >> emanetransportd with the appropriate configuration. >> >> It does not sound like you need to do this. >> >> In either case, you would be using emane0 as the over-the-air interface for >> your routing protocols and/or applications. All packets routed >> over that interface will be processed by the emulator. >> >> -- >> Steven Galgano >> Adjacent Link LLC >> Caution-www.adjacentlink.com >> >> >> >> On 02/02/2018 04:30 PM, Karan, Cem F CIV USARMY RDECOM ARL (US) wrote: >>> Hi all, I'm trying to use EMANE to simulate a small swarm of robotic >>> routers. >>> I think I've figured out just about everything, except for how to use >>> the external transport correctly. I'm building on the tutorials by >>> creating an LXC container for each robot, and having a control >>> application run within the container that communicates over the EMANE >>> network. At least, that's the idea. I know I need to use an external >>> transport so that each container will have an endpoint for my >>> application to connect to, but I'm getting lost when trying to set the >>> 'platformendpoint' and 'transportendpoint' keys on each NEM; I don't >>> know precisely what each is for, so I don't know how to set them. In >>> every example that I can find, each NEM has both keys set. In >>> addition, every NEM's platformendpoint is different from any other >>> NEM's platformendpoint (likewise for the transportendpoints). What are >>> they for, and how do I set them? >>> >>> Thanks, >>> Cem Karan >>> >>> --- >>> Other than quoted laws, regulations or officially published policies, >>> the views expressed herein are not intended to be used as an >>> authoritative state of the law nor do they reflect official positions >>> of the U.S. Army, Department of Defense or U.S. Government. >>> >>> >>> >>> >>> _______________________________________________ >>> emane-users mailing list >>> [email protected] >>> Caution-https://publists.nrl.navy.mil/mailman/listinfo/emane-users >>> > _______________________________________________ emane-users mailing list [email protected] https://publists.nrl.navy.mil/mailman/listinfo/emane-users
