Brad,
Great stuff. Thanks. I'm going on the assumption that $inst-[1] (line
94) is the raw packet, headers and all. I plan to test by pointing pcap at
a capture file and comparing output to input. My next plan is to add a sql
insert of $hexpacket at line 108. My goal is to keep up with an
Nosing around in the mailing list archive I find;
Re: Prioritizing Event Loops
Martijn van Beers
Fri, 18 Jan 2008 11:37:22 -0800
snip
In POE, all your external data, whether from a socket or a file, or
something else entirely, enters your app through a POE::Wheel (you might
not be aware of
Jonathan S. Polacheck wrote:
Nosing around in the mailing list archive I find;
Re: Prioritizing Event Loops
Martijn van Beers
Fri, 18 Jan 2008 11:37:22 -0800
snip
In POE, all your external data, whether from a socket or a file, or
something else entirely, enters your app through a POE::Wheel
I am trying to concoct and script that will take a binary data stream from
tcpdump, feed it into a filter, then in another instance of wheel::run,
hexdump the data stream from the filter. The code I have come up with so
far is in the 6th entry in the Continuous packet capture thread. I
cannot
I have spent a couple of days casting about, looking at examples and
perldoc. I don't seem to be able to get the data from 'tcpdump' (or
POE::Component::PCAP) to the wheel that will process the data. For my last
attempt, I removed Filter::Referece and tried with just the wheel. Still
no luck.
Perhaps this is a case of premature optimization. I am working toward a
continuous packet capture application (as in Infinistream, Gigastor,
NetVCR, etc). So far, I have two perl scripts. One takes Net::Pcap output
and Hexdumps it to a fifo file. The other reads the fifo and inserts the
poe@perl.org,
PMJonathan S. Polacheck
[EMAIL PROTECTED]
cc
