date:20011116

Title: Bad directory Error Message -- Dachstein RC5





Hello, fellow Dachstein users...


I receive this message at my ROUTER's Console, and in the Messages Log...can some one tell me what its' referring to
Nov 16 09:30:02 (none) kernel: free_one_pmd: bad directory entry 0400
Nov 16 09:30:02 (none) kernel: free_one_pmd: bad directory entry 0400
Nov 16 09:30:02 (none) kernel: free_one_pmd: bad directory entry 0800
Nov 16 09:30:02 (none) kernel: free_one_pmd: bad directory entry 0800
Nov 16 09:30:02 (none) kernel: free_one_pmd: bad directory entry 0400
Nov 16 09:30:02 (none) last message repeated 2 times
Nov 16 09:45:02 (none) kernel: free_one_pmd: bad directory entry 0800
Nov 16 09:45:02 (none) kernel: free_one_pmd: bad directory entry 0400
Nov 16 10:15:02 (none) kernel: free_one_pmd: bad directory entry 0800 


Background Info...
I486 DX/100Mhz
32 Mb Ram
Cable  Modem using PPPOE
RamDrive 12mb
Firewall = OK
Memory = OK
RamDrive = Ok
thnks

[Leaf-user] Dachstein RC5 PPPOE

Title: Dachstein RC5 PPPOE

Charles...

As u mentioned weeks ago, u need some "Rabbits" to test the PPPOE in RC3/4/5 seeing that u don't have access to PPPOE Provider..

Well, I'm busy doing some testing, and have some nice things to report..

** Connection is going like a charm, just like it did in EigerStein..
** From my end, I see no difference in connectivity/speed.
** I see no difference in the connection process, so to speak (no problems)

One little request, which I do believe that most ot the PPPOE users would love.
Most PPPOE providers give a DHCP Lease IP, and it's no fun to have a nice hi speed internet connection without any means of connnecting to it from off the road,

The onliest way for us to connect to a Stupid Dynamic ip is vis DDNS, which is provided by some nice DDNS provider..

I was stucked looking for all kind of tools/utils to get my Connection known to the world (stupied me), but I managed to found a nice tool.

ez-ipupd.lrp..

Currently I have it on my BootFlop, I would like to know if u can include it in your next Release of Dachstein, for the PPPOE users,

*** Note ***
Charles, if I should use a RW Cd-Rom, and copy some of these packages to the CD, and include them to run from the lrpkg file, would this work without any problems, or

Is there some hidden script on the CD, that keeps track of the file ORIGINALLY included in your RELEASE..

Let me know if I can test any PPPOE issues for u.(one note, I'm still and NEWBIE) know some Linux Basics...enough to build and do little trouble shoot

Thnks
Reggie

[Leaf-user] Dachstein RC5 -- Hostname problem

Title: Dachstein RC5 -- Hostname problem





Hello Dachstein users...once again..



During the startup of my router, at the point where the hostname is to be configured, I get the following error message:

"Hostname: set hostname: Invalid Argument"


And once my router is started, in place of giving me the hostname is the PROMPT, it just displays "NONE"


When I try to execute the hostname - F /etc/hostname, just as it is in the startup script...I get the same error message listed above..

Any suggestions.???


Reggie

[Leaf-user] Init CPU usage

2001-11-16 Thread Kiril


hello list

i am using lrp 2.9.8 as a base for a thin server. following peculiarity
attracted my attention:

the init process is very active (ps aux shows about 15 times the cpu usage
of an idling ftp server) for about 10 minutes after boot up. after that,
init uses virtually no cpu (as one would expect).

could this be a hint of some misconfiguration somewhere?

i use proftpd, thttpd, qmail, vpopmail, procmail, sshd, most supervised by
daemontools. everything works perfectly, except that it makes no sense to me
why init is so active so long after boot up.

any hints will be appreciated :-)

kiril

btw, if someone needs vpopmail or procmail compiled for lrp - i should be
able to make .lrp out of the binaries.


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

RE: [Leaf-user] RC5 -- SSHD


Thnks...

This did the trick...

Well, actually when I use Dachsten RC3 for the Very, very, first time, I did
the partial backup, and for some reason or the other, my packages were not
being loaded from the floppy, so it was not until I tried the FULL, I saw it
working properly, so that's why I was till using the FULL, but probaly that
boot problem was due to some other config settings I had set incorrectly...
But it's working now

-Original Message-
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, November 15, 2001 14:29
To: Reginald R. Richardson; [EMAIL PROTECTED]
Subject: Re: [Leaf-user] RC5 -- SSHD


> I need some help on this small little issue..
>
> I'm running RC5 of Charles greatest work of the day, but before I make 
> a backup of my SSHD daemon 3.x from J. Nilo, I have about 86% disk 
> space on
my
> Boot flop, (My x486 is not CD-Bootable)...
> Once I try to save the package, it tells me there is not enough 
> space. Currently on my boot flop I only have weblet.lrp root.lrp 
> modules.lrp dnscache.lrp pppoe.lrp and etc.lrp
>
> Can someone explain  to me why is SSHD so large, it's looking for 
> about
300k
> where I only have 231k left over..
>
> Charles maybe u can answer this one...
>
> I was looking in the LRP pakages on the CD, to see if I can find the 
> .conf files for some of the packages that I know won't change to often 
> at my
site,
> eg DNSCACHE, WEBLET, so that I can modify the settings there, and 
> won't
have
> to save them to flop, so that I can have some space over for other
pakages,
> that might need regular changes..

