DOCSLIB.ORG

System Administration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
System Administration System Administration SL1 version 8.12.1 Table of Contents Introduction 6 Who Should Read This Manual? 6 What's In This Manual? 6 Requirements 7 Global Settings 8 Global Settings for API 9 Global Settings for Appliances 11 The Web Configuration Utility 12 Global Settings for Asset Automation 14 Global Settings for User Logins, Discovery, Data Collection, UI Features, and Expiration Warnings 15 Global Settings for Data Retention 27 Global Settings for Inbound Email and Outbound Email 30 Global Settings for Login Alert Messages 34 Global Settings for Password Reset Emails 35 Defining the Email Message for "I forgot my password" 36 Global Settings for System Thresholds 38 Global Settings for Interface Thresholds 42 Settings in Silo.Conf 50 Disabling the User Interface on a Database Server 60 Collector Groups 62 Installing, Configuring, and Licensing Data Collectors 63 Technical Information About Data Collectors 63 Duplicate IP Addresses 64 Open Ports 64 Viewing the List of Collector Groups 64 Creating a Collector Group 65 Editing a Collector Group 67 Collector Groups and Load Balancing 68 Tuning Collector Groups in the silo.conf File 69 Collector Affinity 71 Failover for Collector Groups for Component Devices 72 Collector Groups for Merged Devices 72 Creating a Collector Group for Data Storage Only 73 Deleting a Collector Group 74 Aligning the Collector Group for A Single Device 74 Aligning the Collector Group in a Device Template 75 Changing the Collector Group for One or More Devices 76 Managing the Host Files for a Collector Group 76 Processes for Collector Groups 77 Daily Health Tasks 79 Monitoring System Events 80 Searching the System Logs 80 Deleting Entries from the System Logs 82 Monitoring System Processes 82 Viewing the List of System Processes 82 Searching and Filtering the List of System Processes 83 Monitoring the Status of Each Appliance 84 Monitoring User Actions and Events 86 Viewing the List of Audit Logs 87 Searching and Filtering the List of Audit Logs 87 Special Characters 88 Generating Reports on Audit Logs 92 Monitoring the Status of Data Collectors 92 Updating, Monitoring, and Maintaining SL1 94 Viewing the List of Updates 95 Downloading Patches and Updates 96 Importing Updates on to the Platform 97 Automatic Staging 98 Manually Staging an Update 100 Deploying Updates 102 Viewing the Log Files for Updates 103 Configuring Timeouts for Updates in Distributed Systems 103 Managing New Features on the Content Management Page 103 Remote Reboot After an Update 105 Upgrading Default PowerPacks 106 Monitoring and Managing User Access 107 Viewing Information about Each Access Session 108 Deleting a User's Session 109 Viewing Lockouts and Unlocking Lockouts 109 Global Settings for Lockouts 111 Audit Logs 111 Managing Scheduled Tasks 111 Viewing the List of Schedules 112 Enabling or Disabling One or More Schedules 113 Deleting One or More Schedules 114 Monitoring Overall System Usage and Statistics 114 Viewing an Overview of All Events 115 Viewing Events by Appliance and Event Source 117 Diagnostic Tools 120 Viewing Information About ScienceLogic Processes 121 Viewing the List of ScienceLogic Processes 121 Searching and Filtering the List of ScienceLogic Processes 123 Editing the Parameters of a ScienceLogic Process 124 Debugging a Process and Viewing Debug Logs 126 Viewing Information About Unhandled Exceptions 127 Viewing the List of Unhandled Exceptions 128 Searching and Filtering the list of Unhandled Exceptions 128 Saving the Unhandled Exception to the Local Computer 129 Viewing the Database Tables on the Database Server 130 Accessing the Database Tool 130 Disabling Normalization, Re-Enabling Normalization, and Backfilling Raw Data 132 Changing Passwords and IP Addresses 135 Disabling phpMyAdmin 136 Changing the Password for the Default Account for the User Interface 137 Changing the Password for the Default Console User 138 Changing the Password for the Web Configuration Utility 138 Changing Database Passwords 139 Configuring a New Password in the Database Instance 139 Configuring the Platform to Use the New Password 140 Editing Silo.Conf 140 Updating the master.system_settings_licenses Table 141 Changing IP Addresses 142 Preparing to Change the IP Address of a Database Server 142 Changing the IP Address of an Appliance 143 Reconfiguring Administration Portals After Changing the IP Address of a Database Server 145 Backup Management 147 Overview 147 Creating a Backup Credential 147 Configuration Backups 148 Defining a Configuration Backup 149 Restoring a Configuration Backup 151 Full Backup 152 Defining a Full Backup 153 Restoring a Full Backup 154 Additional Configuration for Solaris NFS Mounts 155 Defining a DR Backup 156 Restoring a DR Backup 158 Subscription Licenses 159 Viewing a Report on License Usage 160 Viewing Delivery Status 161 Manually Uploading License Usage to ScienceLogic 162 Downloading the Daily License-Usage File 162 Manually Uploading the Daily License-Usage File to ScienceLogic 163 Uploading the ScienceLogic Receipt 164 Data Retention Settings for Licensing 165 CAC Authentication 167 Prerequisites 168 Importing an SSL Certificate 169 Updating the ScienceLogic Configuration File 170 Defining the Client Certificate 170 Testing the Configuration 172 Installing an SSL Certificate 174 Certificates for ScienceLogic Servers 175 Requesting a Commercial SSL Certificate 175 Creating Your Own Certificate 176 Installing the Certificate on an SL1 Appliance 177 Authentication Profiles and Resources 180 Authentication Profiles 181 Viewing the List of Authentication Profiles 181 Filtering the List of Authentication Profiles 182 The "default" Authentication Profile 183 Creating an Authentication Profile 184 Editing an Authentication Profile 187 Deleting One or More Authentication Profiles 187 Authentication Resources 187 Viewing the List of Authentication Resources 188 Filtering the List of Authentication Resources 189 The "EM7 Internal" Resource 190 The Legacy Authentication Resources 190 Creating an LDAP/AD Authentication Resource 191 Creating an SSO Authentication Resource 197 Editing an Authentication Resource 202 Deleting an Authentication Resource 202 Managing Host Files 203 Viewing the List of Host Entries 204 Creating a New Host Entry 205 Editing a Host Entry 206 Using an Existing Host File Entry to Create a New Host File Entry (Save As) 208 Deleting One or More Host Entries 209 Chapter 1 Introduction Overview This manual describes the tasks that System Administrators who monitor and maintain the health of SL1 must perform, and the tools they can use to perform those tasks. This chapter includes the following topics: Who Should Read This Manual? 6 What's In This Manual? 6 Requirements 7 Who Should Read This Manual? This manual is intended for System Administrators who must monitor and maintain the health of SL1. This manual describes tasks in the [System] tab that are related to maintenance and monitoring of SL1. This manual also includes advanced tasks that are performed at the console or in an SSH session. What's In This Manual? This manual includes information on global settings, collector groups, health tasks, maintenance tasks, and tools for troubleshooting and debugging. Who Should Read This Manual? 6 Requirements To follow some of the steps listed in this manual, you must have administrator-level access to the console of your SL1 appliances. 7 Requirements Chapter 2 Global Settings Overview In SL1, global settings allow you to define default behavior that applies to all elements in the platform. For settings that affect devices, these global settings can be overridden by applying device-level settings. SL1 includes global settings for: l API l SL1 appliances l Asset Automation l Logins, discovery, data collection, and expiration warnings l Data retention l Inbound email and outbound email l Login Alert Messages l Password Reset Emails l Thresholds for: o System latency, file system usage, counter rollovers, availability, and component devices o Interfaces o Class-based quality of service (CBQoS) You can also define global settings for SL1 appliances, system backups, collector groups, API behavior, and processes. These global settings allow system administrators to define and automate best practices and SOPs for SL1. Use the following menu options to navigate the SL1 user interface: 8 l To view a pop-out list of menu options, click the menu icon ( ). l To view a page containing all of the menu options, click the Advanced menu icon ( ). This chapter includes the following topics: Global Settings for API 9 Global Settings for Appliances 11 Global Settings for Asset Automation 14 Global Settings for User Logins, Discovery, Data Collection, UI Features, and Expiration Warnings 15 Global Settings for Data Retention 27 Global Settings for Inbound Email and Outbound Email 30 Global Settings for Login Alert Messages 34 Global Settings for Password Reset Emails 35 Global Settings for System Thresholds 38 Global Settings for Interface Thresholds 42 Settings in Silo.Conf 50 Disabling the User Interface on a Database Server 60 Global Settings for API The REST API Settings page (System > Settings > API) allows you to define global parameters that affect the behavior of the REST API. When defined, these parameters affect all interaction with the API. NOTE: This page is available only to administrator users. To edit the settings in the REST API Settings page: 1. Go to the REST API Settings page (System > Settings > API). 9 Global Settings for API 2. In the REST API Settings page, edit the values in one or more of the following fields: l Internal Request Account. Specify the user account that allows SL1 to make API requests without a password. For details on building such an API request, see the ScienceLogic API manual. l X-EM7-run-as Header Support. Specifies whether administrator users can make API requests using the permissions of another user without that user's password. Choices are: o Disabled. Administrator users cannot make API requests using the permissions of another user. o Enabled (Admin only). Administrator users can include the X-EM7-run-as Header to make API requests using the permissions of another user.
Load more

