Bug 749 – EmuNetDevice: "Received packet with erroneous context"

Bug 749 - EmuNetDevice: "Received packet with erroneous context"


Summary:	EmuNetDevice: "Received packet with erroneous context"

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	devices
Version:	ns-3.6
Hardware:	All All

Importance:	P5 major
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-11-24 17:46 UTC by Gustavo J. A. M. Carneiro
Modified:	2009-12-02 19:26 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
quick-and-dirty patch (2.58 KB, patch) 2009-11-24 18:01 UTC, Gustavo J. A. M. Carneiro	Details \| Diff
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 Gustavo J. A. M. Carneiro 2009-11-24 17:46:15 UTC

Did someone accidentally break EmuNetDevice when simulator system IDs (or whatever they're called) were introduced?  I see this bug in ns-3-dev, but I got a report from people working on NS-3.6, so it must be an old bug.

root@dark-tower:/home/gjc/projects/ns/ns-3-allinone/ns-3-dev# NS_LOG=PingEmulationExample ./build/debug/examples/emulation/emu-ping --deviceName=wlan0
PingEmulationExample:main(): Ping Emulation Example
PingEmulationExample:main(): Create Node
0s -1 PingEmulationExample:main(): Create Device
0s -1 PingEmulationExample:main(): Add Internet Stack
0s -1 PingEmulationExample:main(): Create IPv4 Interface
0s -1 PingEmulationExample:main(): Create V4Ping Appliation
0s -1 PingEmulationExample:main(): Run Emulation.
Received packet with erroneous context ; make sure the channels in use are correctly updating events context when transfering events from one node to another.
Segmentation fault

Comment 1 Gustavo J. A. M. Carneiro 2009-11-24 18:01:46 UTC

Created attachment 675 [details]
quick-and-dirty patch