All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Tonner <Alistair@nerdnet.ca>
To: netfilter@lists.netfilter.org
Subject: Re: protocol 50 unreachable
Date: Fri, 3 Dec 2004 21:20:44 -0500	[thread overview]
Message-ID: <200412032120.44988.Alistair@nerdnet.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0412030908140.29374-100000@gollum.grajagan.net>

On December 3, 2004 12:11 pm, Helge Weissig wrote:
> ahhh... finally I see something... but what does it mean???
>
> added the following two log rules:
> $IPTABLES -A PREROUTING -t mangle -j LOG --log-level info --log-prefix 'all
> mangle preroute: ' $IPTABLES -A PREROUTING -t mangle -m conntrack --ctstate
> INVALID -j LOG --log-level info --log-prefix 'contrack mangle preroute: '
>
> the second generates the following error:
> iptables v1.2.6a: Couldn't load match
> `conntrack':/lib/iptables/libipt_conntrack.so: cannot open shared object
> file: No such file or directory
 
 The above error indicates you did not build the conntrack match module and 
related iptables code. 

>
> the ESP's however now show up in the log (these are nmap generated):

> Dec  3 09:07:23 gollum kernel: all mangle preroute: IN=eth0 OUT=
> MAC=00:90:27:ca:39:56:00:10:67:00:b4:3e:08:00 SRC=vpn.server.ip
> DST=ext.if.ip LEN=20 TOS=0x00 PREC=0x00 TTL=32 ID=56785 PROTO=ESP
> INCOMPLETE [0 bytes] 

> Dec  3 09:07:23 gollum kernel: all mangle preroute: 
> IN=eth0 OUT= MAC=00:90:27:ca:39:56:00:10:67:00:b4:3e:08:00
> SRC=vpn.server.ip DST=ext.if.ip LEN=20 TOS=0x00 PREC=0x00 TTL=32 ID=7732
> PROTO=ESP INCOMPLETE [0 bytes]
>
 It would be nice to have the other packet(s) that went out to initiate this 
connection.  But it doesn't look good to me -- I *think* that ipt_LOG.c is 
saying that the packet structure for the ESP packet is incomplete.

eh = skb_header_pointer(skb, iphoff+ih->ihl*4,
     sizeof(_esph), &_esph);
  if (eh == NULL) {
   printk("INCOMPLETE [%u bytes] ",
          skb->len - iphoff - ih->ihl*4);
   break;

 Not sure how the packet is arriving in the LOG routine without the relevant 
data.


 Alistair Tonner
 RSO HP Unix admin.
 

> h.




  reply	other threads:[~2004-12-04  2:20 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
2004-12-03 17:11                               ` Helge Weissig
2004-12-04  2:20                                 ` Alistair Tonner [this message]
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=200412032120.44988.Alistair@nerdnet.ca \
    --to=alistair@nerdnet.ca \
    --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.