I think you're missing one of the major points of using the CD...you don't
have to backup the full package to your floppy.  Please note, however, that
until you do a partial backup to your config floppy, the default backup type
for all packages is "full".

You should go to the lrcfg backup menu, and type "t e" followed by "p", to
set the backup type for everything to partial.  Then do "d e" and select
your floppy as the destination for all backups.  Finally, backup any
packages you've configured...you should find you have plenty of disk space.

Sorry this is not explained better in the documentation...

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

[Leaf-user] Dachstein RC5

2001-11-16 Thread Bob Smith


Hi,

I am currently using LRP 2.9.8 and I am very happy, with the exception of
getting inbound Netmeeting sessions to work.

I am interested in using the CD version (Dachstein) and have seen references
to RC5. What is the process for making the CD. Is there an ISO image, or do
I have to download the modules and burn them? What would the link be to get
to the CD file?

I have searched the mail archive, been all over Charles site including
http://lrp.steinkuehler.net/DiskImages/Dachstein.htm and
leaf.sourceforge.net, but have not been able to find out about the CD Image.

Any help would be appreciated.

Cheers

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

RE: [Leaf-user] Dachstein RC5

Follow this link, and you'll find ISO Images, that u can just burn

http://lrp.steinkuehler.net/files/diskimages/dachstein-CD/

-Original Message-
From: Bob Smith [mailto:[EMAIL PROTECTED]] 
Sent: Friday, November 16, 2001 15:03
To: [EMAIL PROTECTED]
Subject: [Leaf-user] Dachstein RC5

Hi,

I am currently using LRP 2.9.8 and I am very happy, with the exception of
getting inbound Netmeeting sessions to work.

I am interested in using the CD version (Dachstein) and have seen references
to RC5. What is the process for making the CD. Is there an ISO image, or do
I have to download the modules and burn them? What would the link be to get
to the CD file?

I have searched the mail archive, been all over Charles site including
http://lrp.steinkuehler.net/DiskImages/Dachstein.htm and
leaf.sourceforge.net, but have not been able to find out about the CD Image.

Any help would be appreciated.

Cheers

___
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

Re: [Leaf-user] Dachstein RC5 PPPOE


> Well, I'm busy doing some testing, and have some nice things to report..
>
> ** Connection is going like a charm, just like it did in EigerStein..
> ** From my end, I see no difference in connectivity/speed.
> ** I see no difference in the connection process, so to speak (no
problems)

Good news!  And I'm currently supporting a user in France, whose PPPoE
connection is working fine...I've even got a VPN link running over it.

> I was stucked looking for all kind of tools/utils to get my Connection
known
> to the world (stupied me), but I managed to found a nice tool.
> ez-ipupd.lrp..
>
> Currently I have it on my BootFlop, I would like to know if u can include
it
> in your next Release of Dachstein, for the PPPOE users,

I probably won't add this to the CD by default (there's just too much stuff
for me to try and put everything on there), but you can add it
yourself...see below

> *** Note ***
> Charles, if I should use a RW Cd-Rom, and copy some of these packages to
the
> CD, and include them to run from the lrpkg file, would this work without
any
> problems, or
> Is there some hidden script on the CD, that keeps track of the file
> ORIGINALLY included in your RELEASE..

There's nothing in the CD that 'knows' what packages are on my original CD
distribution.  You can add (or remove) packages from a local copy of the
CD-Contents directory, and run the mkisofs command in the readme file to
build a new image.  You can also build a new image on a windows system, but
you'll have to see your CD-Burner software documentation for making a
bootable CD...

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

Re: [Leaf-user] Dachstein RC5 -- Hostname problem


> During the startup of my router, at the point where the hostname is to be
> configured, I get the following error message:
>
> "Hostname: set hostname: Invalid Argument"
>
> And once my router is started, in place of giving me the hostname is the
> PROMPT, it just displays "NONE"
>
> When I try to execute the hostname - F /etc/hostname, just as it is in the
> startup script...I get the same error message listed above..
>
> Any suggestions.???

What are the contents of /etc/hostname?

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

Re: [Leaf-user] dmzSpoof


> I've got Dachstein RC5  running and trying to put the final touches on it.
>
> I've got a Counter-Strike server spitting into to another server inmy DMZ.
> I've tried to open this port to allow the info to pass thru into the DMZ
but
> for some reason I just can't figure this one out.
>
> I've tried opening the port up but.
>
> router kernel: Packet log: dmzSpoof DENY eth0 PROTO=17 64.1.132.140:27016
> 64.1.132.143:2002

More details, please.  What sort of DMZ are you trying to setup?  In
general, the dmzSpoof rule denies packets from the outside world that should
have come from the DMZ.  If you've got a block of IP's and are running a
proxy-arp or static-NAT DMZ, you probably have a problem with DMZ_EXT_ADDRS,
which is how the firewall rules know which IP's are on which side of the
router.

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

