Re: [ns] Error: Segmentation Fault (Core Dumped)
How about using gdb or valgrind to trace the problem? Jongman. 2006/4/30, Tomáš Pataj [EMAIL PROTECTED]: Hi NS users, I tried to make some changes in DiffServ module according to Sergio Anderozzi DiffServ patch. His patch is functional in version NS-2.1b8a. Patch is here: http://www.cnaf.infn.it/~andreozzi/research/network/download.html http://www.cnaf.infn.it/~andreozzi/research/network/diffserv.patch I tried to rebuild his add-ons to version NS-2.29. I make changes and compiling seems to be OK but when I run some examples from Sergio: http://www.cnaf.infn.it/~andreozzi/research/network/example.html Always I will get Error mesage: Segmentation Fault (Core Dumped). Can you help me where is problem or how I can change patch or examples? I would appreciate any help Thank you Tomas Pataj -- = Jongman Heo
Re: [ns] AOMDV code? Where is it?
Use Google~ :) http://www.cs.sunysb.edu/~mahesh/aomdv/ 2006/3/22, Alicia Triviño [EMAIL PROTECTED]: Does anyone know where I can download the code for AOMDV ? Thanks in advance, Alicia Triviño / Tl. +34-95.213.71.91 Dpto. Tecnologia Electronica E.T.S. Ing. Telecomunicacion Universidad de Malaga Campus Universitario de Teatinos 29071 Malaga, Spain -- = Jongman Heo
Re: [ns] error msg in ns
It seems that you did not set the LD_LIBRARY_PATH. 21 Mar 2006 16:43:25 -, ravi kumar [EMAIL PROTECTED]: hi everyone, when i run any tcl scripts,it show an error message shch as: [EMAIL PROTECTED] test]# ns test-suite-wireless-lan-newnode.tcl ns: error while loading shared libraries: libotcl.so: cannot open shared object file: No such file or directory please help me how can i recover that problem. Thanks -- = Jongman Heo
[ns] backoff decrement and transmission in 802.11e tkn code
According to section 9.9.1.3 in the IEEE 802.11e standard, one and only one of the following actions is allowed at slot boundaries: - decrement of backoff timer, or - initiate transmission, or - backoff procedure due to internal collision, or - do nothing. So, 1. Backoff counter is resumed one slot time before the AIFS expiration. 2. However, since a single MAC operation per slot is permitted (backoff decrement or packet transmission), when the backoff counter decrements to 0, the station cannot transmit immediately, but has to wait for a further backoff slot if the medium is idle, or a further AIFS expiration if the medium is busy. I think that 802.11e TKN code is a good implementation of IEEE 802.11e. However, it seems that the implementation conforms to the requirement 1, but do not to the requirement 2. Am I correct? ps. The following paper can be a good guide. Giuseppe Bianchi, Understanding 802.11e Contention-Based Prioritization Mechanisms and Their Coexistence with Legacy 802.11 Stations, IEEE Network, 2005
Re: [ns] backoff decrement and transmission in 802.11e tkn code
No. The operation of backoff decrement in 802.11e EDCA is significantly different from 802.11 DCF. In DCF, transmission occurs whenever the backoff counters reach zero. In EDCA, however, transmission occurs on the first slot boundary after the backoff counter has reached zero. STAs wait for a further AIFS expiration if only the medium is busy. As I said, at slot boudaries, decrement of backoff timer and initiation of transmission can not be performed simultaneously. Jongman Heo. 2006/3/15, [EMAIL PROTECTED] [EMAIL PROTECTED]: I have no knowledge about the TKN implementation. However, I don´t agree with the interpretation of item 2. Because, when the backoff counter reach 0, the station can transmit immediately, i.e., in the next slot time. The station doesn´t wait for another AIFS interval. According to section 9.9.1.3 in the IEEE 802.11e standard, one and only one of the following actions is allowed at slot boundaries: - decrement of backoff timer, or - initiate transmission, or - backoff procedure due to internal collision, or - do nothing. So, 1. Backoff counter is resumed one slot time before the AIFS expiration. 2. However, since a single MAC operation per slot is permitted (backoff decrement or packet transmission), when the backoff counter decrements to 0, the station cannot transmit immediately, but has to wait for a further backoff slot if the medium is idle, or a further AIFS expiration if the medium is busy. I think that 802.11e TKN code is a good implementation of IEEE 802.11e. However, it seems that the implementation conforms to the requirement 1, but do not to the requirement 2. Am I correct? ps. The following paper can be a good guide. Giuseppe Bianchi, Understanding 802.11e Contention-Based Prioritization Mechanisms and Their Coexistence with Legacy 802.11 Stations, IEEE Network, 2005 -- = Jongman Heo
