I can't take credit for this, I copied from someone elses code.
sub parse_tcp_flags { my $flagword = shift(@_); my %flags = ("FIN"=>0,"SYN"=>0,"RST"=>0,"PSH"=>0,"ACK"=>0,"URG"=>0) +; $flags{FIN} = ($flagword & 0x01)? 1: 0; $flags{SYN} = ($flagword & 0x02)? 1: 0; $flags{RST} = ($flagword & 0x04)? 1: 0; $flags{PSH} = ($flagword & 0x08)? 1: 0; $flags{ACK} = ($flagword & 0x10)? 1: 0; $flags{URG} = ($flagword & 0x20)? 1: 0; return \%flags; }
Pass this function the flags from parse_tcp_flags

In reply to Re: Re: Re: Re: Re: NetPacket::TCP output by jlargent
in thread NetPacket::TCP output by Benedict

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.