From: Harald Welte <laforge@netfilter.org>
To: Wouter Vanwalleghem <wouter@belnet.be>
Cc: Ramin Dousti <ramin@cannon.eng.us.uu.net>, netfilter@lists.netfilter.org
Subject: Re: Unable to stop tunnel from being "connection-tracked"
Date: Fri, 3 Oct 2003 12:16:55 +0200 [thread overview]
Message-ID: <20031003101655.GS5758@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <1065123318.29721.12.camel@xerxes.sketchingroom.home>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
> A tcpdump on my external interface (ppp0) only shows my echo-requests
> and no packets whatsoever coming from the tunnelbroker PoP. I would at
> least expect to see some or other packet, e.g. an icmp error message,
> coming from the tunnelbroker PoP.
iptables doesn't prevent packets from showing up in tcpdump. So you
will always see everything you receive on the wire in tcpdump,
independent of any iptables configuration.
this is because tcpdump hooks into PF_PACKET, which is at layer2, before
the ipstack (and thus iptables) is consulted at all.
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-03 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 11:10 Unable to stop tunnel from being "connection-tracked" Wouter Vanwalleghem
2003-10-02 13:52 ` Ramin Dousti
2003-10-02 19:35 ` Wouter Vanwalleghem
2003-10-03 10:16 ` Harald Welte [this message]
2003-10-03 19:43 ` Ramin Dousti
2003-10-03 20:02 ` Wouter Vanwalleghem
2003-10-03 10:15 ` Harald Welte
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=20031003101655.GS5758@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=ramin@cannon.eng.us.uu.net \
--cc=wouter@belnet.be \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox