Hey Jordi,
I was trying this on Ubuntu last night and the objects were all
crashing. I didn't fix it, but I tracked it down to this line in
pcap_device_ipaddr4():
sprintf(x-x_host_ip, %s, inet_ntoa(((struct sockaddr_in
*)ifr.ifr_addr)-sin_addr));
Also one problem: since your project
Hi,
Thanks for your help. Finally I renamed pdpcap to pcap (for pd) and
the pdpcap object has been splitted in two objcets pcap_device and
pcap_file.
-pcap_device-captures network traffic in live mode from a net device
(eth0, lo, eth1...).
-pcap_file-reads (captures) network traffic from a pcap
On Oct 5, 2010, at 12:00 PM, IOhannes m zmölnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/2010 01:58 AM, Jordi Sala wrote:
ok, then, the naming can be something like: pcap-live, pcap-
file,.
afaik, there is only one other library that uses the - infix (list-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/2010 01:58 AM, Jordi Sala wrote:
ok, then, the naming can be something like: pcap-live, pcap-file,.
afaik, there is only one other library that uses the - infix (list-abs).
i would suggest using a more common scheme:
e.g. make it
Yeah, instead of making one big mega object that takes lots of
messages, there could instead be a suite of objects like one for live
capture, one for reading/writing files, one for translating port
numbers to services, whatever is appropriate.
.hc
On Oct 1, 2010, at 7:57 PM, Jordi Sala
ok, then, the naming can be something like: pcap-live, pcap-file,.
On 3 October 2010 23:18, Hans-Christoph Steiner h...@at.or.at wrote:
Yeah, instead of making one big mega object that takes lots of messages,
there could instead be a suite of objects like one for live capture, one for
pcap works, or pcap4pd.
I think it would make the most sense to make the pcap file reader a
standalone object, with an interface just like [textfile], [msgfile],
etc. So banging it would give you a packet from the file, it would
have a rightmost outlet which bangs when the end of the
On Thu, 30 Sep 2010, Jordi Sala wrote:
Yes it can be renamed, I named pdpcap when I started the object
(PD+PCAPlib)...,... pcap could be a good nameany suggestions?
name the package pd-pcap and the pd library file pcap.pd_linux for
example.
Several programming languages use such
Hans, so your proposal is to split the current pdpcap in 2 different
objects: one for live (net device) capturing and a second one for pcap file
reading?
I like Mathieu's suggested name:1) the Mathieu's reasoning about naming,
2)the objects I think is differentiated of pdp, 3)doesn't lost
On Wed, 29 Sep 2010, Jordi Sala wrote:
PDPCAP 0.0.4 new features
Could it be renamed so that it doesn't look like it's something to do with
PDP ? (or is it PDP's fault for using non-distinctive naming ?)
___
| Mathieu
Yes it can be renamed, I named pdpcap when I started the object
(PD+PCAPlib)...,... pcap could be a good nameany suggestions?
On 30 September 2010 13:45, Mathieu Bouchard ma...@artengine.ca wrote:
On Wed, 29 Sep 2010, Jordi Sala wrote:
PDPCAP 0.0.4 new features
Could it be renamed so
I was going to change the name to pdpcap, but it would be very confused to
have the same name that the pcaplib, that use pcap.. so, the name could be
pktcap? I will expect until next week if there is any suggestion ...
On 30 September 2010 22:16, ALAN BROOKER alan.brooker2...@gmail.com wrote:
PDPCAP 0.0.4 new features
·pcap files read: Read captured traffic saved in a pcap file .
(wireshark , tcpdump , etc. compatible).
·pcap files dump: Dump pdpcap captured traffic in a pcap file, so it can be
open by any compatible aplication.
·OS X compatible: Thanks to Nicolas Montgermont pdpcap
13 matches
Mail list logo
