Netstat options.filter.state - LISTEN vs LISTENING

[nktnet1]

On Windows, the state for a started HTTP server is LISTENING, but on Linux, it's LISTEN.

Is there a way to consolidate these differences when filtering?

Also, it would be nice if all filter conditions allow for AND/OR operators, or takes an array of possible values to match.

Thank you :).

[danielkrainas]

@nktnet1 as a quick fix: by omitting any filter to node-netstat, you can apply your own advanced filtering strategy in the item handler. I could also look at adding support for specifying a predicate function on the filter object to allow you to enforce whatever logic you'd like