FNG, Latency is not something that is handled by a transport. Transports are tasked with bridging the boundary between emulation and non-emulation space - forwarding traffic in-to and out-of an NEM.
The virtual transport is used to create a virtual interface using tuntap. By default, the interface is called emane0 and all traffic routed to that interface will be forwarded to its respective NEM for processing. Conversely, all packets determined by an NEM to have been received will be sent to the transport and delivered by the kernel to applications listening on emane0. The raw transport takes ownership of an existing interface and uses libpcap to forward traffic into the emulator (emane) and write received traffic back out the interface. The virtual transport uses special MAC address assignments to map MAC address to NEM address and vice versa. The raw transport can be configured to discover NEM to MAC address relationships by peeking into ARP messages or it can be configured to simply treat all packets as NEM broadcast. The latter does not negatively affect the emulation since packets written to the wrong interface get dropped by receive side kernel processing. Consult the RF Pipe MAC documentation for information on how to added latency. -- Steven Galgano Adjacent Link LLC www.adjacentlink.com On 07/18/2013 11:05 AM, EMANE Newbie wrote: > Greetings, > > I would like to induce latency and packet loss on our test network. I am > struggling to understand the virtues of transvirtual.xml versus > transraw.xml. I am using EMANE v6.3 and read the respective PDF files on > each, but I don't know when it's best to use one approach versus the > other. Thanks for your time and support. > > V/R, > > FNG > > > _______________________________________________ > emane-users mailing list > [email protected] > http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users > _______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
