Kory:
Just for completeness...the echowall packages does
support FTP servers, both active and passive mode. There's
a whole section about it in the README file.
And *these* are tested. :}
cheers,
Scott
On Sun, 4 Nov 2001, Kory Krofft wrote:
> Thanks,
>
> I will try it out later
Kory:
Wow, I bet this turned into a whole lot more than you
were expecting. FWIW, posting the firewall packet log was the
*exact* right thing to do.
Try this. Change the whole QUAKE section of the
echowall.rules file to look like this:
#QUAKE#$IPCHAINS -A input -s 0/0 -d $IP_EXT
Thanks,
I will try it out later this week I am back to work tomorrow and will not get
back to it till at least tuesday but I will definitely report back. I did notice
tonight that when I tried to use my FTP client to transfer some files to a web
site I had to reboot with my stock dachstein disk
At 08:16 PM 11/4/01 -0500, Kory Krofft wrote:
>Tom,
>No. I am testing from inside. I assume it would route out and back in ok.
This is always a bad assumption to make when testing firewalls. Maybe yes,
maybe no ... but you can never *count* on out-and-in working the same as a
true connection fro
> I set up D-CD rc3 this:
>
> 192.168.1.0/24 <--> 192.168.1.254 - 24.x.x.x/32 <--> 213.x.x.x/32
> w2k network 10BaseT D-CD BOX -- internet W2K box
>
> Took FOREVER to figure out how to get IPSec to work on the LRP box so that
> it allows my W2K box can access my W2
On Sunday 04 November 2001 05:47 pm, Kory Krofft wrote:
> Tom,
>
> That maakes sense but how do I open that UDP port? I started this
> thread because
> I did not understand the syntax of the ipchains rules. The only down
> side I have found to LRP is no man pages. I tried the HOW-TOs but
> they as
Here's a link to a sample weblet page with new images. The images are
slightly smaller (not much) and relatively attractive (IMHO). They also
have the correct color/name. The page is nonfunctional, but all the images
are there.
If there are no complaints and no one comes up with something bett
Tom,
That maakes sense but how do I open that UDP port? I started this thread
because
I did not understand the syntax of the ipchains rules. The only down side I
have found to LRP is no man pages. I tried the HOW-TOs but they assume a
higher level of Linux knowledge than I have. Scott Best's echo
On Sunday 04 November 2001 05:16 pm, Kory Krofft wrote:
> Tom,
> No. I am testing from inside. I assume it would route out and back in
> ok.
The problem isn't with packets sent from your local client to the
server but rather with packets going in the opposite direction. The
source address on t
Tom,
No. I am testing from inside. I assume it would route out and back in ok. I
just had a friend try from outside and it doesn't work either. My message
loge from the firewall
shows his IP address as being denied.
Nov 4 19:07:07 markii kernel: Packet log: input DENY eth0 PROTO=17
64.109.106.
> I have not upgraded to Dachstein yet, but will soon. I am still running
> EigerStein and I am attempting to upgrade to the newest IPSEC 1.91 that
> Charles just released. I have installed the required LRP files,
> ifconfig, mawk, and IPSEC. Upon booting and before the logon prompt, I
> get th
I have not upgraded to Dachstein yet, but will soon. I am still running
EigerStein and I am attempting to upgrade to the newest IPSEC 1.91 that
Charles just released. I have installed the required LRP files,
ifconfig, mawk, and IPSEC. Upon booting and before the logon prompt, I
get the followin
Thanks for all the help so far. I'm getting there...
I set up D-CD rc3 this:
192.168.1.0/24 <--> 192.168.1.254 - 24.x.x.x/32 <--> 213.x.x.x/32
w2k network 10BaseT D-CD BOX -- internet W2K box
Took FOREVER to figure out how to get IPSec to work on the LRP box so
I haven't used the multi298 package, but you should tell us what you did
in detail, not just that you followed the instructions. In particular,
describe how you modified syslinux.cfg.
-Richard
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ahmad S
Scott,
Thanks for jumping in on this. I went back and started over with a fresh
install of the new version. I thought the safest way for me was to have
two lrpboot disks. One pure Dachstein and one for echowall. When I was
working with it yesterday, I had not done the ./echowall install to make
it
Charles, I'm interesting too
Can you e-mail me the binaries???
@+
Thanks
- Original Message -
From:
elodie.wolanin
To: [EMAIL PROTECTED]
Sent: Wednesday, October 10, 2001 11:50
PM
Subject: [Leaf-user] Webalizer
patch
Hi,
A few days ago, I noticed tha
Ray,
Response inline:
Ray Olszewski wrote:
> Kory --
>
> I haven't used EchoWall in some time now, and Scott's added a lot to it
> (including *all* the support for game servers) since I last worked on it. So
> I can't give you a direct answer as to what is wrong. But if you provide
> some addit
Hello,
Have you looked in the /var/log directory? The "messages" file will have
most of the messages that scrolled by too fast.The other files have
usefull messages also.
I know no good way to just slow the messages coming to the console
short of putting commands in all the scripts that are run a
http://chinese-watercolor.com/LRP/
This is by far the best beginner's tutorial on LRP I have seen. Modules for
just about every reasonable card are linked. It will practically spoon-feed
the answers to you.
Good luck,
Dan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROT
It should, but you're missing one important piece. The latest ne2k-pci
driver also requires pci-scan. Uncomment this module as well, and you
should be in business...
Well I had it uncommented in the first place, but this also didn't work. So
I tried commenting it, to make it work.
Any other s
Okay, some progress. Version 1.32 of the echowall
package is now available in the usual places:
ftp://ftp.echogent.com/EchoWall/echowall.lrp
http://leaf.sourceforge.net/devel/sbest/echowall/
Changes from 1.31:
1. Modified rule-flushing and "!lo" nomenclature so that
it works
This seems like your NICs are not being recognized by the kernel.
Do you have the right modules uncommented?
-prabhakar
>
> I looked at the initialization of the firewall, the only bad things i
> noticed are:
>
> Cannot find device eth0
> eth0 cannot find device eth1
>
> I looked at the initialization of the firewall, the only bad things i
> noticed are:
>
> Cannot find device eth0
> eth0 cannot find device eth1
>
> BTW is it possible to log all this initialization text to a file, or make
it
> scroll really slowly? Really hard 2 read in this fast tempo :)
Use
I cannot be certain based on what you reported, but my first guess is that
you are using the wrong module(s) for your NICs. The other problems you
report are all likely to be secondary consequences of this failure.
Since I don't recall the particular NIC you are using, my first question
back to
Hello,
I'm new to this list.
After 4 years of waiting we finally got cable internet, and my first idea
was to share this connection to my computers in the house (PC, laptop and my
good old Amiga).
I heard of the LR-project and wanted to make use of it. I found myself a
nice package that AFAIK i
My apoligies to the group for the accidental reply
to the digest. I'll try to be more careful in the future.
Henry
Title: Dachstein CD
Hi, all Dachstein Users..
This maybe a crazy question, but for me it makes logic..
I just load my Dachstein, on an ole 486DX 100 / 32Mb Ram, and an old 4x CdRom.
We still figuring how we going to get it fit in the Slimline case that was only made for 2 3.5" devices.
> > A few more details are needed here...why are you using a web proxy?
Where
> > is the proxy logically on your network, and can it see the weblet pages?
> > What proxy settings are you using in your browser?
>
> I'm only using a proxy because of my cable modem connection --- rogers
@home
> (defa
"Scott C. Best" wrote:
>
> Kory:
> Well, how 'bout that. These lines are causing the
> trouble in Dachstein:
>
> > $IPCHAINS -A input -i !lo -s 127.0.0.0/8 -j DENY
> > $IPCHAINS -A input -i !lo -d 127.0.0.0/8 -j DENY
>
> Turns out it needs a space between the "!" and the
> "lo".
Kory:
Well, how 'bout that. These lines are causing the
trouble in Dachstein:
> $IPCHAINS -A input -i !lo -s 127.0.0.0/8 -j DENY
> $IPCHAINS -A input -i !lo -d 127.0.0.0/8 -j DENY
Turns out it needs a space between the "!" and the
"lo". ES2B (what Dachstein is replacing) didn't.
30 matches
Mail list logo
