@@ -89,7 +89,7 @@ have the same set of parameters that specify the flow name (:par:`flowName`
8989parameter), the set of packets that enter or exit the flow (:par: `packetFilter `
9090parameter), and the required measurements (:par: `measure ` parameter).
9191
92- By default, the filters match all packets (``packetFilter = 'true ' ``). The
92+ By default, the filters match all packets (``packetFilter = '* ' ``). The
9393:par: `measure ` parameter is a list containing elements from the following set,
9494separated by spaces:
9595
@@ -156,8 +156,8 @@ The module type :ned:`PacketFlowVisualizer` (also included in
156156:ned: `IntegratedCanvasVisualizer `) can display packet flows in the network as dashed
157157arrows annotated by the flow name. The arrows are color-coded so that flows can
158158be differentiated by color. The visualization can be enabled with the
159- :par: `displayPacketFlows ` parameter, e.g.
160- ``*.visualizer.packetFlowVisualizer.displayPacketFlows = true `` in the .INI
159+ :par: `displayRoutes ` parameter, e.g.
160+ ``*.visualizer.packetFlowVisualizer.displayRoutes = true `` in the .INI
161161file.
162162
163163Example Simulations
@@ -251,7 +251,7 @@ Similarly, we enable the measurement recorder module in the server UDP apps (by
251251 :end-at: *.server *.app[*].measurementRecorder.typename = "FlowMeasurementRecorder"
252252 :language: ini
253253
254- For the packet flow between the two switches, we can enable the built-in ``measurementLayer `` submodule of :ned: `EthernetInterface `:
254+ For the packet flow between the two switches, we can enable the built-in ``measurementLayer `` submodule of :ned: `LayeredEthernetInterface `:
255255
256256.. literalinclude :: ../omnetpp.ini
257257 :start-at: *.switch *.eth[2].measurementLayer.typename = "MeasurementLayer"
0 commit comments