Skip to main content

Initial Settings : Network Settings

[1]. Set static IP address to the server.

( Replace the interface name [ens2] to your own one because it's not the same on any System )

# if you did not set Host Name during installation, set it like follows

[root@localhost ~]# hostnamectl set-hostname dlp.srv.world

# display devices

[root@localhost ~]# nmcli device

DEVICE  TYPE      STATE      CONNECTION

ens2    ethernet  connected  ens2

lo      loopback  unmanaged  --


# set IPv4 address

[root@localhost ~]# nmcli connection modify ens2 ipv4.addresses 10.0.0.30/24

# set gateway

[root@localhost ~]# nmcli connection modify ens2 ipv4.gateway 10.0.0.1

# set DNS

[root@localhost ~]# nmcli connection modify ens2 ipv4.dns 10.0.0.1

# set manual for static setting (it's [auto] for DHCP)

[root@localhost ~]# nmcli connection modify ens2 ipv4.method manual

# restart the interface to reload settings

[root@localhost ~]# nmcli connection down ens2; nmcli connection up ens2

Connection 'ens2' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/1)

Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2)


# show settings

[root@localhost ~]# nmcli device show ens2

GENERAL.DEVICE:                         ens2

GENERAL.TYPE:                           ethernet

GENERAL.HWADDR:                         52:54:00:D0:8F:0B

GENERAL.MTU:                            1500

GENERAL.STATE:                          100 (connected)

GENERAL.CONNECTION:                     ens2

GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveC>

WIRED-PROPERTIES.CARRIER:               on

IP4.ADDRESS[1]:                         10.0.0.30/24

IP4.GATEWAY:                            10.0.0.1

IP4.ROUTE[1]:                           dst = 10.0.0.0/24, nh = 0.0.0.0, mt = 1>

IP4.ROUTE[2]:                           dst = 0.0.0.0/0, nh = 10.0.0.1, mt = 100

IP4.DNS[1]:                             10.0.0.10

IP6.ADDRESS[1]:                         fe80::5054:ff:fed0:8f0b/64

IP6.GATEWAY:                            --

IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 100

IP6.ROUTE[2]:                           dst = ff00::/8, nh = ::, mt = 256, tabl>


# show state

[root@localhost ~]# ip addr show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: ens2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

    link/ether 52:54:00:d0:8f:0b brd ff:ff:ff:ff:ff:ff

    inet 10.0.0.30/24 brd 10.0.0.255 scope global noprefixroute ens2

       valid_lft forever preferred_lft forever

    inet6 fe80::5054:ff:fed0:8f0b/64 scope link noprefixroute

       valid_lft forever preferred_lft forever

[2]. If you don't need IPv6, it's possible to disable it like follows.

[root@localhost ~]# vi /etc/default/grub

# line 7: add

GRUB_CMDLINE_LINUX="ipv6.disable=1 resume=/dev/mapper/fedora-swap.....

# apply changes

[root@localhost ~]# grub2-mkconfig -o /boot/grub2/grub.cfg

Generating grub configuration file ...

done

[root@localhost ~]# reboot

[root@localhost ~]# ip addr show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

2: ens2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

    link/ether 52:54:00:d0:8f:0b brd ff:ff:ff:ff:ff:ff

    inet 10.0.0.30/24 brd 10.0.0.255 scope global noprefixroute ens2

       valid_lft forever preferred_lft forever 

Comments

Post a Comment

Popular posts from this blog

Lambda Function with Amazon SNS

  Amazon SNS is a service used for push notification. In this chapter, we will explain working of AWS Lambda and Amazon SNS with the help of an example where will perform the following actions − Create Topic in SNS Service and use AWS Lambda Add Topics to CloudWatch Send SNS text message on phone number given. Requisites To create Topic in SNS Service and use AWS Lambda Add Topics to CloudWatch, we need not follow the steps given below − Create Topic in SNS Create Role for permission in IAM Create AWS Lambda Function Publish to topic to activate trigger Check the message details in CloudWatch service. To send SNS text message on phone number given, we need to do the following − Add code in AWS Lambda to send message to your phone. Example In this example, we will create a topic in SNS. When details are entered in the topic to publish, AWS Lambda is triggered. The topic details are logged in CloudWatch and a message is sent on phone by AWS Lambda. Here is a basic block diagram which...
Post a Comment
Read more

Building the Lambda Function

AWS Lambda function executes a code when it is invoked. This chapter discusses all these steps involved in the life cycle of AWS Lambda function in detail. Steps for Building a Lambda function The lifecycle of Lambda function includes four necessary steps − Authoring Deploying Monitoring Troubleshooting Authoring Lambda Code AWS Lambda function code can be written in following languages − NodeJS Java, Python C# Go. We can write code for AWS Lambda using the AWS console, AWS CLI, from Eclipse IDE, from Visual Studio IDE, serverless framework etc. The following table shows a list of languages and the different tools and IDE that can be used to write the Lambda function −   NodeJS :  AWS Lambda Console | Visual Studio IDE Java : Eclipse IDE Python : AWS Lambda Console C# : Visual Studio IDE | .NET core Go : AWS Lambda Console Deploying Lambda Code Once you decide the language you want to write the Lambda function, there are two ways to deploy the code − Directly write the code in...
Post a Comment
Read more

Lambda Function with Amazon DynamoDB

DynamoDB can trigger AWS Lambda when the data in added to the tables, updated or deleted. In this chapter, we will work on a simple example that will add items to the DynamoDB table and AWS Lambda which will read the data and send mail with the data added. Requisites To use Amazon DB and AWS Lambda, we need to follow the steps as shown below − Create a table in DynamoDB with primary key Create a role which will have permission to work with DynamoDBand AWS Lambda. Create function in AWS Lambda AWS Lambda Trigger to send mail Add data in DynamoDB Let us discuss each of this step in detail. Example We are going to work out on following example which shows the basic interaction between DynamoDB and AWS Lambda. This example will help you to understand the following operations − Creating a table called customer in Dynamodb table and how to enter data in that table. Triggering AWS Lambda function once the data is entered and sending mail using Amazon SES service. The basic block diagram that ...
Post a Comment
Read more