Would like to change both home domain and Network scheme

[arthurdent4242]

Did you make any manual configuration changes? If you did, it can cause issues with Amahi. I don't see any reason why the script is not working. I presume your HDA is on eth0, correct?

Also does your settings match the amahi.org profile before the change?

If by manual changes you are referring to changes on the HDA, then no. The only "manual" change I made was to the gateway itself.

I don't understand why it isn't working either. Is there some sort of log that this script spits out that could help point us in the right direction?

[bigfoot65]

No log specifically that I am aware. You could check the logs in /var/log directory and see if any show errors.

[arthurdent4242]

No log specifically that I am aware. You could check the logs in /var/log directory and see if any show errors.

I just perused the syslog (syslog.1 to be precise) and I found this:

http://paste.ubuntu.com/6110751/

You notice this happening right around the times that I tried to run the command:

Sep 14 10:03:18 Amahi dhcpd: Not configured to listen on any interfaces!
Sep 14 10:03:18 Amahi dhcpd: Wrote 0 leases to leases file.
Sep 14 10:03:18 Amahi dhcpd:
Sep 14 10:03:18 Amahi dhcpd: No subnet declaration for eth0 (192.168.1.23).
Sep 14 10:03:18 Amahi dhcpd: ** Ignoring requests on eth0. If this is not what
Sep 14 10:03:18 Amahi dhcpd: you want, please write a subnet declaration
Sep 14 10:03:18 Amahi dhcpd: in your dhcpd.conf file for the network segment
Sep 14 10:03:18 Amahi dhcpd: to which interface eth0 is attached. **

After switching back to the current network scheme that entry disappears. What are your thoughts?

[bigfoot65]

Don't know what the deal is with this one. Does your profile still exist on amahi.org for this machine?

If this is working, might just have to leave it alone. I have switched in the past with no issues, but something in your install is preventing that I guess. If the change is necessary, a new HDA profile on amahi.org and reinstall my be the quickest solution.

[arthurdent4242]

Don't know what the deal is with this one. Does your profile still exist on amahi.org for this machine?

If this is working, might just have to leave it alone. I have switched in the past with no issues, but something in your install is preventing that I guess. If the change is necessary, a new HDA profile on amahi.org and reinstall my be the quickest solution.

It does. The profile is not connected to the email address for this username, but the profile exists.

It is working, but it isn't. The reason for wanting to change the IP scheme is because of split tunneling issues with OpenVPN. Basically since one place where I would be using the VPN from most of the time is using a 192.168.1.0/24 scheme as well it causes issues. I can only access devices on the LAN and cannot reach out to the internet. The goal is to change my home IP scheme to something non-standard so that I should not hit this issue ever again.

By a new HDA profile, do you mean signing up again with yet another email address? Or am I able to create a new HDA using the current email address and give it a new IP scheme and what not?

I have a feeling that reinstalling is the only way to fix this as well (which is quite sad really).

[bigfoot65]

Understand. You should be able to create a new HDA profile with the same email address.

As for this issue, well it seems like something got messed up somewhere in the install. No reason why it should not work. As I have said, I changed mine using the same script and it worked fine.

The only explanation is that something is not quite right on the current install. A new one should correct that, at least I would hope so.

Unfortunately when you are not using a standard OS install by itself, things become more complicated. The Amahi platform changes/controls things and sometimes that makes doing something simple stuff like this more difficult. Not impossible, but have to determine if all the time is worth the effort vs just starting over.

[arthurdent4242]

Understand. You should be able to create a new HDA profile with the same email address.

As for this issue, well it seems like something got messed up somewhere in the install. No reason why it should not work. As I have said, I changed mine using the same script and it worked fine.

The only explanation is that something is not quite right on the current install. A new one should correct that, at least I would hope so.

Unfortunately when you are not using a standard OS install by itself, things become more complicated. The Amahi platform changes/controls things and sometimes that makes doing something simple stuff like this more difficult. Not impossible, but have to determine if all the time is worth the effort vs just starting over.

Bigfoot,

Thank you for your guidance in this. I ended up reinstalling the OS. First thing I did was turn the server off, then changed the IP scheme of my network from my router. Then I setup the new HDA on the Amahi site and reinstalled the OS and reattached the greyhole storage pool. It is working fine now. I really wish I didn't have to take the step of reinstalling the whole thing, but such is life. It appears that everything is working fine now.

[bigfoot65]

No problem. Glad you got it sorted out. I am unsure why the script did not work. I have done it in the past with no problems. It was on Fedora 14, so maybe there's an issue with it on other OS versions.

[PatrickDickey]

No problem. Glad you got it sorted out. I am unsure why the script did not work. I have done it in the past with no problems. It was on Fedora 14, so maybe there's an issue with it on other OS versions.

Would something like this fix the "network" issue?

Code: Select all

# Restart hda-ctl and other services related to networking sub RestartServices { system("hda-ctl-hup"); sleep 2; my $fedora = 0; open my $fread "<", "/etc/os-release" or die $!; while (<$fread>) { if (/ID=fedora/) { $fedora = 1; last; } } if ($fedora) { system("service network restart"); } else { system("service networking restart"); } close $fread; sleep 2; system("hda-ctl-hup"); print "It is strongly recommended that you reboot all systems on your network at this point.\n"; }

This is one example of how to do the service network/networking restart, based on which os we're using. Obviously if someone (or the development team) would port this over to something other than Fedora/Ubuntu, you'll have to tweak the script again.

I've verified that the if statement works (as a bash script by using this code:

Code: Select all

#!/bin/bash grep "ID=fedora" /etc/os-release > /dev/null 2>&1 if [ $? = 0 ]; then echo "You are running Fedora" else echo "You are running Ubuntu" fi

It works on both Ubuntu and Fedora. There might be other areas that need to be tweaked like this, to make the script work for both os'es.

Have a great day.
Patrick.

EDITED to put an actual perl version of the script in place of my bash version.