⭕
OpenShift Network Playground
  • Getting Started
    • OpenShift Network Playground Overview
    • Architecture
      • Fedora CoreOS
      • Network
      • DNS
      • DHCP
      • Proxy
      • DNS64
      • NAT64
      • PXE
  • Installation
    • Prerequisites
    • vSphere
    • RHEV
    • Libvirt
  • User Guide
    • Cockpit Console
    • CLI Tool
    • OpenShift Bare Metal IPI Cluster
    • Single Node OpenShift Cluster
    • Backup OpenShift Releases
    • Additional Network Interfaces
    • Cluster Node Access
    • Tools
    • Collection of Manifests
  • Troubleshooting
    • Cockpit Cluster deployment
  • FAQ
    • What is ONP?
    • What problem it solves?
    • How to access the cluster that is deployed inside the ONP?
Powered by GitBook
On this page
  1. Getting Started
  2. Architecture

Network

Network Interface

The main interface of the ONP expose the outside world. Additionally, the machine does have the below list of interfaces.

  • baremetal

  • provisioning

  • onp1

  • onp2

  • sno0

  • nat64

All of the above interfaces are the bridge interface which holds a dummy interface that is created with the same name. For example, baremetal-dummy. For the OpenShift Bare metal IPI cluster uses both the baremetal and provisioning interfaces. The onp1 and onp2 are created for the additional interfaces of the OpenShift cluster nodes. It also provides the DHCP network. The Single Node OpenShift cluster uses the sno0 and nat64 interfaces. The nat64 interface responsible for the IPv6 to IPv4 conversion.

The nmconnection key files are added in the ignition and it will get ready in the startup itself. The MASQUERADE nat rules enables the traffic flow from one interface to another.

PreviousFedora CoreOSNextDNS

Last updated 1 year ago