Pular para o conteúdo principal

Instalando a bridge no Oracle Linux


Create A Network Bridge on CentOS 7 / RHEL 7

3 Comments , ,

Create A Network Bridge on CentOS 7 / RHEL 7
Create A Network Bridge on CentOS 7 / RHEL 7
Sometimes you may need to setup network bridge adapter in Linux; particularly during the configuration of KVM (Kernel-based Virtual Machine), and, also while
setting up Linux containers. This bridge network allows virtual machines to have access to the external network and vice-versa, follow this guide to setup network bridge on CentOS 7 / RHEL 7.

Install Module:

CentOS 7 comes with bridging module loaded on system boot by default, verify it by using below command.

 #modinfo bridge 
 filename:       /lib/modules/3.10.0-327.el7.x86_64/kernel/net/bridge/bridge.ko
 alias:          rtnl-link-bridge
 version:        2.3
 license:        GPL
 rhelversion:    7.2
 srcversion:     905847C53FF43DEFAA0EB3C
 depends:        stp,llc
 intree:         Y
 vermagic:       3.10.0-327.el7.x86_64 SMP mod_unload modversions
 signer:         CentOS Linux kernel signing key
 sig_key:        79:AD:88:6A:11:3C:A0:22:35:26:33:6C:0F:82:5B:8A:94:29:6A:B3
 sig_hashalgo:   sha256
If the module is not loaded, you can load it using the following command.
# modprobe --first-time bridge
Install bridge-utils for controlling the network adaptors.
# yum install bridge-utils -y

Create a Network Bridge:

To create a network bridge, create a file called “ifcfg-virbrN” replacing “N” with a number, such as “0” in the “/etc/sysconfig/network-scripts/“.


File doesn’t necessarily to be “virbrN“, you can also give a name like “brN”
# vi /etc/sysconfig/network-scripts/ifcfg-virbr0
 
Place the following content into that file, modify it according to your environment.
DEVICE="virbr0"
BOOTPROTO="static"
IPADDR="192.168.12.10"
NETMASK="255.255.255.0"
GATEWAY="192.168.12.2"
DNS1=192.168.12.2
ONBOOT="yes"
TYPE="Bridge"
NM_CONTROLLED="no"
 
Now, it’s the time to modify the network configuration of the existing adaptor in such a way that it points to a bridge interface. In this guide, I will use my existing adaptor “eno16777736” for bridging.

# vi /etc/sysconfig/network-scripts/ifcfg-eno16777736
 
Place the content like below.
DEVICE=eno16777736
TYPE=Ethernet
BOOTPROTO=none
ONBOOT=yes
NM_CONTROLLED=no
BRIDGE=virbr0

Restart the network using the following command.
# systemctl restart network

Use ifconfig command to see interface details.
# ifconfig
eno16777736: flags=4163  mtu 1500
        inet6 fe80::20c:29ff:fe6a:692  prefixlen 64  scopeid 0x20
        ether 00:0c:29:6a:06:92  txqueuelen 1000  (Ethernet)
        RX packets 3822  bytes 302382 (295.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 192  bytes 42924 (41.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10
        loop  txqueuelen 0  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4163  mtu 1500
        inet 192.168.12.10  netmask 255.255.255.0  broadcast 192.168.12.255
        inet6 fe80::20c:29ff:fe6a:692  prefixlen 64  scopeid 0x20
        ether 00:0c:29:6a:06:92  txqueuelen 0  (Ethernet)
        RX packets 1454  bytes 109258 (106.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 179  bytes 34372 (33.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
 
Reference:
Redhat Documentation

Comentários

Postar um comentário

Postagens mais visitadas deste blog

Upgrading Iomega ix2-200 to Cloud Edition

You just got your ix2-200 from eBay and there are no disks inside the NAS. Or you have a brand new ix2-200 -yet you could not afford Cloud Edition. No problem. With just a USB stick and a SATA adapter or desktop PC, you will easily upgrade your ix2-200 to ix2-200 Cloud Edition. Not only your ix2-200 will have a brand new interface and Cloud options, but also will become Mac OS X Lion compatible! What do we need? Decrypted! ix2-200 Cloud Edition Firmware 3.1.12.47838 S endSpace or RapidShare * USB Flash Drive with at least 2 GB capacity and LED indicator** SATA to USB adapter or desktop PC Toothpick or paperclip Preparing Hard Drives Preparing hard drives is the first step because you have to wipe all the data inside the hard drives and make them just like brand new. We used 2 x Seagate 2 TB 5900 RPM Drives. Backup any files if you have and then remove both disks from ix2-200 and attach them to SATA to USB adapter or your desktop PC's SATA port. Using ...
1 comentário
Leia mais

How to Fix sub-process /usr/bin/dpkg returned an error code (1)

Introduction The error message “Sub-process /usr/bin/dpkg returned an error code (1)” indicates a problem with the package installer. This can happen in Ubuntu after a failed software installation, or if the installer becomes corrupted. The key phrase in this error is /usr/bin/dpkg. This refers to the dpkg package installer for Linux. A package installer is an application that tracks software, updates, and dependencies. If it is damaged, any new software installation will cause this error message. We cover several possible solutions, from easily-solved and straightforward solutions to more complex processes. This guide will help you resolve the dpkg returned an error code 1 on an Ubuntu operating system. Prerequisites A user account with sudo privileges A terminal window/command-line ( Ctrl - Alt - T ) Options to Fix sub-process /usr/bin/dpkg returned an error code (1) Method 1: Reconfigure dpkg Database ...
Postar um comentário
Leia mais

Installing OpenVAS (GVM) on CentOS 7 (New Manual)

   This is a walkthough for installing and configuring OpenVAS (GVM) on CentOS 7. OpenVAS (Open Vulnerability Assessment System) is an opensource vulnerability scanner. Update 20April2019: Greenbone is deprecating OpenVAS version 9 and version 10 is now known as Greenbone Vulnerability Manager (GVM). Likewise, the new rpms are called ‘greenbone-vulnerability-manager’ and ‘gvm-libs’ which replace the ‘openvas’ and ‘openvas-libraries’ rpms. I f you are upgrading from 9 to the latest version, you may lose your previous tasks and reports so beware! Also, if you are still on version 9 and you simply need a temporary workaround for “Report outdated Scan Engine / Environment (local)” error, scroll to the bottom.  Brief History OpenVAS forked from Nessus when Tenable took the previously opensource product to closed source back in 2005. That’s worth mentioning primarily because on a side note, I’ve used Nessus for many years and I remember when it was forked. S...
1 comentário
Leia mais