From: Arun Sharma <arun.sharma@intel.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: iptables issue
Date: Wed, 17 Aug 2005 16:01:19 -0700 [thread overview]
Message-ID: <4303C1BF.1080006@intel.com> (raw)
This line in network-brige script fails for me:
# iptables -A FORWARD -m physdev --physdev-in ${dev} -j ACCEPT
iptables: No chain/target/match by that name
$ grep CONFIG_IP_NF_MATCH_PHYSDEV *
xen0_defconfig_x86_32:# CONFIG_IP_NF_MATCH_PHYSDEV is not set
xen0_defconfig_x86_64:# CONFIG_IP_NF_MATCH_PHYSDEV is not set
xen_defconfig_x86_32:CONFIG_IP_NF_MATCH_PHYSDEV=m
xen_defconfig_x86_64:CONFIG_IP_NF_MATCH_PHYSDEV=m
xenU_defconfig_x86_64:CONFIG_IP_NF_MATCH_PHYSDEV=m
As a result, packets don't get forwarded between eth0 and xen-br0.
-Arun
next reply other threads:[~2005-08-17 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 23:01 Arun Sharma [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-17 23:13 iptables issue Ian Pratt
2005-08-17 23:14 ` Arun Sharma
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=4303C1BF.1080006@intel.com \
--to=arun.sharma@intel.com \
--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.