Re: [Leaf-user] dmzSpoof

2001-11-16 Thread Alec Miller


sorry...

Ok...I've got a C-Strike server on the outside of my network, unmanaged by
anything.  It is fowarding log files/info from port 27016 to a remote www
server on port 2002 inside the NAT'd DMZ.


- Original Message -
From: Charles Steinkuehler <[EMAIL PROTECTED]>
To: Alec Miller <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, November 16, 2001 8:07 AM
Subject: Re: [Leaf-user] dmzSpoof


> I've got Dachstein RC5  running and trying to put the final touches on it.
>
> I've got a Counter-Strike server spitting into to another server inmy DMZ.
> I've tried to open this port to allow the info to pass thru into the DMZ
but
> for some reason I just can't figure this one out.
>
> I've tried opening the port up but.
>
> router kernel: Packet log: dmzSpoof DENY eth0 PROTO=17 64.1.132.140:27016
> 64.1.132.143:2002

More details, please.  What sort of DMZ are you trying to setup?  In
general, the dmzSpoof rule denies packets from the outside world that should
have come from the DMZ.  If you've got a block of IP's and are running a
proxy-arp or static-NAT DMZ, you probably have a problem with DMZ_EXT_ADDRS,
which is how the firewall rules know which IP's are on which side of the
router.

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

Re: [Leaf-user] Wishing to upgrade to Dachstein


