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
