We had put in a temporary fix by performing a NAT translation for incoming connection to Emulab from our our campus 172.16.x.x addresses, but we keep running our of addresses to allocate after translation. We needed to fix this and the best solution for us was to use a different IP address range for virtual nodes in Emulab that does not conflict with our Campus 172.16.x.x . It has become all the more important for us now since OpenVZ in protogeni is going to use the same address space ..
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 08:56 AM, Leigh Stoller wrote:
Hi guys, I tried a grep for 172.16 on the src tree i got from CVS and it looks like freebsd Jail setup in tmcd has these line (line 78-80) in testbed/tmcd/freebsd/jail/mkjail.pl # XXX my $JAILCNET = "172.16.0.0"; my $JAILCNETMASK = "255.240.0.0"; Does this mean that the 172.16 addresses are still hardcoded for FBSD-JAILS ?Kinda looks that way. How necessary is it that you change the IP space for jails? Lbs