[ns] Why caculationof distCST_ changed in wirelessPhyExt (ns2.34)

Hi, I am still confused on the carrier sense threshold. 1. CS_thresh CS_thresh is too large by default value (6.31e-12, 802.11a), the corresponding range is 168.3m , which equals to transmission range. 2. distCST_ is the carrier sensing range , but it is caculated according to

[ns] CS_thresh in wireless-PhyExt of ns2.34 ( carrier sense threshhold)

Hello everyone, I find the default *CS_Thresh* is too large in wireless-PhyExt of ns2.34. For example, the powerlevel() is 1.31 e-12, received signal power Pr is 1.06 e -12, hence SINR.ratio = Pr/(powerlevel -Pr) = 4.2, SINR.ratio SINR_thresh （3.7）, so the signal can be decoded, but

[ns] CSThresh_ in ns2.34 (wireless-phyExt.cc )

-- Forwarded message -- From: vitacai shun vitacais...@gmail.com Date: 2010/11/30 Subject: CSThresh_ in ns2.34 (wireless-phyExt.cc ) To: ns-users@isi.edu Hi, I want to tune the carrier sense range to be close to transmission range , but finding that it has no effect

[ns] Little question about SIFS_Waiting state in 802.11Etx in ns2.34

Hi, all I encountered a little question about SIFS_Waiting state in802.11 DCF , while attemting to learn and extending the 802.11Ext implementation for NS2.34. When a node(A) receives a RTS frame, it will responds an CTS_1 after aSIFStime if these no NAV, which means

[ns] ExOR model for ns2

Hi All， Does any one can offer an ExOR(an Opportnistic routing protocol ) patch for ns2? Any advice would be appreciated. Sincerely， Kara