Difference between revisions of "Transition to Amahi"
| Line 1: | Line 1: | ||
| − | Probably one of the most difficult part of transitioning to using your Amahi HDA with the | + | Probably one of the most difficult part of transitioning to using your Amahi HDA with the recommended setup is to get all systems to use your HDA for DNS. |
A typical symptom is that either accessing the dashboard as | A typical symptom is that either accessing the dashboard as | ||
| Line 11: | Line 11: | ||
# turn off any other DHCP server in your network, typically in your router/gateway | # turn off any other DHCP server in your network, typically in your router/gateway | ||
| − | # restart the networking (or the whole device) of '''all''' your client devices. | + | # restart the networking (or the whole device) of '''all''' your client devices. |
| + | # turn off the network (WiFi) and turn it back on after a few seconds on your clients, so they get a DHCP lease from your HDA and hence DNS | ||
| + | # sometimes the clients also cache DNS in their browsers, you can hard-refresh the browser, or simply reboot | ||
| − | If you have any fixed IP devices in your network from your router settings, | + | If you have any fixed IP devices in your network from your router settings, these may not pick up a DHCP lease. You may set them up in your HDA under [http://hda/tab/network/hosts Setup > Networking > Fixed IPs]. |
== An Alternative == | == An Alternative == | ||
Revision as of 22:16, 18 October 2015
Probably one of the most difficult part of transitioning to using your Amahi HDA with the recommended setup is to get all systems to use your HDA for DNS.
A typical symptom is that either accessing the dashboard as
http://hda
or apps that have a web interface (or both) are not reachable and leads to some site on the internet (like amahi.net).
For best results, we recommend that you fully transition your network to using your Amahi server at least for DNS.
The easiest and simplest way to do this is to do these things in the following order:
- turn off any other DHCP server in your network, typically in your router/gateway
- restart the networking (or the whole device) of all your client devices.
- turn off the network (WiFi) and turn it back on after a few seconds on your clients, so they get a DHCP lease from your HDA and hence DNS
- sometimes the clients also cache DNS in their browsers, you can hard-refresh the browser, or simply reboot
If you have any fixed IP devices in your network from your router settings, these may not pick up a DHCP lease. You may set them up in your HDA under Setup > Networking > Fixed IPs.
An Alternative
Alternatively, if you cannot or do not want to turn off your router DHCP, you can still use the DNS server in your HDA.
To do this, since the the DNS settings for the DHCP server in your router and fill them (both primary server and secondary) to be the IP of your HDA.
You should set them both to the IP of the HDA, so that the HDA is your DNS server for all your devices, which still need to be rebooted to pick these new settings up.
This way, your clients will still use your router for DHCP, but DNS from your Amahi HDA, hence accessing the apps via the short URLs will work.
The last step is to stop the DHCP server in your HDA under Setup > Networking > Settings. For this menu to show, you have to turn on Advanced settings under Setup > Settings.
If you have further networking trouble, consult the Network Troubleshooting page.
