netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: NAT regression in next tree
Date: Fri, 19 Feb 2010 06:45:43 +0100	[thread overview]
Message-ID: <4B7E2587.3050608@trash.net> (raw)
In-Reply-To: <20100218173633.30bb8c41@nehalam>

Stephen Hemminger wrote:
> Something in net-next tree broke bridging of virtual nets.
> My local VM's can no longer access external networks.
> 
> It is a NAT problem. One of the recent netfilter changes is causing
> the packets to not have there source address rewritten.
> 
> I see:
>     VM1  -- 192.168.100.0/24 -- HOST -- 192.168.1.0/24 -- ROUTER
>                            virbr0    eth0
> 
> Even a simple ping from VM1 doesn't get responded to because
> the 192.168.100.X source address is not getting rewritten.

I'll try to reproduce it locally. What is the HEAD of the broken
tree you're running?

  reply	other threads:[~2010-02-19  5:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100216173658.519b6245@nehalam>
     [not found] ` <201002171526.02493.arnd@arndb.de>
2010-02-19  1:36   ` NAT regression in next tree Stephen Hemminger
2010-02-19  5:45     ` Patrick McHardy [this message]
2010-02-19  5:51       ` Stephen Hemminger
2010-02-19  7:06         ` Patrick McHardy
2010-02-19  7:20           ` Eric Dumazet
2010-02-19  7:27             ` Patrick McHardy
2010-02-19 18:11               ` Stephen Hemminger

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=4B7E2587.3050608@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /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).