Hi Etienne:
I think is interesting, I just want to express some thougths, let me know
what all of you think:
One way is to implement the logic at the lrp box itself,while may be a
logical way I think it's not the better one.
The way a I think will be more interesting is to be able to read configs from
a (or various) LRP box/es throught a secure channel SSH and be able to change
thinks via web interface in a server machine using anything you like java or
perl or whatever you like, then when finish the config, transfer the files to
the lrp and reboot, probabily with filesafe or other mechanism that can boot
the last working config, may be we broke something more times that we want
:-))
anyway I think it's important to keep the lrp as minimalist in concerns about
security as you can, the space is important but secondary IMHO now that you
can boot from a disk on chip or compactflash with 128 MB or more, but even
that if you use a middle server to do that you can use a normal box and
implement as much logic as you want... I'm listening all of you saying. What
about security of that server.... Ok I let this for discussion too ;-)
Francisco Perez
El Dom 16 Sep 2001 10:13, escribiste:
> Hi,
>
> I'd be happy to contribute to a web interface for LEAF
>
> > If there are more people interested, we could join our efforts :=)
>
> Here are some ideas
>
> First of all, the combinaison LRP/Kernel 2.4/Shorewall is not yet very
> common in
> the LRP world and I can understand the lack of feedback Eric got about his
> web interface.
>
> I think that allowing editing existing files through the web interface is a
> lot of work
> with a very small ROI, an applet java allowing ssh access could do the job
>
> IMHO, What we need is a higher level interface ( Like seawall, you have a
> few
> simple configuration files and a lot of work done with the data in those
> files)
>
> I think we could design the web interface as an editor modifying a big file
> ( config.web)
> containing shell variables definitions and a few scripts which process
> configuration files
> templates, replacing the variables in the templates by the actual values
> from config.web and
> write actual configuration files in the right place.
> example: the local interface ip address ( 192.168.1.254) is used in a lot
> of configuration
> files. the web interface should be able to modify this value "everywhere"
>
> It should be easy to add "modules" to the web interface ( a set of pages
> and a set of templates)
> those pages and templates could be stored in the .LRP files or in separate
> packages (with another
> file extension).
>
> now a few questions:
>
> - Should the interface be usable with the floppy version of a LEAF-like
> distribution ????
> ( https ? to allow remote management isnt't it too big ?)
>
> - Should we try to reuse something exisitng or build from scratch ?
>
> - Could we build our interface so that we could derive from it a set of web
> pages or a set of scripts
> using the dialog command ( being usable from the text console )
>
> - how to permit customizations in the templates outside of the web
> interface ( to allow
> modifications not ( yet ) possible from the web interface ??
>
> - I think that it's a big project but it should be possible
>
> PS: Maybe we could move on the leaf-devel list or elsewhere ??
>
> Regards
> Etienne Charlier
> [EMAIL PROTECTED]
>
>
> _______________________________________________
> Leaf-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-user
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
