[ previous ] [ next ] [ threads ]
 
 From:  "Christopher M. Iarocci" <iarocci at eastendsc dot com>
 To:  "Christopher M. Iarocci" <iarocci at eastendsc dot com>
 Cc:  Ugo Bellavance <ugob at camo dash route dot com>, m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Re: monowall monitor
 Date:  Fri, 10 Jun 2005 17:54:05 -0400
Christopher M. Iarocci wrote:

> Ugo Bellavance wrote:
>
>> Don Munyak wrote:
>>  
>>
>>> Is the point of this monitor just to see if m0n0wall is working ?
>>> I did not see any kind of doc's about this.
>>>
>>>   
>>
>>
>> It seems to be giving out statistics about traffic.  I'll tell you more
>> if I can get it to work :)
>>
>>  
>>
>>> - Don
>>>
>>> On 6/9/05, Ugo Bellavance <ugob at camo dash route dot com> wrote:
>>>
>>>   
>>>
>>>> Daniel Foster wrote:
>>>>
>>>>     
>>>>
>>>>> Hi Ugo,
>>>>>
>>>>> Yes I got it working both inside and outside of the network, by 
>>>>> opening
>>>>> port 161.
>>>>>       
>>>>
>>>> I don't understand... nmap reports port 161/udp as open on the 
>>>> monowall
>>>>     
>>>> from the lan.
>>>
>>>   
>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>>>> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>>>>
>>>>
>>>>     
>>>
>>
>>
>>
>>  
>>
> My m0n0wall is wide open from the LAN side to all traffic, yet this 
> app will not connect to it.  I'm using 1.2b8.
>
> Chris

I got mine to work by making the community string "public".  Anything 
other than public, even though they match, will not work.  Makes me 
thing the app doesn't honor the setting put in that field.  Also, once 
it is connected, the graph it makes is tiny, and unreadable.

Chris