> I have a slightly older version of Charles' LRP, with plenty of settings I
> have made and some extra masq modules.  What I need to know is:  What do I
> do to bring my version up to Dachstein without finding and recreating all
> the little settings I have made?  Is this going to be an easy upgrade?
>
> I have been using an IDE version almost since I started.  I have copied
down
> the "normal" Dachstein which, upon reading, has IDE support and the
> necessary VPN (for future, I don't yet use that) in the kernal.  So I'm
> thinking that it shouldn't be too bad.  Another concern is if the masq
> modules are compatible and if I can locate updated ones if necessary.

I think you will find most masquerading modules are now available in the
default kernel build.  You will have to check to be sure...compare what
you're running (use lsmod to find out) with the modules available in the new
kernel tree:
http://lrp.steinkuehler.net/files/kernels/Dachstein-normal/modules/
or
http://lrp.steinkuehler.net/files/kernels/Dachstein-small/modules/

For your configuration, I suggest you migrate your existing network.conf
settings to the new firewall manually.  I normally do this with the
following general procedure:

Rename your existing etc.lrp somehing else (like etcx.lrp) or copy it to a
different disk so it won't get loaded.

Delete your existing modules.lrp, and replace with the modules package from
Dachstein

Boot into Dachstein using the default Dachstein etc.lrp

Configure your modules, adding any required modules not in the default
package, and deleting any you don't need.  Verify everything works using
"svi modultils start", and backup modules.

Unpack your old etc into /tmp.  With the disk containing your old etc
(etcx.lrp) mounted on /mnt, do the following:
  cd /tmp
  zcat /mnt/etcx.lrp | tar -xv

This will put your old etc directory in /tmp/etc.

Copy over any files you may have manually created/modified.  Possibilities
include: crontab, fstab, hostname, ipchains.*, localtime, nsswitch...

Manually merge your settings from your previous network.conf file into the
new network.conf

Reload the firewall rules and verify they match your previous rules.  I like
to create and print out a list of the ipchains rules from my running system,
then build a new configuration on a test machine, comparing it's
configuration with the hardcopy previous config.  When they match (or I know
why they differ), I migrate the test configuration to my production
firewall.  You may find both the output of "svi network ipfilter list" and
"ipchains -nvL --line-numbers" to be useful.

Backup etc

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

RE: [Leaf-user] Dachstein RC5 -- Hostname problem

2001-11-16 Thread Sandro Minola


hi charles, hi reginald

i had the same problem some weeks ago and i also posted it. i got some
replies, but they didn't fix the problem. i fixed it by myself. here the
part of my post:

>The Problem was, that the "hostname" command didn't accept any comments
>in the /etc/hostname file ("hostname - Bad argument"). It seems to be a
>Busybox problem of my Busybox version (0.51).
>Now it works. I removed the echo "Autmatic added by..." > /etc/hostname
>and changed
>echo "$HOSTNAME" >> /etc/hostname into
>echo "$HOSTNAME > /etc/hostname

I'm NOT using Dachstein RC5 but it can probably be the same kind of problem.

I hope this help, but I'm pretty sure that it can't be a general problem
because Charles would noticed it.

Have a nice weekend

---
Sandro Minola   | LEAF Developer (http://leaf.sourceforge.net)
mailto:[EMAIL PROTECTED] | mailto:[EMAIL PROTECTED]
http://www.minola.ch| http://leaf.sourceforge.net/devel/sminola
-
worldcontrol:~ # rm -rf /bin/laden

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Charles
> Steinkuehler
> Sent: Friday, November 16, 2001 3:06 PM
> To: Reginald R. Richardson; [EMAIL PROTECTED]
> Subject: Re: [Leaf-user] Dachstein RC5 -- Hostname problem
>
>
> > During the startup of my router, at the point where the
> hostname is to be
> > configured, I get the following error message:
> >
> > "Hostname: set hostname: Invalid Argument"
> >
> > And once my router is started, in place of giving me the hostname is the
> > PROMPT, it just displays "NONE"
> >
> > When I try to execute the hostname - F /etc/hostname, just as
> it is in the
> > startup script...I get the same error message listed above..
> >
> > Any suggestions.???
>
> What are the contents of /etc/hostname?
>
> 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


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

RE: [Leaf-user] QoS on eth0 - not possible if using DHCP !?

2001-11-16 Thread Sandro Minola


hi jack, hi all

> Seriously, how are you determining that the rules aren't applying?
I turned on FAIRQ/QoS on eth0 and txqlen is not set. I mean, i set
eth0_TXQLEN to 500 and run svi network reload. If i look at the output from
"ip addr", txqlen of eth0 is still 100 (standard setting). I assume that all
other parameters are not set too, then.
I also checked Charles network script which reads network.conf. only
interfaces in $IF_LIST (which is the same as $IF_AUTO because every
network.conf is like this: IF_LIST="$IF_AUTO") are configured by
/etc/init.d/network. or am i wrong?

thank you for your example. do you have experiences with turning QoS on on
the internal interface to queue incoming traffic?

Have a nice weekend

---
Sandro Minola   | LEAF Developer (http://leaf.sourceforge.net)
mailto:[EMAIL PROTECTED] | mailto:[EMAIL PROTECTED]
http://www.minola.ch| http://leaf.sourceforge.net/devel/sminola
-
worldcontrol:~ # rm -rf /bin/laden



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

Re: [Leaf-user] Dachstein RC5 -- Hostname problem


> i had the same problem some weeks ago and i also posted it. i got some
> replies, but they didn't fix the problem. i fixed it by myself. here the
> part of my post:
>
> >The Problem was, that the "hostname" command didn't accept any comments
> >in the /etc/hostname file ("hostname - Bad argument"). It seems to be a
> >Busybox problem of my Busybox version (0.51).
> >Now it works. I removed the echo "Autmatic added by..." >
/etc/hostname
> >and changed
> >echo "$HOSTNAME" >> /etc/hostname into
> >echo "$HOSTNAME > /etc/hostname
>
> I'm NOT using Dachstein RC5 but it can probably be the same kind of
problem.
>
> I hope this help, but I'm pretty sure that it can't be a general problem
> because Charles would noticed it.

This definately WAS a problem...the busybox hostname command was VERY
broken.  I fixed this, and included the updated hostname command in RC4.
Versions RC4 and later should not suffer from the "comment in /etc/hostname
file" bug, and the network scripts returned to adding the warning line
before the hostname.

Can you verify which CD version you're running, and if you boot off a
floppy, make sure you copied the latest root.lrp to your floppy?

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

RE: [Leaf-user] Dachstein RC5 -- Hostname problem


Thnks guys..

The "root.lrp" was indeed the problem, I was still running root.lrp from
RC3, after copying it from the RC5 Cd to the boot flop PROBLEMO was
Solved


cheers

-Original Message-
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]] 
Sent: Friday, November 16, 2001 16:49
To: Sandro Minola; Reginald R. Richardson; [EMAIL PROTECTED]
Subject: Re: [Leaf-user] Dachstein RC5 -- Hostname problem


> i had the same problem some weeks ago and i also posted it. i got some 
> replies, but they didn't fix the problem. i fixed it by myself. here 
> the part of my post:
>
> >The Problem was, that the "hostname" command didn't accept any 
> >comments in the /etc/hostname file ("hostname - Bad argument"). It 
> >seems to be a Busybox problem of my Busybox version (0.51). Now it 
> >works. I removed the echo "Autmatic added by..." >
/etc/hostname
> >and changed
> >echo "$HOSTNAME" >> /etc/hostname into
> >echo "$HOSTNAME > /etc/hostname
>
> I'm NOT using Dachstein RC5 but it can probably be the same kind of
problem.
>
> I hope this help, but I'm pretty sure that it can't be a general 
> problem because Charles would noticed it.

This definately WAS a problem...the busybox hostname command was VERY
broken.  I fixed this, and included the updated hostname command in RC4.
Versions RC4 and later should not suffer from the "comment in /etc/hostname
file" bug, and the network scripts returned to adding the warning line
before the hostname.

Can you verify which CD version you're running, and if you boot off a
floppy, make sure you copied the latest root.lrp to your floppy?

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

[Leaf-user] Easy upgrade to Dachstein 1.0.0

2001-11-16 Thread Victor McAllisteer


I started playing with Dachstein RC5 last night.  I am very
impressed.  Now that RC5 has been replaced with version 1.0.0, all I
have to do is burn another CD and keep the same configuration floppy.
I love it.  Upgrades are so simple.  Thanks Charles.

 http://leaf.sourceforge.net/devel/cstein/files/diskimages/dachstein-CD/

--
Victor McAllister



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

RE: [Leaf-user] Dachstein RC5 PPPOE


Charleshere 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..

If I do EXTERN_DHCP=NO, when INTERN_XXX_SERVER is on, IPCHAINS spits out,
some messages stating that he can't find internal server, this is
Because the EXTERNAL_IP is not set some where in the NETWORK.conf

When I look at this line 

eval EXTERN_IP=\"\${"$EXTERN_IF"_IPADDR:-""}\"

I assume this is where it's defining the External IP if DHCP is not = YES,
but at this point in time PPPOE is not yet RUNNED to get the External IP, so
therefore IPCHAINS starts complaining..

I don't know if it's really necessay to say EXTERN_DHCP=YES is needed for
PPPOE since it's not USING DHCP, I confirm that we still get an IP
If this setting = NOi do believe maybe the PPPOE scrips should be run
some where before the ipfilter.conf is run..

The DHCP scripts does this by giving some BOGUS ip addres for EXTERNAL so
that IPFILTER don't start complaing...

Check this out is see if it's possible to make some changes, or do we HAVE
to choose keep the DHCP setting = YES...


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...



Please do confirm on the above, let me know, if I'm not seeing correctly of
if these are indeed some minor GLITCHES..


Cheers

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

Re: [Leaf-user] packages in the oxygen directory

2001-11-16 Thread Matt Schalit

[EMAIL PROTECTED] wrote:
> 
> Hi all and especially to David,
> 
> I have downloaded some of the packages from the oxygen packages list
> and tried them on my eigerstein beta2 but they all seem to segfault.
> 
> I am talking especially about ethereal and winscan, is this a library problem
> or a kernel version issue? And is it fixable without switching over to an
> oxygen distribution? Because I got quite accustomed to my eigerstein config?
> 
> Thanks in advance.
> 
> Kim

I think it's because ethereal was compiled against 
glibc-2.1.3, whereas your ES2B is a glibc-2.0.x.  I'm 
not positive how David compiled that one, though. I can 
tell you that the current Oxygen runs on kernel 2.2.19.

Here's the info I can give you from installing it and 
running it on Oxygen.

File list:
-
# cat /var/lib/lrpkg/ethereal.list
usr/sbin/editcap
usr/sbin/tethereal
usr/lib/libz.so
usr/lib/libz.so.1
usr/lib/libz.so.1.1.3
usr/lib/libglib-1.2.so.0.0.6
usr/lib/libglib-1.2.so
usr/lib/libglib.so.1
usr/lib/libglib-1.2.so.0
usr/lib/libglib.so.1.0.6
usr/lib/libm-2.1.3.so
usr/lib/libglib.so
usr/lib/libgmodule-1.2.so.0
usr/lib/libgmodule-1.2.so.0.0.6
usr/lib/libsnmp.so.0.4.1.1
usr/lib/libgmodule.so
usr/lib/libsnmp.so.0
usr/lib/libm.so.6
var/lib/lrpkg/ethereal.*

Ethereal brings a lot of libraries over.
-

# ldd /usr/sbin/tethereal
libsnmp.so.0 => /usr/lib/libsnmp.so.0 (0x00125000)
libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x00163000)
libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x00166000)
libdl.so.2 => /lib/libdl.so.2 (0x00189000)
libm.so.6 => /usr/lib/libm.so.6 (0x0018e000)
libz.so.1 => /usr/lib/libz.so.1 (0x001ab000)
libc.so.6 => /lib/libc.so.6 (0x001ba000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0011)

