All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo <p0q0b0d@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: ICMP frag needed not forwarded to MSQ clients
Date: Fri, 27 May 2005 09:07:32 +0200	[thread overview]
Message-ID: <3b1e6f4805052700076d965d98@mail.gmail.com> (raw)
In-Reply-To: <3b1e6f480505270006ea481be@mail.gmail.com>

On 5/26/05, Jozsef Kadlecsik <kadlec@blackhole.kfki.hu> wrote:
>
> Do the packet correspond to what you expect as ICMP reply packet: src and
> dst IP addresses are OK? What's inside the packet, i.e the src/dst IP,
> protocol, ports inside the ICMP error message are OK?
>
> Best regards,
> Jozsef
> -

Everything seems to be ok... src is the next hop after the gateway on
eth2 (the VPN box), dst is eth2, TCP ports are ok. ICMP msg correctly
encapsulate the previos IP datagram (ACK number correspond) that needs
fragmentation...
On the other hand ICMP echo packets works correctly, they report the
same dst (eth2) and are correctly unmasqueraded and forwarded to the
client...

Could it be something distribution-related setting or patch?
I'm using Gentoo.
Thank you
--
Leonardo Arena


  parent reply	other threads:[~2005-05-27  7:07 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
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 [this message]
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=3b1e6f4805052700076d965d98@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.