[ previous ] [ next ] [ threads ]
 From:  "Alex M" <radiussupport at lrcommunications dot net>
 To:  "'Mono Dev List'" <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall-dev] m0n0wall-CMI 1.0-RC1 is out!
 Date:  Thu, 24 Jan 2008 13:22:31 -0500
Also besides hiden options in XML
I know there planty things that require sending commands and executiong bash
scripting when editing settings. Updating XMP is one part, executing scripts
behind the XML is another. Personaly I don't care if I can change the name
of the box remotely, I more need to do advanced options so I don't have to
travel to location, or going to box IP manually...

Also batch editing is what im looking fore, we got 300 boxes

-----Original Message-----
From: Lee Sharp [mailto:leesharp at hal dash pc dot org] 
Sent: Thursday, January 24, 2008 11:15 AM
To: Mono Dev List
Subject: Re: [m0n0wall-dev] m0n0wall-CMI 1.0-RC1 is out!

Gouverneur, Thomas wrote:

>>> Managing many monos remotely, how do us do that? Sending HTTP request
> or >>do
>>> we stoere all configs locally in DB. Also so we have to mode the Mono
>>> Isntall or not?
> Kind of both :) In fact the configuration is stored in a database in an
> "objects" way. 
> Then, when you want to save the config to m0n0wall device, a XML file is
> generated and pushed by HTTP(S). 

So what happens with hidden config options? 
http://doc.m0n0.ch/handbook/faq-hiddenopts.html  Are they lost, or 
handled gracefully?


To unsubscribe, e-mail: m0n0wall dash dev dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash dev dash help at lists dot m0n0 dot ch