> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/how-to/persist-default-route-configuration-with-multiple-interfaces.md).

# How To Persist The Default Gateway Configuration in Case of Multiple Interfaces?

## Problem

How to persist the default gateway configuration in case of multiple interfaces attached to a system?

## Environment

* Platform9 Managed OpenStack - All Versions
* CentOS 7.x

## Procedure

1. By default the system will prefer the gateway of the latest interface that was brought online. If the gateway is defined for all the interfaces in the interface config file, add the option of DEFROUTE=yes for the interface whose gateway should be used for preferred network communication.

{% tabs %}
{% tab title="None" %}

```none
$ less /etc/sysconfig/network-scripts/ifcfg-eth1

DEFROUTE=yes
```

{% endtab %}
{% endtabs %}

## Additional Information

Alternative way is to set DEFROUTE=no in all other interface configuration except for the interface which we want to use by default for all communication.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/how-to/persist-default-route-configuration-with-multiple-interfaces.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.