cheers,
Hussam
(Hussamuddin Nasir)
Netlab Operations Team
-------------------------------------------------------------------
Laboratory for Adv. Networking Phone : (859)218-0059
James F Hardymon Building Fax : (859)323-3740
301 Rose Street, Rm 202 E-mail : nasir@netlab.uky.edu
Lexington, KY 40506-0495 Web : http://www.netlab.uky.edu
University of Kentucky
**********************
-------------------------------------------------------------------
On 12/17/2009 11:12 AM, David M. Johnson wrote:
On Thu, Dec 17, 2009 at 07:21:14AM -0800, Leigh Stoller wrote:Well this has been a problem for us since a long time. The way we have our network setup, we end up having the gateway interface for the private net on our router that is visible to the campus network. The campus network uses the 172.16.x.x for our wireless and dorm pc, causing a routing problem for emulab. So For that reason any person using the campus wireless network and computers from dorms cannot access the Emulab webinterface.Yep, this does sound bad. So, that network is hardwired in several places on the client side, in all of the jail,openvz,xen backend code. To be honest, I am not sure why we do not pass that from tmcd to the phys node during configuration. tbops, can you think of reasons why this would not work?I fixed this in the openvz case awhile back... the jail ctrl net addresses are already passed back from tmcd. I don't know if the fix is in your image though.