Hi, I'm unsure how to open ports to allow an FTP
server running behind it on port 6660 (or 21 if for example). I have a
feeling it's todo with ip_masq_ftp. As i'm a n00bie to this step-by-step
instructions would be usefull. Thanks in advance...
STU.
I have set up LRP from the Dachstein floppy-It works great. The only
problem is that when I added a third NIC to set up a DMZ for a game server,
the box becomes confused. I can ping the interfaces from the box, but
nothing outside it-neither my LAN or public IP. At one point I had actually
I have set up LRP from the Dachstein floppy-It works great. The only
problem is that when I added a third NIC to set up a DMZ for a game
server,
the box becomes confused. I can ping the interfaces from the box, but
nothing outside it-neither my LAN or public IP. At one point I had
Stewart Adey wrote:
Hi, I'm unsure how to open ports to allow an FTP server running behind
it on port 6660 (or 21 if for example).
You have to edit /etc/network.conf. In there are
directions. Search this list by using the search
engine at sourceforge and you'll find similar
questions.
On Tue, 11 Dec 2001, Matthew Schalit wrote:
Stewart Adey wrote:
[...]
I have a feeling it's todo with ip_masq_ftp.
Nope, that module is used for outgoing ftp,
not incoming. It's used to help outgoing ftp
work behind a masq'ing firewall. Outgoing active
ftp needs that help.
With
Some of you using DMZ's may have noticed there's no automated way to provide
restricted access to your DMZ network (allow a service only to specific
remote IP's). The current rules only allow all (0/0) or nothing. While
it's easy enough to hand-code a couple of rules in ipchains.forward (that's
David Douthitt wrote:
# Remove package from packages list:
PKGD=/var/lib/lrpkg
mv $PKGD/packages $PKGD/pkg.old
grep -v $PKGD/pkg.old $PKGD/packages
This has an error; should be:
# Remove package from packages list
PKGD=/var/lib/lrpkg
mv $PKGD/packages $PKGD/pkg.old
grep -v
Matt Schalit wrote:
I agree here with the pci-scan loading before the nic module(s)
and that Dachstein is the simplest and most surefire release to get
you up an running with little effort. There are two major things to setup:
1) # echo 'export EDITOR=e3vi' /etc/profile
#
Dr. Richard W. Tibbs wrote:
I had the same problem (t:t:t:t:) at the boot prompt with the latest
oxygen release
loading on a Gateway 2000 pentium-1 machine.
A serial port (actually two) are certainly present on the Gateway --
so no serial port present shouldn't be the issue,
unless having
Hi.
I am trying to use the latest Oxygen with the firewall data disk as a
second disk.
Everything boots up fine (using IBM aptiva doorstop as my firewall
device, with 2 netgear ethernet NICs).
When asked to configure the system, I answer yes, and I get an edit
session of a script to kick off
I know this question has been touched on before, but I don't think I saw
an answer that really fits my situation.
I have a wireless connection and will soon have a DSL connection as
well. Both are handled by the same ISP. I would like to build a box
that will do either or both of the
Thanks (Charles and Matt). Sorry for the simple question (this is my first
attempt not using a basic coyote install). Added the pci-scan module and
updated all the ip_masq_xxx modules...everything is running smooth.
-Original Message-
From: Matt Schalit [mailto:[EMAIL PROTECTED]]
Sent:
Great! Thanks Exactly what I was looking for.
- Original Message -
From: David Douthitt [EMAIL PROTECTED]
To: LEAF Users List [EMAIL PROTECTED]
Sent: Tuesday, December 11, 2001 9:54 AM
Subject: Re: [Leaf-user] uninstall option for lrpkg
David Douthitt wrote:
# Remove package
I'm trying to upgrade my installations to dachstein cd and I didn't found
the hdsupp hdsupp_s packages
can I use the old ones from charles' site ?
You should be able to...at least I haven't heard from anyone who's had
problems with them yet, and several folks have reported getting HDD
Dr. Richard W. Tibbs wrote:
I am trying to use the latest Oxygen with the firewall data disk as a
second disk.
Everything boots up fine (using IBM aptiva doorstop as my firewall
device, with 2 netgear ethernet NICs).
When asked to configure the system, I answer yes, and I get an edit
Kevin Kropf wrote:
I have Squid running on dachstein-rc2-1680.exe and would like to redirect
all internal port 80 requests to the default Squid port of 3128 on the LRP
box.
I have read through the archives and found very little of use.
What is the best way to do this?
This is in the
On Tue, 11 Dec 2001, David Douthitt wrote:
[...]
grep -v '^'$PKGNAME'$' $PKGD/pkg.old $PKGD/packages
why the rigamarole with the single quotes?
grep -v ^$PKGNAME$ $PKGD/pkg.old $PKGD/packages
---
Jeff Newmiller
Jeff Newmiller wrote:
On Tue, 11 Dec 2001, David Douthitt wrote:
[...]
grep -v '^'$PKGNAME'$' $PKGD/pkg.old $PKGD/packages
why the rigamarole with the single quotes?
grep -v ^$PKGNAME$ $PKGD/pkg.old $PKGD/packages
I was playing chicken :)
The first breaks down this way:
Dr. Richard W. Tibbs wrote:
OK, per some other advice, dachstien is easier to use as basic
firewall.
I built a boot disk based on rc1. Loaded up on doorstop IBM Aptiva.
Several questions:
What is the difference between the various dachstein .bin's? (rc1,
rc2, pr1pr4)?
Versions.
How
I am not that familiar with ipchains and was hoping for a little more
detail.
I put together the following command from the info on the squid FAQ:
$IPCH -A input -p tcp -d 0/0 80 -j REDIRECT 3128
However I am not sure what else is needed and where to put it in
ipfilter.conf
Thanks for any help
20 matches
Mail list logo
