NSOC2011ClickMac - Revision history

Vedranm: Remove manual links and replace them with wiki links

2013-02-10T17:00:35Z

Remove manual links and replace them with wiki links

← Older revision		Revision as of 17:00, 10 February 2013
Line 5:		Line 5:
	* Abstract: This project deals with the MAC extensions for ns-3 click. The current integration of the Click Modular Router with ns-3 is confined to only ns-3’s network device types and doesn’t yet permit the use of Click’s Wifi MAC specific elements. This project aims to enable the same, provide RadiotapHeader support for ns-3's Wifi model and a Monitor Wifi Mac interface to support a Monitor Mode within ns-3.		* Abstract: This project deals with the MAC extensions for ns-3 click. The current integration of the Click Modular Router with ns-3 is confined to only ns-3’s network device types and doesn’t yet permit the use of Click’s Wifi MAC specific elements. This project aims to enable the same, provide RadiotapHeader support for ns-3's Wifi model and a Monitor Wifi Mac interface to support a Monitor Mode within ns-3.

	Mid-term report: [~~http://www.nsnam.org/wiki/index.php/~~NSOC2011ClickMac/MidTermReport]		Mid-term report: [[NSOC2011ClickMac/MidTermReport]]

	== RadiotapHeader support ==		== RadiotapHeader support ==

Ashwin: /* Progress */

2011-08-15T13:31:26Z

Progress

← Older revision		Revision as of 13:31, 15 August 2011
Line 150:		Line 150:
	* June 3 - June 10 : Creation of MonitorWifiMac		* June 3 - June 10 : Creation of MonitorWifiMac
	* June 10 - July 3 : MonitorWifiMac abstraction ready for rx		* June 10 - July 3 : MonitorWifiMac abstraction ready for rx
	* July 4 - July 10 : Test script for RX Monitor Mode support ~~and further testing~~		* July 4 - July 10 : Test script for RX Monitor Mode support
	* July 10 - July 17 : Mid-term review + feedback		* July 10 - July 17 : Mid-term review + feedback
	* July 18 - July 27 : Tx-vector implementation for radiotap header support		* July 18 - July 27 : Tx-vector implementation for radiotap header support
	* July 27 - Aug 5 : Test script for TX Monitor Mode support ~~and further testing~~		* July 27 - Aug 5 : Test script for TX Monitor Mode support
	* Aug 6 - Aug 8 : Addition of comments		* Aug 6 - Aug 8 : Addition of comments
	* Aug 9 - Aug 12 : Testing and fixing holes		* Aug 9 - Aug 12 : Testing and fixing holes
	* Aug 13 - Aug 14 : Cleaning up		* Aug 13 - Aug 14 : Cleaning up
	* Aug 15 : Submitted code for review		* Aug 15 : Submitted code for review

Ashwin: /* Progress */

2011-08-15T13:31:00Z

Progress

← Older revision		Revision as of 13:31, 15 August 2011
Line 154:		Line 154:
	* July 18 - July 27 : Tx-vector implementation for radiotap header support		* July 18 - July 27 : Tx-vector implementation for radiotap header support
	* July 27 - Aug 5 : Test script for TX Monitor Mode support and further testing		* July 27 - Aug 5 : Test script for TX Monitor Mode support and further testing
	* Aug 6 - ~~Present~~ : Addition of comments and ~~cleaning~~ up of code		* Aug 6 - Aug 8 : Addition of comments
			* Aug 9 - Aug 12 : Testing and fixing holes
			* Aug 13 - Aug 14 : Cleaning up
			* Aug 15 : Submitted code for review

Ashwin: /* Test Script */

2011-08-10T06:52:36Z

Test Script

← Older revision		Revision as of 06:52, 10 August 2011
Line 120:		Line 120:
	Rate control was made possible by means of SetTXRate() and different transmission powers were assigned to alternative packets using the RoundRobinSwitch element and assigning two different tx power levels to alternative ARP packets.		Rate control was made possible by means of SetTXRate() and different transmission powers were assigned to alternative packets using the RoundRobinSwitch element and assigning two different tx power levels to alternative ARP packets.

	Note:		*Note:
	Since the test script above can be used for both RX and TX, this script would alone be sufficient to test the monitor mode support for ns-3's Wifi model.		Since the test script above can be used for both RX and TX, this script would alone be sufficient to test the monitor mode support for ns-3's Wifi model.

Ashwin: /* Test Script */

2011-08-10T06:51:28Z

Test Script

← Older revision		Revision as of 06:51, 10 August 2011
Line 119:		Line 119:

	Rate control was made possible by means of SetTXRate() and different transmission powers were assigned to alternative packets using the RoundRobinSwitch element and assigning two different tx power levels to alternative ARP packets.		Rate control was made possible by means of SetTXRate() and different transmission powers were assigned to alternative packets using the RoundRobinSwitch element and assigning two different tx power levels to alternative ARP packets.

			Note:
			Since the test script above can be used for both RX and TX, this script would alone be sufficient to test the monitor mode support for ns-3's Wifi model.

	== Future Work ==		== Future Work ==

Ashwin: /* Progress */

2011-08-10T06:50:00Z

Progress

← Older revision		Revision as of 06:50, 10 August 2011
Line 151:		Line 151:
	* July 18 - July 27 : Tx-vector implementation for radiotap header support		* July 18 - July 27 : Tx-vector implementation for radiotap header support
	* July 27 - Aug 5 : Test script for TX Monitor Mode support and further testing		* July 27 - Aug 5 : Test script for TX Monitor Mode support and further testing
			* Aug 6 - Present : Addition of comments and cleaning up of code

Ashwin: /* Test Script */

2011-08-07T16:15:20Z

Test Script

← Older revision		Revision as of 16:15, 7 August 2011
Line 117:		Line 117:
	== Test Script ==		== Test Script ==
	A click-based script was created for the purpose of testing the TX side of monitor mode support. For this, two nodes were used, one of AdhocWifiMac type and the other of MonitorWifiMac type. The latter has a single host Click configuration for wifi. The node broadcasts ARP requests if it wants to find a destination address and it responds to ARP requests made to it. A click script is used to set radiotap tx parameters (tx power, RTS and data retries).		A click-based script was created for the purpose of testing the TX side of monitor mode support. For this, two nodes were used, one of AdhocWifiMac type and the other of MonitorWifiMac type. The latter has a single host Click configuration for wifi. The node broadcasts ARP requests if it wants to find a destination address and it responds to ARP requests made to it. A click script is used to set radiotap tx parameters (tx power, RTS and data retries).

			Rate control was made possible by means of SetTXRate() and different transmission powers were assigned to alternative packets using the RoundRobinSwitch element and assigning two different tx power levels to alternative ARP packets.

	== Future Work ==		== Future Work ==

Ashwin: /* Transmission side */

2011-08-07T05:24:17Z

Transmission side

← Older revision		Revision as of 05:24, 7 August 2011
Line 111:		Line 111:
	As far as TX part is concerned, there’s a need to use a tx-vector that allows per-packet tx parameters so as to allow for the transmission parameters obtained from the radiotap headers to be used for transmission. The implementation introduces per-packet tx parameters through WifiStationRemoteManager by adding the appropriate menthods for the diﬀerent parameters and for Data, Rts, Cts, Ack.		As far as TX part is concerned, there’s a need to use a tx-vector that allows per-packet tx parameters so as to allow for the transmission parameters obtained from the radiotap headers to be used for transmission. The implementation introduces per-packet tx parameters through WifiStationRemoteManager by adding the appropriate menthods for the diﬀerent parameters and for Data, Rts, Cts, Ack.

	For monitor mode support, the changes required would be using a dummy address and protocol in the NetDevice->Send () arguments in Ipv4L3ClickRoutingProtocol::SendDown () and then modifications in MonitorWifiMac::Enqueue () that include the removal of the wifi-mac and radiotap headers. The radiotap information stripped would then be used to set the per-packet tx-vector parameters. The packet with the stripped headers is sent to the dca_queue.		Changes were made in the existing radiotap header implementation to accommodate the TX parameters in the header. For monitor mode support, the changes required would be using a dummy address and protocol in the NetDevice->Send () arguments in Ipv4L3ClickRoutingProtocol::SendDown () and then modifications in MonitorWifiMac::Enqueue () that include the removal of the wifi-mac and radiotap headers. The radiotap information stripped would then be used to set the per-packet tx-vector parameters. The packet with the stripped headers is sent to the dca_queue.

	MonitorWifiMac::SetTxParametersFromRadiotapHeader() sets the tx-vector relevant parameters in WifiRemoteStationManager before the packet is sent to the dca_queue. The per-packet nature of the tx-vector parameters is preserved owing to the implementation of the HighLatencyTxVectorTag in WifiRemoteStationManager.		MonitorWifiMac::SetTxParametersFromRadiotapHeader() sets the tx-vector relevant parameters in WifiRemoteStationManager before the packet is sent to the dca_queue. The per-packet nature of the tx-vector parameters is preserved owing to the implementation of the HighLatencyTxVectorTag in WifiRemoteStationManager.

Ashwin: /* Transmission side */

2011-08-07T05:18:18Z

Transmission side

← Older revision		Revision as of 05:18, 7 August 2011
Line 112:		Line 112:

	For monitor mode support, the changes required would be using a dummy address and protocol in the NetDevice->Send () arguments in Ipv4L3ClickRoutingProtocol::SendDown () and then modifications in MonitorWifiMac::Enqueue () that include the removal of the wifi-mac and radiotap headers. The radiotap information stripped would then be used to set the per-packet tx-vector parameters. The packet with the stripped headers is sent to the dca_queue.		For monitor mode support, the changes required would be using a dummy address and protocol in the NetDevice->Send () arguments in Ipv4L3ClickRoutingProtocol::SendDown () and then modifications in MonitorWifiMac::Enqueue () that include the removal of the wifi-mac and radiotap headers. The radiotap information stripped would then be used to set the per-packet tx-vector parameters. The packet with the stripped headers is sent to the dca_queue.

			MonitorWifiMac::SetTxParametersFromRadiotapHeader() sets the tx-vector relevant parameters in WifiRemoteStationManager before the packet is sent to the dca_queue. The per-packet nature of the tx-vector parameters is preserved owing to the implementation of the HighLatencyTxVectorTag in WifiRemoteStationManager.

	== Test Script ==		== Test Script ==

Ashwin: /* Test Script */

2011-08-07T05:17:51Z

Test Script

← Older revision		Revision as of 05:17, 7 August 2011
Line 114:		Line 114:

	== Test Script ==		== Test Script ==
	A click-based script was created for the purpose of testing the TX side of monitor mode support. For this, two nodes were used, one of AdhocWifiMac type and the other of MonitorWifiMac type. The latter has a single host Click configuration for wifi. The node broadcasts ARP requests if it wants to find a destination address and it responds to ARP requests made to it. A click script is used to set radiotap tx parameters (tx power, RTS and data retries). MonitorWifiMac::SetTxParametersFromRadiotapHeader() sets the tx-vector relevant parameters in WifiRemoteStationManager before the packet is sent to the dca_queue. The per-packet nature of the tx-vector parameters is preserved owing to the implementation of the HighLatencyTxVectorTag in WifiRemoteStationManager.		A click-based script was created for the purpose of testing the TX side of monitor mode support. For this, two nodes were used, one of AdhocWifiMac type and the other of MonitorWifiMac type. The latter has a single host Click configuration for wifi. The node broadcasts ARP requests if it wants to find a destination address and it responds to ARP requests made to it. A click script is used to set radiotap tx parameters (tx power, RTS and data retries).

	== Future Work ==		== Future Work ==