1. Try setting pathloss to 93.9 so your SINR ~ 3.1. This will result in a PCR of ~ 20% assuming your standard ping packet size is about 100Bytes (including ethernet frame). A 20% PCR with 4 retries, results in ~ 67% completion in 1 direction. Taking into account the ping return should give you ~ 45% ping completion. For a simple 2 node ping, you can play with retries, ping packet size and pathloss to get the loss you are looking for. Once you move to complex scenarios (number of nodes, mobility, traffic profiles, etc.), performance is not easy to predict/control as the model is a behavioral implementation of the 802.11 CSMA/CA channel access protocol.
2. For the 80211abg model, In-Band interference/collision comes into effect by determining channel congestion based on measuring the amount of traffic on the channel and estimating the number of nodes contributing to that congestion. If you just want to introduce noise on the channel, you can have another node configured to use RF-Pipe on the same frequency as your 802.11 network and then have that node blast traffic to raise the noise floor. We still don't know what your emulation objectives are but it doesn't look like you are interested in 802.11 emulation. As such, you might be better off using another model such as RF-Pipe or Comm Effect. Those are much simpler to understand and provides you more precise control on network impairments you want to apply. kb Kaushik B. Patel Adjacent Link LLC On 12/11/2015 08:14 PM, Anders Nilsson Plymoth wrote: > Hi Soroush, > > What *do* you see when you ping? 802.11 uses retransmissions so 54% should > still allow packets through in most cases. What does the stats say about > drop frames? > > Thanks, > Anders > > On Sat, Dec 12, 2015 at 1:44 AM, [REDACTED] <[email protected]> > wrote: > >> Thanks for your respond >> I'm using index 4 which is for 11Mbps and I set pathloss 93 so then: >> >> -97 = -174 + 4dB + 10log(20M) >> SINR = -93-(-97) >> SINR=4 >> and according to curve I have POR45.8 that means 54.2 losses, but I don't >> see that when ping node-b from node-a . >> Also, I've added some interference but it doesn't affect . >> Am i missing some thing ? >> I've include my configuration file. >> >> Thanks, >> >> <!-- 11Mpbs --> >> <datarate index="4"> >> <row sinr="1.0" por="0.0"/> >> <row sinr="2.0" por="0.2"/> >> <row sinr="3.0" por="8.9"/> >> <row sinr="4.0" por="45.8"/> >> <row sinr="5.0" por="82.5"/> >> <row sinr="6.0" por="96.7"/> >> <row sinr="7.0" por="99.6"/> >> <row sinr="8.0" por="100.0"/> >> </datarate> >> >> >> >> >> <?xml version="1.0" encoding="UTF-8"?> >> <!DOCTYPE platform SYSTEM "file:///usr/share/emane/dtd/platform.dtd"> >> <platform> >> <param name="otamanagerchannelenable" value="off"/> >> <param name="eventservicegroup" value="224.1.2.8:45703"/> >> <param name="eventservicedevice" value="lo"/> >> <param name="controlportendpoint" value="0.0.0.0:47000"/> >> >> >> <nem id="1" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8201"/> >> <param name="transportendpoint" value="10.99.0.1:8301"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.1"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="2" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8202"/> >> <param name="transportendpoint" value="10.99.0.2:8302"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.2"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="3" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8203"/> >> <param name="transportendpoint" value="10.99.0.3:8303"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.3"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="4" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8204"/> >> <param name="transportendpoint" value="10.99.0.4:8304"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.4"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="5" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8205"/> >> <param name="transportendpoint" value="10.99.0.5:8305"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.5"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="6" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8206"/> >> <param name="transportendpoint" value="10.99.0.6:8306"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.6"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="7" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8207"/> >> <param name="transportendpoint" value="10.99.0.7:8307"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.7"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="8" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8208"/> >> <param name="transportendpoint" value="10.99.0.8:8308"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.8"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="9" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8209"/> >> <param name="transportendpoint" value="10.99.0.9:8309"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.9"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="10" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8210"/> >> <param name="transportendpoint" value="10.99.0.10:8310"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.10"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> <nem id="11" definition="srw.xml" transport="external"> >> <param name="platformendpoint" value="10.99.0.100:8211"/> >> <param name="transportendpoint" value="10.99.0.11:8311"/> >> <transport definition="transvirtual.xml"> >> <param name="address" value="10.100.0.11"/> >> <param name="mask" value="255.255.255.0"/> >> </transport> >> <phy> >> <param name="frequencyofinterest" value="1.755G"/> >> <param name="frequency" value="1.755G"/> >> </phy> >> </nem> >> >> </platform> >> >> On Fri, Dec 11, 2015 at 2:42 PM, Kaushik B. Patel <[email protected] >>> wrote: >> >>> Not sure what you are trying to do. If all you want to do is see 50% >>> packet loss, use a higher data rate (i.e 11Mbps). If you have to use >>> 1Mbps, replace the 1Mbps PCR curve with positive SINR values. >>> >>> kb >>> >>> Kaushik B. Patel >>> Adjacent Link LLC >>> >>> >>> On 12/11/2015 04:59 PM, [REDACTED] wrote: >>>> Thanks for your respond. >>>> I thought by default EMANE consider some level of noise . >>>> is there any way to consider noise while only one communication between >>> two >>>> nodes is going on and there isnt any interference (considering some >>> level >>>> of noise) ? >>>> I want to see for instance 50% drop packet while ping from node-a to >>> node-b >>>> without any other ongoing communication that cause interference. >>>> >>>> >>>> Thanks >>>> >>>> On Fri, Dec 11, 2015 at 1:42 PM, Kaushik B. Patel < >>> [email protected]> >>>> wrote: >>>> >>>>> Soroush, your RxPower (-103) is below RxSensitivity (-97) so the >>> packets >>>>> are getting dropped within the PHY and not making it up to the 80211abg >>>>> radio model. The negative SINR comes into play within the radio model >>>>> when there is noise and/or interference on the channel. The receive >>>>> power must always be higher than the receiver sensitivity to make it >>>>> past the PHY. >>>>> >>>>> kb >>>>> >>>>> Kaushik B. Patel >>>>> Adjacent Link LLC >>>>> >>>>> >>>>> On 12/11/2015 03:57 PM, [REDACTED] wrote: >>>>>> ok tnx. but why I'm not seeing any drop while configuring EMANE for >>>>>> different pathloss . >>>>>> for instance this is my ieee802.11.xml and ieee802.11 NEM files which >>>>> I've >>>>>> configure . here index data rate is one and I suppose to drop %50 of >>>>> packet >>>>>> roughly base on the PCR curve when assign pathloss of 103 . >>>>>> based on my calculation : >>>>>> >>>>>> -97 = -174 + 4dB + 10log(20M) >>>>>> SINR = -103-(-97) >>>>>> SINR=-6 >>>>>> but when I ping from node A to node B , I'm losing connection between >>>>>> node-a radio and node-b radio , I mean they're not reachable. >>>>>> actually, I'm losing connection between nodes emane0 interface if I >>> set >>>>>> pathloss greater than 96 . >>>>>> Am I doing anything wrong ? >>>>>> >>>>>> Thanks >>>>>> >>>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>>> <!DOCTYPE mac SYSTEM "file:///usr/share/emane/dtd/mac.dtd"> >>>>>> <mac library="ieee80211abgmaclayer"> >>>>>> <param name="mode" value="2"/> >>>>>> <param name="enablepromiscuousmode" value="off"/> >>>>>> <param name="distance" value="1000"/> >>>>>> <param name="unicastrate" value="1"/> >>>>>> <param name="multicastrate" value="1"/> >>>>>> <param name="pcrcurveuri" >>>>>> >>>>>> >>>>> >>> value="file:///usr/share/emane/xml/models/mac/ieee80211abg/ieee80211pcr.xml"/> >>>>>> <param name="flowcontrolenable" value="off"/> >>>>>> <param name="flowcontroltokens" value="10"/> >>>>>> <param name="radiometricenable" value="off"/> >>>>>> <param name="retrylimit0" value="4"/> >>>>>> <param name="retrylimit1" value="4"/> >>>>>> <param name="retrylimit2" value="4"/> >>>>>> <param name="retrylimit3" value="4"/> >>>>>> </mac> >>>>>> >>>>>> >>>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>>> <!DOCTYPE nem SYSTEM "file:///usr/share/emane/dtd/nem.dtd"> >>>>>> <nem name="IEEE 802.11 NEM"> >>>>>> <transport definition="transvirtual.xml"/> >>>>>> <mac definition="ieee80211abgmac.xml"/> >>>>>> <phy> >>>>>> <param name="fixedantennagain" value="0.0"/> >>>>>> <param name="fixedantennagainenable" value="on"/> >>>>>> <param name="bandwidth" value="20M"/> >>>>>> <param name="noisemode" value="outofband"/> >>>>>> <param name="propagationmodel" value="precomputed"/> >>>>>> <param name="systemnoisefigure" value="4.0"/> >>>>>> <param name="txpower" value="0.0"/> >>>>>> <param name="subid" value="1"/> >>>>>> </phy> >>>>>> </nem> >>>>>> >>>>>> >>>>>> <!-- 1Mpbs --> >>>>>> <datarate index="1"> >>>>>> <row sinr="-9.0" por="0.0"/> >>>>>> <row sinr="-8.0" por="1.4"/> >>>>>> <row sinr="-7.0" por="21.0"/> >>>>>> <row sinr="-6.0" por="63.5"/> >>>>>> <row sinr="-5.0" por="90.7"/> >>>>>> <row sinr="-4.0" por="98.6"/> >>>>>> <row sinr="-3.0" por="99.9"/> >>>>>> <row sinr="-2.0" por="100.0"/> >>>>>> </datarate> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Dec 11, 2015 at 12:33 PM, Steven Galgano < >>>>> [email protected]> >>>>>> wrote: >>>>>> >>>>>>> Soroush, >>>>>>> >>>>>>> Please stay on list for this thread. >>>>>>> >>>>>>> That issue has been resolved for two years. Unless you are using a >>>>>>> version of emane prior to 0.9, you are fine. >>>>>>> >>>>>>> -- >>>>>>> Steven Galgano >>>>>>> Adjacent Link LLC >>>>>>> www.adjacentlink.com >>>>>>> >>>>>>> >>>>>>> On 12/11/2015 02:57 PM, [REDACTED] wrote: >>>>>>>> Hi Steven, >>>>>>>> >>>>>>>> here is the link >>>>>>>> >>>>>>> >>>>> >>> https://www.mail-archive.com/[email protected]&q=subject:%22Re%5C%3A+%5C%5Bemane%5C-users%5C%5D+%5C%5Bcore%5C-users%5C%5D+which+pathloss+with+freespace+and%092ray+models%5C%3F%22&o=newest&f=1 >>>>>>>> >>>>>>>> Thanks in advance for your respond . >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Dec 11, 2015 at 11:46 AM, Steven Galgano >>>>>>>> <[email protected] <mailto:[email protected]>> >>> wrote: >>>>>>>> >>>>>>>> Soroush, >>>>>>>> >>>>>>>> To what issue are you referring? >>>>>>>> >>>>>>>> -- >>>>>>>> Steven Galgano >>>>>>>> Adjacent Link LLC >>>>>>>> www.adjacentlink.com <http://www.adjacentlink.com> >>>>>>>> >>>>>>>> >>>>>>>> On 12/11/2015 02:36 PM, [REDACTED] wrote: >>>>>>>> > Hello, >>>>>>>> > >>>>>>>> > I wonder , where may I get patch that resolve issue related to >>>>>>>> pathloss >>>>>>>> > for ieee80211pcr? >>>>>>>> > >>>>>>>> > >>>>>>>> > Thanks, >>>>>>>> > Soroush >>>>>>>> > >>>>>>>> > >>>>>>>> > _______________________________________________ >>>>>>>> > emane-users mailing list >>>>>>>> > [email protected] >>>>>>>> <mailto:[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 >>>>>> >>>>> >>>> >>> >> >> >> _______________________________________________ >> 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
