platform

cpg wrote:

can you

ping 208.67.222.222
ping 208.67.220.220

these are the default DNS providers (OpenDNS).

Did the network change?
If so, use

hda-change-gw IP_OF_THE_ROUTER

also, can you tell us what step you get stuck at in the network troublshooter:

http://wiki.amahi.org/index.php/Network_Troubleshooting

Yes, I can ping both.

1. ping hda (this ensures the dns server is working) - OK
   2. ping router (this ensures your HDA can see the router) - OK
   3. ping 68.180.206.184 (this ensures you can see the rest of the world) - OK
   4. ping yahoo.com (this ensures your dns server can see the world) - FAIL (Unknown host)
   5. in the HDA itself (if you can), access http://hda - OK

By the way, the hda-change-gw script, as well as the hda-change-dns, aren't working due to misused quotes (should be double, used single). You pointed it out to me yourself, but it seems like they haven't been updated yet. Just a reminder. :)

My network didn't change, but I tried using the script anyway and got:

DBD::mysql::st execute failed: Table '$m_database.settings' doesn't exist at /usr/bin/hda-change-gw line 81.
Couldn't execute statement: Table '$m_database.settings' doesn't exist at /usr/bin/hda-change-gw line 81.

ok, so DNS is not working.

btw, the fixes are coming in Amahi 5.1 here is the latest release with them:

http://alpha.amahi.org/tmp/hdactl-3.0-5.i386.rpm

(that is the 32b - change appropriately for 64b)

do this before and after installing the above rpm (with rpm -Uvh ...):

service named status

and paste the putput here ...

cpg wrote:

ok, so DNS is not working.

btw, the fixes are coming in Amahi 5.1 here is the latest release with them:

http://alpha.amahi.org/tmp/hdactl-3.0-5.i386.rpm

(that is the 32b - change appropriately for 64b)

do this before and after installing the above rpm (with rpm -Uvh ...):

service named status

and paste the putput here ...

Did it. Brought up the terminal, switched to root user and used the rpm -Uvh <package's path> command in between two service named status executions. The outputs were as follows:

[root@desktop-server Download]# service named status
version: 9.6.1-P2-RedHat-9.6.1-13.P2.fc12
CPUs found: 1
worker threads: 1
number of zones: 2
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid 1704) está em execução*...
[root@desktop-server Download]# rpm -Uvh hdactl-3.0-5.i386.rpm
Preparando... ########################################### [100%]
1:hdactl ########################################### [100%]
[root@desktop-server Download]# service named status
version: 9.6.1-P2-RedHat-9.6.1-13.P2.fc12
CPUs found: 1
worker threads: 1
number of zones: 2
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid 28497) está em execução*...

*means "is running" in portuguese

As of right now, the HDA is still unable to resolve internet addresses. I haven't rebooted it yet and the router's DHCP is off.

weird.

cat /etc/resolv.conf

cpg wrote:

weird.

cat /etc/resolv.conf

search home.com
nameserver 192.168.91.3 (HDA's IP)

ok, looks good.

next you can try:

hda-change-dns IP1 IP2

where IP1 and IP2 are your providers dns , in case they are blocking OpenDNS.

you can try google's dns with:

hda-change-dns 8.8.8.8 8.8.4.4

to get back to opendns:

hda-change-dns 208.67.222.222 208.67.220.220

Still, no success. But I think it could be my fault. hda-change-dns was not working, so I tweaked it myself (changed single quotes to double quotes in two of its lines).

wait!

when did you have to change hda-change-dns?!?!

it should be fixed by now in the hdactl you installed!!

Oh, I actually tweaked it before updating. So now it should be the official one once again.