From: Gerd Hoffmann <kraxel@suse.de>
To: Reiner Sailer <sailer@us.ibm.com>
Cc: xen-devel@lists.xensource.com, xense-devel@lists.xensource.com,
Bryan D Payne <bdpayne@us.ibm.com>
Subject: Re: RFC: virtual network access control
Date: Fri, 28 Jul 2006 17:13:07 +0200 [thread overview]
Message-ID: <44CA2983.3030602@suse.de> (raw)
In-Reply-To: <OF2D45C46C.D2F566C3-ON852571B9.004CF5F9-852571B9.004E8C1D@us.ibm.com>
Reiner Sailer wrote:
> We are interested in controlling access based on the security labels of
> sender and receiver domains, not based on IP or other traditional
> firewall packet attributes.
>
> We see other problems as well: IPtables seems to not see any of the
> ethernet-bridged packets. If you wanted to use IPtables then you
> would need to replace the ethernet bridge with routing each packet.
You want CONFIG_BRIDGE_NETFILTER=y, this makes iptabes see bridged packets.
Additionally you need CONFIG_NETFILTER_XT_MATCH_PHYSDEV=y, that allows
matching on the physical device name for bridged packets. That way you
can filter by domain (because each domain has its own virtual bridge
port) instead of ip/mac address.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
next prev parent reply other threads:[~2006-07-28 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 20:51 RFC: virtual network access control Reiner Sailer
2006-07-27 20:57 ` Caitlin Bestler
2006-07-28 9:18 ` Keir Fraser
2006-07-28 14:17 ` Reiner Sailer
2006-07-28 14:31 ` Keir Fraser
2006-07-28 14:56 ` Reiner Sailer
2006-07-28 15:06 ` Keir Fraser
2006-07-28 16:30 ` Reiner Sailer
2006-07-28 23:43 ` Mike Day
2006-07-28 14:47 ` Harry Butterworth
2006-07-28 15:13 ` Gerd Hoffmann [this message]
2006-07-28 19:49 ` [Xense-devel] " Reiner Sailer
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=44CA2983.3030602@suse.de \
--to=kraxel@suse.de \
--cc=bdpayne@us.ibm.com \
--cc=sailer@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
--cc=xense-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.