Bug 2088 – when SetMcpsDataIndicationCallback is called UDP data stops

Bug 2088 - when SetMcpsDataIndicationCallback is called UDP data stops


Summary:	when SetMcpsDataIndicationCallback is called UDP data stops

Status:	RESOLVED WONTFIX

Product:	ns-3
Classification:	Unclassified
Component:	lr-wpan
Version:	ns-3.22
Hardware:	PC Linux

Importance:	P5 major
Assigned To:	Tom Henderson

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-04-04 09:14 UTC by ali
Modified:	2016-04-04 13:17 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
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 ali 2015-04-04 09:14:03 UTC

My application contains LrWpanNetDevice.On top of that i have SixLowPan.In application i have UDP data.
When i make SetMcpsDataIndicationCallback on LrWpanNetDevice, i see the UDP data is not flowing.

Comment 1 Tom Henderson 2015-04-04 09:48:25 UTC

(In reply to ali from comment #0)
> My application contains LrWpanNetDevice.On top of that i have SixLowPan.In
> application i have UDP data.
> When i make SetMcpsDataIndicationCallback on LrWpanNetDevice, i see the UDP
> data is not flowing.

Do you have a test case or example that you can share that illustrates this?

Comment 2 Tommaso Pecorella 2015-04-04 10:06:35 UTC

SetMcpsDataIndicationCallback is the callback fired by LrWpanMac when a packet is received. It is set by the LrWpanNetDevice so that it can chain up the packet when it is received.
If you override its setup the NetDevice will not receive anything.

I wouldn't call it a bug. Unless you classify as a bug the fact that there's no warning when you do that.

Comment 3 Tom Henderson 2016-04-04 13:10:20 UTC

(In reply to Tommaso Pecorella from comment #2)
> SetMcpsDataIndicationCallback is the callback fired by LrWpanMac when a
> packet is received. It is set by the LrWpanNetDevice so that it can chain up
> the packet when it is received.
> If you override its setup the NetDevice will not receive anything.
> 
> I wouldn't call it a bug. Unless you classify as a bug the fact that there's
> no warning when you do that.

I agree to mark this as WONTFIX as not being a bug (i.e. the callback should not be overridden by user programs).