From: Kerin Millar <kerframil@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: Xen and netfilter
Date: Sun, 04 Mar 2012 04:21:47 +0000 [thread overview]
Message-ID: <jiuqkr$gju$1@dough.gmane.org> (raw)
In-Reply-To: <1330812708.2053.8.camel@huxley.cinosure.com>
On 03/03/2012 22:11, Jonathan Gowar wrote:
> Hi there,
>
> I've been advised to contact you guys in order to resolve an issue in
> the system log files when using netfilter with Xen. It's with humility
> that I ask, as I can not say with authority where the problem lies.
>
> I get many of these logs, so much so that I can't see any other errors.
>
> Mar 2 13:31:07 esme-grace kernel: [98068.833692] physdev match: using
> --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
> non-bridged traffic is not supported anymore.
> Mar 2 13:31:07 esme-grace kernel: [98068.833697] physdev match: using
> --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
> non-bridged traffic is not supported anymore.
>
> I found a link on Xen Wiki, which has gone some way to repress the
> issue, but there are still a few that crop up.
>
> http://wiki.xensource.com/xenwiki/XenNetworking#head-602e26cd4a03b992f3938fe1bea03fa0fea0ed8b
>
> It's also been suggested to me to ask, either a) to remove the
> informal messages, or ideally b) suppressing the messages if the rule in
> question is doing bridged traffic.
>
Apparently, the issue is with the vif-common.sh script. The fix is to
add --physdev-is-bridged to the offending rules so that only bridged
traffic is considered.
http://xenbits.xensource.com/hg/xen-unstable.hg/rev/b0fe8260cefa
--Kerin
prev parent reply other threads:[~2012-03-04 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 22:11 Xen and netfilter Jonathan Gowar
2012-03-04 4:21 ` Kerin Millar [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='jiuqkr$gju$1@dough.gmane.org' \
--to=kerframil@gmail.com \
--cc=netfilter@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