From: Alan H. <al...@fa...> - 2006-04-28 08:55:13
|
On Fri, 2006-04-28 at 10:09 +0200, Franck Bourdonnec wrote: > Le Vendredi 28 Avril 2006 04:57, Harry Goldschmitt a =C3=A9crit : > > At 8:42 PM -0500 4/27/06, ja...@gu... wrote: > > > > I wan't this features too, but i understand also jackb and the oth= ers. > > >> > > >> Lets think about following: > > >> > > >> We do a initial setup with green/orange/blue/red as in 1.4, > > >> but if a user wants to change green (or orange or red...) > > >> then copy that to greenplus (or green-1 or green-green) where > > >> everything can be changed and disable the original green net. > > >> So we can ask a user if its the green or green-1 'interface'. > > >> > > >> In this way we know that there is anything changed from the origina= l > > >> design and a user can't change the design of original green (from t= he > > >> gui). > > > > > >REAL REAL CLOSE!!! > Designing specs can't be done with two or three mail exchange. > If IPCop 1.5 is still a four fixed interface machine, just say it. > If a major change is allowing any numbers of interfaces, we > have to find best way to implement this. >=20 > We have to mix opinions of > -users > -developpers > -docwriters > -ancestors Agreed. > > Also, please keep in mind us poor documentation types that have to > > document whatever we come up with for folks that don't know > > networking. If we have to document details, we'll loose our current > > simplicity. We currently have pages of documentation trying to > > explain what GREEN, BLUE, ORANGE and RED mean. I hope we won't have > > to have dozens of pages that try to explain the new options. > > > > Harry >=20 > You want have a dozen of 'new page' ! Strange screen like 'blue access' > will disappear. Right. > All top level applications screens (ntp, squid, ...) won't change radical= ly. Yup. > Some messy screens like adslmodem+ppp should be split in to level > -screens discribing hardware link (rnis,adsl,ethX,serial,...) > -screens describing logical interface like ppp0, vpn. I think we could have a single screen here, but with a drop down list of interfaces that IPCop has *detected* only. Then when the user picks that interface. The rest of the screen below adapts to that choice. Much like what we have with pppsetup, but we keep having to click 'refresh' - ugh. > nothing really new here. > simplification is here: >=20 > a unique screen for each network. Allways the same screen > with SIMPLE options listed. > the NAME (color) > the interface it is bound too > the not so big list of rules applied to this interface: > -my IP fixed/dhcp > -checkbox for active service : squid, ntp server, log , snort > -and the firewall rules (buttons to another simple screen): > --list of port transfert > --list of enabled stations (macadress, ip, authen <=3D addon stuff to ext= end=20 > this) > --list of other interface this one can speak with > That 'all >=20 > It is a request users of having 'control' for a network in a single point= and > not to naviguate trought multiple screen to enble this or disable that. Yes. Is it possible for you to work on IPCop 1.5 and change pppsetup.cgi for this Franck ?? You should look at using the /sys directory to probe for hardware that IPCop has found to display in the CGI script. Alan. |