Bug 985 – WiMAX Invalid management message type on wimax-simple

Bug 985 - WiMAX Invalid management message type on wimax-simple


Summary:	WiMAX Invalid management message type on wimax-simple

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	wimax
Version:	ns-3.9
Hardware:	All All

Importance:	P3 normal
Assigned To:	Flavio Kubota

URL:
Keywords:

Duplicates:	1035 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-23 21:28 EDT by Tom Henderson
Modified:	2010-12-28 19:42 EST (History)
CC List:	1 user (show)

See Also:

Attachments
Patch to fix bug 985 (1.87 KB, patch) 2010-09-30 02:10 EDT, José Francisco Lombera	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 Tom Henderson 2010-08-23 21:28:38 EDT

Reported by kwong on ns-3-users list; I confirmed it now.  Not sure it is an error or a correct output, so filing here to track.

"Just downloaded ns3.9 and rerun the wimax-simple example in Verbose
mode.

I'm getting "Invalid management message type" error message ...
scattered in the output. Have not figured out if this is significant
or which module is generating this....yet."

Comment 1 José Francisco Lombera 2010-09-30 02:10:58 EDT

Created attachment 986 [details]
Patch to fix bug 985

The problem arises when using Pcap tracing in WiMax devices.

Is an error in functions "PcapSniffTxEvent" and "PcapSniffRxEvent" in "src/helpers/wimax-helper.cc".

These functions are writing captured packets to the Pcap file. These functions modify the captured packet to match the correct format in the pcap file, but this format is incorrect for WiMax device.

So, when Pcap tracing is enabled in WiMax devices, BS and SS nodes can't comunicate correctly. Hence SS nodes never get registered, and Ip packets never go out!

Simply working in a copy of the packet in these functions solve the problem.

Comment 2 Tom Henderson 2010-11-30 11:06:05 EST

*** Bug 1035 has been marked as a duplicate of this bug. ***

Comment 3 Flavio Kubota 2010-12-28 19:42:55 EST

The proposed patch resolves the bug.