From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alan Ezust <alan.ezust@presinet.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: conntrack -E -i not allowed?
Date: Thu, 09 Nov 2006 18:10:05 +0100 [thread overview]
Message-ID: <455360ED.2030809@netfilter.org> (raw)
In-Reply-To: <200611090852.14878.alan.ezust@presinet.com>
Alan Ezust wrote:
> Thanks for the reply. Ok, I can see how I can generate some IDs, but I first
> want to make sure i have all of the information I need.
>
> When I run conntrack, I only see one protocol number. I think it is a layer4
> protocol (tcp vs udp). If I'm not seeing an l3proto in my output, why might
> that be?
>
> udp 17 12 src=10.10.201.2 dst=204.174.64.1 sport=54475 dport=53
> src=204.174.64.1 dst=209.53.156.2 sport=53 dport=54475 use=1 mark=0
> tcp 6 420332 ESTABLISHED src=10.10.100.3 dst=10.10.1.22 sport=1356
> dport=5432 src=10.10.1.22 dst=10.10.100.3 sport=5432 dport=1356 [ASSURED]
> use=1 mark=0
Are you using nf_conntrack? If so, l3protonum is not shown yet but it
would not be hard to cook a patch to show it. I'll introduce this change
in the new libnetfilter_conntrack API.
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next prev parent reply other threads:[~2006-11-09 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 18:43 conntrack -E -i not allowed? Alan Ezust
2006-11-02 19:11 ` Alan Ezust
2006-11-07 12:40 ` Pablo Neira Ayuso
2006-11-07 18:37 ` Alan Ezust
2006-11-08 19:29 ` Pablo Neira Ayuso
2006-11-09 16:52 ` Alan Ezust
2006-11-09 17:10 ` Pablo Neira Ayuso [this message]
2006-11-09 20:54 ` Alan Ezust
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=455360ED.2030809@netfilter.org \
--to=pablo@netfilter.org \
--cc=alan.ezust@presinet.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.