From: Leonardo <p0q0b0d@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: ICMP frag needed not forwarded to MSQ clients
Date: Thu, 26 May 2005 14:47:31 +0200 [thread overview]
Message-ID: <3b1e6f48050526054740113f78@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505261355220.24500@blackhole.kfki.hu>
On 5/26/05, Jozsef Kadlecsik <kadlec@blackhole.kfki.hu> wrote:
> On Thu, 26 May 2005, Leonardo wrote:
>
> > That's exactly the problem! The clients should receive an ICMP frag
> > needed packet in order to reduce the packet size, however my
> > proxy/router does not forward the ICMP msg to them! WHY?!?!?!
> > The are no iptables rules that block ICMP!
>
> As you have no DROP rule, netfilter does not drop the packets so it's not
> a netfilter/iptables related problem.
May be it's like you say... but really i do not have idea where else
to look for...
> Probably you have got rp_filtering enabled and the routing engine discards
> the ICMP packets.
>
Yes, I have it enabled. Disabling it does not solve the problem... :-(
echo 0 > /proc/sys/net/ipv4/conf/eth2/rp_filter
echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter
ICMP packets type 3 are NOT routed anyway...
> Best regards,
> Jozsef
> -
Thank you.
--
Leonardo Arena
next prev parent reply other threads:[~2005-05-26 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 8:17 ICMP frag needed not forwarded to MSQ clients Leonardo
[not found] ` <200505251112.23022.98111@free.fr>
2005-05-25 11:23 ` Leonardo
2005-05-25 16:25 ` R. DuFresne
2005-05-26 7:25 ` Leonardo
2005-05-26 11:59 ` Jozsef Kadlecsik
2005-05-26 12:47 ` Leonardo [this message]
2005-05-26 13:09 ` Jozsef Kadlecsik
2005-05-26 14:09 ` Leonardo
2005-05-26 14:33 ` Jozsef Kadlecsik
[not found] ` <3b1e6f480505270006ea481be@mail.gmail.com>
2005-05-27 7:07 ` Leonardo
2005-05-27 7:24 ` Jozsef Kadlecsik
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=3b1e6f48050526054740113f78@mail.gmail.com \
--to=p0q0b0d@gmail.com \
--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.