FNG,
The Comm Effect Model is unrelated to the RF Pipe Model. The latter is
a radio model, the former is a network effects model designed to be an
open source replacement for some of the more pricier commercial network
emulators.
If you are only interested in effects such as bitrate, latency, loss,
jitter and duplication use Comm Effect. If you are interested in RF
domain issues: propagation models, interference, antenna profiles, etc
use a radio model.
You can achieve the desired effect settings by using a filter, but if
you want dynamic control you should use Comm Effect events. See the
user manual for information on Comm Effect event generation.
Attached is sample XML configuration. Please note that I am using the
latest version of EMANE.
--
Steven Galgano
www.adjacentlink.com
On 07/31/2013 10:34 AM, EMANE Newbie wrote:
> Hi,
>
> I included the 9 XML files for completeness, but in hindsight, perhaps
> that was too much information. I am mostly interested in rfpipephy.xml
> and commeffectfilters.xml.
>
> rfpipephy.xml
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE phy SYSTEM "/usr/share/emane/dtd/phy.dtd">
> <phy name="RF-PIPE PHY" library="rfpipephylayer">
> <param name="txpower" value="23"/>
> <param name="antennagain" value="0"/>
> <param name="bitrate" value="0"/>
> <param name="jitter" value="0"/>
> <param name="frequency" value="2400"/>
> <param name="bandwidth" value="0"/>
> <param name="propagationdelay" value="0"/>
> <param name="pathlosssource" value="0"/>
> <param name="pathlossalgorithm" value="0"/>
> <param name="defaultconnectivity" value="on"/>
> <param name="minpathlossthreshold" value="95"/>
> <param name="maxpathlossthreshold" value="195"/>
> </phy>
>
> commeffectfilters.xml
>
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE commeffect SYSTEM
> "file:///usr/share/emanecommeffect/dtd/commeffectfilters.dtd">
> <commeffect>
> <filter>
> <description>All Traffic</description>
> <target/>
> <effect>
> <loss>2</loss>
> <latency sec='0' usec='750000'/>
> <unicastbitrate>256000</unicastbitrate>
> </effect>
> </filter>
> </commeffect>
>
> The usec value is a microsecond value? So I expected to see a ping
> latency of ~750 milliseconds, but I don't see it. Thanks for your
> assistance.
>
> V/R,
>
> FNG
>
> ------------------------------------------------------------------------
> From: [email protected]
> To: [email protected]
> Date: Tue, 30 Jul 2013 15:29:59 -0700
> Subject: [emane-users] configuring latency
>
> Hi,
>
> FNG here again. Trying to configure latency.
>
> OS: Fedora 12 32bit
>
> EMANE: v6.3 installed using EMANE RPM packages provided on the website.
> Configured as a centralized server with 4 NEM.
>
> HARDWARE: Physical server, Dell 2850 with 4 network cards (NIC).
>
> SWITCHES: 4 switches.
>
> SUBNETS: 4 subnets, 192.168.0, 192.168.10, 192.168.20, 192.168.30.
>
> OTHER: Each switch has a single NIC connected from the EMANE server and
> an additional Linux server connected by a single NIC which is a test
> server just running nothing much. The additional servers can't connect
> to each other except by using EMANE as a gateway server. The EMANE
> server is acting as a gateway server between the 4 networks.
>
> GOAL: I would like to add latency to all of the network interfaces on
> the EMANE server so the ping responses show latency between the
> networks. Getting all network traffic to show latency is the ultimate goal.
>
> I am not having any luck with my configuration and could use your help.
> I am attaching what I believe to be the correct configuration files to
> achieve the latency I desire.
>
> There are 9 XML file attachments to this email. If they don't come
> through, I will resend the email with the XML inline.
>
> 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
>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE nem SYSTEM "file:///usr/share/emane/dtd/nem.dtd">
<nem name="COMMEFFECT NEM" type="unstructured">
<shim definition="commeffectshim.xml"/>
<transport definition="transraw.xml"/>
</nem>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE shim SYSTEM "file:///usr/share/emane/dtd/shim.dtd">
<shim name="COMMEFFECT SHIM" library="commeffectshim">
<param name="defaultconnectivity" value="off" />
<param name="enablepromiscuousmode" value="off" />
</shim>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE platform SYSTEM "file:///usr/share/emane/dtd/platform.dtd">
<platform name="Platform 1" id="1">
<param name="otamanagerchannelenable" value="off"/>
<param name="eventservicegroup" value="224.1.2.8:45703"/>
<param name="eventservicedevice" value="lo"/>
<nem name="NEM-1" id="1" definition="commeffectnem.xml">
<param name="platformendpoint" value="localhost:8201"/>
<param name="transportendpoint" value="localhost:8301"/>
<transport definition="transraw.xml" group="single">
<param name="device" value="eth1"/>
</transport>
</nem>
<nem name="NEM-2" id="2" definition="commeffectnem.xml">
<param name="platformendpoint" value="localhost:8202"/>
<param name="transportendpoint" value="localhost:8302"/>
<transport definition="transraw.xml" group="single">
<param name="device" value="eth2"/>
</transport>
</nem>
<nem name="NEM-3" id="3" definition="commeffectnem.xml">
<param name="platformendpoint" value="localhost:8203"/>
<param name="transportendpoint" value="localhost:8303"/>
<transport definition="transraw.xml" group="single">
<param name="device" value="eth3"/>
</transport>
</nem>
<nem name="NEM-4" id="4" definition="commeffectnem.xml">
<param name="platformendpoint" value="localhost:8204"/>
<param name="transportendpoint" value="localhost:8304"/>
<transport definition="transraw.xml" group="single">
<param name="device" value="eth4"/>
</transport>
</nem>
</platform>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE transportdaemon SYSTEM "file:///usr/share/emane/dtd/transportdaemon.dtd">
<transportdaemon>
<instance nemid="1">
<param name="transportendpoint" value="localhost:8301"/>
<param name="platformendpoint" value="localhost:8201"/>
<transport definition="transraw.xml">
<param name="device" value="eth1"/>
</transport>
</instance>
<instance nemid="2">
<param name="transportendpoint" value="localhost:8302"/>
<param name="platformendpoint" value="localhost:8202"/>
<transport definition="transraw.xml">
<param name="device" value="eth2"/>
</transport>
</instance>
<instance nemid="3">
<param name="transportendpoint" value="localhost:8303"/>
<param name="platformendpoint" value="localhost:8203"/>
<transport definition="transraw.xml">
<param name="device" value="eth3"/>
</transport>
</instance>
<instance nemid="4">
<param name="transportendpoint" value="localhost:8304"/>
<param name="platformendpoint" value="localhost:8204"/>
<transport definition="transraw.xml">
<param name="device" value="eth4"/>
</transport>
</instance>
</transportdaemon>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE transport SYSTEM "file:///usr/share/emane/dtd/transport.dtd">
<transport name="Raw transport" library="transraw"/>
_______________________________________________
emane-users mailing list
[email protected]
http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
