New Features V3.2-15 cardd was fixed to correctly report the presence of I/O cards in Sentinels. It only runs on Sentinels, every other SCS model is unaffected. exser.o (serial port driver) was modified to work with the new cardd. !!! These changes only affect the Sentinel models, they do not have to be installed on non-Sentinels, or on older (non-SOM) Sentinels. If you are able to connect to the srial ports on your Sentinel, then you do not need to install these fixes. V3.2-14 webserver-1.0-1516.25.noarch.rpm - in some cases the Enter splash screen would overlap the Welcome text. This release moves the splash screen down. webserver-1.0-1516.23.noarch.rpm - fixes a problem between IE6 and the 48 port SCS. If you are using IE6 to access the SCS web interface and have a 48 port SCS, you should upgrade to the rpm version. There is no problem using IE7 or Firefox. IE6 will not allow you to access the serial port settings on a 48 port SCS. V3.2-10 !! Critical bug fix !! A bug was discovered in the SCS web interface. If a user tried to reset a device port from 'getty' mode back to 'device' mode, /etc/rc.serial was recreated without any stty commands. Also, there are conditions where /etc/inittab was empty. The getty & modem options have been removed from the interface. These features are still available by modifying the appropriate configuration files. All users should upgrade their webserver rpm to a version later than 1.0-1516.15 You can determine your version with the command: rpm -q webserver (command result): webserver-1.0-1516.11 (this version should be updated) The update can be found on our ftp site: ftp://ftp.thinklogical.com the updated rpm is named: SCS/updates/V3.2-10I/RPM/webserver-1.0-1516.21.noarch.rpm Instructions on updating rpms are located in the file 'lsi-rpm-HOWTO' which is located on the ftp site or on the SCS in the directory: /usr/local/doc. (The ftp site contains the current document(s), the SCS will contain documents that may now be out of date). Version 3.2-7 The internal modem will automatically be enabled. The root user will still NOT be allowed to login via the modem. You will either have to allow root to login by adding ttyS1 to the file /etc/securetty, or by creating a new user and after logging in as that user, use the command 'su' to gain root privileges. Version 3.2-6 telnet2port.sh now has a --del option that will turn off and remove the feature. It's config file (/etc/sysconfig/sredird) has a variable that allows the user to define a selection of ports that reqiuer telnet access. Previously, the only option was to enable all ports. There is also a --help option. A tzdata rpm has been added to update the timezone files to the new US Daylight Savings time. SAMBA has been added to allow mounting Windows shares. Added python24. linuxconf has been removed and a new web interface installed. The new interface is accessed via: https:// Version 3.1-21 sredird (used for telnet access to the device ports) was modified to buffer more serial data before sending a TCP packet. The previous version sent one byte per packet. telnet2port.sh --break was modified to allow for a '-y' to be used when breaking a connection. This prevents the confirmation question from being asked - the connection is terminated without any user interaction. This was added for those users that use scripts to connect to the SCS. This option is controlled by a line in the config file: /etc/sysconfig/sredird. Please read the comments in that file for more details. R/O access to the device ports is now available from network ports 7001 through 7048. Version 3.1-20 Support for latest SCS hardware. Version 3.1-10 The kernel was recompiled with the advanced routing module enabled. If /etc/mgetty+sendfax/mgetty.config is modified (instructions are located in the file) then some modems may be used on the SCS device ports. The 'telnet to a port' feature now has an option to define a 'break connection' series of sockets. Connecting to one of these sockets will break an existing connection to the associated device port. Version 3.1-8 openSSL 0.9.6g is incompatable with bind-utils (dig, host, etc.) I reverted back to openSSL 0.9.6b. Version 3.1-7 IPV6 support has been added to the kernel. 'getty will now run on the device ports. This allows the SCS to be used as a terminal server. Please read the comments located in the file /etc/sysconfig/lsi. The exser driver will have to be unloaded and then reloaded with new parameters to activate this mode. (rebooting the SCS is the cleanest way to accomplish this) openSSH V4.2 and openSSL 0.9.6g are now included. The user can now control the LCD date/time display format. Refer to the man page for lcd or the comments in /etc/sysconfig/lsi. Factory Restore: The SCS can be restored to it's factory settings by creating the file /.factoryrestore and rebooting the SCS. Cloning: If the file /misc/clone.etc.tar.gz exists, it will be expanded into the RAM drive during startup. If you wish to copy system A onto system B, run 'save' on system A, copy the file /misc/etc.tar.gz to system B with the name /misc/clone.etc.tar.gz, reboot system B --> TWICE. Due to the sequence of events during bootup, the hostname may still reflect the old value. Also, init read the old inittab file during bootup. The second reboot will resync all files. This duplicates the /etc, /var, /lsi, /home and /root directories. Version 3.0-2 The SCS now has the option to allow the user to use telnet to access a device port. This feature is activated by running the script: telnet2port.sh. The default starting port number is 6001. The file used to configue this feature is /etc/sysconfig/sredird. There is an optional timeout that can be used to disconnect the session after a period on inactivity. The inactivity can be measured as no input from the user, or as no input from the user OR the attached device. More information can be found in the files located at /usr/local/doc/sredird. Other Notes Read the man page telnet2port.sh for instructions on enabling telnet access to the device ports. Read the file /usr/local/doc/README.lsisshd for instructions on assinging IP addresses to each device port and using ssh to directly access the ports.