Kwame Nkrumah University of Science and Technology

Total Page:16

File Type:pdf, Size:1020Kb

Kwame Nkrumah University of Science and Technology KWAME NKRUMAH UNIVERSITY OF SCIENCE AND TECHNOLOGY COLLEGE OF SCIENCE DEPARTMENT OF COMPUTER SCIENCE AN IMPROVED COMPUTER NETWORK ACCESS CONTROL USING FREE BSD PFSENSE A CASE STUDY OF UMaT LOCAL AREA NETWORK A THESIS SUBMITTED IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN INFORMATION TECHNOLOGY BY AKPAH SYLVESTER (BSc. INFORMATION TECHNOLOGY) AUGUST 2015 i TABLE OF CONTENTS PAGE DECLARATION ....................................................................................................... vi DEDICATION .......................................................................................................... vii ACKNOWLEDGEMENTS .................................................................................... viii ABSTRACT ............................................................................................................... ix LIST OF FIGURES ................................................................................................... x LIST OF TABLES .................................................................................................. xiv ABBREVIATIONS .................................................................................................. xv CHAPTER ONE ........................................................................................................ 1 INTRODUCTION ...................................................................................................... 1 1.0 Statement of the Problem ............................................................................................... 1 1.1 Objectives of the Thesis ................................................................................................. 3 1.3 Research Methodology .................................................................................................. 3 1.4 Scope of the Thesis ......................................................................................................... 4 1.5 Thesis Organization ........................................................................................................ 4 CHAPTER TWO ....................................................................................................... 5 REVIEW OF RELATED LITERATURE ............................................................... 5 2.1 Local Area Network (LAN) .......................................................................................... 5 2.2 Institute of Electrical and Electronics Engineers (IEEE) .......................................... 6 ii 2.3 The IEEE 802.3 Standards for LAN ............................................................................ 7 2.3.1 10Base-T ....................................................................................................................... 7 2.3.2 100Base-T ..................................................................................................................... 8 2.3.3 Gigabit Ethernet ........................................................................................................... 9 2.3.4 How the Ethernet Works .......................................................................................... 10 2.3.5 IEEE 802.3 Standard Relationship to the OSI Model .......................................... 12 2.3.6 IEEE 802.3 Physical Media of Ethernet Network................................................. 13 2.3.7 Data Transmission ..................................................................................................... 15 2.3.8 Advantages and Disadvantages of the IEEE 802.3 Standard .............................. 17 2.3.9 Attacks on LANs ....................................................................................................... 19 2.3.10 Types of Attacks on LANs ..................................................................................... 19 2.4 Network Security .......................................................................................................... 22 2.4.1 Network Access Control (NAC) ............................................................................. 23 2.4.2 Components of NAC Architecture .......................................................................... 26 2.5 Access Control Models ................................................................................................ 30 2.5.1 Mandatory Access Control (MAC) ......................................................................... 30 2.5.2 Discretionary Access Control (DAC) ..................................................................... 31 2.5.3 Role-Based Access Control (RBAC) ...................................................................... 31 2.6 Functions of Network Access Control ....................................................................... 32 2.7 Access Control with IEEE 802.1X ............................................................................. 36 iii 2.7.1 Categorization of the 802.1X Authentication Process .......................................... 38 2.7.2 Attacks in 802.1x Protocol ....................................................................................... 39 2.7.3 Extensible Authentication Protocol (EAP) ............................................................ 40 CHAPTER THREE ................................................................................................. 49 METHODOLOGY ................................................................................................... 49 3.1 Study Area ..................................................................................................................... 49 3.2 UMaT Network Infrastructure .................................................................................... 50 3.3 Tools Used for Performing Analysis on the UMaT LAN ....................................... 55 3.4 Machine Setup to be the Main Firewall ..................................................................... 55 3.4.1 Hard Specifications ................................................................................................... 56 3.4.2 Software Requirement: ............................................................................................. 56 3.4.3 pfSense Software ....................................................................................................... 57 3.4.4 Steps involved in pfSense installation and Configuration ................................... 58 3.5 Squid Proxy Server ....................................................................................................... 64 3.5.1 Steps Involved in Squid Proxy Server Installation ............................................... 65 3.6 SquidGuard .................................................................................................................... 70 3.6.1 Steps involved in squidGuard Installation ............................................................. 71 3.7 Squid Analysis Resource Generator (SARG) ........................................................... 74 3.7.1 Steps Involved in SARG Installation ...................................................................... 75 3.8 Active Directory ............................................................................................................ 77 iv 3.8.1 Stakeholders of the UMaT Internet Community ................................................... 77 3.8.2 Steps Involved in Creating Organizational Units .................................................. 78 3.8.3 Steps in Creating Staff User Credentials ................................................................ 80 3.8.4 Steps in Creating Student User Credentials ........................................................... 82 CHAPTER FOUR .................................................................................................... 85 TESTING THE SYSTEM AND DISCUSSION OF RESULTS .......................... 85 4.1 Testing the Existing UMaT LAN ................................... Error! Bookmark not defined. 4.1.2 Results of the Existing System ................................................................................ 85 4.2 Testing the Enhanced UMaT LAN ............................................................................. 86 4.2.1 Results and Discussion of Squid Proxy Server ..................................................... 86 4.2.2 Results and Discussion of SquidGuard................................................................... 91 4.2.3 Results and Discussion of Squid Analysis Report Generator (SARG) .............. 94 4.3 Proposed Solution for UMaT LAN ............................................................................ 96 CHAPTER FIVE .................................................................................................... 101 CONCLUSIONS AND RECOMMENDATIONS ............................................... 101 5.1 Conclusions ................................................................................................................. 101 5.2 Recommendations ....................................................................................................... 102 REFERENCES ....................................................................................................... 104 APPENDIX ............................................................................................................. 109 v DECLARATION I hereby declare that this submission is my own work towards the MSc and that, to the best of my knowledge, it contains no material previously published by another
Recommended publications
  • Proceedings of the Bsdcon 2002 Conference
    USENIX Association Proceedings of the BSDCon 2002 Conference San Francisco, California, USA February 11-14, 2002 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2002 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. Flexible Packet Filtering: Providing a Rich Toolbox Kurt J. Lidl Deborah G. Lidl Paul R. Borman Zero Millimeter LLC Wind River Systems Wind River Systems Potomac, MD Potomac, MD Mendota Heights, MN [email protected] [email protected] [email protected] Abstract The BSD/OS IPFW packet filtering system is a well engineered, flexible kernel framework for filtering (accepting, rejecting, logging, or modifying) IP packets. IPFW uses the well understood, widely available Berkeley Packet Filter (BPF) system as the basis of its packet matching abilities, and extends BPF in several straightforward areas. Since the first implementation of IPFW, the system has been enhanced several times to support additional functions, such as rate filtering, network address translation (NAT), and traffic flow monitoring. This paper examines the motivation behind IPFW and the design of the system. Comparisons with some contemporary packet filtering systems are provided. Potential future enhancements for the IPFW system are discussed. 1 Packet Filtering: An Overview might choose to copy only this data.
    [Show full text]
  • 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]
  • Active-Active Firewall Cluster Support in Openbsd
    Active-Active Firewall Cluster Support in OpenBSD David Gwynne School of Information Technology and Electrical Engineering, University of Queensland Submitted for the degree of Bachelor of Information Technology COMP4000 Special Topics Industry Project February 2009 to leese, who puts up with this stuff ii Acknowledgements I would like to thank Peter Sutton for allowing me the opportunity to do this work as part of my studies at the University of Queensland. A huge thanks must go to Ryan McBride for answering all my questions about pf and pfsync in general, and for the many hours working with me on this problem and helping me test and debug the code. Thanks also go to Theo de Raadt, Claudio Jeker, Henning Brauer, and everyone else at the OpenBSD network hackathons who helped me through this. iii Abstract The OpenBSD UNIX-like operating system has developed several technologies that make it useful in the role of an IP router and packet filtering firewall. These technologies include support for several standard routing protocols such as BGP and OSPF, a high performance stateful IP packet filter called pf, shared IP address and fail-over support with CARP (Common Address Redundancy Protocol), and a protocol called pfsync for synchronisation of the firewalls state with firewalls over a network link. These technologies together allow the deployment of two or more computers to provide redundant and highly available routers on a network. However, when performing stateful filtering of the TCP protocol with pf, the routers must be configured in an active-passive configuration due to the current semantics of pfsync.
    [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]
  • Firewall and Proxy Server HOWTO Firewall and Proxy Server HOWTO
    Firewall and Proxy Server HOWTO Firewall and Proxy Server HOWTO Table of Contents Firewall and Proxy Server HOWTO................................................................................................................1 Mark Grennan, mark@grennan.com.......................................................................................................1 1. Introduction..........................................................................................................................................1 2. Understanding Firewalls......................................................................................................................1 3. Firewall Architecture ..........................................................................................................................1 4. Setting up the Linux Filtering Firewall ...............................................................................................1 5. Software requirements.........................................................................................................................1 6. Preparing the Linux system.................................................................................................................1 7. IP filtering setup (IPFWADM)............................................................................................................2 8. IP filtering setup (IPCHAINS).............................................................................................................2 9. Installing a Transparent SQUID
    [Show full text]
  • Block Icmp Ping Requests
    Block Icmp Ping Requests Lenard often unpenned stutteringly when pedigreed Barton calques wittingly and forsook her stowage. Garcia is theropod vermiculatedand congregate unprosperously. winningly while nonnegotiable Timothy kedges and sever. Gyrate Fazeel sometimes hasting any magnetron Now we generally adds an email address of icmp block ping requests That after a domain name, feel free scans on or not sent by allowing through to append this friendship request. Might be incremented on your Echo press and the ICMP Echo reply messages are commonly as! Note that ping mechanism blocks ping icmp block not enforced for os. This case you provide personal information on. Send to subvert host directly, without using routing tables. Examples may be blocked these. Existence and capabilities is switched on or disparity the protocol IP protocol suite, but tcp is beat of. We are no latency and that address or another icmp message type of icmp ping so via those command in this information and get you? Before assigning it is almost indistinguishable from. Microsoft Windows found themselves unable to download security updates from Microsoft; Windows Update would boost and eventually time out. Important mechanisms are early when the ICMP protocol is restricted. Cisco device should be valuable so a host that block icmp? Add a normal packet will update would need access and others from. Now check if you? As an organization, you could weigh the risks of allowing this traffic against the risks of denying this traffic and causing potential users troubleshooting difficulties. Icmp block icmp packets. Please select create new know how long it disables a tcp syn flood option available in specific types through stateful firewalls can have old kernels.
    [Show full text]
  • Internet of Things
    8.5 GB Motorola Xiaomi Mi Lenovo A lightweight and Dual Layer DVD Moto Turbo A Powerful Processor Low on cost but high Yoga 3 Pro Free on performance premium quality Free Smartphone With a Brilliant Screen Pad Tablet Hybrid Laptop convertible `150 Remote Desktop Sharing with Chrome Recover Data from www.pcquest.com Encryped Hard Disk UNDERSTAND • CHOOSE • IMPLEMENT IT MAY 2015 with Ubuntu Internet of Things: The Road Ahead Key industries that are bullish on IoT and why, ISVs that live on IoT, 5 innovative IoT startups, latest trends on IoT adoption by businesses, and more... CONTEST: If your disks are missing, please ask your newsagent or email: [email protected] please ask your newsagent or email: If your disks are missing, WIN Ashampoo Snap 8 screen capturing tool and licensed copy of KEYWIN worth `44,000. See pg 58 for details Hot Trends: Developer Corner: The Pros and Cons of Net Neutrality How to Reduce Vulnerabilities in Android Apps How Online-only Mobile Brands are Shootouts Redefining Retail 12 Portable Bluetooth Speakers 5 Big Data Costs You Can’t Afford to Ignore 10 Budget Smartphones under `10,000 Subscribe to PCQuest and get antivirus worth `1,800 free. For details, go to pg. 74 92 pages including cover Contents 36 COVER STORY Internet of Things: The Road Ahead Moving beyond the initial euphoria, IoT has steadily progressed to impact our lives in several meaningful ways. Going forward we expect both businesses and individuals to make steady returns on their investments 38 5 Key Industries that are Bullish on IoT 42
    [Show full text]
  • Ipfire Duobox Business, 4 GB RAM, 64 GB SSD
    Item no.: 323825 IPFire DuoBox Business, 4 GB RAM, 64 GB SSD from 462,37 EUR Item no.: 323825 shipping weight: 1.20 kg Manufacturer: IPFire Product Description IPFire DuoBox Business, 4 GB RAM, 64 GB SSDThis Firewall version was specifically designed for small offices und home offices, in which a stable and fast Internet connection is essential. The Duo Box Business provides you with fast Internet, while being low-cost and energy-efficient. It keeps your business connected and, most importantly, it keeps your network safe. Main Features: ● 2x Gigabit Ethernet for LAN and WAN ● 1x 300 Mbit dual-band Wi-Fi with access point mode ● optionally upgradeable with LTE Scope of Delivery: ● System ● Power Cable ● PSU ● 2x WLAN antennas Specifications Application: Firewall application for SOHO, branch offices and IoT Type: aluminum profile construction without venting holes, black anodized Dimensions (W x D x H): 134 x 108 x 55 mm Weight: 1.2 kg Cooling: directly attached to chassis Operating conditions: 0 - 50 °C / 80 % rel. humidity CPU: Intel Pentium 3558U, 2x 1.7 GHz RAM: 4 GB DDR3L Mainboard: customized eNUC platform I/O front (standard): 1x RS232, 1x USB 3.0, 1x Audio I/O back: 2x HDMI, 2x USB 3.0, 2x RJ45 (Realtek GLAN) I/O internal: internal I/O might be occupied - depending on your configuration, 1x mSATA/mPCIe full size, 2x USB 2.0 Storage: 1x 2.5" 64 GB SSD (industrial, MLC, 0 - +70 °C ) Graphics: Intel HD, up to 2 independend displays supported, max. resolution: 3840 x 2160 px Wireless LAN, Unex DNUR-S2 300 Mbit dual-band WLAN module LTE: Huawei 909u-5214G LTE (FDD) B1/B2/B3/B5/B7/B8/B203G DC-HSPA+/HSPA+/HSPA/UMTS B1/B2/B5/B82G EDGE/ GPRS/ GSM - 850/900/1800/1900MHz Power-In: DC wide-input 9..19V, 5.5 x 2.5 mm plug PSU: FSP060-DHAN3; external AC/DC adapterInput: 90 to 264 V ACOutput: 12 V / 60 W Power consumption: Idle 6 W, 100% load (Cel.) 11 W OS compatibility: IPFire, OPNSense, PFSense, Ubuntu Linux Scan this QR code to view the product All details, up-to-date prices and availability Powered by TCPDF (www.tcpdf.org).
    [Show full text]
  • Pf3e Index.Pdf
    INDEX Note: Pages numbers followed by f, n, priority-based queues, 136–145 or t indicate figures, notes, and tables, match rule for queue assignment, respectively. 137–138 overview, 134–135 Symbols performance improvement, 136–137 # (hash mark), 13, 15 queuing for servers in DMZ, ! (logical NOT) operator, 42 142–144 setting up, 135–136 A on FreeBSD, 135–136 on NetBSD, 136 Acar, Can Erkin, 173 on OpenBSD, 135 ACK (acknowledgment) packets transitioning to priority and class-based bandwidth allocation, queuing system, 131–133 139–140 anchors, 35–36 HFSC algorithm, 124, 126, 142 authpf program, 61, 63 priority queues, 132, 137–138 listing current contents of, 92 two-priority configuration, loading rules into, 92 120–121, 120n1 manipulating contents, 92 adaptive.end value, 188 relayd daemon, 74 adaptive firewalls, 97–99 restructuring rule set with, 91–94 adaptive.start value, 188 tagging to help policy routing, 93 advbase parameter, 153–154 ancontrol command, 46n1 advskew parameter, 153–154, 158–159 antispoof tool, 27, 193–195, 194f aggressive value, 192 ARP balancing, 151, 157–158 ALTQ (alternate queuing) framework, atomic rule set load, 21 9, 133–145, 133n2 authpf program, 59–63, 60 basic concepts, 134 basic authenticating gateways, class-based bandwidth allocation, 60–62 139–140 public networks, 62–63 overview, 135 queue definition, 139–140 tying queues into rule set, 140 B handling unwanted traffic, 144–145 bandwidth operating system-based queue actual available, 142–143 assignments, 145 class-based allocation of, 139–140 overloading to
    [Show full text]
  • Freebsd and Netbsd on Small X86 Based Systems
    FreeBSD and NetBSD on Small x86 Based Systems Dr. Adrian Steinmann <[email protected]> Asia BSD Conference in Tokyo, Japan March 17th, 2011 1 Introduction Who am I? • Ph.D. in Mathematical Physics (long time ago) • Webgroup Consulting AG (now) • IT Consulting Open Source, Security, Perl • FreeBSD since version 1.0 (1993) • NetBSD since version 3.0 (2005) • Traveling, Sculpting, Go AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 2 Focus on Installing and Running FreeBSD and NetBSD on Compact Flash Systems (1) Overview of suitable SW for small x86 based systems with compact flash (CF) (2) Live CD / USB dists to try out and bootstrap onto a CF (3) Overview of HW for small x86 systems (4) Installation strategies: what needs special attention when doing installations to CF (5) Building your own custom Install/Maintenance RAMdisk AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 3 FreeBSD for Small HW Many choices! – Too many? • PicoBSD / TinyBSD • miniBSD & m0n0wall • pfSense • FreeBSD livefs, memstick • NanoBSD • STYX. Others: druidbsd, Beastiebox, Cauldron Project, ... AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 4 PicoBSD & miniBSD • PicoBSD (1998): Initial import into src/release/picobsd/ by Andrzej Bialecki <[email protected]
    [Show full text]
  • IP Filter - TCP/IP Firewall/NAT Software
    IP Filter - TCP/IP Firewall/NAT Software IP Filter Current version: 5.1.0 Next release status Patches for last release What's new ? Click here! Mailing list ? Send mail to [email protected] with "subscribe ipfilter" in the body of the mail. What is it ? IPFilter is a software package that can be used to provide network address translation (NAT) or firewall services. To use, it can either be used as a loadable kernel module or incorporated into your UNIX kernel; use as a loadable kernel module where possible is highly recommended. Scripts are provided to install and patch system files, as required. To see an overview of how IP Filter fits into the overall picture of TCP/IP with your kernel and the order in which the various phases of packet processing is done, click here. The IPFilter FAQ by Phil Dibowitz! It comes as a part of the following operating systems: FreeBSD-current (post 2.2) NetBSD-current (post 1.2) xMach Solaris 10 Open Solaris http://coombs.anu.edu.au/~avalon/ip-filter.html (1 of 7)19.2.2011 •. 14:01:49 IP Filter - TCP/IP Firewall/NAT Software It has been tested and run on: Solaris/Solaris-x86 2.3 - 9 SunOS 4.1.4 - 4.1.4 NetBSD 1.0 - 1.4 FreeBSD 2.0.0 - 2.2.8 BSD/OS-1.1 - 4 IRIX 6.2, 6.5 OpenBSD 2.0 - 3.5 Linux(*) 2.4 - 2.6 HP-UX 11.00 Tru64 5.1a AIX 5.3 ML05 QNX 6 Port * - It has been tested and shown to work on RedHat 9.0, SuSE 9.1 and will, in general work with 2.4 and 2.6 kernels.
    [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]