Inode™ V1.9.0 Release Notes

iNODE™ v1.9.0 release notes

Release Notes

All rights reserved. No part of this document may be reproduced in any form, including photocopying or transmission electronically to any computer, without prior written consent of Dataways Communications S.A. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)

Trademarks The Dataways name and logo and the iNODE™ Connectware name and logo are trademarks or registered trademarks in Greece and other countries. Linux is a registered trademark of Linus Torvalds. All other trademarks are properties of their respective holders.

iNODE™ Connectware 2 July 2017 iNODE™ v1.9.0 release notes

TABLE OF CONTENTS

WHAT’S NEW IN V1.9.0 ...... 4 BUG FIXES ...... 7 KNOWN PROBLEMS ...... 11 HARDWARE SUPPORT ...... 13 HARDWARE RECOMMENDATIONS ...... 20 HOW TO INSTALL ...... 22 UPGRADE FROM PREVIOUS VERSIONS ...... 22 OLDER VERSIONS BACKUP COMPATIBILITY ...... 23 FAQ ...... 24 FURTHER HELP ...... 26

iNODE™ Connectware 3 July 2017 iNODE™ v1.9.0 release notes

What’s new in v1.9.0

This release contains several new features, bug fixes and enhancements. It is available to all existing and new customers with a valid support contract.

For more details you can view the online help or ask your Reseller.

New Features and Enhancements

The most notable features are described below.

• Feature #1616 OpenVPN SSL VPN Support iNODE™ can now act as an OpenVPN server and as an OpenVPN client. Configuration of the service is available at Configuration :: VPN Service. Monitoring of the service is available at Monitoring :: VPN Service.

• Feature #1776 TRIM support on SSD devices This feature takes advantage of an SSD's firmware TRIM command. iNODE™ can now inform a solid-state drive which blocks of data are no longer considered in use and can be wiped internally, preventing write performance degradation and increasing drive life.

• Feature #1884 Restart Services from service settings forms A RESTART button has been added in all service forms for easier user experience when a service restart is needed.

• Feature #1965 Individual user authentication on LDAP shared address- book via groupware It is now possible to specify an LDAP shared address-book to be used via groupware, where each user authenticates to the LDAP server using his own credentials. This implies that the LDAP server where the address book is stored is also used as the authentication backend.

• Feature #1988 Monitoring IPSec status A new IPsec dynamic status page has been implemented showing connections, IKE SAs and IPSec SAs in detail.

• Feature #2118 Caldav/Carddav support on Email Server The mail server can also act as a calendar and scheduling (CalDAV) server. Calendar mailboxes contain calendar collections (events) that use RFC 5322 messages to store iCalendar data. Address-book mailboxes contain address-book collections (contacts) that use RFC 5322 messages as vCard data. Calendars and address-books are not accessible via IMAP. They can be accessed via CalDAV and CardDAV clients.

iNODE™ Connectware 4 July 2017 iNODE™ v1.9.0 release notes

Calendars are accessible using the URL form below:

http://[servername]:9080/dav/calendars/user/[username]/[calendar]/ or https://[servername]:9443/dav/calendars/user/[username]/[calendar]/

Address-books are accessible using the URL form below:

http://[servername]:9080/dav/addressbooks/user/[username]/[calendar]/ or https://[servername]:9443/dav/addressbooks/user/[username]/[calendar]/

The same URLs are also available from the corresponding Groupware ports (80 HTTP and 443 HTTPS by default). A default calendar and a default address-book are automatically created when the user first logs in the service.

• Feature #2120 Delayed purge/delete on Email Server E-mails and mailboxes no longer get deleted immediately from the mail server, allowing a period where they can be safely restored. This feature is by default enabled but can be disabled. Note that when this feature is enabled, since e-mail data is not immediately deleted, storage space requirements increase.

• Feature #1532 SPF check in MailRewrite Mail Filter service Sender Policy Framework (SPF) checks are now available for the MailRewrite Mail Filter service. Until now, these checks were available only for the AntiSpam service with minor impact on the antispam score. With the new SPF checks, emails that result in hard failure are instantly rejected.

• Feature #2040 Main menu search A search box has been in added in top of the main menu to filter user- specified keywords and show only menus associated with that.

• Feature #2077 OpenDNS (Cisco umbrella) dynamic DNS client support iNODE™ can now make use of the OpenDNS service with a dynamic IP connection. Create an account on OpenDNS and add the appropriate settings in iNODE™. The OpenDNS client will automatically update the IP of the network specified in the OpenDNS account, whenever it changes. You can find the new interface at Configuration :: System :: General Settings.

• Feature #2094 64-bit hardware support iNODE™ is now 64-bit ready. Support for processors that are not 64-bit is dropped. Please note that iNODE™ cannot run on 32-bit CPUs. Before running a fresh install or make an update make sure your server is 64-bit capable, otherwise installation will fail.

