From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: Andy Furniss <andy.furniss@dsl.pipex.com>
Cc: netfilter@lists.netfilter.org, "Taylor,
Grant" <gtaylor@riverviewtech.net>
Subject: Re: Help: iptables NAT broken with pppoe
Date: Tue, 10 May 2005 11:36:55 +0100 [thread overview]
Message-ID: <42808EC7.80805@dsl.pipex.com> (raw)
In-Reply-To: <42808D9C.2000603@dsl.pipex.com>
Andy Furniss wrote:
> Taylor, Grant wrote:
>
>>> Set them all to either 0 or 1 - still the same picture, the reply
>>> from the remote server results (in tcpdump) in the one with "win 0"
>>> being sent back instead of passing it to eth0.
>>
>>
>>
>> Hmm. Would it be possible to see the output of iptables-save? I'm
>> just wondering if there is something else in the mix that is messing
>> things up.
>>
>>> Any idea whom I could ask here for help? Maybe the Linux kernel
>>> mailing list? Or is there a more specialised one for networking issues?
>>
>>
>>
>> Sorry, I don't know off hand where to send you. Any one else have any
>> advice here?
>
>
> One thought - the tcpdump is incomplete by just looking at port 80 you
> can't see what ICMP are being sent.
>
> Andy.
Add OP to CC
next prev parent reply other threads:[~2005-05-10 10:36 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 [this message]
2005-05-10 11:02 ` Albrecht =?unknown-8bit?q?Dre=DF?=
2005-05-10 13:19 ` Andy Furniss
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=42808EC7.80805@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox