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

[Xen-users] Xen 3: Functional NAT Possible?


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Jeff Utter <jeffutter.lists@xxxxxxxxx>
  • Date: Wed, 04 Jan 2006 21:04:55 -0500
  • Delivery-date: Thu, 05 Jan 2006 02:10:28 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=EaxLSH2KBJUTU1YzXRplq5uBdlvR602lBXJZ0lHv8KgyKAr1KufwlfcAwpN1r3QE3g9bbrszk9egGkax25qSMmvDOKBFOrqI5RE7w37SnlsoOjXo34oFUJ+C8x9dlZmYauQ4vSqiEs+MgwbChDZbl0ToHTcsRVJTp+480w+7kl4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

I have been trying for days now to get a working nat setup with my domU's using the default nat scripts.

I find the biggest problem being that each time a new domU is started, it gets thrown on a separate subnet.

Here is an example of dom0's network setup with 2 vm's started:

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:10.0.1.128  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8601 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8932 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1997282 (1.9 MiB)  TX bytes:2003904 (1.9 MiB)

vif9.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:10.0.9.128  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:684 (684.0 b)  TX bytes:0 (0.0 b)

domU-1 :

eth0      Link encap:Ethernet  HWaddr 00:50:22:22:22:01
          inet addr:10.0.1.1  Bcast:10.0.255.255  Mask:255.255.0.0

domU-2 (default)

eth0      Link encap:Ethernet  HWaddr 00:50:22:22:22:02
          inet addr:10.0.9.1  Bcast:10.0.255.255  Mask:255.255.255.0

domU-2 (via dhcp)

eth0      Link encap:Ethernet  HWaddr 00:50:22:22:22:02
          inet addr:10.0.1.1  Bcast:10.0.255.255  Mask:255.255.0.0

my dhcpd conf:

subnet 10.0.0.0 netmask 255.255.0.0 {
  range 10.0.1.10 10.0.1.100;
  option routers 10.0.1.128;
  option ip-forwarding off;
  option broadcast-address 10.0.255.255;
  option subnet-mask 255.255.0.0;
  option domain-name-servers 10.0.1.128;
  host mailserver {
    hardware ethernet 00:50:22:22:22:01;
    fixed-address 10.0.1.1;
  }
  host webserver {
    hardware ethernet 00:50:22:22:22:02;
    fixed-address 10.0.1.2;
  }
}


The problem is, no matter what i do, the interface for the domU on my dom0 gets ips in different subnets, therefore they can't talk to each other and each domU requires a different gateway.. is there any way around this, it is getting very frustrating.

Thanks,
Jeff

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