iNODE™ Connectware 5 July 2017 iNODE™ v1.9.0 release notes

• Feature #2129 Wide hypervisor’s technology support iNODE™ running in a virtualized environment as guest can support several hypervisor technologies like VMware, Hyper-V, Citrix XenServer and KVM. Under each platform it is run with optimized drivers with memory ballooning support.

• Feature #2144 Key usage of certificates Certificates issues from the CA management interface can now specify the Certificate type. This determines the purpose of the public key contained in the certificate (X509 Extended Key Usage). This determines whether the certificate will be used at the server end of a TLS or SSL connection or at the client end. This is necessary for the OpenVPN server certificate since OpenVPN clients check for the certificate's usage.

• Feature #2175 Require authentication for email with sender in local domain iNODE™ Mail Service can now be configured to require authentication for users sending emails with an envelope sender in any of the local domains (MAIL FROM: user@localdomain).

• Feature #2177 DNSSEC validation support Domain Name System Security Extensions (DNSSEC) can now be enabled in the DNS service. You can find the interface at Configuration :: DNS Service :: General Settings.

• Feature #781 Use selectable LAN/Management interface In previous versions the first detected Ethernet interface was automatically considered the LAN/Management interface. For new installations, CD setup wizard now provides the ability to select the LAN/Management interface from the list of available Ethernet interfaces.

iNODE™ Connectware 6 July 2017 iNODE™ v1.9.0 release notes

Bug fixes

This release includes several bug fixes. It is also includes previous version patches (patches of previous version 1.8.7a). These patches are 187a-003, 187a-004, 187a-005.

The most notable bug fixes are described below:

• Bug #59 Some hardware could not be detected and presented during system boot Some cases where reported that hardware could not be detected and presented during system boot. Now, hardware detection and presentation has been re-factored.

• Bug #1130 Directories shared through File Server that reside on a CIFS mounted sharepoint appear as files Under certain circumstances, a directory on a remote sharepoint could appear as a zero-length file. This is now fixed.

• Bug #1746 Intel NUC in UEFI mode freezing during reboot It was possible that the Intel NUC could not reboot when was booted in UEFI mode. This has been fixed.

• Bug #1846 NETBIOS name longer than 15 characters fails to join domain Values longer than 15 characters in the following fields would prevent iNODE™ from joining a Windows Domain.

• Bug #1878 GroupWARE folders not appearing correctly Public mailboxes and personal mailboxes are not distinguished in GroupWARE webmail as they appear hierarchical in the same level, which is incorrect. This is due to the mail server's mailbox namespace and how it is handled by roundcube. Personal mailboxes appear under "INBOX", shared folders appear in root ("/"), and other users' mailboxes appear under "user" (user/username). It is now possible to specify an alternative namespace for the mail server's mailboxes. In fact, new installations will have by default that alternative namespace. With the alternative namespace all personal mailboxes appear in the root folder in the same level as INBOX, shared folders appear under "Shared Folders" and other user mailboxes appear under "Other Users". This makes things clearer and roundcube handles mailbox names properly.

In order to change the namespace in an existing installation, connect to ind (the command line interface) either via telnet from LAN or via web interface internal_ind.php page.

Enter the following command to change the namespace:

iNODE™ Connectware 7 July 2017 iNODE™ v1.9.0 release notes

mail.alternate_namespace yes When the namespace is changed, sieve scripts that may contain mailbox paths need to be converted. Use the following command to perform this conversion automatically: cmd mail.translatesieve

Note 1: Since the paths of the mailboxes change as seen from IMAP, some mail clients may re-download all email in order to synchronize their contents with the new server’s IMAP folder structure! Note 2: The sieve script conversion process is one-way only. If the namespace needs to be changed again, the users' scripts would have to be changed manually!

• Bug #1911 Problems with the user's email forwarding interface The e-mail forwarding interface under the user management editing had multiple problems. This is now fixed.

• Bug #1936 Para-virtual network interfaces not functioning properly under VMWare ESXi It was reported that the para-virtual network interfaces provided by VMWare ESXi was not function properly. This has been fixed. Please find more on Hardware support section.

• Bug #1957 Some time-zones cause problems to the web interface Some time-zones could make the interface not functioning properly. This has been fixed.

• Bug #2001 Status of current IPSec connections reported incorrectly In some cases the status of the current active IPsec connections as reported in "IPsec service status" may be incorrect. A detailed view of the IPsec service status can now be seen in IPSec Live status.

• Bug #2036 Restoring a mail backup may fail with "Process aborted by user or an error occurred" In some cases restoring a mail backup would fail with the above error. This has now been fixed.

