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. ES2B (what
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
(default
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
My apoligies to the group for the accidental reply
to the digest. I'll try to be more careful in the future.
Henry
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
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
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
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
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
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 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
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
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
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
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 W2K network
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 from
16 matches
Mail list logo
