Thanks for this info, I'll take this discussion to the mentioned list then.
Ákos
On 3 December 2011 19:02, Guy Harris wrote:
>
> On Dec 3, 2011, at 9:40 AM, Akos Vandra wrote:
>
>> So in order to support a new data source only libpcap should be
>> modified?
>
> Ideally, yes.
>
>> I have no exper
On Dec 3, 2011, at 9:40 AM, Akos Vandra wrote:
> So in order to support a new data source only libpcap should be
> modified?
Ideally, yes.
> I have no experience with it, so I'm not sure how wireshark
> and libpcap are interfaced... Does libpcap offer a list of available
> capture source for wi
So in order to support a new data source only libpcap should be
modified? I have no experience with it, so I'm not sure how wireshark
and libpcap are interfaced... Does libpcap offer a list of available
capture source for wireshark, so it can use a new capture source
without any modification to wir
On Dec 3, 2011, at 2:00 AM, Akos Vandra wrote:
> I have a custom interface generating packet data. I'd like to use
> wireshark to display them and dissect the packets.
>
> The dissection I can do with dissector plugins, but how can I feed the
> packet data to wireshark?
Make a patch to libpcap/
On Fri, Dec 2, 2011 at 10:04 PM, Guy Harris wrote:
>
> On Dec 2, 2011, at 12:57 PM, Yegor Yefremov wrote:
>
>> So your play field is very limited. That's why I'm thinking about
>> making an option to choose the desired high level protocol in
>> socketcan settings.
>
> If the protocol transported a
A little extra info:
Yeah, I need to do it live, saving to pcap, and opening with wireshark
later is not an option.
No, it doesn't necessarily need to be super fast, theoretical max is
5-10k packets/s, but mostly about max 3-500 packets/s.
On 3 December 2011 11:00, Akos Vandra wrote:
> Hi!
>
>
Hi!
I have a custom interface generating packet data. I'd like to use
wireshark to display them and dissect the packets.
The dissection I can do with dissector plugins, but how can I feed the
packet data to wireshark?
Regards,
Ákos Vandra
___
