From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Jonathan Tripathy <jonnyt@abpni.co.uk>
Cc: netfilter@vger.kernel.org
Subject: Re: ebtables and anti-spoofing rules not working 100%?
Date: Sun, 29 Aug 2010 20:36:02 +0200 [thread overview]
Message-ID: <4C7AA892.2050608@wpkg.org> (raw)
In-Reply-To: <4C7AA590.6040704@abpni.co.uk>
On 29.08.2010 20:23, Jonathan Tripathy wrote:
>> I can use anything, as long as it "pins" given MAC/IP addresses to a
>> VM guest - and that any "rogue" guest is not able to disrupt traffic
>> to other VM guests (or, worse, the gateway) - i.e. by changing its own
>> IP/MAC to something else, possibly addresses used by other guests /
>> gateway.
>>
>>
> Yes, but the INPUT chain is only relevant for traffic destined for the
> host itself. Does the host actually do anything in your case, or is it
> just a bridging device?
Not sure I understand your question correctly, or if we refer to the
same thing if we use "host".
The "host system" is a bridge and gateway, and runs VM guests (KVM).
As guests are fully virtualized systems, they are technically free to
change their IP and MAC address (users have root access). This means
they can be a danger to other virtual guests, or generally network
infrastructure, if they change their IP or MAC addresses to something
different they should have.
Therefore, I would like to prevent it, but so far, my tries with
iptables or ebtables were not really successful.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2010-08-29 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 13:59 ebtables and anti-spoofing rules not working 100%? Tomasz Chmielewski
2010-08-29 15:28 ` Pascal Hambourg
2010-08-29 16:46 ` Tomasz Chmielewski
2010-08-29 17:25 ` Jonathan Tripathy
2010-08-29 17:34 ` Tomasz Chmielewski
2010-08-29 18:23 ` Jonathan Tripathy
2010-08-29 18:36 ` Tomasz Chmielewski [this message]
2010-08-30 18:14 ` Pascal Hambourg
2010-08-30 18:38 ` Tomasz Chmielewski
2010-08-30 21:34 ` Pascal Hambourg
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=4C7AA892.2050608@wpkg.org \
--to=mangoo@wpkg.org \
--cc=jonnyt@abpni.co.uk \
--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 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.