# tethereal --help
Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (IF-MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
Cannot find module (UDP-MIB): At line 0 in (none)
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (SNMPv2-SMI): At line 0 in (none)
Cannot find module (UCD-SNMP-MIB): At line 0 in (none)
Cannot find module (UCD-DEMO-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-TYPES): At line 0 in (none)
Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 0 in (none)
Cannot find module (SNMP-COMMUNITY-MIB): At line 0 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 0 in (none)
Cannot find module (SNMP-MPD-MIB): At line 0 in (none)
Cannot find module (SNMP-USER-BASED-SM-MIB): At line 0 in (none)
tethereal: invalid option -- -
This is GNU tethereal 0.8.15, compiled with GTK+ (version unknown), with libpcap 0.4, 
with libz 1.1.3, with UCD SNMP 4.0.1
tethereal [ -vVhlp ] [ -c count ] [ -f  ]
[ -F  ] [ -i interface ] [ -n ]
[ -o  ] ... [ -r infile ] [ -R  ]
[ -s snaplen ] [ -t  ] [ -w savefile ] [ -x ]
Valid file type arguments to the "-F" flag:
libpcap - libpcap (tcpdump, Ethereal, etc.)
rh6_1libpcap - Red Hat Linux 6.1 libpcap (tcpdump)
suse6_3libpcap - SuSE Linux 6.3 libpcap (tcpdump)
modlibpcap - modified libpcap (tcpdump)
nokialibpcap - Nokia libpcap (tcpdump)
ngsniffer - Network Associates Sniffer (DOS-based)
snoop - Sun snoop
netmon1 - Microsoft Network Monitor 1.x
ngwsniffer_1_1 - Network Associates Sniffer (Windows-based) 1.1
default is libpcap

Just a little info to help you diagnose your setup
and whether it's useful to persue this ethereal.  I'm
going to pass on the winscan analysis :)
Matthew

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

