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:
>> domain3,domain4 -->vlan101, assigning the IP address:
>> domain1 can ping domain2 successfully, domain3 and domain4 can ping
>> 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.
Xen-users mailing list