From: Patrick McHardy <kaber@trash.net>
To: elendil@planet.nl
Cc: Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 8519] New: NAT prerouting over tun interface broken
Date: Tue, 22 May 2007 00:28:07 +0200 [thread overview]
Message-ID: <46521CF7.3070601@trash.net> (raw)
In-Reply-To: <20070521131343.cbf3bcaa.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Mon, 21 May 2007 13:05:36 -0700
> bugme-daemon@bugzilla.kernel.org wrote:
>
>>Problem Description:
>>I have the hercules s/390 emulator running on an EM64T host, both running
>>Debian unstable. I use a tun interface, a second IP address on eth0 and
>>iptables/nat so the emulator has it's own address on my local network.
>>
>>With 2.6.21.1 on the host, networking between the emulator and the host system
>>is fine (I can ssh from the host into the emulator without problems), but
>>communication from the emulator with other boxes is broken. Other boxes also
>>don't see the emulator if I ping its external address.
>>
>>If I ping another box on my LAN from the emulator while running wireshark on
>>the host, I can see that:
>>- the echo request gets sent OK
>>- the other box replies OK
>>- the host receives the echo reply
>>- but the tun interface never gets it.
>>
>>If I boot the host with 2.6.20 everything works fine again.
Please post the output of lsmod and cat /proc/net/ip_conntrack after
sending a ping.
prev parent reply other threads:[~2007-05-21 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705212005.l4LK5aJk029945@fire-2.osdl.org>
2007-05-21 20:13 ` [Bugme-new] [Bug 8519] New: NAT prerouting over tun interface broken Andrew Morton
2007-05-21 22:28 ` Patrick McHardy [this message]
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=46521CF7.3070601@trash.net \
--to=kaber@trash.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=elendil@planet.nl \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).