[Leaf-user] The script to send log files

2001-11-16 Thread Binh Do


Hi Robert, I like the idea of sending the log files periodically. Could you
share it with us?

Thank you.

-Original Message-

From: Robert Williams <[EMAIL PROTECTED]>

>> I just upgraded to Dachstien CD rc5 from rc4. I have crontab
>>  scheduled to email me my logs which it has been doing faithfully
>>  until today. Somehow the name lookup fails from the router. DNS is


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

Re: [Leaf-user] The script to send log files

2001-11-16 Thread Robert Williams


Hi Binh,
It's quite easy to have your fire wall email you your logs. I have them sent every 
morning after the logs are rotated. I have appended the following line to my 
/etc/crontab file. It is on one line with no breaks. Try the mail command on the 
command line to make sure that you mail settings are set up correctly. They are 
configured in /etc/POSIXness.conf.

56 6* * *   rootmail -s "Logs" [EMAIL PROTECTED] < /var/log/messages.0

Let me know if you have any problems.
Robert Williams


>Hi Robert, I like the idea of sending the log files periodically. Could you
>share it with us?
>
>Thank you.
>
>-Original Message-
>
>From: Robert Williams <[EMAIL PROTECTED]>
>
>>> I just upgraded to Dachstien CD rc5 from rc4. I have crontab
>>>  scheduled to email me my logs which it has been doing faithfully
>>>  until today. Somehow the name lookup fails from the router. DNS is
>
>
>___
>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

RE: [Leaf-user] Wishing to upgrade to Dachstein

2001-11-16 Thread John Mullan


Thanks Charles.  I'll be giving this a try on the weekend.  I'll post my
successes/failures.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Charles
Steinkuehler
Sent: Friday, November 16, 2001 9:26 AM
To: John Mullan; Leaf-User
Subject: Re: [Leaf-user] Wishing to upgrade to Dachstein


> I have a slightly older version of Charles' LRP, with plenty of settings I
> have made and some extra masq modules.  What I need to know is:  What do I
> do to bring my version up to Dachstein without finding and recreating all
> the little settings I have made?  Is this going to be an easy upgrade?
>
> I have been using an IDE version almost since I started.  I have copied
down
> the "normal" Dachstein which, upon reading, has IDE support and the
> necessary VPN (for future, I don't yet use that) in the kernal.  So I'm
> thinking that it shouldn't be too bad.  Another concern is if the masq
> modules are compatible and if I can locate updated ones if necessary.

I think you will find most masquerading modules are now available in the
default kernel build.  You will have to check to be sure...compare what
you're running (use lsmod to find out) with the modules available in the new
kernel tree:
http://lrp.steinkuehler.net/files/kernels/Dachstein-normal/modules/
or
http://lrp.steinkuehler.net/files/kernels/Dachstein-small/modules/

For your configuration, I suggest you migrate your existing network.conf
settings to the new firewall manually.  I normally do this with the
following general procedure:

Rename your existing etc.lrp somehing else (like etcx.lrp) or copy it to a
different disk so it won't get loaded.

Delete your existing modules.lrp, and replace with the modules package from
Dachstein

Boot into Dachstein using the default Dachstein etc.lrp

Configure your modules, adding any required modules not in the default
package, and deleting any you don't need.  Verify everything works using
"svi modultils start", and backup modules.

Unpack your old etc into /tmp.  With the disk containing your old etc
(etcx.lrp) mounted on /mnt, do the following:
  cd /tmp
  zcat /mnt/etcx.lrp | tar -xv

This will put your old etc directory in /tmp/etc.

Copy over any files you may have manually created/modified.  Possibilities
include: crontab, fstab, hostname, ipchains.*, localtime, nsswitch...

Manually merge your settings from your previous network.conf file into the
new network.conf

Reload the firewall rules and verify they match your previous rules.  I like
to create and print out a list of the ipchains rules from my running system,
then build a new configuration on a test machine, comparing it's
configuration with the hardcopy previous config.  When they match (or I know
why they differ), I migrate the test configuration to my production
firewall.  You may find both the output of "svi network ipfilter list" and
"ipchains -nvL --line-numbers" to be useful.

Backup etc

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


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

[Leaf-user] Dachstein

2001-11-16 Thread Hilton Travis


Rocks.  I just changed from Tel$tra cable to Optus@home cable, downloaded
Dachstein RC2, and installed it fine.  works a treat.

I'll be making images for Tel$tra BigPond and Optus users, and replacing my
earlier images on http://quarkau.cjb.net when I get back from camping next
week.

Regards,
Hilton Travis


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

[Leaf-user] Dachstein-CD: dnscache vs. tinydns ???



OK, this is really not about Dachstein, although that is the
distribution that we're using ;>

What are the primary differences between dnscache and tinydns ???

What are the criteria we ought to consider, in deciding which to deploy?

What do you think?

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .

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

[Leaf-user] Dachstein-CD: tinydns startup error ???



/etc/rc2.d/S47tinydns: UID: readonly variable

Is this a bash thingy?

I notice that my environment always contains the UID variable that
always points to my current UID . . .

What do you think?

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .

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

Re: [Leaf-user] Dachstein-CD: dnscache vs. tinydns ???

2001-11-16 Thread Jacques Nilo


> OK, this is really not about Dachstein, although that is the
> distribution that we're using ;>
>
> What are the primary differences between dnscache and tinydns ???
http://leaf.sourceforge.net/devel/jnilo/dnscache1.html
http://leaf.sourceforge.net/devel/jnilo/tinydns1.html

> What are the criteria we ought to consider, in deciding which to
deploy?
Really two different needs. If you only need to access the web dnscache
will speed up your requests (that is the "cache" part of it) but it will
also make your request more secure.
Tinydns is needed if you want to serve the adresses of your domain(s).
Basically it will be here a replacement for BIND (in fact BIND combines
the dnscache & tinydns function in the same program). But tinydns is
much more secure and a LOT LOT smaller (compare size of tinydns.lrp &
bind.lrp :-) )
Background material here:
http://leaf.sourceforge.net/devel/jnilo/dnscache6.html

