128
edits
Changes
From Amahi Wiki
How to use two HDAs on the same network (view source)
Revision as of 13:40, 29 May 2012
, 13:40, 29 May 2012no edit summary
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 ...
{{Code|hda-change-dns ipHDA1 ipHDA1}}
<u><b>Configuring Amahi HDA on SSL Port 443</b></u> (Needs Details)<br/>
Change HDA2 to listen on port 443
*Complete steps of Amahi Wiki "Access HDA over SSL" (http://wiki.amahi.org/index.php/Access_HDA_over_SSL)
<u><b>Apps You Need</b></u><br/>
*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. :-)<br/>
<u><b>Configuring OpenVPN ALS</b></u> (Needs Details)<br/> <ol><li>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: {{Text|<VirtualHost *:443> ServerName adito ServerAlias username.yourhda.com SSLEngine On SSLCertificateFile /etc/httpd/conf/filename.crt SSLCertificateKeyFile /etc/httpd/conf/filename.key}}Note: *Substitute 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.
<li>Web Forwards - Tunneled Web Apps
* Login as administrator
<li>Configure Shares. See http://wiki.amahi.org/index.php/Adito for more details.<br/>
<u><b>Router Configuration</b></u> (Needs Details)<br/>
This is the configurations under DD-WRT v.24-2
*Port Forwarding<br/>
*Turn off DHCP in both HDAs. Allow DD-WRT to handle DHCP.<br/>
Under "Services > DHCP Server" in DD-WRT set "Used Domain" to "LAN & WAN"<br/>
Give the router's LAN a name and assign static DHCP leases for each HDA using the real MAC addresss, hostname and IP of each.<br/>
*DO NOT turn off DNS on either HDA.<br/>
*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.<br/>
Under "DNSMasq" enable "DNSMasq" and "Local DNS".<br/>
Under "Additional DNSMasq Options" input something like the following.
<blockquote>server=/hda1username.com/192.168.1.20
ptr-record=20.1.168.192.in-addr.arpa,hda1username.com
server=/hda2username.com/192.168.1.21
ptr-record=12.1.168.192.in-addr.arpa,hda2username.com
expand-hosts</blockquote>
Just change this to reflect your hostnames and IP addressess. (Note that ptr-record ips are backwards.)
<u><b>Cutting Down Confusion</b></u><br/>
