Configuration

Manage users | TOC | Statistics

1.  Configure HAiku

1.1  Main configuration

The main configuration is done through the config/environment.rb file.

You will need to reload your web server daemon in order to make the changes done to the config/environment.rb file available in HAiku.

ENABLE_NEMO defines if we enable the support for NEtwork MObility in HAiku. Example:

 ENABLE_NEMO = "true"

ENABLE_IPSEC_TP defines if we enable the support for Traffic payload protection in HAiku.

Traffic payload protection is not well supported by current implementations:

  • NetBSD Home Agent will crash
  • Linux Mobile Nodes will crash if kernel has not been patched

Only enable this feature if you know what you are doing. Moreover, users who have created MN with traffic payload protection will need to save their MNs for this option to take effect when changing from "true" to "false".

Example:

 ENABLE_IPSEC_TP = "false"

HA_FILES_ROOT points to a directory where the local files for the HA should be saved. This directory has to be readable and writable by the web server daemon. Example:

 HA_FILES_ROOT = "/usr/local/v6/etc/mobileip6"

STATS_FILES_ROOT points to the location where the graphics for statistics are stored. Filenames must have a special format to be understood by HAiku. This directory has to be readable by the web server daemon. Leaving this parameter blank will disable statistic display support. Example:

 STATS_FILES_ROOT = "/usr/local/mobileip6/stats"

STATS_MODULES contains the name of the statistics modules that should be displayed by HAiku. Leave it empty if you do not provide statistics. Example:

 STATS_MODULES = [ 'coa', 'memory', 'cpu', 'eth7', 'ip6tnl1' ]

SERVICE_URL is the URL of your service that will be included in generated configuration files. Example:

 SERVICE_URL = "https://op-ha.nautilus6.org"

The LIVE_CD_BASE_URL parameter lets you define the base URL from where the Live CDs are downloaded. Leaving this parameter blank will disable Live CD support. Example:

 LIVE_CD_BASE_URL = "http://demo.nautilus6.org/live-cd/"

The TOS_URL parameter should point to the URL of the Term of Service if you have defined one. This is generally a good idea to provide a service policy when you offer a public service. Users will have to accept the terms of service on registration. Leave this parameter blank will disable the terms of service. Example:

 TOS_URL = "http://op-ha.nautilus6.org/documentation/Site/TOS"

The DOCUMENTATION_URL parameter should point to the URL of your online documentation if you have one. This will add a link to the documentation from the left menu in HAiku. Leave this parameter blank will disable documentation link. Example:

 DOCUMENTATION_URL = "http://op-ha.nautilus6.org/documentation/"

The ISSUE_TRACKER_URL parameter should point to the URL of your online issue tracker if you have one. This will add a link to the issue tracker from the left menu in HAiku. Leave this parameter blank will disable issue tracker link. Example:

 ISSUE_TRACKER_URL = "https://nautilus6.org/trackers/roundup.cgi/haiku/"

1.2  Configure mailing

The mailing configuration is done through the config/environments/user_environment.rb file.

You will need to reload your web server daemon in order to make the changes done to the config/environment.rb file available in HAiku.

The configuration parameters are defined in a CONFIG table, such as the following:

 CONFIG = {
  :foo => 'bar'
 }

The :email_from parameter represents the source address of the mails sent to the users. You may choose to set it statically in this file or you may want to leave it blank in which case it will automatically be set to the contact address of your service as defined in HAiku. Example:

 :email_from => 'my_contact_address@server',

The :admin_email parameter stands for the address where system error messages are sent.

 Example:
 :admin_email => 'my_operator_address@server',

The service URL, represented by the :service_url parameter, will appear in the mails sent to the users. Example:

 :service_url => 'https://op-ha.nautilus6.org',

The service name, represented by the :service_name parameter, will also appear in the mails sent to the users. Example:

 :service_name => 'the Nautilus6 Operational HA Service',

The :service_name_short parameter represents the name of the service that will be included in the mails' subject in the form [foo]. Example:

 :service_name_short => 'N6 HA Service',

2.  Configure Home Agent

The Home Agent configuration in HAiku is done for the first time when the first user created logs in the web interface. Any administrator can change this configuration later, from the HA administration page. He will have to push the "Edit" button below the summarized information about the Home Agent.

Upcoming version of HAiku will offer a way to configure your Home Agent daemon from the web. For the moment, the configuration of the Home Agent from HAiku must reflect the configuration of your Home Agent daemon. We invite you to read the manual pages coming with your Home Agent daemon software to find information on how to configure it.

2.1  Home Agent name and description

Administrators have to give a name to the Home Agent and give a useful description. The name of the Home Agent could be the name representing the Home Agent in the DNS servers and the description could for instance be a short text that details the location of the Home Agent or what service it proposes. These two parameters are currently only informative and independent of the Home Agent daemon configuration.

2.2  Home Agent address

The IPv6 address of the Home Agent, as configured for Home Agent daemon, has to be supplied to HAiku as well as the prefix length of the Home Network. The administrator has to be very careful when changing this parameter as it will affect all the previous generated Mobile Nodes making them unusable. Changing the Home Agent address for a new one in the same or in a different network will have the same effect: users will have to destroy the previously created Mobile Nodes and create new ones.

Change the IPv6 Address of the Home Agent parameter with extreme care.

2.3  Mobile Network prefixes

When NEMO support has been enabled, administrator must provide a Mobile Network Prefix pool for MNP to be delegated to Mobile Routers. There is currently no check whether a new MNP pool is already present therefore this is discouraged to create a new prefix pool when the administrator has not checked himself that there is no collision with an existing MNP pool (already delegated to a Mobile Router or listed as available MNP).

When an user creates a new Mobile Router, the available MNP pool list is updated accordingly. Same when user frees a MNP by destroying a Mobile Router.

2.4  IPsec default policy

Administrators can chose what is the default policy concerning the protection of the traffic payload with IPsec. Protecting traffic payload between the Home Agent and the Mobile Nodes provides a better confidentiality for Nodes in the visited networks.

Note that users still have the possibility to disable traffic payload protection when you have enabled this option and vice-versa.

2.5  Contact address

The administrator defines a contact mail address that is the address that the users of the Home Agent can contact in case they have a problem. Make sure that the contact address of your Home Agent can receive mails. If the administrator left the :email_from parameter empty in the mailing configuration then the sender of the emails sent to the users will be this contact address.

Manage users | TOC | Statistics

 Nautilus6
 WIDE
Powered by PmWiki