> Charles....here is some stuff I came across while using PPPOE...dunno if > it's bugs or, what... > > First of all, I would like to know how high up in the scrips is the > EXTERNAL_IP configured..? > Because when using PORTFORWDING with INTERN_POP3_SERVER etc......the folling > happens.. <snip> > Check this out is see if it's possible to make some changes, or do we HAVE > to choose keep the DHCP setting = YES...
This is all an artifact of not having clean PPPoE (or even ppp) support from the outset...what's needed is a way to tell the scripts your IP is dynamic, and to read it directly from the interface. That's what setting EXTERN_DHCP=YES does, but this also interacts with the dhclinet (if you actually load it...with most PPPx setups you shouldn't have to), so it's not exactly optimal. Looks like a couple of tweaks to etc are in order for a PPPoE disk image, with a new way of handling IP assignment in the next major release... > Next I find a little bug in the IPFILTER.conf..... > > if [ -n "$INTERN_POP3_SERVER" ] ; then > > $IPMASQADM portfw -a -P tcp -L $EXTERN_IP pop-3 -R $INTERN_WWW_SERVER > pop-3 > fi > > If we take a good look at the above lines......we are using the if statement > on $INTERN_POP3_SERVER, but on the below line > We are portforwarding it to the $INTERN_WWW_SERVER and the pop-3 protocol... This is a bug...it's been reported before, but somehow didn't get fixed... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