• Bug #2053 IPSec tunnels down after re-auth In some cases IKEv1 connections may fail after re-authentication occurs for IKEv1 connections when start. This issue has been fixed but it is recommended to either change the protocol to IKE v2 or the tunnel activation type from "Start" to "Route" when possible.

• Bug #2082 IPSec policies seem applied, but not working In some rare cases restarting the IPsec service or making multiple configuration changes too fast results in messages like "policy already exists, try to update it" reported in the log. This has now been fixed.

iNODE™ Connectware 8 July 2017 iNODE™ v1.9.0 release notes

• Bug #2097 SMTP smart relay not working as expected in case a hostname is specified When an SMTP smart relay host has been specified, the behavior of the mail server would be to try to resolve the hostname entered as a domain, performing an mx lookup for it. This was not the case when an IP was specifies. This has now been fixed, making the MX lookup a configurable option.

• Bug #2109 Email headers limited to 256 bytes Email FROM/TO headers would be truncated if longer than 256 bytes. This limitation has been increased to 1024.

• Bug #2110 Download attachment from OWA/O365 over proxy fails Some proxy service settings were tweaked to optimize the connection establishment of certain URLs which resolve to many IPs.

• Bug #2111 Email replication does not continue automatically if replica is temporarily down The e-mail replication process should now be automatically restarted if the replica is temporarily down and then up again.

• Bug #2115 Vacation filter script containing Unicode subject header not sent properly Subject header in vacation filter scripts containing Unicode characters were not handled properly, resulting in badly encoded subjects sent to recipients. This is now fixed.

• Bug #2116 Mail backup of specific public mailbox contains extra data A mail backup task which contains only one public mailbox may end up containing a lot of extra mail data. This is now fixed.

• Bug #2122 FTP server fails to start when host based access rules exist on sharepoints Host based access rules in sharepoints could cause the FTP service to fail. This is now fixed.

• Bug #2143 Bayesian classifier training over IMAP folders fails for folders containing spaces IMAP folders with spaces in their names, were unable to be used by the Bayesian Classifier training procedure. This is now fixed.

• Bug #2147 Restoring of specific mailboxes may fail Certain mailboxes may fail to be restored. This is now fixed.

• Bug #2152 Backups could be corrupted if saved to remote sharepoints Certain settings in the CIFS protocol may corrupt large file transfers due to network unavailability. Those settings are now tweaked for optimal data transfer integrity.

iNODE™ Connectware 9 July 2017 iNODE™ v1.9.0 release notes

• Bug #2155 Mail2fax with number@domain format -> destination 12pt In Mail to Fax service, if the Destination Format is selected to be 'number@format' it may cause an error and the recipient's address ends to be '12pt'. This is now fixed.

• Bug #2160 Outgoing fax routing editing always displays the first modem selected During editing of outgoing fax routing rules, the modem/modem group present is not the actual selected by the user. This is now fixed.

• Bug #2161 Fax master email incorrect in case of errors and external mail server used for notifications E-mail notifications produced by the Fax Service, could be sent in the wrong e-mail recipients. This is now fixed.

• Bug #2185 Replicator tasks include/exclude lists not working properly File inclusion or exclusion in the content delivery service tasks did not work. This is now fixed.

• Bug #2195 User mailbox size misreported The user's mailbox size as reported in "Monitoring :: E-mail Service :: User mailbox size" may differ from the actual size. When the same email is delivered to multiple mailboxes, the mail server uses hard links in order to actually store only one copy, preserving valuable disk space. The mailbox size report would take this into account and only report the usage of each mail once, to the first user where it was found, to be exact. The way the mailbox size is now reported has changed, ignoring the hard links. This gives a precise view of each mailbox's size.

NOTE: The total mailboxes size, as reported now, is the sum of all mailboxes which may differ from the storage space used.

• Bug #2203 Editing a translation rule fails when selecting a network host Editing a translation rule would fail if selecting a network host as the source or the destination of the rule. This is now fixed.

• Bug #2204,#2205 Improper escaping of double quotes In some cases, data containing double quotes could cause issues due to improper handling of the double quote character ("). This was noticed in user passwords in LDAP authentication backend or when a user attempts to access the users' web interface. Double quotes are now properly escaped and should not cause any issues.

iNODE™ Connectware 10 July 2017 iNODE™ v1.9.0 release notes Known Problems

Known problems in this release are:

• Partial preview of outgoing FAX jobs with multiple documents Outgoing FAX jobs that contain more than one document (which is common with jobs coming from mail to fax server) cannot be previewed properly from the web interface. The web interface will only display the last document of the job.

• Mail attachments without proper MIME type cannot be sent over mail to fax Since the email client that composes the email is responsible to properly indicate the type of the attachments of the email, any misconfiguration of the mail client or mail sent from systems not aware of some document types can lead to attachments that do not have the appropriate MIME type indicator and they are usually marked as the generic MIME type "application/octet-stream". These attachments are considered as unknown type and thus the mail to fax service cannot be convert them.

