EndRun Tempus LX GPS, User Manual

Page: 109 / 116

T e m p u s L X G P S U s e r M a n u a l 97
"Smarter Timing Solutions"
Appendix
I
Software Release Notes for Previous Tempus LX Users
Version 2.60 of the Linux root file system (RFS) and the new IPv6-capable Linux 2.4.31-IPV6 kernel
are now shipping in new products. Both files are also available for download so that you can up-
grade your installed units in the field. This is a major upgrade, and features updated versions of all
applications, utilities and shared libraries typically installed in an embedded Linux-based system. In
addition, the critical open source protocol implementations, NTP, OpenSSH, Net-SNMP and Syslog-
ng are now IPv6-capable, along with other various support daemons and configuration utilities that
need to understand IPv6 addresses. The NTP implementation is now capable of “autokey” crypto-
graphic operation. Previously, only symmetric MD5 cryptography was available.
Easy Field-Installable
Upgrade
The new system detects the presence of an IPv6-capable kernel and enables the IPv6 configuration
menus and command line utilities automatically. As with all of our firmware upgrades, we have de-
signed the upgrade to be as seamless as possible for existing customers, which means that after apply-
ing the update, your existing configuration settings and passwords will continue to function properly.
However, due to the magnitude of the changes included in this upgrade, there are a couple of cases
where configuration files must be re-configured:
If You Are Using DHCP
The new version DHCP client daemon included in the 2.60 RFS will by default overwrite the /etc/
ntp.conf. This will cause serious problems. If you have a pre-existing /boot/etc/rc.d/rc.inet1 that is
set up to invoke
dhcpcd
to configure the ethernet interface, you will need to re-run
netconfig
im-
mediately after performing the upgrade and re-boot. This will replace the old /boot/etc/rc.d/rc.inet1
with a new one that will invoke
dhcpcd
with the appropriate arguments to inhibit this behavior.
If You Are Operating NTP Without MD5 Authentication
The new version NTP server daemon included in the 2.60 RFS interprets certain keywords in the
“restrict” directive differently than the previous version. In particular, it will now interpret the
“notrust” keyword to mean that it will not reply to client requests that do not use authentication (MD5
or autokey). Previous versions of the NTP server did not operate this way. If you have a pre-existing
/boot/etc/ntp.conf , and any of your NTP clients are configured to not use MD5 authentication, you
should re-run
ntpconfig
immediately after performing the upgrade and re-boot. This will replace
the old /boot/etc/ntp.conf with a new one that will have the “notrust” keyword removed from the
“restrict” directive. The new file will also contain the “keysdir” directive to support operation with
autokey.
Freedom of Choice
EndRun Technologies understands that IPv6 is still in the experimental stage with essentially no
mainstream deployment. Customers who are not interested in IPv6 need not perform the Linux