These requirements must be met for each location utilizing a GUAPPLE.  One GUAPPLE is required at each branch location; GUAPPLEs cannot be shared between locations.  For each GUAPPLE, the following network requirements must be met:
  • Each GUAPPLE requires a static IP address on the network
  • All CU*Answers routing requirements must be met: What are the network routing requirements for CU*BASE GOLD?
  • The GUAPPLE must have the following outbound access:
    • Access to all CU*Answers privately routed network (listed here) on all ports
    • Access to ubuntu.com and all subdomains on ports 21 (FTP), 80 (HTTP), and 443 (HTTPS) - used for security updates
  • The GUAPPLE must have the following inbound access:
    • Access from all CU*Answers privately routed network (listed here) on all ports
    • Access from all LAN subnets on all ports
What if I want to place the GUAPPLE in a DMZ?

It is recommended that you place the GUAPPLE on your local network to allow for an easier connection from your workstations to the file shares on the unit.  However, it is possible to place the GUAPPLE in a DMZ for additional security if you would like.  All of the client workstations need to be able to communicate with the GUAPPLE, and CU*Answers will need access to the GUAPPLE from it's privately routed networks.  If the CU*Answers Cisco router is on a different subnet than the GUAPPLE and client workstations, access from the router will be needed also.

The final consideration is DNS/NetBIOS.  When the GUAPPLE is on your local network, it broadcasts its hostname (e.g., "GM1") using NetBIOS.  When on a DMZ you will likely need to create a DNS entry on your DNS server for the GUAPPLE to allow your clients to resolve the name properly.