Link Gateway ISO Installation Manual

Link Gateway ISO Installation Manual

Copyright 2016 NetLinkz. All Rights Reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means without the written permission of NetLinkz as provided by the explicit terms and conditions of our license agreement. Basic Rights of Use Thank you for choosing NetLinkz. For more information visit us at http://www.netlinkz.com. Trademarks Microsoft, Windows, Windows NT, and Vista are registered trademarks of Microsoft Corporation. Other brand and product names are registered trademarks or trademarks of their respective holders. Statement of Conditions To ensure proper operational function and/or reliability of the product is maintained, NetLinkz reserves the right to make changes to the product described within this document, via electronic means or otherwise, without notice. NetLinkz does not assume any liability that may occur due to the use, or application of, the product described herein.

Table of Contents Link Gateway ISO Installation Manual... 1 Table of Contents... 3 Introduction... 4 System Requirements... 4 Prerequisites... 4 Installation on a physical machine... 4 Installation on a virtual machine (VM)... 4 Note on ordering of Ethernet interfaces... 5 Image copy of ISO image to USB memory stick... 5 Using a Linux machine...5 Using a Mac... 6 Installation from ISO image... 7 1 - Installing an ISO image that is built for a specific target Link Gateway machine... 12 2 - Installing an ISO image that is not built for the target Link Gateway machine.... 15 Internal Interface... 17 External Interface... 18 Note on configuring a 2-NIC Shuttle (DS57U or similar)... 26 Begin Installation... 27

Introduction The purpose of this document is to describe the installation of the Link Gateway operating system from the ISO image on a physical or virtual machine. After installation from the ISO image, follow the Link Gateway Initial Configuration manual to perform the initial configuration to the point of following the Invitation URL to join a Link Network. Then refer to the Link Platform manual to complete the Link Gateway configuration. System Requirements Supported Operating Systems Link Gateway is built on CentOS 7 System Requirements 8GB of hard drive space 1GB of RAM 1 CPU 2 Ethernet interfaces Prerequisites Before you start you will need the following: Installation on a physical machine The Link Gateway ISO image. A physical machine with at least two Ethernet interfaces. A Linux or Mac machine to copy the ISO image to a USB memory stick. We will refer to this as the 'ISO copy machine'. A USB memory stick of 1GB or greater capacity. A monitor, keyboard and mouse to interface to the Link Gateway for installing from the ISO image on the USB memory stick. A secure network with access to the Internet. The Link Gateway external interface must be connected to this network. Installation on a virtual machine (VM) The Link Gateway ISO image. A VM with at least two Ethernet interfaces. A secure network with access to the Internet. The Link Gateway external interface must be connected to this network.

Note on ordering of Ethernet interfaces Note that, for physical or virtual machines, the Ethernet interfaces are ordered alphabetically according to device name. The first interface is designated as the internal interface and all subsequent interfaces are designated as external interfaces. Image copy of ISO image to USB memory stick WARNING: Follow these processes carefully and at your own risk - there is potential to cause damage to your system by writing to the wrong disk (e.g. the system disk). Using a Linux machine 1. Copy or download the Link Gateway ISO image to the ISO copy machine. 2. Insert the USB memory stick into a USB port on the ISO copy machine. 3. Open a console or terminal on the ISO copy machine. 4. Run dmesg and/or lsblk to determine the device name of the USB memory stick - e.g. sdb. Example dmesg output $ dmesg... [ 244.962109] usb 3-6: new high-speed USB device number 4 using xhci_hcd [ 245.090684] usb 3-6: New USB device found, idvendor=0781, idproduct=5572 [ 245.090687] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 245.090688] usb 3-6: Product: Cruzer Switch [ 245.090689] usb 3-6: Manufacturer: SanDisk [ 245.090690] usb 3-6: SerialNumber: 4C530009721208100412 [ 245.132840] usb-storage 3-6:1.0: USB Mass Storage device detected [ 245.132908] scsi5 : usb-storage 3-6:1.0 [ 245.132967] usbcore: registered new interface driver usb-storage [ 246.130720] scsi 5:0:0:0: Direct-Access SanDisk Cruzer Switch 1.26 PQ: 0 ANSI: 6 [ 246.130994] sd 5:0:0:0: Attached scsi generic sg2 type 0 [ 246.131845] sd 5:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB) [ 246.132906] sd 5:0:0:0: [sdb] Write Protect is off [ 246.132908] sd 5:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 246.133172] sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 246.139611] sdb: sdb1 [ 246.140390] sd 5:0:0:0: [sdb] Attached SCSI disk

