An example of working port-forwarding configuration » History » Revision 11
Revision 10 (Anchi Cheng, 10/25/2013 10:09 PM) → Revision 11/15 (Anchi Cheng, 10/25/2013 10:42 PM)
h1. An example of working port-forwarding configuration h2. (Paraphrased from description by Brian J. Gibbens) and tested For those interested, this is how I set up Leginon on the TF20 in the Kornberg lab at NRAMM Stanford with the following configuration: Local network (192.168.xxx.xxx in this example) can not be accessed directly through institute network that has internet access before port forwarding. h2. The computer hosts involved in this port-forwarding configuration listed by hostname and operation system in ( ): configuration: # *ScopePC* (Windows) - The computer controlling the microscope ** connected only to local network ** Static local IP addresses (192.168.200.99 in this example) is set to this host. # *SupportPC* (Windows) - The computer provided by FEI to protect *ScopePC* while allow RAPID system support from them through internet. ** Two network cards are on this computer. ** Local network Static IP address (192.168.200.100 in this example) ** Outbound institute network Static IP address (137.131.204.250 in this example) # *ProcessingLinux* *LeginonMain* (Linux) - The computer that runs Leginon processing. ** Institute network Static IP address (137.131.204.500 in this example) # *DatabaseLInux* (Linux) - The computer that runs Leginon database server. processing/database/storage. In a simpler setup this might Could be the same computer as the ProcessingLinux as illustrated in the figure below. multiple. Here assumes just 1 ** Institute network Static IP address (137.131.204.700 (137.131.204.500 in this example) !http://emg.nysbc.org/attachments/2484/PortForward.png! *Ethernet cables should be connected like in the figure above.* h2. TCP/IP Gateway Settings on *ScopePC* This should be set to the local IP address of the *SupportPC* like this: !gateway.png! h2. Firewall settings on *SupportPC* ** allow communication to both *ScopePC* and *ProcessLinux* and *DatabaseLinux*. *LeginonMain*. h2. Hosts file addition if needed --Appropriate IP addresses and hostnames added to the hosts files (C:/WINDOWS/System32/drivers/etc/hosts.txt on Windows PC's and /etc/hosts on Linux). * On *ScopePC* - list both hostnames of *SupportPC*, *DatabaseLinux* *SupportPC* and *ProcessingLinux* *LeginonMain* * On *SupportPC* - list both hostnames of *ScopePC* and *DatabaseLinux* and *ProcessingLinux* *LeginonMain* * On *ProcessingLinux* and *DatabaseLinux* *LeginonMain* - list only hostname of *SupportPC* in additional to other linux hosts but not *ScopePC* since all communication from *ScopePC* to these *LeginonMain* through *SupportPC* will appear to come from *SupportPC* h2. Install port forwarding program AUTAPF which allows needed host/port specification on *SupportPC* The Below is a screen shot below shows that case where: of how we configured AUTAPF for a test at NRAMM. The hosts are represented as follows: * Port 55555 is opened by legion/laumcher.py (often called Leginon Client") on *ScopePC*, intended to serve data to *ProcessingLinux*. (Fixed port) localdefcon3: the microscope PC running leginon client/launcher * Ports 49152 and 49153 are opened by two processes to send/receive data to *ScopePC". (You may need to add more ports in case of blockage. defcon3: See [[Ports used by Leginon]]) the support PC with AUTAPF installed * Port 3306 is dedicated for database connection. (Fixed port) amilab7: the remote linux running main leginon !autapf.PNG! ______ [[Network Configuration| Go up]] ______