Bug 1746 – PacketSink Rx trace does not fire

Bug 1746 - PacketSink Rx trace does not fire


Summary:	PacketSink Rx trace does not fire

Status:	CLOSED INVALID

Product:	ns-3
Classification:	Unclassified
Component:	applications
Version:	ns-3.16
Hardware:	All All

Importance:	P5 normal
Assigned To:	George Riley

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-08-07 11:37 UTC by Konstantinos Katsaros
Modified:	2013-08-08 11:53 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
A test case of for the problem. (10.13 KB, application/octet-stream) 2013-08-07 11:37 UTC, Konstantinos Katsaros	Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Konstantinos Katsaros 2013-08-07 11:37:38 UTC

Created attachment 1653 [details]
A test case of for the problem.

I started a discussion here: https://groups.google.com/d/msg/ns-3-users/xVvrIMH4hVk/DMeexvAW76IJ

For some strange reason when I install the PacketSink application on a subset of nodes (the sink nodes only) the tracesource does not fire. When I install it on ALL nodes, it fires.

FlowMonitor results suggest that the packets are received in both cases.

Comment 1 Konstantinos Katsaros 2013-08-08 07:42:17 UTC

It was a problem with the sink socket assignment that cause this strange behavour.

Comment 2 Daniel L. 2013-08-08 11:53:31 UTC

Closed.
See https://groups.google.com/forum/#!msg/ns-3-users/xVvrIMH4hVk/DMeexvAW76IJ for discussion.