changing network config

[akreaxun]

Hi it's me again

In this post it seemed that I found a solution to the problem. Yet it was only "temporary". Similar problems returned after a day. Now, the DNS problem is kind of on/off.

I still think there must be a solution to that problem. There are too many people working with amahi AND routers in the same network. I may found another rabbit hole to go down: My amahi config online looks like this Image. But the IPs in my network all have '0' in the third block. Can I change this somehow? (Either on the amahi/router or in the pre-settings on amahi.org.)

thanks
akrea

[bigfoot65]

Yes you can change the 3rd octet via the Amahi Dashboard for your network. See the Change IP Address tutorial. If you network needs changed, this will do it.

The info on amahi.org is not updateable. If you configured it wrong, the only non-destructive way to correct it is asking support if they can help.

[akreaxun]

Thanks

I must be stupid. In the amahi dash I can only change the 4th (last) number for the gateway. Am I doing something wrong?

And how do I change the amahi's IP to 192.168.1.10 and the settings for the leases?

[bigfoot65]

Sorry, I see the confusion.

You need to use the hda-change-gw script to change the 3rd octet. The Dashboard does the 4th.

My mistake for not making that clear. The wiki is a bit confusing as well. We will have to correct that part.

[akreaxun]

Thanks for the quick reply. The amahi support was equally quick and changed the IPs on amahi.org. I will now observe the network for a few days to see if the positive effect it has right now is lasting and will come back to let you know.

[bigfoot65]

Great! Hope it's resolved.

[akreaxun]

It's been a while. Unfortunately the problem came back. I did some additional test. In one of it I circumvented the ISP router completely by using an access point and switching off the routers Wi-Fi. Yet same behavior. When I turn off amahi and le the router handle DHCP/DNS it works. By now I figured that the kindel's have got the same issue. I would like to dig deeper. A friend of mine who uses amahi does not have any issues with his Android phone (not the same brand though).

Does amahi keep a DNS-log?

[bigfoot65]

Not sure. Since DHCP and DNS are accomplished via dnsmasq, there may be a log in /var/log folder.

Do you have all the DNS set in your network to the HDA? This issue has similar characteristics of a network where the Primary and Secondary DNS are different. They must be the same or the network will get confused.

[akreaxun]

What do you mean by

Do you have all the DNS set in your network to the HDA?

?

Having set my devices to DHCP I can see that the HDA IP goes in DNS 1 and 2. I wouldn't know where to "set DNS in my network" other than let amahi handle it...

[bigfoot65]

Having set my devices to DHCP I can see that the HDA IP goes in DNS 1 and 2. I wouldn't know where to "set DNS in my network" other than let amahi handle it...

Many routers allow setting of a custom DNS. Check to see you don't have that option set. Also another way to verify if the HDA is setting the DNS correctly for Windows clients is to do the following via command line:

Code: Select all

ipconfig /all

Check to see that the DHCP and DNS servers list the HDA IP address. There are similar commands for Linux and Mac OS that you can find on the internet.