From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: "Albrecht Dreß" <albrecht.dress@arcor.de>
Cc: netfilter@lists.netfilter.org, gtaylor@riverviewtech.net
Subject: Re: Help: iptables NAT broken with pppoe
Date: Tue, 10 May 2005 14:19:33 +0100 [thread overview]
Message-ID: <4280B4E5.1070209@dsl.pipex.com> (raw)
In-Reply-To: <4448571.1115722979939.JavaMail.ngmail@webmail-06.arcor-online.net>
Albrecht Dreß wrote:
>>One thought - the tcpdump is incomplete by just looking at port 80 you
>>can't see what ICMP are being sent.
>
>
> Well, the idea was to reduce the amount of data reported by tcpdump. My naive assumption was that running the two tcpdump's on eth0 and ppp0, I would see the request packet coming from eth0, the masqueraded one on ppp0, and the same process in the opposite direction for the reply.
>
> Why do you think it would be important to see the icmp's, too?
Just thought it would be better to be able to see all what was going on
- I have no specific ideas, though.
Andy.
next prev parent reply other threads:[~2005-05-10 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 16:36 Help: iptables NAT broken with pppoe Albrecht Dreß
2005-05-07 6:12 ` Taylor, Grant
2005-05-07 20:00 ` Albrecht Dreß
2005-05-09 5:56 ` Taylor, Grant
2005-05-09 14:08 ` Jason Opperisano
2005-05-09 18:37 ` Albrecht Dreß
2005-05-09 18:43 ` Taylor, Grant
2005-05-10 10:31 ` Andy Furniss
2005-05-10 10:36 ` Andy Furniss
2005-05-10 11:02 ` Albrecht =?unknown-8bit?q?Dre=DF?=
2005-05-10 13:19 ` Andy Furniss [this message]
2005-05-11 17:00 ` Albrecht Dreß
2005-05-11 18:39 ` Taylor, Grant
2005-05-10 3:00 ` R. DuFresne
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=4280B4E5.1070209@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=albrecht.dress@arcor.de \
--cc=gtaylor@riverviewtech.net \
--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.