On Tue, Feb 06, 2007 at 09:53:32AM +0800, Jeff Morriss wrote:
> > I have just on concern... The Cisco allows the user to set the syslog
> > facility and severity when starting the debug. The values you saw were
> > the default values. Therefore, checking for LOCAL0/DEBUG only might
> > cause proble
Hi Abhik,
Abhik Sarkar wrote:
> Thanks for your help with this, for the explanation of the changes and
> for including it in the code. I still have a lot to learn.
So did I, that's why it took me a while to rework your patch ;-)
> I have just on concern... The Cisco allows the user to set the s
Hi Jeff,
Thanks for your help with this, for the explanation of the changes and
for including it in the code. I still have a lot to learn.
I have just on concern... The Cisco allows the user to set the syslog
facility and severity when starting the debug. The values you saw were
the default value
Abhik Sarkar wrote:
>> I have also been trying to find out a way to get the syslog dissector
>> to tells all subsequent dissectors that the byte array was generated
>> and not present in the actual capture and hence to mark their protocol
>> tree items using the PROTO_ITEM_SET_GENERATED macro, bu
Sorry! Forgot to change the subject in my previous post :-(
On 1/29/07, Abhik Sarkar <[EMAIL PROTECTED]> wrote:
> > Date: Sun, 28 Jan 2007 14:57:58 +0800
> > From: Jeff Morriss <[EMAIL PROTECTED]>
> > Subject: Re: [Wireshark-dev] Dissector for Cisco ITP packe
Abhik Sarkar wrote:
[...]
> First an introduction in the form of a quote from the Cisco ITP manual...
>
>
> The ITP Packet Logging facility uses the BSD syslog protocol (RFC
> 3164) to send selected (SS7) MSUs to a user-selected monitoring tool
> via the UDP connectionless protocol (RFC 768). Ci
Hello All,
This probably doesn't qualify as a "dissector", but this has been very
useful for me since I wrote it a couple of days back and I thought it
might be useful for someone else too...
First an introduction in the form of a quote from the Cisco ITP manual...
The ITP Packet Logging facil
