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] can't add vlans successfully

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] can't add vlans successfully
From: Zhang Li <cindy.zhangli@xxxxxxxxx>
Date: Wed, 12 Aug 2009 11:04:21 +0800
Cc: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 11 Aug 2009 20:05:02 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fU0BF5hso8DW6cUKkYLSF4nLFHAeL1ENt+AfnW6PXWQ=; b=QEiqtezq1d0SbA1SzLgWHCxKkJ997VlUFMGxvTHe3IOl/GgXo47cA7vFUXFO6gHzAL 6c7nrnP8VBcEfL2ZKymSSp5FGoH65AZ4UjHuPlUrPq0tQZVBImCGr2WxhOt6vqWZ84dT Bv2mllwU7JKmtMi+fMWeYcB4WwcZrtFPUBlLQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sHSR0JEtNWbpFU/wFfxbfFRjbPFNhYXMJRQ/2LKpqSpT3ZY2TIKdMkWE5U7xqfL7OY JFdEPH3/Y+EgzM+ZV/xlSE7DPIZ4MSZuz7b0hnBqE9Q/Uli7EpQAENMy8doGK9SgK5rb fLwUWesSv5JW786r920OkxWpA4I8vp/lM6U/I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0908111957l3e7e493cgfacf34403d7c0108@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/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>
References: <790b14c90908102056o3a091803w793b4e861584da57@xxxxxxxxxxxxxx> <7207d96f0908102146t40548690s2a1d1fbc068f1c3f@xxxxxxxxxxxxxx> <790b14c90908110231j4d848b32r9a0f49ea6749f63e@xxxxxxxxxxxxxx> <7207d96f0908110246w1c7350c9t80e8cd365184e83@xxxxxxxxxxxxxx> <790b14c90908110339p430125arcbbb05cc59f99d5@xxxxxxxxxxxxxx> <7207d96f0908111847t7c4e2568q203b93c4abe343ed@xxxxxxxxxxxxxx> <790b14c90908111948r14eb84c5x10f8a4e423fcb608@xxxxxxxxxxxxxx> <7207d96f0908111957l3e7e493cgfacf34403d7c0108@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I get it. It helps me great. Thanks very much :)

On Wed, Aug 12, 2009 at 10:57 AM, Fajar A. Nugraha<fajar@xxxxxxxxx> wrote:
> On Wed, Aug 12, 2009 at 9:48 AM, Zhang Li<cindy.zhangli@xxxxxxxxx> wrote:
>> I am considering the situation:
>> If I setup VLANs, for example: domain1, domain2, domain3, domain4.
>> domain1,domain2 --> vlan100 , assigning the IP address: 
>> 192.168.2.2/192.168.2.3
>> domain3,domain4 -->vlan101,  assigning the IP address: 
>> 192.168.3.2/192.168.3.3
>>
>> domain1 can ping domain2 successfully, domain3 and domain4 can ping
>> successfully.
>>
>> In Domain0, br100, br101 ip adress is: 192.168.1.100/192.168.1.101.
>> gateway: 192.168.1.1
>>
>
> There you go, there's you're source of problem right there: dom1 and
> dom2 is on 192.168.2.0/24 but dom0's br100 (which is on the same vlan)
> is using 192.168.1.100/24. Is doesn't work that way.
>
> When using bridge (especially with vlans), think of dom0 like a L2 or
> L3 switch, and domUs like any other physical network. Get help from
> your networking guys if you're not sure. For starters :
> - make sure eth0 is connected to a switch, whose port is already
> configured as trunk, allowing (at least) vlans 100 and 101
> - br100 and br101 needs to be on different subnets (otherwise there's
> no point of having a different vlan in the first place), which is
> similar to an L3 switch: you have a vlan, and you have an ip address
> on that vlan interface.
> You could also remove their IP address altogther, which is similar  to
> an L2 switch: it knows the vlan, but it doesn't have an Ip address on
> that vlan.
> - setup dom1 and dom2 to be on the same subnet as other hosts on
> vlan100 on your network
> - setup dom3 and dom4 to be on the same subnet as other hosts on
> vlan101 on your network
>
> Again, don't hesitate to get help from your network guys, cause it's
> very similar networking setup with that of a L2/L3 switch.
>
> --
> Fajar
>



-- 
Best regards
--Li

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