Russell Bryant wrote:
> On Nov 8, 2008, at 1:30 PM, Atis Lezdins wrote:
>
>> Asterisk offers very much the same flexibility. You can disable
>> specific log levels (for example warnings) in logger.conf or you can
>> log everything to syslog, where filter out this specific message.
>>
> Of c
On Nov 8, 2008, at 1:30 PM, Atis Lezdins wrote:
> Asterisk offers very much the same flexibility. You can disable
> specific log levels (for example warnings) in logger.conf or you can
> log everything to syslog, where filter out this specific message.
Of course, there is always this method, whi
On Sat, Nov 08, 2008 at 09:30:59PM +0200, Atis Lezdins wrote:
> On Sat, Nov 8, 2008 at 9:20 AM, Louis-David Mitterrand
> <[EMAIL PROTECTED]> wrote:
> > On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
> >> Tzafrir Cohen wrote:
> >> > On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton w
On Sat, Nov 8, 2008 at 9:20 AM, Louis-David Mitterrand
<[EMAIL PROTECTED]> wrote:
> On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
>> Tzafrir Cohen wrote:
>> > On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
>> >
>> >
>> >> I'd take this warning seriously. It means that you
Tzafrir Cohen wrote:
> On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
>
>>> Maybe it's me, but I think that "warning" should be regarding a problem
>>> I can fix. Malformed network content does not neceserily fall under that
>>> definition. "notice"?
>>>
>>>
>> Absolutely
On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
> Tzafrir Cohen wrote:
> > On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
> >
> >
> >> I'd take this warning seriously. It means that your monitoring app isn't
> >> monitoring what you think it is.
> >>
> >> I always want t
On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
> Tzafrir Cohen wrote:
> > On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
> >
> >
> >> I'd take this warning seriously. It means that your monitoring app isn't
> >> monitoring what you think it is.
> >>
> >> I always want t
Tzafrir Cohen wrote:
> On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
>
>
>> I'd take this warning seriously. It means that your monitoring app isn't
>> monitoring what you think it is.
>>
>> I always want to know when I get malformed protocol packets in. It is
>> always bad news, m
Rob Hillis wrote:
> Louis-David Mitterrand wrote:
>
>> On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
>>
>>
>>> Your monitoring app is not sending valid IAX2 packets to the server. If
>>> it was sending a true IAX2 POKE, it would be a valid packet and wouldn't
>>> gene
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
> I'd take this warning seriously. It means that your monitoring app isn't
> monitoring what you think it is.
>
> I always want to know when I get malformed protocol packets in. It is
> always bad news, mostly either a misconfiguration (
Tim Panton <[EMAIL PROTECTED]> writes:
> I always want to know when I get malformed protocol packets in.
It's easy for an attacker to fill your log drive then.
/Benny
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asteris
On 7 Nov 2008, at 09:57, Louis-David Mitterrand wrote:
> On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
Your monitoring app is not sending valid IAX2 packets to the
server. If
it was sending a true IAX2 POKE, it would be a valid packet and
wouldn't
gener
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
> >>
> >> Your monitoring app is not sending valid IAX2 packets to the
> >> server. If
> >> it was sending a true IAX2 POKE, it would be a valid packet and
> >> wouldn't
> >> generate this warning.
> >
> > Could asterisk at least _not_ rep
On 7 Nov 2008, at 08:49, Louis-David Mitterrand wrote:
> On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
>> Louis-David Mitterrand wrote:
>>
>>> When monitoring an asterisk through its iax2 port I get these
>>> warnings
>>> at the console:
>>>
>>> [Nov 6 13:15:15] WARNING
Louis-David Mitterrand wrote:
> On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
>
>> Your monitoring app is not sending valid IAX2 packets to the server. If
>> it was sending a true IAX2 POKE, it would be a valid packet and wouldn't
>> generate this warning.
>>
>
> Could a
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
> Louis-David Mitterrand wrote:
>
> > When monitoring an asterisk through its iax2 port I get these warnings
> > at the console:
> >
> > [Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process:
> > midget packet recei
On Thursday 06 November 2008 08:53:40 Louis-David Mitterrand wrote:
> On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
> > Louis-David Mitterrand wrote:
> > > When monitoring an asterisk through its iax2 port I get these warnings
> > > at the console:
> > >
> > > [Nov 6 13:15:15
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
> Louis-David Mitterrand wrote:
>
> > When monitoring an asterisk through its iax2 port I get these warnings
> > at the console:
> >
> > [Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process:
> > midget packet recei
Louis-David Mitterrand wrote:
> When monitoring an asterisk through its iax2 port I get these warnings
> at the console:
>
> [Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process:
> midget packet received (1 of 4 min)
>
> This is triggered by the monitoring app sending a POKE t
19 matches
Mail list logo
