Bugzilla – Bug 1984
expose additional internet random variables to configuration system
Last modified: 2014-09-11 14:18:24 EDT
classes Ipv6Extension and Ipv4GlobalRouting use random variables that are not exposed to the config store system. The ArpL3Protocol attribute is an example of how to do this: .AddAttribute ("RequestJitter", "The jitter in ms a node is allowed to wait before sending an ARP request. Some jitter aims to prevent collisions. By default, the model will wait for a duration in ms defined by a uniform random-variable between 0 and RequestJitter", StringValue ("ns3::UniformRandomVariable[Min=0.0|Max=10.0]"), MakePointerAccessor (&ArpL3Protocol::m_requestJitter), MakePointerChecker<RandomVariableStream> ()) In addition, it would be useful to document the usage of randomness in the internet stack, in the Internet documentation (rst and documentation)... this is a cross-cutting issue (would be nice for all modules). This bug is filed as a reminder to revisit this.