> For the complete documentation index, see [llms.txt](https://learn.netmaker.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.netmaker.io/help-articles/the-guide-for-opnsense-integration-doesnt-work.md).

# The Guide for OPNsense Integration Doesn't Work

{% hint style="info" %}
Note: The documentation page has been updated and should have the complete instructions for integrating OPNsense with Netmaker. Please see the doc page here: <https://docs.netmaker.io/docs/how-to-guides/integrating-non-native-devices>
{% endhint %}

Issue:

There's something missing in the guide for OPNsense integration. I followed all the steps carefully but still nodes from my Netmaker network can't reach the egress ranges I've specified on the Client Config, and vice versa.

![screenshot](https://downloads.intercomcdn.com/i/o/989334071/9232066a26398af9c4fa0fce/image.png?expires=1769018400\&signature=9451ae827702a378868aca2988bc94e0a3b49b8622ff3e69298aa1244740fa09\&req=fSguFcp6nYZeFb4f3HP0gH58p%2B6wKH0OvkuM71hVPNsK90JCWpGUyzVs8BlV%0AexmOtPmFGH4j6RoK6g%3D%3D%0A)

Resolution:

It is missing a couple of steps which will be added in the documentation soon. You need to add a routing entry in order for the two networks to reach each other.

{% stepper %}
{% step %}

### Create a gateway

Go to System -> Gateways -> Configuration, then click on the add icon and specify the tunnel interface and its IP, similar to the image below:

![add gateway](https://downloads.intercomcdn.com/i/o/989334782/7ff98c97684189c9cfa8fe95/integration-opnsense-add-gw.jpg?expires=1769018400\&signature=57daadbf387bd778ae9b3eec7ec4c117c0d2ba61db3e17352b501d88c0684a6b\&req=fSguFcp6moldFb4f3HP0gFNYhbXlYJUZhrYLpJtUUIz1QEzS3VQ2WH%2BoB330%0ApaY%3D%0A)
{% endstep %}

{% step %}

### Add the routing entry

Go to System -> Routes -> Configuration, then click on the add icon and specify a route to the Netmaker network via the gateway created in the previous step:

![add routing entry](https://downloads.intercomcdn.com/i/o/989328731/ac9bab1e3e64d03e35b7a490/integration-opnsense-add-routing-entry.jpg?expires=1769018400\&signature=f1941090b59e510ea31f6670c9558cedea36b6cbbed59572692a192c485bfd5f\&req=fSguFct2moJeFb4f3HP0gH5hc9%2BEbR61eDUxxUmXaxhT7S5C7hmyMK0IwEgz%0AAcWiDs%2FnRnBy2N0%2BGQ%3D%3D%0A)
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.netmaker.io/help-articles/the-guide-for-opnsense-integration-doesnt-work.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
