From: "Erik Ahlner" <whyz@home.se>
To: netfilter@lists.netfilter.org
Subject: Iptables and kernel 2.6.4 on slackware 9.1
Date: Mon, 29 Mar 2004 15:53:25 +0200 [thread overview]
Message-ID: <000c01c41595$34b4a1a0$0200a8c0@whyzpc> (raw)
hello!
I've recently reentered this mailinglist and thus i don't know if this
question has been asked before.. i hope i'm not alone with this problem!
Last week I bought a new harddrive for my box, and installed slackware 9.1
(had 8.0 earlier) and compiled kernel 2.6.4 (had 2.4.22 earlier). At first,
everything seems to be fine, iptables runs.
But after half an hour or so, iptables just stops working. It's only
iptables that does this (i suppose), the server/router still has connection
to the internet and the computers behind it.
(I.e i have a ventrilo server running on the router, and i can still talk to
users connecting to it from the internet, while i'm connected to it from
inside the lan).
After about 5 minutes of downtime iptables suddenly starts working again,
and the computers on the NAT has internet access again.
These are my rules:
IPTABLES=/usr/sbin/iptables
EXTIF="eth0"
INTIF="eth1"
$IPTABLES -P INPUT ACCEPT
$IPTABLES -F INPUT
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -F OUTPUT
$IPTABLES -P FORWARD DROP
$IPTABLES -F FORWARD
$IPTABLES -t nat -F
$IPTABLES -A FORWARD -i $EXTIF -o $INTIF -j ACCEPT
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE
Nothing here has changes since i was running kernel 2.4.22.
What could be the problem?
Anyone else who has experienced this?
I'm using iptables v1.2.9
Regards
Erik Ahlner
next reply other threads:[~2004-03-29 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 13:53 Erik Ahlner [this message]
2004-03-31 0:49 ` Iptables and kernel 2.6.4 on slackware 9.1 Mark E. Donaldson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000c01c41595$34b4a1a0$0200a8c0@whyzpc' \
--to=whyz@home.se \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.