How to use two HDAs on the same network

Make sure both HDA use different domain names.

You'll need to re-apply this fix on every update of hdactl.

You'll need to run the commands below on both your HDAs.

You'll need to edit named.patch before executing the patch command:
On your main HDA: replace home.com with your second HDA domain name, and 192.168.1.10 with your second HDA real IP address.
On your second HDA: replace home.com with your main HDA domain name, and 192.168.1.10 with you HDA real IP address.

As root user:

bash code
​wget -O named.patch http://wiki.amahi.org/images/c/ca/Named.patch patch -p0 < named.patch service hdactl restart​

---

The above instructions no longer work on current versions of Amahi

Here are the steps that I followed: (This may be very specific to my setup so take it as it is.)

Prerequisites
A router that can hand out DNS. (DD-WRT .v24 with DNSMasq can handle that nicely.)
This assumes that Fedora 14 & Amahi are installed on both HDAs.
BE SURE that each HDA has a unique hostname (domain name) & IP address that is within your network.

Accessing HDAs Locally

You have to access BOTH the shares and the dashboard of each server by IP address of the HDA.

For example, "\\192.168.1.20" in Window will get you to the shares on the HDA with that IP address, if you have established a user and password for that client. Also, 192.168.1.20 in a web browser will take you to the dashboard of the HDA with that IP address.

I personally deleted all of the Amahi links on each HDA's Fedora desktop and created a launcher that opens the Amahi dashboard by IP address.

Change External DNS on HDA2
In order to prevent Domain Name Server conflict, you have to change the external DNS on one of the HDAs. On HDA2, change the external DNS to point to the IP address of HDA1. In terminal ...

bash code
​hda-change-dns ipHDA1 ipHDA1​

Apps You Need (Needs details)

• Amahi Web-Apps Proxy (http://www.amahi.org/apps/amahi-web-apps-proxy) on both HDAs. Access the Amahi Web-Apps Proxy for each HDA the first time from a client computer outside of the Local Area Network. Then change the user name and password to suite your needs.
  
• Ajaxplorer (http://www.amahi.org/apps/ajaxplorer) on HDA1
  
• OpenVPN ALS (formerly Adito)(http://www.amahi.org/apps/openvpn-als) on HDA2. This app has a convenience fee to install that it is well worth it. :-)
  

Configuring OpenVPN ALS (Needs Details)

1. Change OpenVPN ALS to listen on port 443
   • Complete steps of Amahi Wiki "Access HDA over SSL" (http://wiki.amahi.org/index.php/Access_HDA_over_SSL)
   • Complete all steps of Amahi Wiki "Secure App Access" (http://wiki.amahi.org/index.php/Secure_App_Access) but be sure when you are editing the ####-adito.conf file that you change it is like what is listed below, substituting your server's dynamic dns address and correct SSL certificate .crt & .key file names and locations.

   Text
   ​<VirtualHost *:443> ServerName adito ServerAlias username.yourhda.com SSLEngine On SSLCertificateFile /etc/httpd/conf/filename.crt SSLCertificateKeyFile /etc/httpd/conf/filename.key ​

   substituting your server's dynamic dns address and correct SSL certificate .crt & .key file names and locations.
   Do not change anything from "DocumentRoot" or below in the file.

2. Web Forwards - Tunneled Web Apps
   • Login as administrator
   • Select Web Forwards (middle left menu)
   • Select Create Web Forward
   • Select Tunneled Web and select Next
   • Enter Application Name and Description.
   • Check Add to Favorites and select Next
   • Enter http://application for Destination URL. Be sure URLs are entered as local area network addresses (i.e. http://subsonic.yourlocalhostaddress.com). Local address are used since the VPN tunnel is creating an environment as if you were in the Local Area Network. Applications that use a port other than 80, you need to specify that as part of the URL, for example http://subsonic.yourlocalhostaddress.com:4040. Select Next.
   • Select Everyone, select Add, and select Next
   • Select Finish and select Exit Wizard
   • Keep in mind not all HDA apps will work outside your network
   • This method makes use of Adito Agent (java web agent)
   • Each time the agent is executed, the SSL tunnel uses a random port (may not work with firewalled client network)
3. Configure Shares. See http://wiki.amahi.org/index.php/Adito for more details.
   

Router Configuration (Needs Details)

• Port Forwarding
  
• DHCP Server Static Leases
  
• Turn off DHCP in both HDAs. Allow DD-WRT to handle DHCP.
  
• DO NOT turn off DNS on either HDA.
  
• DD-WRT Dnsmasq config. The DNSMasq feature in DD-WRT allows you to direct DNS requests to the each of the DNS servers of the respective HDAs. This prevents one HDA from taking over DNS and preventing the other from using its DNS driven apps.
  

Cutting Down Confusion
If you want to avoid confusion as to which server dashboard you are working on at the moment, you could edit the Dashboard theme. Look in the Theme directory.

bash code
​/var/hda/platform/html/public/themes/main​

Using GIMP2 I added "HDA#1" to the "logo.png" right under the Amahi logo. Then I did the same to HDA#2.

-Places that "Need Details" I will edit more later.