It looks like you may be trying to print out any lines returned from your netstat command that have the strings "invalid headers" or "packets dropped" in them. If so, I think this may be something that will work for you... 
my @netstat = `netstat -s`;
my @matches=("invalid headers", "packets dropped");
my $matches = join('|', @matches);
foreach (@netstat) {
    print if /$matches/;
}

[download]
However, if you go through alot of records this will be slow as it has to reparse the regular expression over and over. If your regex (list of strings to match) is truely variable and you process lots of records then it might be more efficient to assemble some perl code and eval it. The advanced perl book ( the one with the panther on it ) has a good example in it in the eval chapter.

In reply to Re: Trouble with foreach loop.... I think by mifflin
in thread Trouble with foreach loop.... I think by u235sentinel

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.