# Why kernel parameter was changed when I installed ElasticSearch 7.X via 'yum install'

**URL:** <https://discuss.elastic.co/t/why-kernel-parameter-was-changed-when-i-installed-elasticsearch-7-x-via-yum-install/182839>\
**Category:** Elasticsearch\
**Created:** [May 27, 2019, 5:45am UTC](https://discuss.elastic.co/t/why-kernel-parameter-was-changed-when-i-installed-elasticsearch-7-x-via-yum-install/182839 "2019-05-27T05:45:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![homi.e](https://avatars.discourse-cdn.com/v4/letter/h/cdc98d/32.png) [@homi.e](https://discuss.elastic.co/u/homi.e)\
**Post date:** [May 27, 2019, 5:45am UTC](https://discuss.elastic.co/t/why-kernel-parameter-was-changed-when-i-installed-elasticsearch-7-x-via-yum-install/182839/1 "2019-05-27T05:45:39Z")

</div>

In my project, some servers used kernel parameter(net.ipv4.conf.all.rp\_filter=0) for network architecture.

When I installed ElasticSearch 7.X via 'yum install elasticsearch', That kernel parameter was also changed 0 =\> 1. Is there reason for this to change??

`Before Install`  
# rpm -qa | grep elasticsearch  
# sysctl -a | grep net.ipv4.conf.all.rp\_filter  
net.ipv4.conf.all.rp\_filter = 0

`Install & After Install`  
# yum install -y elasticsearch  
# rpm -qa | grep elasticsearch  
elasticsearch-7.1.0-1.x86\_64  
# sysctl -a | grep net.ipv4.conf.all.rp\_filter  
net.ipv4.conf.all.rp\_filter = 1

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 24, 2019, 5:45am UTC](https://discuss.elastic.co/t/why-kernel-parameter-was-changed-when-i-installed-elasticsearch-7-x-via-yum-install/182839/2 "2019-06-24T05:45:49Z")

</div>

Closed on June 24, 2019, 5:45am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.