Example lsblk output $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk sda1 8:1 0 795M 0 part sda2 8:2 0 100M 0 part sda3 8:3 0 128M 0 part sda4 8:4 0 463.1G 0 part /mnt/win sda5 8:5 0 10.5G 0 part sda6 8:6 0 1M 0 part sda7 8:7 0 279.4G 0 part /home sda8 8:8 0 93.1G 0 part / sda9 8:9 0 15.6G 0 part [SWAP] sdb 8:16 0 7.5G 0 disk sdb1 8:17 0 621M 0 part sr0 11:0 1 1024M 0 rom 5. Perform an image copy using the ISO image as the input file (if) and the device name of the USB memory stick as the output file (of). Note that this is the dangerous part of the procedure - be careful not to overwrite your system disk (e.g. /dev/sda). Also note that the output file (of) needs to be the entire disk (e.g. /dev/sdb) and not the partition (e.g. /dev/sdb1): Example image copy of ISO to USB memory sudo dd if=gateway-shuttle-2.0.1.191-4.iso of=/dev/sdb bs=512 6. Note that it will take several minutes or more to execute the copy. It may seem like nothing is happening, but give it some time and wait for the cursor to return to the command prompt. You should then see something like the following: Example output of dd image copy 1271808+0 records in 1271808+0 records out 651165696 bytes (651 MB) copied, 147.231 s, 4.4 MB/s 7. Remove the USB memory key from the machine. It is now ready for installing on a hardware Link Gateway. Using a Mac 1. Copy or download the Link Gateway ISO image to the ISO copy machine. 2. Insert the USB memory stick into a USB port on the ISO copy machine. 3. Open a console or terminal on the ISO copy machine. 4. Run mount to determine the disk device name of the USB memory stick - e.g.:

Example of running mount on a Mac $ mount /dev/disk1 on / (hfs, NFS exported, local, journaled) devfs on /dev (devfs, local, nobrowse) map -hosts on /net (autofs, nosuid, automounted, nobrowse) map auto_home on /home (autofs, automounted, nobrowse) /dev/disk3 on /Volumes/Link Gateway (cd9660, local, nodev, nosuid, readonly, noowners) 5. Notice that the device name for the USB memory stick in this example is /dev/disk3. 6. Un-mount the USB memory stick: Example of unmounting a USB memory stick sudo umount /dev/disk3 7. Perform an image copy using the ISO image as the input file (if) and the device name of the USB memory stick as the output file (of). Note that this is the dangerous part of the procedure - be careful not to overwrite your system disk (e.g. /dev/disk1). Also note that the output file (of) needs to be the entire disk (e.g. /dev/disk3) and not the partition (e.g. /dev/disk3s1): Example image copy of ISO to USB memory sudo dd if=downloads/gateway-shuttle-2.0.1.191-4.iso of=/dev/disk3 bs=512 8. Note that it will take several minutes or more to execute the copy. It may seem like nothing is happening, but give it some time and wait for the cursor to return to the command prompt. You should then see something like the following: Example output of dd image copy 1271808+0 records in 1271808+0 records out 651165696 bytes transferred in 447.174595 secs (1456178 bytes/sec) 9. Eject the USB memory stick: Example of ejecting USB memory stick $ diskutil eject /dev/disk3 Disk /dev/disk3 ejected Installation from ISO image There are a couple of possible installation scenarios: 1. Installing an ISO image that is built for a specific target Link Gateway

machine - e.g. a VirtualBox VM or a Shuttle DS57U. 2. Installing an ISO image that is not built for the target Link Gateway machine. We will note the differences below in these two ISO installation scenarios. In this example we will be installing on Virtual Machines (VMs), and will point out the steps that differ for physical machine installation. VM Configuration - Link Gateway with two network interfaces 1 CPU 1GB RAM 8GB disk Network Adapter 1: Internal Network (intnet1) Network Adapter 2: Bridged Adapter (eno1) Note: for a physical machine, Boot the Link Gateway machine with the USB memory stick inserted. Press the correct key (machine dependent) to interrupt the boot process and boot on the USB memory stick.

The VM is booted on the Link Gateway ISO image:

After selecting Install Link Gateway, the operating system boots, the installer runs and presents the following screen:

Under LOCALIZATION, Click DATE & TIME, select your timezone: When you click Done it will take you back to the previous screen.

There are two installation scenarios that follow at this point: 1. Installing an ISO image that is built for a specific target Link Gateway machine - e.g. a VirtualBox VM or a Shuttle DS57U. 2. Installing an ISO image that is not built for the target Link Gateway machine. 1 - Installing an ISO image that is built for a specific target Link Gateway machine Note that when installing an ISO image that is built for the specific target machine, if the external and internal interfaces are connected to their respective networks, then you should see their status as Connected under NETWORK & HOST NAME, under SYSTEM.

