For example I was quite surprised to know that it does not support
quantifiers, alternation construct, optional sign "?". You can not use
\d, you have to use [0-9] and who knows what more is missing there.
It is easier to list what it supports than what it doesn't.
So if I want 3 or 4 digits port number, I can not use \:[0-9][0-9][0-9][0-9]?
I can not use \:[0-9]{3,} either...
While searching for 4-digit port numbers works OK.
C:\WIN>netstat -an | findstr 127.*\:[0-9][0-9][0-9][0-9]
TCP 127.0.0.1:1042 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1734 127.0.0.1:2424 TIME_WAIT
TCP 127.0.0.1:1737 127.0.0.1:2431 TIME_WAIT
TCP 127.0.0.1:1738 127.0.0.1:2435 TIME_WAIT
TCP 127.0.0.1:1739 127.0.0.1:2437 ESTABLISHED
TCP 127.0.0.1:1740 127.0.0.1:2440 ESTABLISHED
TCP 127.0.0.1:2437 127.0.0.1:1739 ESTABLISHED
TCP 127.0.0.1:2440 127.0.0.1:1740 ESTABLISHED
UDP 127.0.0.1:1025 *:*
UDP 127.0.0.1:1030 *:*
UDP 127.0.0.1:1900 *:*
--------------------------------------------------------------
If it is OK in your situation, export your output to a text file and
process it there with a text editor allowing full featured regexes.
--
Regards, Eugeny