[Xen-users] [Q][Xen-3.2] Can i resort to old network naming of b

To:	xen-users@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-users] [Q][Xen-3.2] Can i resort to old network naming of bridges and interfaces?
From:	"pradeep singh rautela" <rautelap@xxxxxxxxx>
Date:	Wed, 27 Feb 2008 18:12:32 +0530
Delivery-date:	Wed, 27 Feb 2008 04:43:02 -0800
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=PW3ej9bzQkWCEJngkzi343n+CqV/uT/7r3d0y8goT1w=; b=oAyjVmOd/TthA1inHr6CwSlLr9CWiATebeNCwAx1VHhqBxEzkMpk2OlkAgzs0p1lQWH4iIt3iHbc5dSvdaZPtr4MVc6R/fuFk/gSB8v37FndvYeazzSHSoPctAw6jIEgsE3Cgvr3bYj2NPkZ/6s+fr41MTWion9nMvrKZV0LWl0=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=MYjUWSgfmFBg0eFFotzAzDscDCv+aSysSwoQ6ipbtk52XRb6tDglE8jdy+0CfCVlKAnotrNPm7peouUDE0rr8zBHmEaP1mD6uimyHh5vq13/tB7ExOlaPjcUI5lbrX14eOy7QjdCMTpariFVDCKCURk3s4eMtcWUepWKaFVo1TM=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
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>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Hi,

xen-3.2 seem to have changed the way bridges and virtual interfaces
are handled in Xen now.

Bridges seem to called eth0, eth1 ... and so on with IP addresses
attached to them.

Is there a way that i can resort to old method of using xenbr0,
xenbr1... vif0.0, vif0.1...and so on?

Reason is, in my old Xen setup, i was able to detach vif0.1 from
xenbr1 and still able to ping  eth1 in a domU from an external
machine, which is really handy at times.This way eth1 in domain0 was
not pingable but eth1 in a domU still was.

Now in xen 3.2 this seems to be not possible with things changing.

How can i do this in Xen-3.2 ? If it is not possible, can i resort to
old way of interfaces and their naming and working in Xen-3.2?

Any help or pointers will be appreciated.

Thanks,
         --Pradeep

-- 
Pradeep Singh Rautela
http://eagain.wordpress.com
http://emptydomain.googlepages.com

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

WARNING - OLD ARCHIVES

xen-users

[Xen-users] [Q][Xen-3.2] Can i resort to old network naming of bridges a