Amahi Forums

Hi All,

I'm converting from WHS to Amahi. My WHS HDD crashed and I'm lucky to be able to retrieve some of the data from it. I have now installed an enterprise drive as the main drive and installed Fedora 14 and Amahi, following the step by step instructions.

Everything has been working well. I setup the new Amahi install at work, then took the Pc home and now it is causing issues. I turned off DHCP as described in the Wiki. Every 5 minutes the IP Changes from 192.168.1.1 to 192.168.241.1.... My Amahi control panel is setup correctly showing it as 192.168.1.1 and gateway as 192.168.1.254.

I am getting sick of having to keep configuring it a static IP. My Billion router at home is controlling DHCP leases and everything else is working fine(On the 192.168.1.* Network).

My Amahi control panel is now showing the PC as "Not Updating".

On a side note, I did convert Greyhole back to MySQL.

Any ideas of whats going on?

Thanks,

I'm thinking it is related to the install code or an issue with the internet connection when installing (After inputting the install code).

Okay, My works network is 192.168.241.*

Appears that if the server is assigned an IP when installing, it preferences that IP over the installation code IP.

Every 5 minutes the IP Changes from 192.168.1.1 to 192.168.241.1 ...

How can this be? That is a major network change!

Whose IP changes? The HDA?
How do you know?
Who changes it??

When running the Amahi installer, the IP of the HDA is fixed to what you set in amahi.org. As in, ... a static IP.

I am getting sick of having to keep configuring it a static IP. My Billion router at home is controlling DHCP leases and everything else is working fine(On the 192.168.1.* Network).

My Amahi control panel is now showing the PC as "Not Updating".

This means your HDA cannot update Amahi with the Dynamic DNS settings.

It's a good indication that things are not quite right.

Yes, the installer autodetects if the IP/network the HDA installs in is not what it's assigned in amahi.org, however, there are no provisions to update the amahi.org ip to reflect the real IP at the moment. Several people have asked for this and we will do it.

The question is why the change to 1.1?

Everything in the network is fine, aside from the HDA.

I know because I did not change the IP, and my network consists of about 4 devices.

I am unsure what exactly triggers the change. Usually I was just browsing Google for a solution and not changing anything.

I eventually had to add a second network profile and save my settings into that. They then stuck. However the DNS under the DNS tab still changed to 192.168.241.1. Again, not sure what triggered it.

I have since re-installed and due to being on my 192.168.1.* network, everything went smooth.