On Sat, 26 Jan 2002, guitarlynn wrote:

> On Saturday 26 January 2002 17:42, Jack Coates wrote:
> > Finally got a couple of hours to upgrade my router to Dachstein 1.0.2
> > -- very nice improvement over ES2B. Thanks Charles!
> >
> > One thing that hasn't changed with DS is that there are a ton of
> > places to tweak in order to get a working config. Next time I get a
> > couple of hours, I'm going to take a crack at chopping network.conf
> > down to half size.
>
> Jack, I've just finished some install/config scripts that are on the
> lrcfg menu (added). This allows a simple config to be done in under
> 30 seconds if you have any idea what your doing. I haven't done any
> ppp/pppoe scripts, so those will follow sometime in a different image.
>
> I'm fixing to upload a custom floppy "root.lrp" and a full custom image
> to
>       http://leaf.sourceforge.net/devel/guitarlynn/
>
> here in a few minutes. I think these scripts take right at 15K
> compressed and generate full network.conf and modules files that are
> consistant with Charles files.
>
> These should be much easier for first time users and save some time
> for experienced users.
>
> Any feedback is appreciated.
>

Well, this is a good start, especially with the modules; there used to
be (like LRP version 2.9.4 or something) a web-based configger that
would give end-users a custom kernel and modules.lrp; this looks like
the basis for another one of those.

The network configger doesn't address the thing that was bugging me
though, which is:
a] network.conf is confusing
b] network.conf contains code in addition to data (not sure if it's
possible to break this up).

Having EXTERN_DHCP and EXTERN_DYNADDR both in there just confuses
things. There should just be two options, dynamic or static. Of course
since I don't use PPPoE there might be something I don't know about
causing this; still that should be clearly commented. If the external
interface isn't dynamic, then EXTERN_IP should auto-set to
\$"$EXTERN_IF"_IPADDR.

The Internal Interface section should be pulled up below External
Interface and above SILENT_DENY. Once $INTERN_IF is set, INTERN_NET and
INTERN_IP should be auto-set again.

It's difficult to ascertain which sections of the opened ports and
portforwards are relevant. New headers would do it:

#####################################################
# Ports to open -- these must be opened for services
# that are hosted on or behind the firewall.
#####################################################
SILENT_DENY
EXTERN_ICMP/UDP/TCP/GENERIC

#####################################################
# Port-forward an aliased or bridged IP here
#####################################################
INTERN_SERVERS="tcp_${EXTERN_IP}_ftp_192.168.1.1_ftp"

#####################################################
# Port-forward the primary external IP here
#####################################################
INTERN_FTP_SERVER=192.168.1.1  # Internal FTP server


-- 
Jack Coates
Monkeynoodle: A Scientific Venture...


_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user

Reply via email to