[5935] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: [Vmware-release] running Athena virtual machine from

daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Mar 14 10:25:26 2008

From: Greg Hudson <ghudson@MIT.EDU>
To: Chris Murphy <chris@mit.edu>
Cc: Alex T Prengel <alexp@mit.edu>, release-team@mit.edu, gettes@mit.edu,
   vmware-release@mit.edu
In-Reply-To: <1DE65F83-4C43-483A-8942-A8835E44D342@mit.edu>
Content-Type: text/plain
Date: Fri, 14 Mar 2008 10:24:49 -0400
Message-Id: <1205504689.5898.0.camel@error-messages.mit.edu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Spam-Flag: NO
X-Spam-Score: 0.00

AFS is sometimes flaky behind NATs depending on the UDP association
timeout.  More importantly, you can't just bring a machine with a static
18.* address home and expect to see packets routed to it.

On Fri, 2008-03-14 at 00:49 -0400, Chris Murphy wrote:
> I may be wrong, but I was under the impression AFS doesn't work behind  
> a NAT?
> 
> -Chris
> 
> On Mar 14, 2008, at 12:22 AM, Alex T Prengel wrote:
> 
> >
> > Hi,
> >
> > to follow up on Bill's report today:
> >
> >> Alex Prengel and I are experimenting with Athena in a VMware image.
> >> Yesterday he brought a problem to me that I have reproduced myself:
> >>
> >> Repeat by:
> >>
> >> Start Athena VMware image.
> >> Log in.
> >> Suspend image.
> >> Let sit over night.
> >> Resume image.
> >>
> >> Actual behavior:
> >>
> >> The network is down.
> >> AFS is dead.
> >> A little while later the panel disappears with the helpful message,
> >> "Killed"
> >> in the console window.
> >
> >> ...
> >
> >> I was able to recover by:
> >>
> >> su
> >> /etc/sysconfig/network-scripts/ifdown eth0
> >> /etc/sysconfig/network-scripts/ifup eth0
> >> /etc/init.d/openafs stop
> >> /etc/init.d/openafs start
> >
> > There is a further problem, most likely related to this one, in  
> > attempting to
> > run an Athena virtual machine from off-campus. I have an Athena  
> > virtual machine
> > that works reliably on campus (at least for time periods up to  
> > several hours).
> > I can suspend and resume it correctly (though only tested over a few  
> > hours).
> >
> > When I copy the machine to one of my home computers (I have a Verizon
> > FIOS connection) and try to restore the machine, network and AFS are
> > dead and unlike Bill's experience, I can't restart them with "ifup
> > eth0", "network start" or "openafs start" commands.
> >
> > I did a further test- I put a working Athena virtual machine on a  
> > laptop on
> > campus. I verified that I could suspend/resume the machine  
> > repeatedly and
> > reliably. I then suspended the machine, took it home and resumed.  
> > Again
> > no network or AFS, and no way to restart them.
> >
> > I tried turning off both the PC firewall and the router firewall on my
> > home system to see if those might be causing this. Didn't make any
> > difference.
> >
> > I checked /etc/sysconfig/network-scripts/ifcfg-eth0 in the virtual
> > machine and there was no HWADDR entry. The IPADDR entry was
> > correct. My virtual machine has a fixed IP address, like Bill's. I set
> > this and the hostname in /etc/athena/rc.conf in the virtual
> > machine. Most on my testing was on Windows host OSes, but I
> > experienced the same thing at home with a Linux (Fedora 7) host OS.
> >
> >                                      Alex
> > _______________________________________________
> > Vmware-release mailing list
> > Vmware-release@mit.edu
> > http://mailman.mit.edu/mailman/listinfo/vmware-release
> 


home help back first fref pref prev next nref lref last post