Hello everyone
> [EMAIL PROTECTED] wrote:
> > 
> > hi everyone,
> > 
> > I was thinking... (this is odd :) and I came with one more idea about home
> > user interface, and it goes like this...
> > 
> > if we manage to create a XML schema or some other LEAF standart to store
> > filter rules and other config data, I could code a win32 app client to
> > provide a easy UI for rules creation, log view, and overall config for home
> > routers. that way the average home user, simply deploys a LEAF image, goes
> > to his/her win machine, installs the app and uses some wizards to configure
> > the router.
> > 
> > that wizard would change the default password, apply interface IP changes,
> > act on the rule set, config the log options, daemons, test internet
> > connection, config traffic shaping (when fully supported), etc...
> > 
> > users run this wizard on upon the LEAF system installation, and use the app
> > subsequently for minor changes, log viewing, package updating, etc..
> > 
> > this win client would connect via ssh.
> > 
> > all this providing that LEAF is able to store his configs on some sort of
> > standart like XML.
> > 
> > comments please...
> 
I agree that it would be a could idea to be able to describe a router 
/firewall in a standard format  for example XML which is becoming a 
kind of  standard interface in lot of other automats. 
The problem is that the description is not that easy as it would 
seem at the first glance 
see thread  about the firewall design  (for a week or so)


> All
> 
> This is a good idea, especially for a target audience of typical 'Joe
> home user with a new cable/DSL connection', however I'd be opposed to
> doing it in XML more or less on philosophical grounds. I only go with
> proprietary Micro$oft solutions as a last desperate resort:) As LEAF is
> an open source project some other mechanism, seems much more
> appropriate. I find the quote below, from Petreley's column on
> LinuxWorld, sums it up quite nicely.
I don't think xml is an "invention " from Micro$oft, because it is a 
derivate of sgml.  Something which was used in Unix environment 
much more :)
The good thing about xml is that it is readable and understandable 
by everybody who has a basic knowledge of the subject. Designing 
is something different ( like reading a book is easier than write it;) )
Don't see it as a programming language it is at the most a 
database. 
> 
> "In fact, I'd bet people refer to XML as a technology these days only
> because Microsoft has succeeded in its bizarre public relations campaign
> to position XML as a replacement for Java. Microsoft undoubtedly hopes
> that by the time people notice that XML versus Java is a crackbrained
> comparison, Microsoft will have already shoved Java out of the picture
> and replaced it with the C# language. Good luck, Microsoft." 
The (best) server sided  application for XML work on Java  
 I am not that an expert to defend the word best ;)
> The whole text can be found at:
> http://www.linuxworld.com/linuxworld/lw-2001-01/lw-01-penguin_4.html
> 
> I'm no Java evangelist, there are other cross-platform solutions as
> well. Php, Python? Pedro's idea is a good one, I cringe at the thought
> of tainting things with M$ though.
> 
> Paul


I played with the idea of using the php from our Website as an 
interactive Interface to create for example the modules.conf and 
parts of Network.conf, and give the user a kind of a shopping list , 
like in a online shop. 

I do see a security problem in creating and remote controlling the 
LEAF box , as far as it changing the running configuration 
concerns.
If i can do it, somebody else could do it too. ( to be more precisely 
if I can do it everybody else can do it  ;)) 

I personally would prefer to create a  setup script, plattform 
independent and describing my router in detail. This could be done 

This is the script we could exchange for support and so on,

Reply via email to