From: Dennis Jacobfeuerborn <d.jacobfeuerborn@conversis.de>
To: netfilter@vger.kernel.org
Subject: iptables sporadic "sendmsg: operation not permitted" problem and packet loss
Date: Sat, 07 Mar 2009 22:33:37 +0100 [thread overview]
Message-ID: <49B2E831.3040809@conversis.de> (raw)
Hi,
I'm running into a problem on a machine that right now acts as a simple
gateway but is supposed to become a firewall too. When I start iptables
using "/etc/init.d/iptables start" on the Centos 5.2 machine first
everything works fine but after about 30 seconds I'm seeing packet loss and
running a ping outputs "sendmsg: operation not permitted" sporadically.
The moment I stop iptables again everything returns to normal. What is
consufing to me is that I don't even have any rules defined so far. This is
what my "/etc/sysconfig/iptables" file looks like:
# Generated by iptables-save v1.3.5 on Thu Mar 5 17:40:28 2009
*filter
:INPUT ACCEPT [26715202:4750206096]
:FORWARD ACCEPT [1382646771:1563210213960]
:OUTPUT ACCEPT [22930985:6256734041]
COMMIT
iptables -L says:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Does anyone have an idea why that would have such a severe impact on the
traffic? The fact that it takes a moment for the problems to show up makes
me suspect some kind of buffer issue so that the packet loss only begins to
occur after some buffer begins to overflow. That just a guess though and I
have no idea what buffer that could be.
Regards,
Dennis
next reply other threads:[~2009-03-07 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 21:33 Dennis Jacobfeuerborn [this message]
2009-03-09 13:33 ` iptables sporadic "sendmsg: operation not permitted" problem and packet loss Gáspár Lajos
2009-03-09 15:11 ` Dennis J.
2009-03-09 20:12 ` Mart Frauenlob
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=49B2E831.3040809@conversis.de \
--to=d.jacobfeuerborn@conversis.de \
--cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox