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

C++ How to use Date and Time

The C++ standard library does not provide a proper date type. C++ inherits the structs and functions for date and time manipulation from C. To access date and time related functions and structures, you would need to include <ctime> header file in your C++ program. There are four time-related types: clock_t, time_t, size_t , and tm . The types clock_t, size_t and time_t are capable of representing the system time and date as some sort of integer. The structure type tm holds the date and time in the form of a C structure having the following elements: struct tm { int tm_sec ; // seconds of minutes from 0 to 61 int tm_min ; // minutes of hour from 0 to 59 int tm_hour ; // hours of day from 0 to 24 int tm_mday ; // day of month from 1 to 31 int tm_mon ; // month of year from 0 to 11 int tm_year ; // year since 1900 int tm_wday ; // days since sunday int tm_yday ; // days since January 1st int tm_isdst ; // hours of daylight savin...
Post a Comment
Read more

C++ References

A reference variable is an alias, that is, another name for an already existing variable. Once a reference is initialized with a variable, either the variable name or the reference name may be used to refer to the variable. C++ References vs Pointers: References are often confused with pointers but three major differences between references and pointers are: You cannot have NULL references. You must always be able to assume that a reference is connected to a legitimate piece of storage. Once a reference is initialized to an object, it cannot be changed to refer to another object. Pointers can be pointed to another object at any time. A reference must be initialized when it is created. Pointers can be initialized at any time. Creating References in C++: Think of a variable name as a label attached to the variable's location in memory. You can then think of a reference as a second label attached to that memory location. Therefore, you can access the contents of the variabl...
Post a Comment
Read more

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