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

[Xen-users] NAT and cross-domU comunications



Hi there,
  I have a working configuration using nat for domUs (private IPs for each VM 
and a single public IP for the dom0). 
Now I need to let domUs to comunicate each other, but it's not so easy for 
me ..

The running configuration is:

- host1
vif             = [ 'mac=00:16:3e:00:00:01, vifname=vm_1.0, ip=10.0.0.101' ]
gateway         = "10.0.0.228"
ip              = "10.0.0.101"

-host2
vif             = [ 'mac=00:16:3e:00:00:02, vifname=vm_2.0, ip=10.0.0.102' ]
gateway         = "10.0.0.229"
ip              = "10.0.0.102"

I had to specify the gateway since I can't find a way to force the dom0 ip 
and/or mac address.. the IP is always 127+"last number in the domU's IP", and 
the MAC address is always FE:FF:FF:FF:FF:FF:

vm_1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:10.0.0.228  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:510352 errors:0 dropped:0 overruns:0 frame:0
          TX packets:405047 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:500629686 (477.4 MiB)  TX bytes:114119233 (108.8 MiB)

vm_2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:10.0.0.229  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:651 errors:0 dropped:0 overruns:0 frame:0
          TX packets:793 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:320398 (312.8 KiB)  TX bytes:330502 (322.7 KiB)

I think the problem is arp-related, since sniffing in dom0 I can see ARP 
requests and reply indicating FE:FF:FF:FF:FF:FF as the 2nd domU haddr, but it 
is only the one in dom0... and it is the same of the 1st host.. so maybe the 
arp reply should be able to address the two different hosts with two 
different HADDR:

mi01:/etc/xen# arping 10.0.0.102 -I vm_2.0
ARPING 10.0.0.102 from 10.0.0.229 vm_2.0
Unicast reply from 10.0.0.102 [00:16:3E:00:00:02]  0.654ms

mi01:/etc/xen# arping 10.0.0.101 -I vm_1.0
ARPING 10.0.0.101 from 10.0.0.228 vm_1.0
Unicast reply from 10.0.0.101 [00:16:3E:00:00:01]  0.598ms

mi01:/etc/xen# arp
Address         HWtype  HWaddress           Flags Mask     Iface
10.0.0.102      ether   00:16:3E:00:00:02   C              vm_2.0
10.0.0.101      ether   00:16:3E:00:00:01   C              vm_1.0


in domU n°1:

# arp
Address          HWtype  HWaddress           Flags Mask            Iface
10.0.0.228       ether   FE:FF:FF:FF:FF:FF   C                     eth0
# ping 10.0.0.102
PING 10.0.0.102 (10.0.0.102) 56(84) bytes of data.
From 10.0.0.101 icmp_seq=1 Destination Host Unreachable

--- 10.0.0.102 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4005ms
, pipe 3
# arp
Address          HWtype  HWaddress           Flags Mask            Iface
10.0.0.228       ether   FE:FF:FF:FF:FF:FF   C                     eth0
10.0.0.102               (incomplete)                              eth0


Anyone has some tips plz ???
Thanks in advance
-- 
<?php echo '     Emiliano Gabrielli (aka AlberT)     ',"\n",
'  socio fondatore e membro del direttivo del GrUSP  ',"\n",
' AlberT_at_SuperAlberT_it   -   www.SuperAlberT.it  ',"\n",
'  IRC:    #php,#AES azzurra.com ',"\n",'ICQ: 158591185'; ?>

_______________________________________________
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®.