To change the IP address of this device, enter the address, subnet mask, and gateway, then click "Change IP". Set the IP address to 255.255.255.255 to specify that DHCP should be used to obtain an IP address upon power-up. IP address change will take effect upon next power cycle (or when Restart is clicked on the Config File page). The "Refresh" button only updates the information shown on this page, it does not submit a DHCP renewal request. DHCP renewal is automatic.

The default port for web page serving is 80. If you wish to change it, enter the port number and click Set Port. This change will take effect upon the next power-up. If the port is anything other than 80, you must include the port number in the URL. For example, if you would normally use http://10.0.0.101/ to get here and you change the port to 8215, you would now use http://10.0.0.101:8215/. You cannot disable the web port. If set HTTP to port 0, it will revert back to HTTP port 80. (Note: The port change is accepted only if you are logged in as the root user.)

You may also reassign the default Modbus and Telnet ports, as well as default SNMP ports. You may also disable the Modbus and Telnet ports and their services by entering zero. If you will not use the service, it is a good idea to disable the service for better security. The enable/disable change can only take effect upon the next system restart.

You may use domain names instead of static IP addresses in several instances. If domain names are used, you must supply the IP address of at least one DNS server here. The DNS server must be at a static IP address. These changes take effect immediately. Note: If you are using DHCP, the DNS addresses will be supplied by the DHCP server and should be set to 0.0.0.0 here.

The numbers shown to the right of input windows are the actual numbers in the system. For example, entering an IP address of 255.255.255.255 causes the system to acquire a dynamic IP address via DHCP. The IP address shown to the right is the currently leased IP address. When DHCP is used, static DNS entries are ignored, and the actual DNS entries provided by DHCP are shown.

If you are using a Dynamic DNS service to keep track of this device on the Internet, select the service type, enter the host name you have told that service about for this device, and enter the user name and password associated with that update service. Click "Apply DNS" to register this information, and be sure to save the configuration file to retain this data indefinitely.

DDNS status should normally show "OK" or "No update needed". It may show "Local IP not checked yet" for a short time after booting up. If it shows "Tentative" and a reply of "nochg", it means an update was forced with no changes to actually register. Repeated "nochg" occurrences is regarded as abuse by the dynamic DNS service(s), and therefore a third occurrence will be treated as an error condition locally.

Any occurrence of a serious error will put the DDNS update in the "Suspended" state. If this occurs, you need to resolve the problem and restart the system or click Reset DNS. DO NOT simply click Reset DNS without knowing that the problem is resolved. Repeated attempts to update DNS inappropriately may result in the blocking of your host name. Clicking Reset DNS will result in an immediate IP verification and attempt to re-update DNS. Updates resulting in no change ("nochg" reply) are considered abuse if repeated. Repeated IP verification (more frequently than once every 10 minutes) is also considered abuse.

Connection errors are internal network related errors. Connection errors include:

2001 General socket error
2005 Could not reach local DNS to look up remote host
2006 HTTP Client aborted a web session
Other error codes under 200 are network errors that should not occur (contact support@csimn.com if they do).

Error messages that may be returned by the dynamic DNS service(s), noted as "last reply", include:

badauth - user name and/or password do not match host name
nohost - the host name specified does not exist
notfqdn - host name is not a fully qualified domain name (not in form of name.domain.com)
!yours - the host name does exist, but not under the user name given
abuse - the host name given is blocked for abuse

Error messages that could be returned by the dynamic DNS service(s) that require attention of support@csimn.com include:

badsys - sycodestem not valid
badagent - user agent not specified or blocked for non-conformance to specifications
!donator - invalid option specified
numhost - too many or too few hosts found

Error messages that indicate a DDNS server error will be either "dnserr" or "911", and in both of these cases, you should wait a minimum of 1 hour before restarting the system and/or contact the DDNS service to see when the problem will be resolved.

Client update requires a special server. HTTP Client Update is a method of reporting data from a remote site with no on-site configuration other than obtaining Internet access. Contact Control Solutions (support@csimn.com) for information about server requirements for using this feature.