Disabling defensive filters for a single stack

To disable defensive filtering for a TCP/IP stack, while you continue to support defensive filtering for other stacks on the system, take the following actions:

Update the DMD configuration file and change the mode of the stack to Inactive on the DmStackConfig statement.
Issue the MODIFY REFRESH command for the DMD.

Results:

All defensive filters are removed from the stack.
The DMD's persistent memory of defensive filters for the stack is cleared.
Additional defensive filters cannot be added to this stack.

Tips:

If you cannot update your DMD configuration file, you can issue the MODIFY FORCE_INACTIVE command for the DMD to disable defensive filtering for the stack. However, a later MODIFY REFRESH command will use the DMD configuration file, so if you want defensive filtering to remain disabled, you should update the DMD configuration file as soon as possible.
Removing the DmStackConfig statement from the DMD configuration file does not delete existing defensive filters from the stack. If you remove the DmStackConfig statement, the defensive filters remain in the stack until they expire. To remove the defensive filters from the stack immediately, add the DmStackConfig statement back to the DMD configuration file and specify mode Inactive, or issue the MODIFY FORCE_INACTIVE command for the stack.