WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] IP blocking

To: shacky <shacky83@xxxxxxxxx>
Subject: Re: [Xen-users] IP blocking
From: mail4dla@xxxxxxxxxxxxxx
Date: Tue, 7 Aug 2007 18:21:05 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 07 Aug 2007 09:18:43 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=eS/7yicBrIUvRbN04Tyn1pmudFyJNexEUUJ09rC2pznt+owxuenc87WdaTV2F2XcHEBhcQEDTYpvqTxYOQ0akF95l/ffWBVJFfZGexy2ppvC3pPMkZ8dcnldBiLYzsJ99sexCxuqx97Qfq+JApsA899I77UCiNIDDKrx+jwu59Q=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=GNqRCEIKgNu4hs5VM9meDDrgMmClk/e5GR3cse9jsUi1udKKcJ7oQhlHvWn9JdGbQkqX4xq2E+Y+CgxjnV6dL81Te3woRhrB9bC7KID3OgbN2hfnNG9QAfLnrvfsOFCwy90l/CaOjZcsevwj0Ji+w0pJQhFt8POhUjSDfbxRCq8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <7fedbc910708061234u32199d0ekdbe9f124710eb0d7@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <7fedbc910708060518s510357cdx7e3be43159616815@xxxxxxxxxxxxxx> <f9264670708060553x6ad7df3ao4a8748c1b01da7fc@xxxxxxxxxxxxxx> <7fedbc910708061234u32199d0ekdbe9f124710eb0d7@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Well, first of all, you have to disconnect the vifX.Y from xenbrZ.
Then, you configure an IP address on both ethY (in the DomU) and vifX.Y (in the Dom0). You can dig up my mail on the topic "Re: Poin to point connection" on this list.
If you enable routing, everything should be fine. Of course you also have to make propagate the route back to the DomUs (via your Dom0's IP) on the network.
I can't tell you what to do, because I do not know *excactly* what you're aiming at.
If you're dependent on some sort of provider, i.e. you have rented some server, you're probably best at following the already mentioned approach of using iptables and ebtables. It has the great benefit that you do not need cooperation (or at least, less cooperation) from your provider. However, in the default setup, every DomU has its own MAC address that becomes visible on the network. You should definitely check that this is OK within your network.

Cheers,
dla

On 8/6/07, shacky <shacky83@xxxxxxxxx> wrote:
> I suggest you stop to bridge the DomUs directly to the network.

Could you tell me how I can stop it?

> iptables should also be able to do this on bridge level, but I would not
> consider this a clean approach.

Have you ever used Shorewall to control the routing of the domUs?
Could you help me to understand how to write the iptables rules to
make what I wrote at the beginning of this thread?

I thank you very much for your help! :-)

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>