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] vif-common.sh and iptables

To: Dmitry Nedospasov <dmitry@xxxxxxxxx>
Subject: Re: [Xen-users] vif-common.sh and iptables
From: Andrew McGlashan <andrew.mcglashan@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 26 Apr 2011 22:19:32 +1000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 26 Apr 2011 05:21:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110426110624.GA641@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Affinity Vision Australia Pty Ltd
References: <20110426110624.GA641@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.24 (Windows/20100228)
Hi Dmitry,

Dmitry Nedospasov wrote:
I have a question about vif-common.sh. I run multiple bridges attached
on dummy interfaces, which allow me to put guests in seperate subnets
(routed through the dom0). As you might expect I already have quite
extensive iptables scripts to accomidate this kind of routing.

I was just hoping someone on this list can confirm, that I understand
what the iptables lines in vif-common.sh actually do:

iptables "$c" FORWARD -m physdev --physdev-in "$vif" "$@" -j ACCEPT \
  2>/dev/null &&
iptables "$c" FORWARD -m state --state RELATED,ESTABLISHED -m physdev
\
  --physdev-out "$vif" -j ACCEPT 2>/dev/null

From what i can tell the goal of these lines is to allow networking even
if the default FORWARD policy is DENY, am I right? Is there any
additional side-effect if I comment these lines out in vim-common.sh,
that I'm not considering?

That caused me issues and those settings were in place due to "anti-spoofing" setup.

I dropped anti-spoofing to "fix" my setup somewhat. Until I did that, I couldn't get to the DomU machines directly via the bridged interface.

Now I can get through, but there are still issues that are not resolved [1] -- sometimes I connect, sometimes I don't; I really need a fix for this.


[1]  http://comments.gmane.org/gmane.comp.emulators.xen.user/66214



--
Kind Regards
AndrewM

Andrew McGlashan
Broadband Solutions now including VoIP


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>