Difference between revisions of "Network customizations"

From Amahi Wiki
Jump to: navigation, search
 
Line 15: Line 15:
 
* DYN_HI: high end of the dynamically allocated DHCP range (defaults to 254)
 
* DYN_HI: high end of the dynamically allocated DHCP range (defaults to 254)
  
The syntax for <code>/etc/hdactl.conf</code> is <code>$VARIABLE="value"</code>. For example, to change the dynamic IP range:
+
The syntax for <code>/etc/hdactl.conf</code> is a sequence of lines with
 +
 
 +
    $VARIABLE="value";
 +
 
 +
For example, to change the dynamic IP range:
  
 
     $DYN_LO="110";
 
     $DYN_LO="110";
 
     $DYN_HI="200";
 
     $DYN_HI="200";
  
After you change a setting, you must
+
After settings are changed, the service has to be stopped completely and started:
  
 
   service hdactl stop
 
   service hdactl stop

Latest revision as of 20:02, 21 July 2012

Warning.png WARNING
This should only be attempted by advanced users. It also needs more proper documentation.


Amahi has a daemon that helps configure the network settings. It's called hdactl.

This network daemon can de customized by advanced users. Configuring things improperly can yield an invalid configuration and a broken DNS, DHCP or network subsystem.

The following settings can be customized by creating /etc/hdactl.conf

  • DEVICE: set it to eth1 to make services attach to eth1 (default: eth0)
  • NETMASK_SIZE: number of bits in the netmask (default: 24 ... i.e. 255.255.255.0)
  • NET_START: what's the start of your network, passed into the acl trusted group (defaults to 0)
  • DYN_LO: low end of the dynamically allocated DHCP range (defaults to 100)
  • DYN_HI: high end of the dynamically allocated DHCP range (defaults to 254)

The syntax for /etc/hdactl.conf is a sequence of lines with

   $VARIABLE="value";

For example, to change the dynamic IP range:

   $DYN_LO="110";
   $DYN_HI="200";

After settings are changed, the service has to be stopped completely and started:

  service hdactl stop
  service hdactl start

for the setting to be picked up. Merely restarting or reloading the service will not do it.