Everything boots up fine, works fine, except get a load of ipchains: protocal
not available.
Now, I was not aware I even used this, the /etc/default/ipchains says "no."
Is it now absent in the kernel, deprecated so get rid of the init.d script?
Iptables is being used.
--
To U
On Tue, Feb 12, 2008 at 03:42:04PM -0500, Zach wrote:
> Anyone know a way (or even better have a script) to convert a file of
> ipchains rules into iptables rules?
Rather then using a script you could try shorewall. It is very well
documented very powerful and not hard to use.
Regards,
I have attached a diagram which was posted a while back on the path of packets
through the kernel
might help
On Wed, Feb 13, 2008 at 07:50:12PM +1000, Adrian Levi wrote:
> On 13/02/2008, Zach <[EMAIL PROTECTED]> wrote:
> > On Feb 12, 2008 7:20 PM, Adrian Levi <[EMAIL PROTECTED]> wrote:
> > >
>
On 13/02/2008, Zach <[EMAIL PROTECTED]> wrote:
> On Feb 12, 2008 7:20 PM, Adrian Levi <[EMAIL PROTECTED]> wrote:
> >
> > The topology of chains to tables is fundamentally different, In chains
> > a packet that is to be forwarded must also go though the input and
> > output chains. Under tables this
On Feb 12, 2008 7:20 PM, Adrian Levi <[EMAIL PROTECTED]> wrote:
>
> The topology of chains to tables is fundamentally different, In chains
> a packet that is to be forwarded must also go though the input and
> output chains. Under tables this packet only has to traverse the
> forward table, input a
On 13/02/2008, Zach <[EMAIL PROTECTED]> wrote:
> Anyone know a way (or even better have a script) to convert a file of
> ipchains rules into iptables rules?
The topology of chains to tables is fundamentally different, In chains
a packet that is to be forwarded must also go though t
Anyone know a way (or even better have a script) to convert a file of
ipchains rules into iptables rules?
Zach
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
like that), and they should be
installed under /lib/modules/2.2.20/
You should be able to find it with "find /lib/modules | grep ipchains",
or "locate ipchains.o"
But if it is there, as it should be, then a simple "modprobe ipchains"
ought to load it.
I don't hav
Yes, ipchains is installed
# apt-get install ipchains
Reading Package Lists... Done
Building Dependency Tree... Done
Sorry, ipchains is already the newest version.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# ipchains -V
ipchains 1.3.10, 1-Sep-2000
No, it doesn't
On Wed, Jan 05, 2005 at 04:53:10PM +0100, Pierre A. Damas wrote:
> Since I installed the woody distribution, I am the happy owner of a
> kernel 2.2.
> I would like to use ipchains, but it is "not supported in this
> Kernel", so I searched everywhere to find an ipchains.o
y old Pentium-MMX 200 65Mb RAM, two network adapters
(ne and 8139too).
Prerequisite: I don't want to compile my kernel myself (insmod
should be sufficient), certainly not on that machine (which is my
only linux).
I understood that ipfwadm is used for kernel 2.0, ipchains for 2.2
and iptabl
William Ballard <[EMAIL PROTECTED]> writes:
> Sarge installs ipchains by default.
> Nothing that depends on ipchains is installed by default.
>
> I don't use ipchains. I use less.
>
> Can we have less in the base install and not ipchains?
It already is that way.
l
Sarge installs ipchains by default.
Nothing that depends on ipchains is installed by default.
I don't use ipchains. I use less.
Can we have less in the base install and not ipchains?
I use OpenBSD as my firewall.
I think it's fair for people who want to use this non-essential
feat
On Mon, 21 Jun 2004 15:30:52 +0200
Paal Marker <[EMAIL PROTECTED]> wrote:
> David Fokkema wrote:
>
> >I bet there's a 2.4 kernel available. While installing the
> >machines, you could have chosen bf24 instead of linux, vanilla or
> >expert signifying that you wanted a 2.4 kernel installed.
> >
>
On Mon, Jun 21, 2004 at 03:30:52PM +0200, Paal Marker wrote:
> David Fokkema wrote:
>
> >On Mon, Jun 21, 2004 at 03:06:40PM +0200, Paal Marker wrote:
> >
> >
> >>debian 3.0r2 kernel 2.2.20
> >>
> >>Still I am configuring the boxes in kiosk mode.
> >>
> >>First now I observe that the debian I down
David Fokkema wrote:
On Mon, Jun 21, 2004 at 03:06:40PM +0200, Paal Marker wrote:
debian 3.0r2 kernel 2.2.20
Still I am configuring the boxes in kiosk mode.
First now I observe that the debian I downloaded last week included 2.2
kernel and not 2.4. Wich means I can not use the firewall script
On Mon, Jun 21, 2004 at 03:06:40PM +0200, Paal Marker wrote:
> debian 3.0r2 kernel 2.2.20
>
> Still I am configuring the boxes in kiosk mode.
>
> First now I observe that the debian I downloaded last week included 2.2
> kernel and not 2.4. Wich means I can not use the firewall script wich
Ar
debian 3.0r2 kernel 2.2.20
Still I am configuring the boxes in kiosk mode.
First now I observe that the debian I downloaded last week included 2.2
kernel and not 2.4. Wich means I can not use the firewall script wich
use iptables. So I have rewritten the script for ipchains. I used the
same
I assume something is missing from some
ipchains or iptables or inetd.conf file, but as a relative newbie, I find
those things fairly intimidating! Any suggestions where to start?
Thanks! - John
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
yikes!! i have hit the wall at 37!!! i am running a 2.4 kernel and
should have asked about iptables NOT ipchains.
At Tuesday, 9 December 2003, Arnt Karlsen <[EMAIL PROTECTED]> wrote:
>On Tue, 9 Dec 2003 09:08:15 -0500,
>Debian User <[EMAIL PROTECTED]> wrote in message
>
On Tue, 9 Dec 2003 09:08:15 -0500,
Debian User <[EMAIL PROTECTED]> wrote in message
:
> I am searching for a good HowTo on firewalls and ipchains.
>
> http://www.tldp.org/HOWTO/Firewall-HOWTO-8.html references a dead
> link at
> http://www.adelaide.net.au/~rustcorp/ipfwc
On Tue, 9 Dec 2003, Debian User wrote:
> I am searching for a good HowTo on firewalls and ipchains.
>
> http://www.tldp.org/HOWTO/Firewall-HOWTO-8.html references a dead
> link at
> http://www.adelaide.net.au/~rustcorp/ipfwchains/ipfwchains.html
>
> Does anyone have an
On Tue, Dec 09, 2003 at 09:08:15AM -0500, Debian User wrote:
> I am searching for a good HowTo on firewalls and ipchains.
>
> http://www.tldp.org/HOWTO/Firewall-HOWTO-8.html references a dead
> link at
> http://www.adelaide.net.au/~rustcorp/ipfwchains/ipfwchains.html
>
On Tue, 9 Dec 2003, Debian User wrote:
> I am searching for a good HowTo on firewalls and ipchains.
>
> http://www.tldp.org/HOWTO/Firewall-HOWTO-8.html references a dead
> link at
> http://www.adelaide.net.au/~rustcorp/ipfwchains/ipfwchains.html
>
> Does anyone have an
I am searching for a good HowTo on firewalls and ipchains.
http://www.tldp.org/HOWTO/Firewall-HOWTO-8.html references a dead
link at
http://www.adelaide.net.au/~rustcorp/ipfwchains/ipfwchains.html
Does anyone have another reference worth reading?
--
To UNSUBSCRIBE, email to [EMAIL
On Thu, Sep 11, 2003 at 12:01:57PM -0700, coco the talking chimp wrote:
> ipchains not installed by default? I thought Linux was made for
> networking.
ipchains *is* installed by default in woody, as is iptables (unless
you're using a wacky architecture).
--
C
at was used to
build the kernel you are using. Changing options in that file won't
change your kernel in any way.
Either you recompile the kernel from source using that changed config
file, or you install another kernel image that already has ipchains
(2.2 and 2.4) or iptables (2.4 on
Hans Wilmer wrote:
There´s a very nice tutorial describing how things work, which kernel
options you need, including samples that make a very good point to
begin with. The tutorial is called ´Iptables Tutorial 1.1.16´ (maybe a
newer version is available) and was written by Oskar Andreasson ---
I got it from at the moment, but searching for it with google you
should be able to find it. Give me a note if you can´t find it; I could
mail it to you.
Using ipchains isn´t recommended ...
GH
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
ok so I just found the
/boot/config-2.2.20-compaq. This, i figure, is where the options
CONFIG_FIREWALL=y and CONFIG_IP_FIREWALL=y should be. Of course they are
not there. Should I just type them in or what? Plus the
/proc/net/ip_fwchains/ file isn't there but I think that's for older
Hello
coco the talking chimp (<[EMAIL PROTECTED]>) wrote:
> ipchains not installed by default? I thought Linux was made for
> networking. Anyway, I'm not too familiar with this but here is my
> problem. When I run ipchains it says incompatible with this kernel.
> I
If you have a 2.4 kernel, ipchains is obsolete -- iptables is much
easier to understand in my opinion, anyway.
on Thursday 09/11/2003 coco the talking chimp([EMAIL PROTECTED]) wrote
> ipchains not installed by default? I thought Linux was made for networking.
> Anyway, I'm not t
ipchains not installed by default? I thought
Linux was made for networking. Anyway, I'm not too familiar with this but
here is my problem. When I run ipchains it says incompatible with this
kernel. I'm on compact debian 3.0 so kernel must be 2.2.2.0. Modprobe
ipchains sa
Hello
jones joens (<[EMAIL PROTECTED]>) wrote:
> Hello, I am new to the linux game and am running into some difficulty.
> I cannot get ipchains, iptables, or ipfwadm to work. All three give
> me errors that say something is missing in the kernel. Such that
>
> i
Hello, I am new to the linux game and am running into some difficulty. I cannot get ipchains, iptables, or ipfwadm to work. All three give me errors that say something is missing in the kernel. Such that
ipfwadm --> Generic IP Firewall Chains not in this Kernel
ipchains -L --> Incomp
Hello
Steven wrote:
> On Saturday, July 26, 2003, at 09:06 AM, Andreas Janssen wrote:
>> Steven wrote:
>>> I'm recompiling my kernel - I forgot to add ipchains support last
>>> time.
>>> The problem is that ipchains isn't listed in the menucon
* Steven ([EMAIL PROTECTED]) [030726 09:44]:
>
> On Saturday, July 26, 2003, at 09:06 AM, Andreas Janssen wrote:
>
> >Hello
> >
> >Steven wrote:
> >
> >>I'm recompiling my kernel - I forgot to add ipchains support last
> >>time.
> >
On Saturday, July 26, 2003, at 09:06 AM, Andreas Janssen wrote:
Hello
Steven wrote:
I'm recompiling my kernel - I forgot to add ipchains support last
time.
The problem is that ipchains isn't listed in the menuconfig stuff.
Where do I build it in? I also searched .config for ipc
Hello
Steven wrote:
> I'm recompiling my kernel - I forgot to add ipchains support last time.
> The problem is that ipchains isn't listed in the menuconfig stuff.
> Where do I build it in? I also searched .config for ipchains, but it
> wasn't found. Thanks for any
I'm recompiling my kernel - I forgot to add ipchains support last time.
The problem is that ipchains isn't listed in the menuconfig stuff.
Where do I build it in? I also searched .config for ipchains, but it
wasn't found. Thanks for any help.
Steven
--
To UNSUBSCRIBE,
On Tue, Mar 11, 2003 at 11:25:39PM -0300, Franco Galian wrote:
> Hi, I'm having trouble with a kernel update.
> First of all, I'd installed a Debian 3.0-r1. Everything worked fine, except
> for ipchains.
> When I tried to run ipchains -L, the following message appeared:
>
On Tue, Mar 11, 2003 at 11:25:39PM -0300, Franco Galian wrote:
> It says something about "unable to mount root...".
What filesystem do you have? If you are using reiserfs or something else
which is not included in the stock kernels, that would precisely explain
your problem.
Solution: Obtain and
Hi, I'm having trouble with a kernel update.
First of all, I'd installed a Debian 3.0-r1. Everything worked fine, except
for ipchains.
When I tried to run ipchains -L, the following message appeared:
"ipchains: Incompatible with this kernel".
After doing some research, I de
gging to syslog. There are still oddities, firewall events that
show up in the logs days after the fact.
HTH,
Jeffrey
Quoting Jeremy Gaddis <[EMAIL PROTECTED]>:
> Has anyone experienced an issue with ipchains not logging
> via syslog? The log info for the packets that should be
>
Has anyone experienced an issue with ipchains not logging
via syslog? The log info for the packets that should be
logged is output to the first VT, but this is hardly
convenient as the machine is put up in a closet.
[EMAIL PROTECTED]:pts/0:~]$ uname -a
Linux mars 2.2.23 #4 Thu Jan 23 22:15:03
On Thu, Feb 20, 2003 at 02:32:37PM -0500, Narins, Josh wrote:
>
> I spent a good amount of time with my old 2.2.x ipchains firewall.
>
> Because it was a laptop, it included different start scripts based on 10.x
> or 192.x or static IPs (I seem to recall)
>
> I liked it
The question is whether or not there is something I can use to just convert
these to iptables world.
When you configure the kernel in the netfilter/iptbales configuration
(under networking) there are two options: ipchains support and ipfw support.
With these you can compile a 2.4 kernel, use
* Narins, Josh ([EMAIL PROTECTED]) [030220 11:51]:
>
> I spent a good amount of time with my old 2.2.x ipchains firewall.
>
> Because it was a laptop, it included different start scripts based on 10.x
> or 192.x or static IPs (I seem to recall)
>
> I liked it. It was very
I spent a good amount of time with my old 2.2.x ipchains firewall.
Because it was a laptop, it included different start scripts based on 10.x
or 192.x or static IPs (I seem to recall)
I liked it. It was very nicely formatted (no tabs, well spaced) and was
organized in a way I felt was
Hello nate,
It works now!! Thanks.
It's caused by my ipchains rule, I was confused with packet that go into internal
network
from the FW server itself. I allowed "FW (unprivport) -> PCAHostInternalIP
(5632/5631)" only,
after I change it to "PCAExternalIP (unprivport) -&g
Simon Tneoh Chee-Boon said:
> Hello nate,
> 'Coz ipchains always displays that message, so I've commented the
> REDIRECT
> rule.
> So for my objective, the important parts are the ipchains, ipmasqadm
> portfw and route table, right?
yep, don't need redirect
Hello nate,
'Coz ipchains always displays that message, so I've commented the REDIRECT
rule.
So for my objective, the important parts are the ipchains, ipmasqadm portfw and
route table, right?
For my case, do I need any settings like CONFIG_IP_TRANSPARENT_PROXY=y?
And will ipchains&
Simon Tneoh Chee-Boon said:
> Hello nate,
>When I try to some REDIRECT in ipchains, I got the following message:
> ipchains: No target by that name (Maybe this kernel doesn't support
> transparent proxying?)
> Could this cause the problem?
> I'm using Linux wira 2
Hello nate,
When I try to some REDIRECT in ipchains, I got the following message:
ipchains: No target by that name (Maybe this kernel doesn't support transparent
proxying?)
Could this cause the problem?
I'm using Linux wira 2.2.20 #1 Sat Apr 20 11:45:28 EST 2002 i686 unknown.
I&#
Simon Tneoh Chee-Boon said:
> Hello nate,
> I suspect could it be my ipchains rule block the internal
> connections?
>>From internal network, when I try to PCAnywhere external PCAnywhere
> Host, I
> can something like the following in the syslog file:
> 1)
Hello nate,
I suspect could it be my ipchains rule block the internal
connections?
>From internal network, when I try to PCAnywhere external PCAnywhere
Host, I
can something like the following in the syslog file:
1) internalIP (unprivportA) -> externalHostIP (5632)
2) fwexternalIP (unpri
ved autofw but it still failed.
> > My machine details:
> > server FW (IP: x.x.x.a interfaces: x.x.x.x/29 and 192.168.1.0/24
> > ipchains running on it)
> > pc C (IP: x.x.x.b PCAnywhere client)
> > server P (IP: 192.168.1.2 it behinds server A, PCAnywhere host)
ces: x.x.x.x/29 and 192.168.1.0/24
> ipchains running on it)
> pc C (IP: x.x.x.b PCAnywhere client)
> server P (IP: 192.168.1.2 it behinds server A, PCAnywhere host)
> So my externalip would be x.x.x.a and internal IP is 192.168.1.2. On
> server
> FW, I've allowed both TCP a
Hello nate,
Thanks for your reply.
I saw some examples using both portfw and autofw, that's why I was
trying
both.
I've removed autofw but it still failed.
My machine details:
server FW (IP: x.x.x.a interfaces: x.x.x.x/29 and 192.168.1.0/24
ipchains running on it)
pc C (I
On Sat, Jan 04, 2003 at 09:07:31PM -0800, Geoff Hunsicker wrote:
> We are using kernel 2.4.20. When we try to use
> ipchains it tells us it is not compatible with the
> kernel. Is this because we have left out a kernel
> option, or are ipchains no longer supported?
There&#
We are using kernel 2.4.20. When we try to use
ipchains it tells us it is not compatible with the
kernel. Is this because we have left out a kernel
option, or are ipchains no longer supported?
Also, we are trying to use DHCP to connect to our
cable modem. We can ping systems on our ISP's net
Hello nate,
Thanks for your reply.
I saw some examples using both portfw and autofw, that's why I was trying
both.
I've removed autofw but it still failed.
My machine details:
server FW (IP: x.x.x.a interfaces: x.x.x.x/29 and 192.168.1.0/24 ipchains running
on it)
pc C (I
Simon Tneoh Chee-Boon said:
>
>I've executed the following commands:
> ipmasqadm portfw -a -P tcp -L externalip 5631 -R internalip 5631
> ipmasqadm portfw -a -P udp -L externalip 5631 -R internalip 5631
> ipmasqadm portfw -a -P tcp -L externalip 5632 -R internalip 5632
> ipmasqadm portfw -a -P
Hello all,
Thanks in advance for any helps.
I've searched through the internet to find information on how to allow
PCAnywhere connection from external interface into an internal server
under ipchains' control.
The server running the ipchains has MASQ running on it already, th
also sprach Richard Hector <[EMAIL PROTECTED]> [2002.12.07.0030 +0100]:
> I'm not saying it's a bad idea; I'm just saying I don't know how to do
> it. Any suggestions?
snort.
and i'd go as far as to log everything that the firewall drops and
then add rules to drop certain packets without logging
On Sat, Dec 07, 2002 at 12:30:34PM +1300, Richard Hector wrote:
> I'm not saying it's a bad idea; I'm just saying I don't know how to do
> it. Any suggestions?
apt-get install ippl logcheck
--
.''`. Baloo <[EMAIL PROTECTED]>
: :' :proud Debian admin and user
`. `'`
`- Debian - when
Richard Hector said:
> I get stuck in a loop when I try to figure out what to monitor.
totally depends on what you WANT to monitor really and how much
time you want to spend doing it. My home network I recently revamped
everything so it is monitored like a hawk (see http://monitor.aphroland.org
b
martin f krafft said:
> also sprach nate <[EMAIL PROTECTED]> [2002.12.06.0136 +0100]:
>> firewall-and-forget.
>
> maybe for a private system. this is *not* the way to practice
> security. security involves ongoing monitoring.
this is the best way if you have limited resources. Why should I care
ab
On Sat, 2002-12-07 at 10:59, martin f krafft wrote:
> also sprach nate <[EMAIL PROTECTED]> [2002.12.06.0136 +0100]:
> > firewall-and-forget.
>
> maybe for a private system. this is *not* the way to practice
> security. security involves ongoing monitoring.
I get stuck in a loop when I try to figu
also sprach nate <[EMAIL PROTECTED]> [2002.12.06.0136 +0100]:
> firewall-and-forget.
maybe for a private system. this is *not* the way to practice
security. security involves ongoing monitoring.
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud Debian developer, admin, and user
On Thu, Dec 05, 2002 at 04:36:09PM -0800, nate wrote:
> If you try to inquire about every blocked packet on
> your firewall, someday you may be spending all your free time doing it.
Not to mention making you look like an idiot to your ISP's support
staff and make them live in fear of having to sit
John Conover said:
>
> Does anyone have any idea what the following in syslog means:
>
> Dec 5 14:58:01 themachine kernel: Packet log: input DENY ppp0 PROTO=0
> 0.0.0.0:65535 0.0.0.0:65535 L=40 S=0x00 I=55674 F=0x T=64 (#8)
>
> What's PROTO 0, IP address 0.0.0.0?
proto 0 is IP (check /etc
Does anyone have any idea what the following in syslog means:
Dec 5 14:58:01 themachine kernel: Packet log: input DENY ppp0 PROTO=0
0.0.0.0:65535 0.0.0.0:65535 L=40 S=0x00 I=55674 F=0x T=64 (#8)
What's PROTO 0, IP address 0.0.0.0?
Thanks,
John
BTW, its a ppp dialup c
In Debian 3.0r0, what syslog facility does IPchains log to? The
messages are showing up on all virtual terminals, but not in any of
the /var/log files.
TIA,
Jeffrey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Nov 11, 2002 at 10:25:08AM -0500, Geoffrey Deasey wrote:
> mail:/proc/net# ipchains -A inout -s 205.139.153.202 -d 0/0 -p tcp -y -j
> ACCEPT
> ipchains: Protocol not available
I'm not sure, but I doubt the stock boot floppy kernel has ipchains
built in. apt-get instal
mail:/proc/net# ipchains -A inout -s 205.139.153.202 -d 0/0 -p tcp -y -j ACCEPT
ipchains: Protocol not available
When I try to run ipchains I get a message about protocol not available,
how do i fix this ?
This is a stock kernel that can the install.
Geoffrey
Geoffrey Deasey
VP Systems
Henrik Johansson <[EMAIL PROTECTED]> writes:
> Hi everybody!
Hi Henke.
A lot about not able to connect to port 25
> Connected to flaskan.lillehenke.cjb.net.
If I run:
lari@thor:~$ host flaskan.lillehenke.cjb.net
flaskan.lillehenke.cjb.net A 213.66.203.147
lari@thor:~$ host 213.66
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everybody!
I checked some more and now know my problems aren't caused by my firewall.
I get the following behaviour no matter if my ipchains firewall is on or if
all rules are flushed:
I run exim on a (woody) machine with one int
.)
Anyhow...
I used Bastille to set up the ipchains firewalling and ipmasqing, leaving
ports 21, 22, 25 and 80 open. I then made a small script (a couple of lines)
that forwarded ports 21 and 80 to my regular computer. The ipmasqing and
port-forwarding worked fine (and still do).
I then configured exim
Derrick 'dman' Hudson <[EMAIL PROTECTED]> writes:
> On Fri, Jun 28, 2002 at 11:30:00AM -0400, Brian P. Flaherty wrote:
> | This works for me:
> |
> | ipchains -A input -s 12.27.41.66 -j DENY -l
>
> Does this send back a "connection refused" packe
On Fri, Jun 28, 2002 at 11:30:00AM -0400, Brian P. Flaherty wrote:
| This works for me:
|
| ipchains -A input -s 12.27.41.66 -j DENY -l
Does this send back a "connection refused" packet? I forget what the
target names are for ipchains, but with iptables you want to use
"DROP"
This works for me:
ipchains -A input -s 12.27.41.66 -j DENY -l
You can drop the final -l if you don't want to log.
HTH.
Brian Flaherty
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I know this should be easy, but I cannot seem to get the syntax correct
for ipchains (2.2 kernel) to drop all traffic from a single IP address.
aloha,
dave
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
t;:
Having compiled a 2.4.18 kernel with Freeswan I discover the following
problem:
When I try to give the command, for example: ipchains -P forward DENY
I get an error: "ipchains: Protocol not available"
But I see that I the ipchains packet installed. There isn't an ipchains
So, iptables replace ipchains?
Mike Egglestone wrote:
Hi,
You many want to look at using iptables with kernel 2.4.x
Cheers,
Mike
Quoting curtis <[EMAIL PROTECTED]>:
Having compiled a 2.4.18 kernel with Freeswan I discover the following
problem:
When I try to give the command, for e
Hi,
You many want to look at using iptables with kernel 2.4.x
Cheers,
Mike
Quoting curtis <[EMAIL PROTECTED]>:
> Having compiled a 2.4.18 kernel with Freeswan I discover the following
> problem:
>
> When I try to give the command, for example: ipchains -P forward DEN
Having compiled a 2.4.18 kernel with Freeswan I discover the following
problem:
When I try to give the command, for example: ipchains -P forward DENY
I get an error: "ipchains: Protocol not available"
But I see that I the ipchains packet installed. There isn't an ipchains
t
"Mark" <[EMAIL PROTECTED]> writes:
>
> I have the following rule on my WAN interface (eth1):
>
> ipchains -A input -s 63.148.99.0/24 -j DENY -l -i eth1
>
> So why is 63.148.99.229 able to access my Apache server?
Two possibilities come to mind. First, an
Ron Johnson wrote:
[snip]
Linux box for sharing my DSL connection. For a few years it used to be
just a 486, but I recently upgraded it to a K6-2/500 :)
Woo Hoo!! Go, Speed Racer, go! (Did the 486 die?)
One of them died, but the last one I was using just got replaced.
You don't even need
On Wed, 12 Jun 2002 19:48:14 -0700 (PDT)
"Alvin Oga" <[EMAIL PROTECTED]> wrote:
> trivial to run ipchains under 2.4.18...
This all depends on what features of ipchains you are using. The
compatibility layer provided for ipchains in the 2.4.x series does not
provide 100% of
On Wed, 2002-06-12 at 22:37, Chris Gushue wrote:
> Ron Johnson wrote:
> > On Wed, 2002-06-12 at 21:25, Chris Gushue wrote:
> [snip]
[snip]
> Linux box for sharing my DSL connection. For a few years it used to be
> just a 486, but I recently upgraded it to a K6-2/500 :)
Woo Hoo!! Go, Speed Racer,
Ron Johnson wrote:
On Wed, 2002-06-12 at 21:25, Chris Gushue wrote:
[snip]
On my home router, I'm still using a 2.2 kernel. I tried 2.4 at one
point, but found the ipmasq modules lacking (unless I missed something,
which is likely). Overall, it shouldn't hurt to stick with ipchai
On Wed, 2002-06-12 at 21:25, Chris Gushue wrote:
> Andrew Perrin wrote:
[snip]
> On my home router, I'm still using a 2.2 kernel. I tried 2.4 at one
> point, but found the ipmasq modules lacking (unless I missed something,
> which is likely). Overall, it shouldn't hurt
On Wed, Jun 12, 2002 at 10:16:09PM -0400, Andrew Perrin wrote:
| I'd like to upgrade my home machine's kernel to 2.4.18, but I'm not too
| excited about moving from ipchains to iptables. (This machine acts as a
| router from the home network [on eth0] and our DSL service [eth1]
hi ya andrew
On Wed, 12 Jun 2002, Andrew Perrin wrote:
> I'd like to upgrade my home machine's kernel to 2.4.18, but I'm not too
> excited about moving from ipchains to iptables. (This machine acts as a
> router from the home network [on eth0] and our DSL service [eth1].
Andrew Perrin wrote:
I'd like to upgrade my home machine's kernel to 2.4.18, but I'm not too
excited about moving from ipchains to iptables. (This machine acts as a
router from the home network [on eth0] and our DSL service [eth1].) So, a
few questions:
- How easy or hard is i
I'd like to upgrade my home machine's kernel to 2.4.18, but I'm not too
excited about moving from ipchains to iptables. (This machine acts as a
router from the home network [on eth0] and our DSL service [eth1].) So, a
few questions:
- How easy or hard is it to migrate an ipch
There is no provision that I am aware of in 2.2 kernels for iptables.
You do have to set up packet filtering, etc., when you build your
kernel. 2.4 kernels do allow for ipchains, but you must selet that
option when you build them. Selecting one (ipchains or iptables)
blocks use of the other, so
On Fri, May 31, 2002 at 03:52:15PM -0700, Paul E Condon wrote:
> OK, so I'm really using kernel 2.2.19, but...
> I have been under the impression that the method of packet
> filtering/forwarding
> changed from something called 'ipchains' in 2.2 to something called
Jamin W. Collins wrote:
> On Tue, 28 May 2002 15:30:04 +0200
> "Marcus Przyklink" <[EMAIL PROTECTED]> wrote:
>
> > Jamin W. Collins wrote:
> > > On Tue, 28 May 2002 15:02:24 +0200
> > > "Marcus Przyklink" <[EMAIL PROTECTED]> wrote:
> > > > wotan:~ # cat masquerading
> > > > iptables -t nat -A POS
1 - 100 of 485 matches
Mail list logo
