Bugzilla – Bug 4
'iwconfig eth1 frag off/auto/fixed' not supported
Last modified: 2005-10-02 11:53:37
You need to log in before you can comment on or make changes to this bug.
SF: 931399 Feature request to add the functionality to turn fragmentation off, make it automatic, or reset it to a fixed value. Actual behavior right now is that off and auto generate "Invalid argument" errors and fixed does not set the value to a fixed value. Shown below: %iwconfig eth1 frag off This gives the error message: Error for wireless request "Set Fragmentation Threshold" (8B24) : SET failed on device eth1 ; Invalid argument %iwconfig eth1 frag auto This gives the error message: Error for wireless request "Set Fragmentation Threshold" (8B24) : SET failed on device eth1 ; Invalid argument %iwconfig eth1 frag fixed After this is done, %iwconfig shows that the Fragment thr is 10B less than the previous threshold. Expected - Fragment threshold would be reset to some pre-defined value that doesn't change each time 'iwconfig eth1 frag fixed' is run. Date: 2004-04-22 14:52 Sender: jnfleisc Logged In: YES user_id=558102 We won't be supporting anything special for auto. ------------------------------------------------------------------------------- - Date: 2004-04-15 15:38 Sender: jnfleisc Logged In: YES user_id=558102 In 0.40-pre2, the 'iwconfig eth1 frag off' functionality now functions as expected. In 0.40-pre2, the 'iwconfig eth1 frag fixed' does not decrease fragmentation threshold by 10B. It leaves it as it was previously set. (Still expect that the threshold would be reset to some pre-defined value that doesn't change.)
bumping up the priority
The bug exists in ipw2100 v0.56
I've cleaned up the code a bit; but I didn't change anything that should have fixed the problem from this defect, specifically that the fragmentation size was decreasing by 10B between a 'frag off' and 'frag fixed' call. With the wireless tools I have installed (27pre26), calling 'frag fixed' sets the fragmentation, then turns and immediately turns it off, but based on debug messages, the code appears to be doing the correct thing. AUTO is not supported, and will continue to provide the Invalid argument return string.
So James, do you think "iwconfig eth1 frag off/fixed" works as expected? And "iwconfig eth1 frag auto" will not be supported in the future? If it is, I will mark the bug as verified and change our test cases accordingly.
Verified that off works as expected (using 0.62.)