Kevin -- Can't help you with the Echowall part, but I can answer your IDENT
question.
At 12:15 AM 6/23/01 -0400, Kevin wrote:
[large cut]
...
>Put original floppy in, reboot and I could get on the internet, FTp, mail,
>www still no IRC
>
>I then found this in the ipfilter.conf file for the PP
If I follow the instructions as posted, the firewall will not allow me to
access anything on the internet.
I am running the eiger3beta with PPPoP from Ken.
I was curios as to why my IRC will not work with the current set-up so I
tried Echowall tonight. After 4 hours, still no luck
I made a copy
OK, I get it now. I was just wondering was all.
Still getting that error message (posted in my other email), but it doesnt
seem to be affecting anything directly.
Now if I could just get sshd to listen like it should, I will be all set.
Will post on that later, need to get all my info down...
At 02:01 PM 6/22/01 -0500, Chris wrote:
>More of a curiosity really. I was just wondering why echowall uses MAC
>addresses instead of IP for forwarding traffic? Or is this a clueless
>question about ipchains, of which I know very little?
>
>I have some services that move from box-to-box
Fabian ==>
Thank you, for your insights . . .
Fabian Linzberger wrote:
>
> What actually worries me most, is that somebody might break in at night,
> take out the floppy, modifies it as he pleases and reboots the router.
> Turning around the floppy drive helps, but most people know how to use a
--- Sorry if you get this message twice, just
realized I sent it the first time from the wrong account.
I am trying to get echowall running on an
Eigerstein 2BETA day 5/27/01. So far, this is what I have
done:
1. Got echowall.lrp on my disk
2. Added echowall to
Syslinux.cfg
3. Execu
I am trying to get echowall running on an
Eigerstein 2BETA day 5/27/01. So far, this is what I have
done:
1. Got echowall.lrp on my disk
2. Added echowall to
Syslinux.cfg
3. Executed ./echowall install from its
directory and rebooted
Here is what I am getting in my boot
messages:
Hi all:
I downloaded and configured Charles Steinkuehler's Static Eiger disk
image. I managed to get it working with my intel ethernet cards and
also added vim and set it up to port forward a fews services to multiple
hosts. All works great. I have been using it for a month now with no
poblems
On Fri, 22 Jun 2001, Michael D. Schleif wrote:
> LEAF'ers ==>
>
> OK, so far, we're running exclusively as root user.
>
> Usually, we consider the larger number of users, the less secure a given
> system becomes.
>
> Using ssh to remotely access the firewall and without telnet and ftp
> allowe
Well Thank you for the immediate response!
Part of the confusion on my part was I never totally understood how the
packages worked. I knew that some parts belonged to some packages, but
until I had to worry about it.I didn't. I took it on faith, you
guys [developers] knew what to do, and I
> OK, so far, we're running exclusively as root user.
>
> Usually, we consider the larger number of users, the less secure a given
> system becomes.
>
Dedicated users created in order to follow a "least privilege" policy
are usually more secure than running everything as the superuser (like
wind
LEAF'ers ==>
OK, so far, we're running exclusively as root user.
Usually, we consider the larger number of users, the less secure a given
system becomes.
Using ssh to remotely access the firewall and without telnet and ftp
allowed, the firewall appears to be moderately secure.
However, it both
"Michael D. Schleif" wrote:
>
> OK, I've gotten by that snafu with last night's http file transfers ;>
>
> iptraf works -- somewhat -- and is somewhat broken on our LRP-CD.
>
> When I invoke its CLI it starts up and immediately informs me:
>
> ``Unable to tag this process''
>
> This
More of a curiosity really. I was just wondering why echowall uses MAC
addresses instead of IP for forwarding traffic? Or is this a clueless
question about ipchains, of which I know very little?
I have some services that move from box-to-box (its my DR strategy :P).
But with MAC address
It's here:
http://groove.jpj.net/pub/lrp
I couldn't find one, so I built this. It's running on my custom LRP
system, but you shoudln't have a problem with a Eiger/Eigerstein setup.
You *do* need the PPTP masq modules, FSwan LRP package, etc. 2.2.16
modules should work fine.
-Paul
_
On Fri, 22 Jun 2001 [EMAIL PROTECTED] wrote:
> Hello
> Dear LRP Guru
> Could I ask some of question again?cause I'm not software experimenter,maybe just
>Hardware homebrew.
You are experimenting with software now :)
>
> Just finished made my modules(XXX.o) after compiled in kernel
> 2.0.36.M
"Kelly D. Wason" wrote:
>
> >
> > I am using Eigerstein as a firewall. I want to mail a copy of the log LRP
> > produces periodically to myself. Is there a way to schedule a cron job to
> > send a copy of the log and then flush the log? For that matter, does cron
> > even run on LRP?
>
> No o
>
> I am using Eigerstein as a firewall. I want to mail a copy of the log LRP
> produces periodically to myself. Is there a way to schedule a cron job to
> send a copy of the log and then flush the log? For that matter, does cron
> even run on LRP?
No one has responded to my query. Is this so
Anthony, et al. ==>
Anthony Lieuallen wrote:
>
> I just started using iptraf on my LRP box also, and it relies on a
> configuration directory existing. I was getting those messages also,
> but as soon as I made it everything was better. I got the name from
> the docs on their site, IIRC it was
I just started using iptraf on my LRP box also, and it relies on a
configuration directory existing. I was getting those messages also,
but as soon as I made it everything was better. I got the name from
the docs on their site, IIRC it was '/var/iptraf'
Dunno if that will fix that memory thing
> Na, I have all the modules, just was at a loss how to get /sbin/insmod
> to load in root.lrp instead of modules.lrp. I had no idea that it was
> as simple as deleting the lines /sbin/insmod and /sbin/rmmod from
> /var/lib/lrpkg/modules.list. This forces the files to be backed up with
> root.lr
Aparently, this didn't make it to the list.
I apologise if you got it twice...
-Original Message-
>Ah, I see, in other words, no need to worry about loading modules,
>they'd be in the kernel already
I see now that you've got the message right! :)
>See what I mean about being subt
Speaking of SCSI HD's, does anyone know a way to spin down the drive
after it has served its purpose? I have seen a couple of old programs
that say they can do this, but they are for the 2.0.x kernel.
I wrote the author of hdpram and asked if his program will spin down a
SCSI drive and he state
Try this and give me some feedback
http://users.skynet.be/Etienne.Charlier/DachSteinPPPoEech.htm
Etienne
- Original Message -
From: "Kenneth Hadley" <[EMAIL PROTECTED]>
To: "Liam Tumulty" <[EMAIL PROTECTED]>
Cc: "[LEAF-user]" <[EMAIL PROTECTED]>
Sent: Friday, June 22, 2001 3:05 PM
Subject
- Original Message -
From: "Liam Tumulty" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 22, 2001 2:54 AM
Subject: pppoe
> Hi, I'm putting together a linux router and got your image up and running
> (thanks), but would like to use some of the features in the new EigerStei
Ah, I see, in other words, no need to worry about loading modules,
they'd be in the kernel already
See what I mean about being subtle? Sometimes I can be as thick as a
brick
Thanks Luis,
Tony
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf O
No, I have a bad english :)
What I mean was:
If you compile a NEW kernel with the scsi module as (*) instead of (M),
it is part of the kernel.
That was what I meant with my previous email...
-Original Message-
From: Tony [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 22, 2001 12:52 PM
T
Good Morning,
Na, I have all the modules, just was at a loss how to get /sbin/insmod
to load in root.lrp instead of modules.lrp. I had no idea that it was
as simple as deleting the lines /sbin/insmod and /sbin/rmmod from
/var/lib/lrpkg/modules.list. This forces the files to be backed up with
ro
Maybe your problem is as simple as having the relevant scsi module
compiled in the kernel.
This means of course you should recompile the kernel in order to have
the module as part o the kernel.
I recall a similar problem with RedHat that if the module were not in
the initrd archive (similar to o
29 matches
Mail list logo
