From: Bourne Without <blackhole@airpost.net>
To: markus lottmann <LottvomSchlott@gmx.de>
Cc: netfilter@vger.kernel.org
Subject: Re: EPERM instead of ENETUNREACH for "to unreachable" route
Date: Mon, 15 Apr 2013 16:46:51 +0200 [thread overview]
Message-ID: <516C12DB.1090804@airpost.net> (raw)
In-Reply-To: <trinity-0ed09791-dae7-40db-b90e-85e114c79679-1366032496429@3capp-gmx-bs01>
On 15.04.2013 15:28, markus lottmann wrote:
[...]
> In this setup the command: ping -Q 1 8.8.8.8 yields EPERM instead of the expected ENETUNREACH. Does anyone have an explanation for this? The only thing I found in a web search was that EPERM is returned if an OUTPUT rule in the filter table is dropping packets.
http://marc.info/?l=netfilter-devel&m=136518055130415&w=2
might answer this
prev parent reply other threads:[~2013-04-15 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 13:28 EPERM instead of ENETUNREACH for "to unreachable" route markus lottmann
2013-04-15 14:46 ` Bourne Without [this message]
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=516C12DB.1090804@airpost.net \
--to=blackhole@airpost.net \
--cc=LottvomSchlott@gmx.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