All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Craig <philipc@snapgear.com>
To: Helge Weissig <helgew@grajagan.org>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: protocol 50 unreachable
Date: Fri, 03 Dec 2004 16:35:59 +1000	[thread overview]
Message-ID: <41B0094F.2010602@snapgear.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0412021120210.25230-100000@gollum.grajagan.net>

Helge Weissig wrote:
> I mean with "incomplete" that the tcpdump traffic I see does not show up 
> in the logs. I used your rules at the end of your reply and see the same 
> thing: ESP from VPN_SERVER hits $EXTIF, triggers the "protocol 50 
> unreachable" icmp response and no log entry ever shows up in the kernel 
> log from the iptables log rule. I am suspecting that your option 3) is 
> indeed the problem.
> 
> h.

It is possible that a conntrack already exists, or the packet can't be
conntracked, so the packet doesn't pass through nat PREROUTING.

Try putting the log rule in the mangle PREROUTING chain.
If they do match a log rule here, check if they are invalid
with -m conntrack --ctstate INVALID.

Also check if there are any esp conntracks in /proc/net/ip_conntrack

-- 
Philip Craig - SnapGear, A CyberGuard Company - http://www.SnapGear.com


  parent reply	other threads:[~2004-12-03  6:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 22:51 protocol 50 unreachable Helge Weissig
2004-12-01 23:59 ` John A. Sullivan III
2004-12-02  0:07   ` Helge Weissig
2004-12-02  0:29 ` Jason Opperisano
2004-12-02  3:29   ` Helge Weissig
2004-12-02  3:46     ` Jason Opperisano
2004-12-02  4:00       ` Helge Weissig
2004-12-02  4:09         ` John A. Sullivan III
2004-12-02  4:12         ` Jason Opperisano
2004-12-02  4:53           ` Helge Weissig
2004-12-02  5:15             ` John A. Sullivan III
2004-12-02  5:44               ` Helge Weissig
2004-12-02 15:14                 ` Jason Opperisano
2004-12-02 15:13                   ` Helge Weissig
2004-12-02 17:25                     ` Jason Opperisano
2004-12-02 18:22                       ` Helge Weissig
2004-12-02 18:54                         ` John A. Sullivan III
2004-12-02 20:11                         ` Jason Opperisano
2004-12-02 19:26                           ` Helge Weissig
2004-12-02 20:56                             ` Jason Opperisano
2004-12-02 20:12                               ` Helge Weissig
2004-12-02 21:30                                 ` Jason Opperisano
2004-12-03  6:35                             ` Philip Craig [this message]
2004-12-03 17:11                               ` Helge Weissig
2004-12-04  2:20                                 ` Alistair Tonner
2004-12-04  2:35                                   ` Jason Opperisano
2004-12-04  3:03                                     ` Helge Weissig
2004-12-02  4:03   ` John A. Sullivan III
2004-12-04 17:07 ` Helge Weissig

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=41B0094F.2010602@snapgear.com \
    --to=philipc@snapgear.com \
    --cc=helgew@grajagan.org \
    --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.