All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
Date: Fri, 3 Sep 2010 09:55:35 +0200	[thread overview]
Message-ID: <20100903075535.GA24488@aepfle.de> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01A92A23@trantor>

On Fri, Sep 03, James Harper wrote:

> I see lots and lots of " physdev match: using --physdev-out in the
> OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not
> supported anymore." in the kernel logs. You can turn off some of the
> iptables stuff by turning off antispoofing but the stuff in
> vif-common.sh is not under admin control.
> 
> Not tested, but I think something like this might be required to make it
> work better:
> 
> ---
> /usr/local/src/xen-4.0-testing.hg/dist/install/etc/xen/scripts/vif-commo
> n.sh        2010-08-25 22:05:47.000000000 +1000
> +++ vif-common.sh       2010-09-03 10:05:03.316931684 +1000
> @@ -66,6 +66,11 @@
> 
>  frob_iptable()
>  {
> +  if [ `cat /proc/sys/net/bridge/bridge-nf-call-iptables` != "1" ]

Does that file always exist?
Better do "`${shell_code}`" to force an empty string if cat fails.

Olaf

      reply	other threads:[~2010-09-03  7:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03  0:06 physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore James Harper
2010-09-03  7:55 ` Olaf Hering [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=20100903075535.GA24488@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.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 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.