Project Ideas - Revision history

Tomh at 18:41, 19 February 2026

2026-02-19T18:41:48Z

← Older revision		Revision as of 18:41, 19 February 2026
Line 1:		Line 1:
	{{TOC}}		{{TOC}}

	'''Note:''' If you are here looking for '''Google Summer of Code project ideas''', visit [[~~GSOC2020Projects~~ \| this page]].		'''Note:''' If you are here looking for '''Google Summer of Code project ideas''', visit [[Summer_Projects#Google_Summer_of_Code_2026 \| this page]].

	One way to get involved with ns-3 is to work with a mentor on a suggested project. These are typically project suggestions that would be valued contributions but the proposer does not have enough time to do it himself or herself, but is willing to mentor someone else to do it.		One way to get involved with ns-3 is to work with a mentor on a suggested project. These are typically project suggestions that would be valued contributions but the proposer does not have enough time to do it himself or herself, but is willing to mentor someone else to do it.

Tomh at 16:42, 22 February 2020

2020-02-22T16:42:46Z

← Older revision		Revision as of 16:42, 22 February 2020
Line 1:		Line 1:
	{{TOC}}		{{TOC}}

			'''Note:''' If you are here looking for '''Google Summer of Code project ideas''', visit [[GSOC2020Projects \| this page]].

	One way to get involved with ns-3 is to work with a mentor on a suggested project. These are typically project suggestions that would be valued contributions but the proposer does not have enough time to do it himself or herself, but is willing to mentor someone else to do it.		One way to get involved with ns-3 is to work with a mentor on a suggested project. These are typically project suggestions that would be valued contributions but the proposer does not have enough time to do it himself or herself, but is willing to mentor someone else to do it.

Tommaso at 23:19, 3 January 2019

2019-01-03T23:19:46Z

@@ Line 66: / Line 66: @@
 * Flow labels for vertical flows are not rendered correctly (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2970)
 * GooCanvas API inconsistency for bounds resizing (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2969)
 == Wifi rate control example ==
@@ Line 113: / Line 101: @@
 Please do not apply for mentoring help on a class project unless you have approval from the instructor to receive mentoring.
 == Decouple traffic generation from sockets ==

Tommaso: /* Make NetAnim more modular */

2019-01-03T23:18:17Z

Make NetAnim more modular

← Older revision		Revision as of 23:18, 3 January 2019
Line 71:		Line 71:
	Edited from the bug description (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2968):		Edited from the bug description (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2968):

	~~Netanim~~ ns-3 interface is "hardwired" on the modules it can understand.		NetAnim ns-3 interface is "hardwired" on the modules it can understand.
	As a result, if you try to enable only a specific module and NetAnim, ~~netanim~~ will build unnecessarily a lot of other stuff.		As a result, if you try to enable only a specific module and NetAnim, NetAnim will build unnecessarily a lot of other stuff.

	In light of modularizing ns-3, it would be helpful to have ~~netanim~~ probe for the available modules and build itself accordingly.		In light of modularizing ns-3, it would be helpful to have NetAnim probe for the available modules and build itself accordingly.
	~~Netanim~~ should be slimmed down to its bare minimum, and each module should (optionally) include its own code to support ~~netanim~~.		NetAnim should be slimmed down to its bare minimum, and each module should (optionally) include its own code to support NetAnim.

	Adding new types support to NetAnim could be way easier in this way, leaving the burden to write the proper code to the specific modules developers.		Adding new types support to NetAnim could be way easier in this way, leaving the burden to write the proper code to the specific modules developers.

Tommaso: /* Make NetAnim more modular */

2019-01-03T23:17:43Z

Make NetAnim more modular

← Older revision		Revision as of 23:17, 3 January 2019
Line 69:		Line 69:
	== Make NetAnim more modular ==		== Make NetAnim more modular ==

	~~Please see~~ (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2968) ~~for~~ a ~~description~~ of the ~~issue~~.		Edited from the bug description (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2968):

			Netanim ns-3 interface is "hardwired" on the modules it can understand.
			As a result, if you try to enable only a specific module and NetAnim, netanim will build unnecessarily a lot of other stuff.

			In light of modularizing ns-3, it would be helpful to have netanim probe for the available modules and build itself accordingly.
			Netanim should be slimmed down to its bare minimum, and each module should (optionally) include its own code to support netanim.

			Adding new types support to NetAnim could be way easier in this way, leaving the burden to write the proper code to the specific modules developers.

	== Wifi rate control example ==		== Wifi rate control example ==

Tomh: /* Feature requests */

2018-11-06T16:34:27Z

Feature requests

← Older revision		Revision as of 16:34, 6 November 2018
Line 137:		Line 137:

	The following projects have been suggested in the past. If you are working on them, please let us know on the developers or users list so that we can coordinate activities. If you want to add a project, please describe it below.		The following projects have been suggested in the past. If you are working on them, please let us know on the developers or users list so that we can coordinate activities. If you want to add a project, please describe it below.

			== TCP congestion window validation ==

			Linux uses TCP congestion window validation (CWV) but ns-3 lacks this option. This draft provides details:
			https://tools.ietf.org/html/rfc7661

	== Path MTU discovery ==		== Path MTU discovery ==

Tomh: /* Projects needing completion */

2018-08-15T20:47:04Z

Projects needing completion

← Older revision		Revision as of 20:47, 15 August 2018
Line 66:		Line 66:
	* Flow labels for vertical flows are not rendered correctly (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2970)		* Flow labels for vertical flows are not rendered correctly (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2970)
	* GooCanvas API inconsistency for bounds resizing (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2969)		* GooCanvas API inconsistency for bounds resizing (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2969)

			== Make NetAnim more modular ==

			Please see (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2968) for a description of the issue.

	== Wifi rate control example ==		== Wifi rate control example ==

Tomh: /* Projects needing completion */

2018-08-15T20:36:50Z

Projects needing completion

← Older revision		Revision as of 20:36, 15 August 2018
Line 57:		Line 57:

	Some projects were started in the past and never brought to completion.		Some projects were started in the past and never brought to completion.

			== PyViz open issues ==

			As of ns-3.29, PyViz has been ported to GTK+3 but several open issues remain. There are open tracker issues on each of these.

			* The 'show_last_packets.py' plugin needs an update away from use of Python Kiwi library (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2972)
			* Use of ipython needs to be tested (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2971)
			* Flow labels for vertical flows are not rendered correctly (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2970)
			* GooCanvas API inconsistency for bounds resizing (https://www.nsnam.org/bugzilla/show_bug.cgi?id=2969)

	== Wifi rate control example ==		== Wifi rate control example ==

Natale at 08:35, 24 November 2016

2016-11-24T08:35:54Z

← Older revision		Revision as of 08:35, 24 November 2016
Line 24:		Line 24:
	We wrote the udp-echo.cc example when there was no TCP in the system. Now that we have some TCPs, it would be useful to make a tcp-echo.cc and associated applications. In our documentation, it would be very useful go through the same kind of tutorial as everyone else in the world, with a tcp echo walkthrough followed by a udp echo walkthrough.		We wrote the udp-echo.cc example when there was no TCP in the system. Now that we have some TCPs, it would be useful to make a tcp-echo.cc and associated applications. In our documentation, it would be very useful go through the same kind of tutorial as everyone else in the world, with a tcp echo walkthrough followed by a udp echo walkthrough.

	The code is already there, and it ~~would~~ be ~~wonderful to~~ read and to ~~adapt~~ to latest ns-3 by an interested student.		The code is already there, and it is perfect to be read and to be adapted to latest ns-3 by an interested student.

	== Sockets should support the setting of QoS ==		== Sockets should support the setting of QoS ==

Natale at 08:35, 24 November 2016

2016-11-24T08:35:07Z

← Older revision		Revision as of 08:35, 24 November 2016
Line 12:		Line 12:

	This project category is for smaller, simpler projects for new developers to get started. If you would like to work on one of these, please coordinate with the named mentor.		This project category is for smaller, simpler projects for new developers to get started. If you would like to work on one of these, please coordinate with the named mentor.

			== tcp-echo example and relative tutorial section ==

			'''Mentor''': [mailto:natale.patriciello@gmail.com Natale]

			References:
			* https://www.nsnam.org/bugzilla/show_bug.cgi?id=454

			From the bug report: Pretty much every introduction to BSD sockets ever written uses a TCP echo client server pair to start with. It then moves to a UDP echo client server pair to illustrate datagrams.

			We wrote the udp-echo.cc example when there was no TCP in the system. Now that we have some TCPs, it would be useful to make a tcp-echo.cc and associated applications. In our documentation, it would be very useful go through the same kind of tutorial as everyone else in the world, with a tcp echo walkthrough followed by a udp echo walkthrough.

			The code is already there, and it would be wonderful to read and to adapt to latest ns-3 by an interested student.

	== Sockets should support the setting of QoS ==		== Sockets should support the setting of QoS ==