Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Why "net.ipv4.neigh.default.*" parameter settings does not take effect on interfaces after a reboot?

Solution Verified - Updated 2014-12-18T06:37:30+00:00 -

Issue

While trying to set "net.ipv4.neigh.default.*" values for the interfaces, the changes does not get applied to all interfaces if set via sysctl.conf or rebooting the host.
We could see that only bond devices gets the newly applied values while all other physical (non-bonded) interfaces still reflects the old values.
Why does this happen?

Environment

Red Hat Enterprise Linux (RHEL) 6.5 and earlier
Red Hat Enterprise Linux (RHEL) 5 (all versions)
Kernel parameters for tuning network subsystem

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)