If you click on NETWORK & HOST NAME, you should see both interfaces enabled (toggle switch to the right is ON) and you should see their respective network configurations: Above you can see the internal interface enabled (ON). It is already configured with a static IP address of 192.168.1.1.

Clicking on the second interface in the list, we can see the external interface enabled (ON) and it has been configured via DHCP: In this scenario, there is no more configuration that is needed - we can just click on Done.

2 - Installing an ISO image that is not built for the target Link Gateway machine. Follow the same process to set up a VM with two network interfaces and boot on the ISO image. You will then see something like the following INSTALLATION SUMMARY: Note the warning symbols by INSTALLATION SOURCE and SOFTWARE SELECTION - these will disappear after a little while - there is no need to change either of these. Under LOCALIZATION, Click DATE & TIME and select your timezone as in the first example above. Note that when installing an ISO image that is NOT built for the target machine, if the external and internal interfaces are connected to their respective networks, then you should see the status as Connecting... or Not connected under

NETWORK & HOST NAME, under SYSTEM: If you click on NETWORK & HOST NAME, you should see two Ethernet interfaces listed. You then need to configure each interface as follows:

Internal Interface If the internal interface is enabled, then disable it by clicking the toggle button on the right so that it switches from ON to OFF:

External Interface DHCP Configuration Select the external interface in the column on the left:

Ensure that the external interface is connected to a secure network with a DHCP server. Enable the external interface by clicking the toggle button on the right so that it switches from OFF to ON: Note that when the interface is enabled, it will request its network configuration via DHCP. You should then see the assigned network settings as in the example screenshot above.

Enable external interface on boot By default, the Ethernet interfaces after the first one listed are not enabled on boot by default. The external interface must be enabled on boot as follows: Click Configure. You should then see something like the following:

Click the General tab:

Check Automatically connect to this network when it is available: Click Save.

Static IP Configuration (optional) Note that you also have the option of configuring a static IP address on the external interface as follows: Then click the IPv4 Settings tab:

1. Change Method to Manual. 2. Under Addresses, click Add and insert the Address, Netmask and Gateway appropriately for the target network.. 3. Add DNS servers (separated by commas) that can resolve public addresses. 4. Check Require IPv4 addressing for this connection to complete:

Click Save and you should be back at the screen listing the Ethernet interfaces and showing the configuration you have just set: Click Done on the NETWORK & HOST NAME page once the network configuration is complete and there is a connection to the network. Note that if a Link Gateway machine is configured as per the above instructions, then the external interface will be enabled and configured to receive its networking information via DHCP, but the internal interface will be disabled. Thus the only access to the Link Gateway Admin UI will be via the external interface. See Link Gateway Initial Configuration manual for how to access the Link Gateway Admin UI on the external interface.

Note on configuring a 2-NIC Shuttle (DS57U or similar) If configuring a 2-NIC Shuttle (DS57U or similar), there will be 3 interfaces listed: 1. Ethernet (eno1) should already be enabled (toggle switch ON) and have an address of 192.168.1.1. This is the internal interface and is the interface closest to the USB ports. The DHCP service is running on the internal interface so that you can plug a computer into the internal interface, receive a DHCP address and then connect to the Link Gateway Admin UI via http://192.168.1.1. 2. Ethernet (enp2s0) should already be enabled (toggle switch ON). This is the external interface and is the interface closest to the power socket. This should be plugged into a secure network which has a DHCP server and access to the Internet. Once it is plugged into such a network, you will see it receive its networking configuration via DHCP. 3. Wireless (wlp3s0) must be disabled by selecting it in the left panel and then clicking the toggle switch in the right panel so that it changes state from ON to OFF.

Begin Installation Click Begin Installation once the timezone has been set and the network is connected:

The installer then installs the base operating system and packages needed:

Once the installation is complete, the machine will automatically reboot and present a console login prompt: Note: on a physical machine, it is likely that you will be presented with a boot from USB screen here. Power the machine off at this point, remove the USB memory stick and power the machine on again. At this point, ISO installation of Link Gateway is complete and it is ready for configuration. To shut the machine down gracefully, press the power button on a physical machine or perform an ACPI shutdown on a virtual machine.

The Link Gateway Admin UI can either be accessed on the internal interface (if it was enabled and set up with a static address of 192.168.1.1) or on the external interface. To access it via the external interface, log in at the console as user net password password and run ip a to see the DHCP-assigned address on the external interface. Just open a web browser to the IP address on the internal or external interface and you should be presented with a login screen. Log in as user net password password. Please refer to the Link Gateway Initial Configuration manual for configuring the Link Gateway past this point.