Bug 372 – fragmentation is broken

Bug 372 - fragmentation is broken


Summary:	fragmentation is broken

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	wifi
Version:	pre-release
Hardware:	All All

Importance:	P3 normal
Assigned To:	Mathieu Lacage

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-10-02 21:33 UTC by Mathieu Lacage
Modified:	2008-10-16 03:49 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
don't be confused about fragment offset (3.91 KB, patch) 2008-10-02 21:34 UTC, Mathieu Lacage	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 Mathieu Lacage 2008-10-02 21:33:38 UTC

in ns-3.2, wifi fragmentation does not preserve the payload of anything but the first fragment.

Patch attached.

Comment 1 Mathieu Lacage 2008-10-02 21:34:28 UTC

Created attachment 263 [details]
don't be confused about fragment offset

Comment 2 Mathieu Lacage 2008-10-02 21:35:05 UTC

patch needs --python-scan but I have no working python binding support locally so, I can't do this myself.

Comment 3 Gustavo J. A. M. Carneiro 2008-10-03 06:45:39 UTC

It's funny, I am not having any problem with --python-scan atm.

I know this is the wrong bug report to discuss this, but is there "process" problem with python bindings?  Should we be doing something about like:

 1- Document a process (e.g. setting a wscript flag) by which python bindings are temporarily disabled by one developer until another developer -- a python maintainer -- re-scans the header files;

 2- Create a working snapshot of gccxml and link to working pygccxml release.

I am open to suggestions.

Comment 4 Mathieu Lacage 2008-10-16 03:49:03 UTC

changeset 73e7bb607014