Change Details

Handling the case of enabled ipfw by tests themselves is tedious and error prone. It's better to handle it globally for the whole test suite.

Initially, it was added to cover a conflicting case of ipfw and pf used together. But there are more drawbacks than benefits: - A half of these tests are always skipped. That leads to misunderstanding, while the test suite strives to avoid ambiguous situations. - Handling enabled ipfw on the test level is tedious, error-prone, and less maintainable. - CI and similar parties already know how to deal with ipfw for the test suite, like making it open by default. Extra complexity is not needed. In addition, ipfw+pf use cases are not officially supported.

Handling the case of enabled ipfw by tests themselves is tedious andInitially, it was added to cover a conflicting case of ipfw and pf used error prone.together. But there are more drawbacks than benefits: - A half of these tests are always skipped. That leads to misunderstanding, while the test suite strives to avoid ambiguous situations. - Handling enabled ipfw on the test level is tedious, error-prone, and less maintainable. - CI and similar parties already know how to deal with ipfw for the test suite, like making it open by default. Extra complexity is not needed. In addition, It's better to handle it globally for the whole test suiteipfw+pf use cases are not officially supported.