Jacques


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

[Leaf-user] Announcing official release of Dachstein-CD


The official release (v1.0.1) of Dachstein-CD is now available for download
from the usual places:
slow:
http://lrp.steinkuehler.net/files/diskimages/dachstein-CD/
fast:
http://lrp1.steinkuehler.net/files/diskimages/dachstein-CD/
http://lrp2.steinkuehler.net/files/diskimages/dachstein-CD/

There was a 'silent' release of v1.0.0 for internal use yesterday.  Changes
from the last release candidate include configuration tweaks (dnscache and
ipsec), the inclusion of the ipsec binaries patched for x.509 certificate
support, and fixes to a couple minor bugs (a problem with the POSIXness cut
command, and setting custom backup destinations didn't work properly).

With a couple minor updates to root.lrp, folks booting off floppy will need
to copy the latest root.lrp to their floppy disk to get the updates.
Otherwise, just pop in the new CD and re-boot...

--
Changes from Dachstein-CD v1.0.0 to Dachstein-CD v1.0.1:
--

Modified dnscache package configuration:
  listen IP changed to 0.0.0.0
  127.0.0.1 added to allowed query IPs

Fixed bug when setting custom backup destinations

root version changed to 4.0.5

--
Changes from Dachstein-CD rc5 to Dachstein-CD v1.0.0:
--

POSIXness cut fixed to handle regex and sed special characters as delimiters

root version changed to 4.0.4

Updated README.txt

Modified ipsec.lrp (now backs up all /etc/ipsec* files, allowing an
  /etc/ipsec/ directory or ipsec.*.conf for configuration include files)

Added ipsec509.lrp (x.509 patched versions of pluto and auto) for folks
  using certificates

--

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

RE: [Leaf-user] Announcing official release of Dachstein-CD

Charles, u ain't joking, u giving food for thaught faster than M$, do u ever
sleep dude...?

cheers

-Original Message-
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]] 
Sent: Friday, November 16, 2001 17:07
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [Leaf-user] Announcing official release of Dachstein-CD

The official release (v1.0.1) of Dachstein-CD is now available for download
from the usual places:
slow: http://lrp.steinkuehler.net/files/diskimages/dachstein-CD/
fast: http://lrp1.steinkuehler.net/files/diskimages/dachstein-CD/
http://lrp2.steinkuehler.net/files/diskimages/dachstein-CD/

There was a 'silent' release of v1.0.0 for internal use yesterday.  Changes
from the last release candidate include configuration tweaks (dnscache and
ipsec), the inclusion of the ipsec binaries patched for x.509 certificate
support, and fixes to a couple minor bugs (a problem with the POSIXness cut
command, and setting custom backup destinations didn't work properly).

With a couple minor updates to root.lrp, folks booting off floppy will need
to copy the latest root.lrp to their floppy disk to get the updates.
Otherwise, just pop in the new CD and re-boot...

--
Changes from Dachstein-CD v1.0.0 to Dachstein-CD v1.0.1:
--

Modified dnscache package configuration:
  listen IP changed to 0.0.0.0
  127.0.0.1 added to allowed query IPs

Fixed bug when setting custom backup destinations

root version changed to 4.0.5

--
Changes from Dachstein-CD rc5 to Dachstein-CD v1.0.0:
--

POSIXness cut fixed to handle regex and sed special characters as delimiters

root version changed to 4.0.4

Updated README.txt

Modified ipsec.lrp (now backs up all /etc/ipsec* files, allowing an
  /etc/ipsec/ directory or ipsec.*.conf for configuration include files)

Added ipsec509.lrp (x.509 patched versions of pluto and auto) for folks
  using certificates

--

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

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

RE: [Leaf-user] Announcing official release of Dachstein-CD


Charles

I found the bug, I confirm it in Dachstein 1.01

if [ -n "$INTERN_POP3_SERVER" ] ; then
$IPMASQADM portfw -a -P tcp -L $EXTERN_IP pop-3 -R $INTERN_WWW_SERVER
pop-3

Check it out, and post some kind of advisory notes for fellow USERS>.


reggie

-Original Message-
From: Reginald R. Richardson [mailto:[EMAIL PROTECTED]] 
Sent: Friday, November 16, 2001 18:45
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [Leaf-user] Announcing official release of Dachstein-CD


Charles, u ain't joking, u giving food for thaught faster than M$, do u ever
sleep dude...?

cheers

-Original Message-
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]] 
Sent: Friday, November 16, 2001 17:07
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [Leaf-user] Announcing official release of Dachstein-CD