Recommended publications
  • SNMP Trap - Firewall Rules
    SNMP Trap - Firewall Rules Article Number: 87 | Rating: 1/5 from 1 votes | Last Updated: Wed, Jan 13, 2021 at 4:42 PM Fir e wall Rule s These steps explain how to check if the Operating System (OS) of the Nagios server has firewall rules enabled to allow inbound SNMP Trap UDP port 162 traffic. The different supported OS's have different firewall commands which are explained as follows. You will need to establish an SSH session to the Nagios server that is receiving SNMP Traps. RHEL 7/8 | C e nt O S 7/8 | O r ac le Linux 7/8 First check the status of the firewall: systemctl status firewalld.service IF the firewall is running , it should product output like: ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2018-11-20 10:05:15 AEDT; 1 weeks 0 days ago Docs: man:firewalld(1) Main PID: 647 (firewalld) CGroup: /system.slice/firewalld.service └─647 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid IF the firewall is NO T running, it will produce this output: ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled) Active: inactive (dead) since Tue 2018-11-27 14:11:34 AEDT; 965ms ago Docs: man:firewalld(1) Main PID: 647 (code=exited, status=0/SUCCESS) If the firewall is NOT running, this means that inbound traffic is allowed. To ENABLE the firewall on b o o t and to s ta rt it, execute the following commands: systemctl
    [Show full text]
  • Firewalld ↔ Iptables (Continued)
    firewalld ↔ iptables (continued) Or, better said as, Understanding Linux Firewall Changes and Tools A firewall evolution and system management process Presented to SLUUG By David Forrest August 9, 2017 Bio I am David Forrest, a businessman in the housing and construction materials industry. Always keen to use the open and supportable solution even if it means getting my hands dirty. I was there, I did that, I have the t-shirt. And, I'm retired so now I can work on the “bleeding edge” - so on to the testing kernel! Why tonight? Why should we switch to firewalld? I felt a continuation was in order to address the problems that are caused by the virtual world and the interaction of processes within today's machines. Our various distributions seem to be jumping to the systemd init setup as it appears to offer better administration control to Linux Kernel machines. Firewalld just one of many efforts to see the future. In recent years, operating system virtualization has taken the industry by storm. But I'm still on CentOS7 and it uses firewalld as its default firewall along with systemd https://wiki.debian.org/Debate/initsystem/systemd firewalld It's a daemon and a command line interface to all the backends! One can start it as a service with a default setup and change it dynamically with a command line or with the daemon using D-Bus or NetworkManager. And with the new nftables release, we'll be able to combine several rules in one rich rule. The firewalld Architecture Firewalld and nft Systems have also moved toward Software Defined Networking (SDN) and system density has increased.
    [Show full text]
  • Red Hat Enterprise Linux 7 Firewalld Howto
    Red Hat Enterprise Linux 7 Firewalld HowTo Patrick Ladd Technical Account Manager, Red Hat [email protected] What Is firewalld? • Dynamic, modern control of system firewall functions • Still iptables underneath • Major features; – Real time rule changes without interruption – Zones to simplify and segregate configuration – Separate network traffic & rules by interface and zone – GUI that works – System configs in /usr/lib/firewalld/* – Custom configs in /etc/firewalld/* – Daemon runs in user space – Protocol independent: IPv4 & IPv6 Zones ● Manages groups of rules ● Dictate what traffic should be allowed – Based on level of trust in connected network(s) – Based on origin of packet ● Network interfaces are assigned a zone Default Pre-Defined Zones ● drop Drop all incoming traffic unless related to outgoing traffic (do not even respond with ICMP errors). ● block Reject all incoming traffic unless related to outgoing traffic. ● dmz Reject incoming traffic unless related to outgoing traffic or matching the ssh pre-defined service. ● external Reject incoming traffic unless related to outgoing traffic or matching the ssh pre-defined service. Outgoing IPv4 traffic forwarded through this zone is masqueraded to look like it originated from the IPv4 address of the outgoing network interface. Default Pre-Defined Zones ● public Reject incoming traffic unless related to outgoing traffic or matching the ssh, or dhcpv6-client pre-defined services. The default zone for newly-added network interfaces. ● work Reject incoming traffic unless related to outgoing traffic or matching the ssh, ipp-client, ordhcpv6-client pre- defined services. Default Pre-Defined Zones ● internal Reject incoming traffic unless related to outgoing traffic or matching the ssh, mdns, ipp-client, samba-client, or dhcpv6-client pre-defined services.
    [Show full text]
  • The Next Generation Firewall for Red Hat Enterprise Linux 7 RC Thomas Graf Red Hat Agenda
    The Next Generation Firewall for Red Hat Enterprise Linux 7 RC Thomas Graf Red Hat Agenda ● FirewallD – Firewall Management as a Service ● Kernel – New Filtering Capabilities ● Nftables – A Look Ahead FirewallD Firewall Management as a Service Existing Packet Filtering Architecture User iptables ip6tables ebtables Land Kernel Netfilter IPv4 IPv6 Bridge Protocol dependent packet filter and utilities Firewall Management as a Service Application Reports User Interface Direct Graphical Access CLI FirewallD IPv4 IPv6 Bridge FirewallD – Features • Unified firewall management as a service • No service disruptions during rule updates • Firewall zones • D-Bus interface • Runtime & permanent configuration • Graphical & console user interface • Direct access FirewallD – Policy Abstraction Policy Zone FirewallD – Zone Policy • Default policy • Enabled services • Rich rules • Masquerading • Port forwarding • ICMP filter FirewallD – Graphical User Interface FirewallD – Command Line Interface • Add interface “eth0” to zone “public” permanently: # firewall-cmd --permanent --zone=internal --add-interface=eth0 • List enabled services: # firewall-cmd --zone=public --list-services RHEL7 Netfilter Kernel Changes Scaling of Legacy Applications (xt_cpu) 80 8080 CPU 1 App #1 on 8080 REDIRECT 80 8081 RSS CPU 2 App #2 on 8081 REDIRECT 80 808n CPU n App #n on 808n REDIRECT # iptables -t nat -A PREROUTING -p tcp --dport 80 \ -m cpu --cpu 0 -j REDIRECT --to-port 8080 # iptables -t nat -A PREROUTING -p tcp --dport 80 \ -m cpu --cpu 1 -j REDIRECT --to-port 8081 Connection
    [Show full text]
  • Dirección De Posgrado Y Formación Continua
    ESCUELA SUPERIOR POLITÉCNICA AGROPECUARIA DE MANABÍ MANUEL FÉLIX LÓPEZ DIRECCIÓN DE POSGRADO Y FORMACIÓN CONTINUA INFORME DE TRABAJO DE TITULACIÓN PREVIA LA OBTENCIÓN DEL TÍTULO DE MAGÍSTER EN TECNOLOGÍAS DE LA INFORMACIÓN MENCIÓN EN REDES Y SISTEMAS DISTRIBUIDOS MODALIDAD: PROYECTO DE INVESTIGACIÓN Y DESARROLLO TEMA: ACCESO A REDES INALÁMBRICAS DE LA ESPAM MFL MEDIANTE UN SERVIDOR RADIUS AUTOR: JOSÉ RUBÉN LOOR ANCHUNDIA PORTADA TUTOR: ING. JOFFRE RAMÓN MOREIRA PICO, M.Sc, COTUTOR: ING. JAVIER HERNÁN LÓPEZ ZAMBRANO, M.Sc, CALCETA, SEPTIEMBRE 2019 ii DERECHOS DE AUTORÍA JOSÉ RUBÉN LOOR ANCHUNDIA, declaro bajo juramento que el trabajo aquí descrito es de mi autoría, que no ha sido previamente presentado para ningún grado o calificación profesional, y que he consultado las referencias bibliográficas que se incluyen en este documento. A través de la presente declaración cedo los derechos de propiedad intelectual a la Escuela Superior Politécnica Agropecuaria de Manabí Manuel Félix López, según lo establecido por la Ley de Propiedad Intelectual y su Reglamento. ______________________________ JOSÉ RUBÉN LOOR ANCHUNDIA iii CERTIFICACIÓN DE TUTOR ING. JOFFRE RAMÓN MOREIRA PICO, M.Sc, certifica haber tutelado el trabajo de titulación, que ha sido desarrollada por JOSÉ RUBÉN LOOR ANCHUNDIA, previa la obtención del título de Magister en Tecnologías de la Información con mención en Redes y Sistemas Distribuidos de acuerdo al REGLAMENTO DE LA UNIDAD DE TITULACIÓN DE PROGRAMAS DE POSGRADO de la Escuela Superior Politécnica Agropecuaria de Manabí Manuel
    [Show full text]
  • GL275 Enterprise Linux Network Services
    EVALUATION COPY Unauthorized Reproduction or Distribution Enterprise Linux Network Prohibited Services Student Workbook EVALUATION COPY Unauthorized Reproduction GL275 ENTERPRISE LINUX NETWORK SERVICES RHEL7 SLES12 or Distribution The contents of this course and all its modules and related materials, including handouts to audience members, are copyright ©2017 Guru Labs L.C. No part of this publication may be stored in a retrieval system, transmitted or reproduced in any way, including, but not limited to, photocopy, photograph, magnetic, electronic or other record, without the prior written permission of Guru Labs. This curriculum contains proprietary information which is for the exclusive use of customers of Guru Labs L.C., and is not to be shared with personnel other than those in attendance at this course. This instructional program, including all material provided herein, is supplied without any guarantees from Guru Labs L.C. Guru Labs L.C. assumes no liability for damages or legal action arising from Prohibited the use or misuse of contents or details contained herein. Photocopying any part of this manual without prior written consent of Guru Labs L.C. is a violation of federal law. This manual should not appear to be a photocopy. If you believe that Guru Labs training materials are being photocopied without permission, please email [email protected] or call 1-801-298-5227. Guru Labs L.C. accepts no liability for any claims, demands, losses, damages, costs or expenses suffered or incurred howsoever arising from or in connection
    [Show full text]
  • List of Versions Added in ARL #2588
    List of versions added in ARL #2588 Publisher Product Version 1E Nomad Branch 7.0 45RPM software MailRaider 3.60 45RPM software MailRaider 3.22 Acesoft Tracks Eraser Pro 8.7 Acqualia Software Soulver 3.4 activePDF activePDF Toolkit 7.1 Acuant Software Developers Kit 10.08 Adlice Software RogueKiller 12.1 Adlice Software RogueKiller 13.1 Adobe Creative Cloud Desktop Application 5.4 Adobe Flash Player PPAPI 34.0 Adobe UXP Developer Tool Unspecified Adobe Experience Manager forms 10.0 Aide CAD Systems Aide PDF to DXF Converter 10.0 ALK Technologies PC*MILER|Rail 23.0 ALK Technologies PC*MILER|Rail 24.0 ALK Technologies PC*MILER|Rail 25.0 ALK Technologies PC*MILER|Rail 26.0 Alsoft DiskWarrior 5.2 Altium Designer SOLIDWORKS 2.1 Altus Group ARGUS Developer Unspecified Amazon system-release 2 Amazon man-pages 3.5 Amazon ed 3.1 Amazon pcre2 8.3 Andreas Hegenberg BetterTouchTool 3.400 Andritz IDEAS 6.5 Antibody Software WizTree 3.3 aONe Keka 1.2 Apache Software Foundation Hive Metastore Unspecified Apple CFNetwork 902.1 Apple CFNetwork 902.3 Apple Scripting Bridge 1.3 Apple System Image Utility 10.13 Apple CalendarUI 14.6 Apple Ruby for Mac 10.5 Apple Xcode 12.0 Apple AirPort Utility 17.0 Apple Xcode 11.7 Apple Xcode 12.3 Apple Directory Utility for Mac 5.0 Apple Pages Mobile 10 Apple iMovie 10.2 Apple Compressor 4.5 Apple PhotosUI 1.0 Apple WebKit 136 Apple WebKit 146 Applied Computer Services Timer Pro NET 19.0 ARES PRISM PRISM G2 45.1 Aspect Software Prophecy platform 20.0 Aspect Software Workforce Management Advanced Modules 18.2 Aspect Software
    [Show full text]
  • Lenovo Big Data Validated Design for Cloudera Enterprise on Thinksystem SR655 and SR635 Servers
    Lenovo Big Data Validated Design for Cloudera Enterprise on ThinkSystem SR655 and SR635 Servers Last update: 28 June 2021 Version 1.3 Reference architecture for Solution based on the Cloudera Enterprise with Apache ThinkSystem SR635/SR655 server Hadoop and Apache Spark with AMD CPU inside Deployment considerations for Solution based on ThinkSystem scalable racks including detailed SR655 compute node with storage validated bills of material pool Xiaotong Jiang (Lenovo) Xifa Chen (Lenovo) Ajay Dholakia (Lenovo) Weixu Yang (Lenovo) Dan Kangas (Lenovo) Lenovo Big Data Validated Design for Cloudera Enterprise on ThinkSystem SR655 and 1 SR635 Servers Table of Contents 1 Introduction ............................................................................................... 4 2 Business problem and business value ................................................... 5 3 Requirements ............................................................................................ 7 Functional Requirements ......................................................................................... 7 Non-functional Requirements................................................................................... 7 4 Architectural Overview ............................................................................. 8 Cloudera Enterprise ................................................................................................. 8 Bare-metal Cluster ................................................................................................... 8
    [Show full text]
  • Red Hat Enterprise Linux 8 Securing Networks
    Red Hat Enterprise Linux 8 Securing networks Configuring secured networks and network communication Last Updated: 2021-09-16 Red Hat Enterprise Linux 8 Securing networks Configuring secured networks and network communication Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Installing Firewalld
    CHAPTER 40. FIREWALLS 1 Lab 40.1: Installing firewalld While most recent Linux distributions have the firewalld package (which includes the firewall-cmd multi-purpose utility) available, it might not be installed on your system. First you should check to see if it is already installed, with $ which firewalld firewall-cmd /usr/sbin/firewalld /usr/bin/firewall-cmd If you fail to find the program, then you need to install with one of the following, depending on your distribution in the usual way: $ sudo yum install firewalld $ sudo zypper install firewalld $ sudo apt-get install firewalld If this fails, the firewalld package is not available for your distribution. For example, this will be the case for the older RHEL6/CentOS6 distributions. In this case you will have to install from source. To do this, go to https://fedorahosted.org/firewalld/ and you can get the git source repository, but it is much easier to download the most recent tarball (firewalld-0.3.13.tar.bz2 as of this writing.) Then you have to follow the common procedure for installing from source: $ tar xvf firewalld-0.3.13.tar.bz2 $ cd firewalld-0.3.13 $ ./configure $ make $ sudo make install Note this source also has an uninstall target: $ sudo make uninstall in case you have regrets. You will have to deal with any inadequacies that come up in the ./configure step, such as missing libraries etc. When you install from a packaging system, the distribution takes care of this for you, but from source it can be problematic. If you have run the Linux Foundation's ready-for.sh script on your system, you are unlikely to have problems.
    [Show full text]
  • JA SÄHKÖTEKNIIKAN TIEDEKUNTA Arttu Vuosku
    TIETO- JA SÄHKÖTEKNIIKAN TIEDEKUNTA Arttu Vuosku Kotipalomuurien tietoturva Kandidaatintyö Tietotekniikan tutkinto-ohjelma 2021 Vuosku. (2021) Kotipalomuurien tietoturva. Oulun yliopisto, tietotekniikan tutkinto-ohjelma. Kandidaatintyö, 33 s. TIIVISTELMÄ Kotiverkko on herkkä kohde rikollisuudelle ja vakoilulle. Palomuuri on yksi keino suojata verkkoja virustorjuntaohjelmien ohella. Se on järjestelmä, joka sijaitsee kahden verkon rajalla ja kaiken liikenteen tulee kulkea sen läpi. Käyttäjä voi konfiguroida palomuuriin itse sopivia sääntöjä. Kotiverkon uhkia ovat madot, murtautumiset, haittaohjelmat ja palvelunestohyökkäykset. Työssä tutustuttiin erilaisiin palomuurityyppeihin ja tietoturva-aukkojen eli haavoittuvuuksien löytämiskeinoihin. Työssä testattiin pfSense-palomuuria kotikäytössä ja arvioitiin sen käytettävyyttä konfiguroimalla siihen erilaisia sääntöjä. Lisäksi etsittiin avoimia portteja oman asiakasohjelmiston avulla ja tutkittiin kotiverkon haavoittuvuuksia Nessus Essentials Vulnerability Scanner -ohjelmiston avulla. Tuloksissa huomattiin, että pfSense ei ole välttämättä helppokäyttöisin vaihtoehto kotikäyttäjälle, koska se vaatii käyttäjältä perehtymistä. Kotiverkosta ei löydetty kriittisiä haavoittuvuuksia. Työn kokeellisessa osassa selvitettiin, kuinka kotiverkkojen tietoturvaa voisi kehittää tehokkaasti ja ehkäistä mahdollisia uhkia parhaiten. Avainsanat: palomuuri, kotiverkko, haavoittuvuus, uhka Vuosku A. (2021) The security of home firewalls. University of Oulu, Degree Programme in Computer Science and Engineering. Bachelor’s
    [Show full text]
  • Oracle® Linux 8 Configuring the Firewall
    Oracle® Linux 8 Configuring the Firewall F20786-06 July 2021 Oracle Legal Notices Copyright © 2019, 2021 Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]