Changes

From Amahi Wiki
Jump to: navigation, search
m
{{NeedsUpdate}}<br This was tested and compiled using Fedora 25 />Amahi 10 (accordingly use at your own risk, but ''should'' work on Fedora 23 / Amahi 9).
Make sure both HDA use different domain namesUpdated and amended by [[user:Spaceman | spaceman]] 17:33, 27 March 2017 (BST).
You=== Prerequisites ===*A router that can hand out DNS. (DD-WRT .v24-sp2 which comes with DNSMasq can handle that nicely.) Find out more at http://www.dd-wrt.com/site/index<br/>*This document assumes that Fedora 23 & Amahi are installed (but see '''ll need to re-apply this fix on every update of hdactlIssue each HDA a unique IP address and hostname''' before deploying your second HDA).<br/>
You=== Issue each HDA a unique IP address and hostname ===For convenience edit the IP Address ''when building''ll need to run the commands below on both your HDAssecond HDA ("HDA").<br/>
You'll need to edit named.patch before executing When stepping through the patch command:<br/>On your main HDA: replace home.com with your second HDA domain namebuild process (as circled in red), and 192.168.1.10 with your second HDA real modify the static IP address.<br/>On your second HDApre-configured in the Amahi control panel: replace home.com with your main HDA domain name, and 192.168.1.10 with you HDA real IP address.<br/>
[[Open_Terminal_as_rootFile:start.jpg|As '''root''' user:450px]] wget -O named.patch <nowiki>http://wiki.amahi.org/images/c/ca/Named.patch</nowiki> patch -p0 < named.patch service hdactl restart}}
<hr>Select '''Start building a new HDA'''
The above instructions no longer work on current versions next step sets the '''IP address''' of Amahiyour HDA and router ('''Network Gateway'''). If this is the second HDA you are building change the IP address to something distinct from your first, for example 192.168.1.20 (only change the fourth octet of the IP address (as circled in red):
Here are the steps that I followed[[File: (This may be very specific to my setup so take it as it isip.)jpg|450px]]
Check this has applied:<upre><b>Prerequisiteshostname</bpre>The output should simple be your '''newhostname'''. </upre><br/>*A router that can hand out DNS. (DDhostnamectl set-WRT .v24hostname -sp2 which comes with DNSMasq can handle that nicely.) Find out more at http://www.dd-wrt.com/site/indexstatic newhostname<br/pre>*This document assumes that Fedora 14 & Amahi are installed on both HDAs.<br/>*BE SURE that each HDA has Replace '''newhostname''' with a unique hostname (domain name) & IP address that is within of your networkchoice. Apply this, with different hostnames, on both servers.<br/><br /><u><b>Accessing HDAs Locally</b></u><br/>You have to access BOTH the shares and the dashboard of each server by IP address of the HDA. <br/><blockquote>For can make one '''hda''', for example, "\\192.168.1.20" in Window will get you to the shares on the HDA with that IP addressother can be '''hda2''', if you have established a user or something more distinct 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/or meaningful.
I personally deleted all of === Accessing HDAs Locally ===You have to access BOTH the Amahi links on each HDA's Fedora desktop shares and created a launcher that opens the Amahi dashboard of each server by IP addressof the HDA. <br/>To create <blockquote>For example, "\\192.168.1.20" on a Windows client will get you to the launcher*Right-click shares on an empty space of the Fedora Desktop and choose "Create Launcher"*Change "Type" to "LocationHDA, ''with that IP address''. Also, 192."*Give it a name (i168. e1. <i>Amahi HDA Dashboard</i>)*Under "Command" enter http:// and 20 in a web browser will take you to the IP dashboard of the HDA<br /><u><b>Change External DNS on HDA2</b></u><br/>: ''with that IP address''.
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 ...": <pre>hda-change-dns ipHDA1 ipHDA1</pre>
</blockquote>
<u><b>Configuring Amahi In our example '''ipHDA1''' is the default 192.168.1.10, if your HDA on SSL Port 443</b></u><br/> uses a different address (i.e. one you configured, instead of accepting the defaults) then use this address instead.
=== Configuring Amahi HDA for SSL (Port 443) ===
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)
=== Optional ===<u><b>==== Apps You Might Need</b></u><br/>====
*Amahi Web-Apps Proxy (http://www.amahi.org/apps/amahi-web-apps-proxy) on both HDAs.
<blockquote>*Go to the Amahi Dashboard and under "Apps" find and install Amahi Web-Apps Proxy. In order to configure Amahi Web-Apps Proxy, access the Amahi Web-Apps Proxy for each HDA the first time from a computer <u>outside</u> of the Local Area Network. Then change the user name and password to suite your needs.</blockquote>
<ul>
<br />
<u><b>==== Configuring OpenVPN ALS</b></u><br/>====
<li>Web Forwards - The Tunneled Web Apps feature of OpenVPN ALS (Adito) allows clients to externally use an application on your HDA as if they are in the Local Area Network.
* Login as administrator
</ul>
<br />
<u><b>=== Router Configuration</b></u><br/>===
This is the configurations under DD-WRT v.24-2
*Turn off DHCP in both HDAs. Allow DD-WRT to handle DHCP.<br/>
First enable '''Settings''' | '''Advanced Settings''' in your HDA's Dashboard (circled red):
 
[[File:settings.jpg]]
 
In the '''Network''' section select '''Settings''' and ''untick'' the '''DHCP Server''' checkbox (circled in red) from '''both''' HDAs.
 
[[File:dhcpserveroff.jpg]]
 
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 address, 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/>
Just change the above to reflect your hostnames and IP addressess. (Note that ptr-record ips are backwards.)
=== DNS Aliases ===To access apps installed on the HDA that is '''not''' servicing DNS queries you will need to add '''DNS aliases''' to point to the ''other'' HDA (in the following example HDA2 is 192.168.0.100): Note the application on "HDA2" are directed to 192.168.0.100, if you have used the settings listed above your second HDA will have the IP address 192.168.1.20 instead. [[File:dnsaliases.jpg]] This will allow you to access apps, in this example '''Couchpotato''' and '''Mediawiki''', by entering in your browser: <unowiki>http://couchpotato<b/nowiki>Cutting Down Confusionand <nowiki>http:/b></u>mediawiki<br/nowiki>respectively. === Cutting Down Confusion ===If you want to avoid confusion as to which server dashboard you are working on at the moment, you use an different theme on each Dashboard. Alternatively, you could ''edit '' the Dashboard theme. Look in the Theme directory.
/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.
68

edits