The official release (v1.0.1) of Dachstein-CD is now available for download
from the usual places:
slow: http://lrp.steinkuehler.net/files/diskimages/dachstein-CD/
fast: http://lrp1.steinkuehler.net/files/diskimages/dachstein-CD/
http://lrp2.steinkuehler.net/files/diskimages/dachstein-CD/

There was a 'silent' release of v1.0.0 for internal use yesterday.  Changes
from the last release candidate include configuration tweaks (dnscache and
ipsec), the inclusion of the ipsec binaries patched for x.509 certificate
support, and fixes to a couple minor bugs (a problem with the POSIXness cut
command, and setting custom backup destinations didn't work properly).

With a couple minor updates to root.lrp, folks booting off floppy will need
to copy the latest root.lrp to their floppy disk to get the updates.
Otherwise, just pop in the new CD and re-boot...

--
Changes from Dachstein-CD v1.0.0 to Dachstein-CD v1.0.1:
--

Modified dnscache package configuration:
  listen IP changed to 0.0.0.0
  127.0.0.1 added to allowed query IPs

Fixed bug when setting custom backup destinations

root version changed to 4.0.5

--
Changes from Dachstein-CD rc5 to Dachstein-CD v1.0.0:
--

POSIXness cut fixed to handle regex and sed special characters as delimiters

root version changed to 4.0.4

Updated README.txt

Modified ipsec.lrp (now backs up all /etc/ipsec* files, allowing an
  /etc/ipsec/ directory or ipsec.*.conf for configuration include files)

Added ipsec509.lrp (x.509 patched versions of pluto and auto) for folks
  using certificates

--

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

___
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

Re: [Leaf-user] Dachstein



Hilton Travis wrote:
> 
> Rocks.  I just changed from Tel$tra cable to Optus@home cable, downloaded
> Dachstein RC2, and installed it fine.  works a treat.
> 
> I'll be making images for Tel$tra BigPond and Optus users, and replacing my
> earlier images on http://quarkau.cjb.net when I get back from camping next
> week.

Please, consider a post-RC release . . .

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .

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

RE: [Leaf-user] Dachstein

2001-11-16 Thread Hilton Travis


I will, once one is available, but there was only an RC2 on the site a day
ago...

- Hilton

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Michael D.
> Schleif
> Sent: Saturday, 17 November 2001 11:34
> To: Hilton Travis
> Cc: LEAF Users; LEAF Developers
> Subject: Re: [Leaf-user] Dachstein
>
>
>
> Hilton Travis wrote:
> >
> > Rocks.  I just changed from Tel$tra cable to Optus@home cable,
> downloaded
> > Dachstein RC2, and installed it fine.  works a treat.
> >
> > I'll be making images for Tel$tra BigPond and Optus users, and
> replacing my
> > earlier images on http://quarkau.cjb.net when I get back from
> camping next
> > week.
>
> Please, consider a post-RC release . . .
>
> --
>
> Best Regards,
>
> mds
> mds resource
> 888.250.3987
>
> Dare to fix things before they break . . .
>
> Our capacity for understanding is inversely proportional to how much we
> think we know.  The more I know, the more I know I don't know . . .
>
> ___
> 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

Re: [Leaf-user] Announcing official release of Dachstein-CD

Charles Steinkuehler wrote:
> 
> The official release (v1.0.1) of Dachstein-CD is now available for download
> from the usual places:
> slow:
> http://lrp.steinkuehler.net/files/diskimages/dachstein-CD/
> fast:
> http://lrp1.steinkuehler.net/files/diskimages/dachstein-CD/
> http://lrp2.steinkuehler.net/files/diskimages/dachstein-CD/
> 
> There was a 'silent' release of v1.0.0 for internal use yesterday.  Changes
> from the last release candidate include configuration tweaks (dnscache and
> ipsec), the inclusion of the ipsec binaries patched for x.509 certificate
> support, and fixes to a couple minor bugs (a problem with the POSIXness cut
> command, and setting custom backup destinations didn't work properly).

As always, this is truly superb stuff!  Bravo, Charles !!!

Couple questions, even though these items appeared in RC5:

[1] What is the purpose of the ``leaf'' user?

[2] Should /home/leaf exist -- provided that we agree that such an user
ought to exist?

-- 

Best Regards,

mds
mds resource
888.250.3987

Dare to fix things before they break . . .

Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . .

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

Re: [Leaf-user] Announcing official release of Dachstein-CD