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

[Xen-users] DHCP problem in privleged domU from ISP

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Frank DiRocco" <ofanged1@xxxxxxxxx>
  • Date: Mon, 13 Mar 2006 14:23:39 -0500
  • Delivery-date: Mon, 13 Mar 2006 19:25:00 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=F/VErXQg9gnpU0ZViC/7dihERbFmn23YnJIoXt+/PKoRTInFoUah+grpL5dZp1jJ32iC6eUx9Cu1ED3JCNVy5ZUsv8TAL4X4OxwUVgXDpAzGtDBbiPL5qabAlQb8IE9/e3LNjTLdWnBnd1PcffSqptNCW9eoz8GS+16XaQ3cR0E=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello again! I've got my vmware privleged domu running great and a shorewall based firewall doing all the routing perfectly. so i decided to use the procedure on my production server (mirrored so no big deal if it goes down from time to time). the setup is exactly the same as in vmware:
           |     ___________________________            |
           |     |                                                     |           |
eth0----+----|        msxen0 from option-c.com       |----------+------eth1 LAN
           |     |          domu shorewall firewall         |           |
           |     |___eth2______________eth3___ |           |
           |              |                                  |                     |
           |              |                                  |_DMZ            |
           |              |                                                        |  yes this is broken on purpose so dmz access cannot reach dom0
           |              |                                                        |
           |_______|_________________|__________ |
           |                                                                       |
           |             dom 0 w/ dummy module                    |
           |    physdev_dom0_hide=(my nic interfaces)      |
           |___________________________________ | (sorry my asci stinks)

as you can hopfully see dom0 only has two interfaces, dummy0 and dummy1. the firewall domu has 4 eth0 eth1 eth2 eth3. The PROBLEM is i can not get a dhcp address from my ISP, it eventually times out. Although, the exact same setup on a virtual machine inside my lan, eth0 recives a dhcp address (localy) with no problems.

xm list firewall (on both real server and test-server)
(vif (idx0) (vif0) (mac:aa:00:00:09:3e:fc) (vifname vif 1.0) (bridge br0) (evtchn 14 4) (index 0))
(vif (idx0) (vif1) (mac:aa:00:00:09:3e:fc) (vifname vif 1.1) (bridge br0) (evtchn 15 5) (index 1))
(vif (idx0) (vif2) (mac:aa:00:00:09:3e:fc) (vifname vif 1.2) (evtchn 16 6) (index 2))
(vif (idx0) (vif3) (mac:aa:00:00:09:3e:fc) (vifname vif 1.3) (evtchn 17 7) (index 3))

Is there anything I have to do the get the dhcp address from the isp as oppesed to getting from a debian server on my lan.
All comments questions and whatnot are welcomed and appriciated.

Thank you,
Frank  Di Rocco

"Does an optimistic person look at a hard drive as half-full or half-empty?" -ofanged1-at-gmail.com
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.