• Services that do not support external authentication backends. There are some services that do not support the new authentication backends. This is mainly the content delivery service (RSync). Content delivery service has absolutely no support for other backends, so in all cases, the local user database should be used for authenticating to it.

• HTTP Upload or Download file size limit. The maximum upload file size in web interface form is limited to 2GB. This could be a problem if you want to restore a fax backup which is greater than 2GB in size. In such a case you need to upload the backup via a File Server Share point or via System FTP service. System FTP is available on port 9221. The same credentials as in administrative web interface can be used.

• Maximum FileAV check filesize is 2GB. File Server Antivirus service will not scan for viruses in files that are more than 2GB in size.

• AVM Fritz!Card PCI Fax reception. We’ve noticed that there are reception only problems in cases where AVM Fritz!Card PCI board is used from the Fax Server. Such problems noticed only from some Fax machines (some Xerox models). These fax machines cannot sent fax to AVM Fritz!Card at all. On these cases the Fax Server will receive the message “Error no fax data was received” on real time log. We recommend using Active ISDN boards or external Fax/modems for production.

iNODE™ Connectware 11 July 2017 iNODE™ v1.9.0 release notes

• Random Fax preview problems. Rarely in some cases may be not possible to preview a fax document. This problem may occur randomly with error “File does not begin with '%PDF-'” (Bug#256).

• Per sender/recipient Mail Statistics may be incorrect. There is a known problem on mail server statistics page where per sender or per recipient statistics may be incorrect. (BUG#268).

• Some Real-time log lines may be not shown. In certain cases involving rapid generation of log entries, some lines may be not shown in real-time log view (Bug#303).

• Shared Printer Drivers are not accessible by SMB Print Clients. Client printer drivers are not accessible by SMB clients as defined by Client Driver Administrator.

• Dialogic DIVA Server and AVM Fritz!Card PCI Fax conflicts. Do not use Dialogic Diva Server board together with AVM Fritz!Card PCI on the same system. They are conflicting on kernel CAPI stack.

• Dialogic DIVA Server boards cannot be used for data connections. Due to Dialogic Diva Server boards driver changes you cannot use them for data calls yet.

• User export file limitation. User export and import have been implemented using JSON format. Existing export files exported from earlier iNODE™ versions are not currently supported in UI’s user import process. (Bug#1433).

iNODE™ Connectware 12 July 2017 iNODE™ v1.9.0 release notes Hardware Support iNODE™ from version 1.9.0 is only 64-bit compatible. o Updates to iNODE™ version 1.9.0 on a 32-bit machine, will fail. o Installing a fresh iNODE™ 1.9.0 to a 32-bit machine, will fail. iNODE™ v1.9.0 is supported to run on both BIOS and modern UEFI systems. iNODE™ v1.9.0 Setup Tool can be run from Installation CD and is working on both BIOS and EFI machines.

Hypervisor support iNODE™ is able to run efficiently as a guest under Citrix XenServer, VMware ESXi, Microsoft Hyper-V and QEMU/KVM hypervisors.

CAUTIONS on Citrix XenServer:

• The virtual CD/DVD device is not currently available. A bug has been filed and will be resolved as soon as possible. • In XEN PV mode, shutdown or reboot may not work. User needs to manually shutdown or reboot the VM. Before running a new installation or an update, it is strongly advised to switch the VM from PV to HVM mode.

CAUTIONS on Microsoft Hyper-V:

• You should only add IDE storage controllers from the virtual machine's settings. SCSI controllers are not boot-able. It's a Microsoft design issue. See the link below: https://blogs.msdn.microsoft.com/virtual_pc_guy/2009/12/01/why-hyper-v- cannot-boot-off-of-scsi-disks-and-why-you-should-not-care/ • During the CD SETUP WIZARD, you may see one disk as two separate entries under the disk selection menu. You can select either but is recommended to select Microsoft Virtual Disk for better performance. This is not a problem, however it will be fixed in the future.

CAUTIONS on VMWare ESXi:

• You should not add the BusLogic Parallel storage controller from the virtual machine's settings. It is no longer used in 64-bit virtual machines. It's a VMware design issue. See the link below: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&c md=displayKC&externalId=2010470 • In case you update iNODE™ from a previous version and the selected storage controller is BusLogic Parallel you should run the procedure at the following steps:

1. Update iNODE™. When finished it will automatically reboot your system. You must shut it down yourself. 2. Select another controller from the virtual machine's settings.

iNODE™ Connectware 13 July 2017 iNODE™ v1.9.0 release notes

3. Start the virtual machine with iNODE™ DVD inserted and boot from it. 4. From the main menu select 'Repair iNODE™' and follow the instructions. When finished, reset the virtual machine.

CAUTIONS on KVM:

• You should not add the Paravirtual VirtIO storage controller from the virtual machine's settings. It is not supported by iNODE™. • Memory hot-add and CPU hot-plug is currently not working properly. Do not alter memory and cpu options while the VM is running.

Hardware compatibility list

For a complete report of supported hardware please refer to the table below.

Processor Architecture CPU Type X86_64 64 -bit CPU SMP support Yes CPU technologies Multi -core & Hyper threading support Max CPUs 16 Memory Maximum RAM 2T B ACPI Power Control Power Button support Batteries Smart Battery System support CPU/Thermal CPU, Thermal zone support Chipset support ATA/ATAPI Disk IDE/ATAPI CDROM OPTi 82C621 CMD640 enhanced RZ1000 AEC62XX ALI M15x3 AMD and nVidia IDE ATI IXP IDE CMD64{3|6|8|9} Co mpaq Triflex IDE CY82C693 chipset Cyrix CS5510/20 MediaGX Cyrix/National Semiconductor CS5530 MediaGX AMD CS5535 HPT34X, HPT34X AUTODMA, HPT36X/37X JMicron JMB36x National SCx200 Intel PIIXn /ICH iNODE™ Connectware 14 July 2017 iNODE™ v1.9.0 release notes

IT8172, IT821X IDE NS87415 PROMISE PDC20 2{46|62|65|67} PROMISE PDC202{68|69|70|71|75|76|77} ServerWorks OSB4/CSB5/CSB6 Silicon Image SiS5513 SLC90E66 Tekram TRM290 Toshiba TC86C001 ISDN Controllers AVM B1 PCI v4 AVM C4/C2 Dialogic (Eicon) Diva Server 1BRI -2M, 4BRI -8M, E1 - PRI-30M PCI and PCIe support AVM Fritz!PCI PCI Serial Controllers 8250/16550 PCI support more than 4 serial ports with sharing irq USB Support Bus OHCI HCD (USB 1.1) EHCI HCD (USB 2.0) UHCI HCD (Intel & VIA) xHCI HCD (USB 3.0) Mode ms USB Modems with CDC ACM support Printers USB Printers Serial USB Serial support USB FTDI Single Port Keyboard USB AT Keyboards support Storage USB Flash, USB Storage support Storage Controllers Paraller ATA Generic ATA ALi PATA ATI PATA AMD/NVidia PATA ARTOP 6210/6260 PATA CMD 64x PATA EFAR SLC90E66 PATA Intel PATA MPIIX Promise PATA 2027x IT 8211/2/3 PATA HPT 366/368/370/370A/371/372/374/302 PATA HPT 371N/372N /202N/343/363 PATA SiS PATA JMicron PATA Marvell PATA

iNODE™ Connectware 15 July 2017 iNODE™ v1.9.0 release notes

Nat Semi NS87415 PATA RADISYS 82600 PATA RDC PATA Intel SCH PATA SERVERWORKS OSB4/CSB5/CSB6/HT1000 PATA Winbond SL82C105 Nat Semi NS87410 PATA Winbond SL82C105 PATA PC Tech RZ100 0 PATA VIA PATA Serial ATA AHCI SATA In tel ESB, ICH, PIIX3, PIIX4 SATA NVIDIA SATA Promise SATA TX2/TX4 Pacific D. SATA QStor Marvell SATA ServerWorks Frodo / Apple K2 SATA Silicon Image SATA Silicon Image 31xx SATA SiS 964/ 965/966/ 180 SATA Promise SATA SX4 ULi Electronics SATA VIA SATA VIT. VSC -7174/i31244 SATA SCSI/SAS BusLogic SCSI Family AdvanSys SCSI Adaptec AIC7xxx Family Adaptec AIC94xx SAS/SATA Adaptec AIC79xx Family Future Domain 16xx SCSI/AHA -2920A ACARD SCSI Tekram DC395/DC315(U) SCSI Tekram DC390 and Am53/79C974 SCSI Intel(R) C600 Series Chipset SAS LSI MPT Fusion SAS 2.0 LSI MPT Fusion SAS 3.0 Microsoft Hyper -V virtual storage Marvell 88SE64XX/88SE94XX SAS/SATA DMX3191D SCS I Broadcom NetXtreme II iSCSI Broadcom NetXtreme II FCoE Brocade BFA Fibre Channel SYM53C8XX v2 SCSI PMC -Sierra SPC 8001 SAS/SATA VMware PVSCSI Virtio -scsi Xen front -end PV SCSI

iNODE™ Connectware 16 July 2017 iNODE™ v1.9.0 release notes

Tekram DC390(T)/Am53/79C974 SCSI Chelsio T3 iSCSI Chelsio T4 iSCSI Chelsio Com munications FCoE Chelsio S3XX iSCSI Hardware RAID HP Smart Array SCSI 3ware 9xxx /97xx SATA -RAID 3ware 5 -8xxx ATA -RAID Initio INI -A100U2W Adaptec AACRAID Family ARECA ARC1XX0 /12xx/13xx/16xx SATA /SAS RAID NETCELL Revolution RAID Adaptec I2O RAID Adaptec AIC7xxx Fas t -> U160 Adaptec AIC79xx U320 ATTO Technology's ExpressSAS RAID adapter Intel/ICP (GDT) RAID HighPoint RocketRAID 3xxx /4xxx Initio 9100U(W) IBM Power Linux RAID IBM ServeRAID I2O SCSI OSM LSI Logic Legacy MegaRAID LSI Logic MegaRAID NG LSI Logic MegaRAID SAS RAID LSI Fusion MPT/SAS LSI MPT Fusion SAS 2.0 LSI Fusion MPT/FC LSI Fusion MPT/SPI PMC SIERRA Linux MaxRAID Cisco FNIC Driver Promise SuperTrak EX Series FC HBAs (w/o HA) Emulex LightPulse F/C Qlogic QLA 1240/1x8 0/1x160 QLogic QLA2XXX Fibre Channel QLogic ISP4XXX and ISP82XX USB Disks USB Flash disk USB External Disk Network Interface Card support 3c590/3c900 series (592/595/597) "Vortex/Boomerang" 3cr990 series "Typhoon" Adaptec Starfire/DuraLAN Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit AMD 8111 (new PCI LANCE) AMD PCnet32 PCI Atheros L2 Fast Ethernet

iNODE™ Connectware 17 July 2017 iNODE™ v1.9.0 release notes

Atheros/Attansic L1 Gigabit Ethernet Atheros L1E Gigabit Atheros L1C Gigabit Ethernet Qualcomm Atheros AR816x/AR817x Broadcom 44 0x/47xx ethernet Broadcom NetXtremeII Broadcom Tigon3 Broadcom NetXtremeII 10Gb Brocade 1010/1020 10Gb Chelsio 10Gb Chelsio gigabit Ethernet Chelsio Communications T3 10Gb Ethernet Chelsio Communications T4/T5 Ethernet Cisco VIC Ethernet NIC Dave ethernet Early DECchip Tulip (dc2104x) PCI DECchip Tulip (dc2114x) PCI Generic DECchip & DIGITAL EtherWORKS PCI/EISA Winbond W89c840 Ethernet Davicom DM910x/DM980x ULi M526x DL2000/TC902x -based Gigabit Sundance Alta ServerEngin es' 10Gbps NIC - BladeEngine Exar Xframe 10Gb Ethernet Exar X3100 Series 10GbE PCIe HP 10/100VG PCLAN (ISA, EISA, PCI) Intel(R) PRO/100+ Intel(R) PRO/1000 Gigabit Intel(R) PRO/1000 PCI -Express Gigabit Intel(R) PRO/10GbE Intel(R) 10GbE PCI E xpress Intel(R) Ethernet Controller XL710 IP1000 Gigabit Ethernet JMicron(R) PCI -Express Gigabit Marvell Yukon Gigabit Ethernet Marvell Yukon 2 Mellanox Technologies 1/10/40Gbit Ethernet Micrel KS8851 MLL Micrel KSZ8841/2 PCI Microsoft Hy perV NIC Myricom Myri -10G Ethernet Myson MTD -8xx PCI Ethernet National Semiconductor DP8381x series PCI National Semiconductor DP83820 PCI NE2000 nForce Ethernet OpenCores 10/100 Mbps Ethernet

iNODE™ Connectware 18 July 2017 iNODE™ v1.9.0 release notes

Packet Engines Hamachi GNIC -II Packet Engines Yellowfin Gigabit -NIC RedHat KVM Virtio NIC QLogic QLA3XXX QLOGIC QLCNIC 1/10Gb QLogic QLGE 10Gb Ethernet NetXen Multi port (1/10) Gigabit Ethernet AT -LAN -TEC/RealTek RealTek RTL -8139 C+ PCI Fast Ethernet RealTek RTL -8129/8130/8139 PCI Fas t Ethernet Realtek 8169 gigabit ethernet RDC R6040 Fast Ethernet Samsung 10G/2.5G/1G SXGBE Ethernet Silan SC92031 PCI Fast Ethernet SiS 900/7016 PCI Fast Ethernet SiS190/SiS191 gigabit ethernet Solarflare SFC4000/SFC9000/SFC9100 -family Sola rflare SFC9000/SFC9100 -family SMC EtherPower II SMSC LAN911x/LAN921x SMSC LAN9420 PCI STMicroelectronics 10/100/1000 Sun Happy Meal 10/100baseT Sun GEM Sun Cassini Sun Neptune 10Gbit Tehuti Networks 10G TI ThunderLAN VIA Rhine VIA V elocity VMware V MXNET3 WIZnet W5100 WIZnet W5300 Xen NetFront

Deprecated hardware iNODE™ from version 1.9.0 does not support the following deprecated hardware:

o Systems based on 32-bit x86 CPU o ELSA Microlink o Cyclades PC300 o Eicon Diva passive adapter o Sangoma S514x PCI

iNODE™ Connectware 19 July 2017 iNODE™ v1.9.0 release notes Hardware Recommendations

The minimum and recommended hardware requirements to run iNODE™ v1.9.0 is shown on the following matrix.

Minimum Recommended CPU Single Core Dual Core RAM 768MB 4GB CDROM SATA/SCSI SAS, USB HARDSIDK IDE/SATA 10GB SATA 120GB NIC One 100BaseT Two 1000BaseT

As a general guide for memory requirements on your system you can consult the following matrix:

RAM requirements (MBytes) Base System 320 DHCP Server 6 DNS Server 2 minimum – user defined cache VPN Server – PPTP 2 each pptp connection 2,5 VPN Server – IPSec 11,5 VPN Server - L2TP 1,8 each L2TP connection 2 VPN Server - OpenVPN 25 each OpenVPN connection 2 VPN Client – PPTP 6 VPN Client – OpenVPN 4 Fax Server 10 each capi modem 2,8 each legacy modem 5 Email to fax service enabled 2 File Server 47 each CIFS client connection 9 Print Server 8 Publisher 2 each data courier socket 3 Data Courier task 6,5 Web Courier task 5,5 Mail Server 220 Replication process 25 each SMTP socket 3 each POP3 or IMAP4 socket 19 Webmail 78 Content filtering engine 80 SMTP proxy base 2

iNODE™ Connectware 20 July 2017 iNODE™ v1.9.0 release notes

each SMTP proxy connection 2 POP3 proxy base 4 each POP3 proxy connection 4 each thread (default 3) w/o Antispam 22 each thread (default 3) with Antispam 41 ClamAV Engine 900 Proxy Server 25 Proxy RAM user defined (20 default) LDAP Server 130 LDAP cache User defined(50 default) LDAP replication 100 LDAP Proxy 35

iNODE™ Connectware 21 July 2017 iNODE™ v1.9.0 release notes How to install

iNODE™ v1.9.0 installation is a straight forward procedure with minimum skills required. The installation process will start after booting from the Installation CD. There are some questions about correct time/date and about hard disk preparation. The installation process will take about 15 minutes to complete. You can find more information in the iNODE™ Quick start Guide.

Upgrade from previous versions

ATTENTION: BEFORE PROCEEDING TO AN UPGRADE DO NOT FORGET TO TAKE A SYSTEM & DATA BACKUP ON THE RUNNING iNODE™ SYSTEM. iNODE™ v1.9.0 upgrade from previous release v1.8.7a is available for download on the website. The system requirements are at least 768MB total physical RAM and 8GB free hard disk space. Otherwise proceed to a clean-up of logs and File server files to free up disk space or upgrade RAM before doing the software upgrade. Total upgrade time including reboot is about 5 minutes.

Note: During update from 1.8.7a to 1.9.0, any patches released, that apply to version 1.8.7a are included in the 1.9.0 update and are installed automatically. It is not required to manually install any of these patches.

iNODE™ Connectware 22 July 2017 iNODE™ v1.9.0 release notes Older versions backup files compatibility

ATTENTION: ALL BACKUP FILES ARE DESIGNED FOR DISASTER RECOVERY AND CAN BE USED FOR RESTORE PURPOSES. AFTER A RESTORE YOU WILL RECOVER THE FUNCTIONALITY TO THE LAST STATE JUST BEFORE THE BACKUP OPERATION. AS A GENERAL RULE YOU SHOULD NOT RESTORE ANY BACKUP FROM OLDER iNODE™ VERSIONS!

The Restore operations on iNODE™ v1.9.0 accepts backup files according to the following matrix:

Backup file Version Acceptance System backup 1.9.0 Yes System backup 1.x.x No File Backup 1.8.x, 1.7.x, 1.6.x Yes File Backup Other 1.x.x No 1.8.x, 1.7 .x, 1.6.x, Fax backup Yes 1.5.x, 1.4.x, 1.3.x Fax backup Other 1.x.x No Fax archive 1.8.x, 1.7.x, 1.6.x Yes Mail backup * 1.8.x, 1.7.x, 1.6.x, 1.5.x Yes Mail backup Other 1.x.x No

* You cannot restore a backup from release 1.8.1 or later to earlier versions before 1.8.1.

iNODE™ Connectware 23 July 2017 iNODE™ v1.9.0 release notes FAQ

About Installation

Q: What is the minimum hardware requirements in order to install iNODE™?

A: Please see on Hardware Recommendations section above

Q: Do I need to have Linux skills in order to install iNODE™?

A: Not at all. iNODE™ is a software package for novice administrators. You need to boot from the Installation CD. So, you need to set the appropriate PC BIOS booting sequence. After boot up there are only a few simple questions about system clock and hard disk preparation.

Q: Can I have iNODE™ and other Operating System co-resident on the same PC?

A: No. iNODE™ will use all system resources during normal operation. If you need to install it for demo purposes into your mobile PC you can install it as a virtual machine by using known virtual PC environments.

Q: Can I use Installation CD to upgrade from an existing earlier iNODE™ release?

A: No. By using Installation CD a fresh installation will be applied to the installed system. If you need to retain your previous settings you need to perform the upgrade via iNODE™ web interface or you should configure them manually.

Q: Will my settings remain intact during upgrade from an existing earlier iNODE™ release?

A: Yes. Your current settings and operating data will be retained.

Q: Is it possible to install iNODE™ on a RAID system or a SCSI hard disk?

A: Yes. iNODE™ supports installation on IDE P-ATA, SATA/SATAII or SCSI, SAS, RAID, SAN disk storage. You should check your storage system against the Hardware Support section above. New storage drivers are constantly added. Please contact technical support for assistance on using an unsupported storage driver; such drivers are usually validated and officially included in later software updates. Software RAID Controller (common embedded RAID controllers) is not currently supported.

Q: Is it possible to make a copy of the iNODE™’s hard disk?

A: No. iNODE™’s hard disk cannot be copied to another hard disk. The only way is to reinstall it via Installation CD. We do not recommend installations via disk cloning. Always use the standard installation procedure.

Q: I have the installation CD. Can I install it and use it for trial purposes?

iNODE™ Connectware 24 July 2017 iNODE™ v1.9.0 release notes

A: The iNODE™’s installation CD is the same whether you have purchased the iNODE™ system or you are installing it for trial or demo purposes. Once installed and configured through the startup wizard the system will operate for 30 days. If you decide to purchase the system then you can contact your local reseller or the manufacturer.

Q: My network interface has failed. Can I replace it?

A: Yes. Once the new network interface has been installed you will have to contact your reseller and ask for an activation key.

Q: I have installed iNODE™ on XenServer and I need to install XenTools in order to be optimized. How I can proceed?

A: iNODE™ automatically install Optimized drivers during and you do not need to install XenTools. By running iNODE™ in both PV and HVM mode it uses optimized IO drivers and is designed to run optimally on this environment.

Q: Can I install iNODE™ on ESXi or HyperV or KVM virtualization environments?

A: Yes. iNODE™ has been tested to run on these environments and you can install it on them as guest by booting from installation CD. All appropriate optimized drivers and memory ballooning support will be used without any additional action.

General Questions

Q: How can I obtain an Installation CD?

A: You can download the ISO image via Download section of the web site (http://www.inode.gr/support_downloads.php). Also it is possible to ask for a Demo CD by sending an email to democd at inode.gr.

Q: What is included in the INODE™ support contract?

A: It includes all software updates and support through the reseller that iNODE™ was purchased from.

Q: I have problems with the installation procedure. Where can I get help?

A: All support services are offered through the reseller network which is certified from the manufacturer. Through the certified reseller you can get all the assistance you might need. In case there is a major problem the reseller can contact the manufacturer and together they can give a solution to your problem.

Q: Am I able to download the sources of OSS used by iNODE™?

A: Yes. You can download all OSS used on iNODE™ from Download section of http://www.inode.gr .

iNODE™ Connectware 25 July 2017 iNODE™ v1.9.0 release notes Further Help

You can obtain further help and documentation on iNODE™ website http://www.inode.gr or by contacting to your Reseller directly.

If you have a valid support contract you can contact Dataways at:

Dataways Communications S.A. 27, Georgikis Scholis Ave. – GR57001 Thessaloniki – Greece Tel. +30.2310 953953 Fax +30.2310 953963

iNODE™ Connectware 26 July 2017 iNODE™ v1.9.0 release notes

27, Georgikis Scholis Ave. – GR57001 Thessaloniki – Greece Tel. +30.2310 953953 Fax +30.2310 953963 – inode.gr

© 2017 Dataways S.A. All Rights Reserved iNODE™ Connectware names and logo are registered trademarks of Dataways Communications S.A. All other referenced trademarks and names belong to their respective owners. Doc Rev1.2 July 2017

iNODE™ Connectware 27 July 2017