Difference between revisions of "Dnsmasq troubleshooting"
From Amahi Wiki
(Created page with "Steps in troubleshooting the new [http://www.thekelleys.org.uk/dnsmasq/doc.html dnsmasq] setup in Amahi 7. # Check what is in /etc/resolv.conf. ## There should be three lines...") |
|||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | Steps in troubleshooting the new [http://www.thekelleys.org.uk/dnsmasq/doc.html dnsmasq] setup in Amahi 7. | + | Steps in troubleshooting the new [http://www.thekelleys.org.uk/dnsmasq/doc.html dnsmasq] setup in Amahi 7 or greater (Fedora 19 or greater). |
# Check what is in /etc/resolv.conf. | # Check what is in /etc/resolv.conf. | ||
− | # | + | #* There should be three lines, something like search YOURHOMEDOMAIN and two with nameserver IP (where IP is the internal IP of your HDA) |
− | # | + | #* If that is not right, then try restarting hda-ctl, as root and check again: |
+ | systemctl restart hda-ctl.service | ||
# See if dnsmasq is running with ps guax | grep dnsmasq | # See if dnsmasq is running with ps guax | grep dnsmasq | ||
− | # | + | #* You should see a line like this: nobody ..... /usr/bin/dnsmasq (where instead of dots you see numbers and a time/date) |
− | # | + | #* If it's not running for some reason, try restarting it as root with: systemctl restart dnsmasq.service |
# Check the dnsmasq configuration files in /etc/dnsmasq.d | # Check the dnsmasq configuration files in /etc/dnsmasq.d | ||
− | # | + | #* There should be at least three files there: amahi-common.conf, amahi-dhcp.conf and amahi-dns.conf |
# There should be some settings in them and they should not mentioned that a service (DNS or DHCP) is not enabled | # There should be some settings in them and they should not mentioned that a service (DNS or DHCP) is not enabled | ||
# In the DNS file, there should be two server lines, with an IP, like this: server=208.67.222.222 | # In the DNS file, there should be two server lines, with an IP, like this: server=208.67.222.222 | ||
− | # | + | #* Make sure you can ping those two IP addresses. If not, you have an issue with your routing ... perhaps you cannot reach your router from your HDA? |
− | + | # Your router address should be in the amahi-dhcp.conf file, in a line like this: dhcp-option=option:router,192.168.1.1 | |
− | # | + | #* Make sure the address of your router is proper there |
+ | |||
If these configuration parameters are not right, please access your HDA dashboard and access Setup > Network and change accordingly. | If these configuration parameters are not right, please access your HDA dashboard and access Setup > Network and change accordingly. |
Latest revision as of 01:44, 2 June 2017
Steps in troubleshooting the new dnsmasq setup in Amahi 7 or greater (Fedora 19 or greater).
- Check what is in /etc/resolv.conf.
- There should be three lines, something like search YOURHOMEDOMAIN and two with nameserver IP (where IP is the internal IP of your HDA)
- If that is not right, then try restarting hda-ctl, as root and check again:
systemctl restart hda-ctl.service
- See if dnsmasq is running with ps guax | grep dnsmasq
- You should see a line like this: nobody ..... /usr/bin/dnsmasq (where instead of dots you see numbers and a time/date)
- If it's not running for some reason, try restarting it as root with: systemctl restart dnsmasq.service
- Check the dnsmasq configuration files in /etc/dnsmasq.d
- There should be at least three files there: amahi-common.conf, amahi-dhcp.conf and amahi-dns.conf
- There should be some settings in them and they should not mentioned that a service (DNS or DHCP) is not enabled
- In the DNS file, there should be two server lines, with an IP, like this: server=208.67.222.222
- Make sure you can ping those two IP addresses. If not, you have an issue with your routing ... perhaps you cannot reach your router from your HDA?
- Your router address should be in the amahi-dhcp.conf file, in a line like this: dhcp-option=option:router,192.168.1.1
- Make sure the address of your router is proper there
If these configuration parameters are not right, please access your HDA dashboard and access Setup > Network and change accordingly.