client not acquiring address on tapipop interface

[J Greenbaum]

Hi,

I'm trying to get a small cluster running on VMware ESXi server using
a custom GroupVPN. So far it seems that the server and worker nodes
are running correctly. I am able to type "condor_status" on both and
see that the worker node is available. However, the client node is
not acquiring an IP address on the tapipop interface. Is there
anything obvious that could be causing this behaviour? Any help would
be appreciated. Please let me know if you need any more details
regarding my setup. Thanks!

-Jason

[Renato Figueiredo]

Jason,

It's hard to say why - from a networking perspective there shouldn't be any difference between client and server/worker floppies. It could be due to many reasons (including problems with VMware connectivity or difficulty with NAT traversal). Can you check that the client VM is able to ping a well-known public host (e.g. sudo ping www.google.com)?

Are you using your own local P2P bootstrap overlay, or our PlanetLab overlay? Are all the VMs on the same network? Are they bridged or NATed? If you describe your setup in a bit more detail it will help.

--rf

--

You received this message because you are subscribed to the Google Groups "acis.p2p.users" group.
To post to this group, send email to acisp2...@googlegroups.com.
To unsubscribe from this group, send email to acisp2pusers...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/acisp2pusers?hl=en.

--
Dr. Renato J. Figueiredo
Associate Professor
ACIS Lab - ECE - University of Florida
UF Site Director, Center for Autonomic Computing
http://byron.acis.ufl.edu
ph: 352-392-6430