[Xen-users] Dom0 gateway

["Sergio Maffioletti (CSCS)" <sergio.maffioletti@xxxxxxx>]

Dear All

I'm getting little bit confuse with networking settings for Dom0 when domUs 
are configured with public IP addresses.

I'm not really sure whether dom0 really needs to setup any particular iptable 
or not.

basically each domU I have uses the subnet gateway and the default DNS as they 
were "ordinary" nodes.

on dom0 (debian 2.4.30) : ifconfig
-----------------
eth0      Link encap:Ethernet  HWaddr 00:0F:1F:D8:3B:59  
          inet addr:148.187.33.171  Bcast:148.187.33.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11167773 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12111328 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:932153715 (888.9 MiB)  TX bytes:3032069910 (2.8 GiB)
          Interrupt:16 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:28372 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28372 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2153493 (2.0 MiB)  TX bytes:2153493 (2.0 MiB)

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:28703 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2897647 errors:0 dropped:124 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2278631 (2.1 MiB)  TX bytes:182743341 (174.2 MiB)

vif4.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:45984 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2879171 errors:0 dropped:207 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:6263702 (5.9 MiB)  TX bytes:179213789 (170.9 MiB)

xen-br0   Link encap:Ethernet  HWaddr 00:0F:1F:D8:3B:59  
          inet addr:148.187.33.171  Bcast:148.187.33.255  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11149307 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12099488 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:709590887 (676.7 MiB)  TX bytes:2982270139 (2.7 GiB)
-----------------

on domU vif4.0 (slc-3.0.5 kernel 2.4.30) ifconfig
eth0      Link encap:Ethernet  HWaddr AA:14:00:00:00:03  
          inet addr:148.187.33.220  Bcast:148.187.33.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2891601 errors:0 dropped:0 overruns:0 frame:0
          TX packets:46389 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:179968772 (171.6 Mb)  TX bytes:6352167 (6.0 Mb)

on domU vif1.0 (slc-3.0.5 kernel 2.4.30) ifconfig
eth0      Link encap:Ethernet  HWaddr AA:14:00:00:00:01  
          inet addr:148.187.33.168  Bcast:148.187.33.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2910674 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28838 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:183542936 (175.0 Mb)  TX bytes:2288739 (2.1 Mb)


and everything seems to work beside that vif4.0 cannot ping vif1.0 (vice versa 
works indeed)

I'm also experiencing temporary (order of 10 seconds) domUs unreachable. 
does this has anything to do with the scheduler ?
or am I just lucky that with a screwed up configuration things are randomly 
working ?

thanks for any suggestion
Regards
Sergio :)

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