Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Description

This article will explain how to customize and set network interfaces on Linux to run with CHARON. All commands are given as an example, configuration can be done using other tools.

If you use the Charon Linux Toolkit, you must set the ifcfg file name to match the network interface. Example: if the network interface name is "charon", the ifcfg file name must be "ifcfg-charon"

 

Related Linux distributions and versions: Red Hat 7 for management and CHARON dedicated interfaces, Red Hat 6 and Fedora 20+ for CHARON dedicated interfaces

Step-by-step guide

(blue star) The examples below assume the NetworkManager service is active.

Do not name the management interface "internet" (don't use this name to DEVICE and NAME parameters) because it will make the NIC not recognized.

In the examples below, we assume we have a server with 3 Network Interfaces Cards (NIC), 1 dedicated for management with static IP address and the 2 others for CHARON.

The management interface will be named "stromasys" and the 2 others will be named "charon_pluto" and "charon_nix".

At first step, we can see the 3 interfaces settings:

ifconfig command:

# ifconfig -a

ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        ether 00:0c:29:7e:b3:91  txqueuelen 1000  (Ethernet)

        RX packets 919  bytes 98295 (95.9 KiB)

        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

 

ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        ether 00:0c:29:7e:b3:9b  txqueuelen 1000  (Ethernet)

        RX packets 919  bytes 98295 (95.9 KiB)

        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

 

ens35: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        ether 00:0c:29:7e:b3:a5  txqueuelen 1000  (Ethernet)

        RX packets 919  bytes 98295 (95.9 KiB)

        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

 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 0  (Local Loopback)

        RX packets 650  bytes 55900 (54.5 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 650  bytes 55900 (54.5 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

nmcli command:

# nmcli con

NAME   UUID                                  TYPE            DEVICE

ens33  308df8bd-f8ca-4809-95ea-37f2535a84bb  802-3-ethernet  --    

ens34  20f68a8b-034e-4606-9f24-cffbd74f93fe  802-3-ethernet  --    

ens35  d84c3f9b-afa2-4b1f-9d59-86197ac42798  802-3-ethernet  --    

# nmcli dev

DEVICE  TYPE      STATE         CONNECTION

ens33   ethernet  disconnected  --        

ens34   ethernet  disconnected  --        

ens35   ethernet  disconnected  --        

lo      loopback  unmanaged     --

We will now rename the interface names, devices and will assign an IP address to the management NIC and set the 2 others to run with CHARON.

Move to the /etc/sysconfig/network-scripts folder and rename the ifcfg-ens33 file to ifcfg-stromasys for example

(info) We've decided to use ifcfg-ens33 because the content of that file shows the MAC address (HWADDR line) and it corresponds to the one we've decided to use

# cd /etc/sysconfig/network-scripts/

# ls ifcfg-*

ifcfg-ens33  ifcfg-ens34  ifcfg-ens35  ifcfg-lo

cat ifcfg-ens33

HWADDR=00:0C:29:7E:B3:91

TYPE=Ethernet

BOOTPROTO=dhcp

DEFROUTE=yes

PEERDNS=yes

PEERROUTES=yes

IPV4_FAILURE_FATAL=no

IPV6INIT=yes

IPV6_AUTOCONF=yes

IPV6_DEFROUTE=yes

IPV6_PEERDNS=yes

IPV6_PEERROUTES=yes

IPV6_FAILURE_FATAL=no

NAME=ens33

UUID=308df8bd-f8ca-4809-95ea-37f2535a84bb

ONBOOT=no

 

TO BE COMPLETED

Red Hat Enterprise Linux 6 - Interface Configuration Files (not necessary?)

Red Hat Enterprise Linux 7 - IP Networking

Fedora 20 - Networking Guide (not necessary?)

Readers/approval

  • Your approval is needed for this document 

  • No labels