[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] IP blocking


  • To: "mail4dla@xxxxxxxxxxxxxx" <mail4dla@xxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: shacky <shacky83@xxxxxxxxx>
  • Date: Mon, 6 Aug 2007 21:34:12 +0200
  • Delivery-date: Mon, 06 Aug 2007 12:32:06 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AFGb9jnQtMiQOQqAta0G3kRmCdA0hAwEdplxI/QAQu+UfmijOgbJNAJ2PiRP8LPVwLd6s8oV0J794cCZhB2Pn0rylcn45iC+/L51mp6JvQyqUAoVV+DUS0TmU7E3VzVV7wt0rbD8+xnVAo3UsW6JWkODoQLvM1iCq4CAepcjuFk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.