> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/connectivity/configuration/power-options-for-outdoor-gateways/use-a-poe-switch-with-outdoor-gateways.md).

# Use a PoE Switch with Outdoor Gateways

Use a PoE Switch with outdoor gateways to increase the power and number of ports for downstream devices

You can use a PoE switch with the outdoor gateway to increase power and/or the number of ports available to downstream devices, such as Verkada cameras. We recommend following this topology:

<div align="left" data-with-frame="true"><img src="https://1814166542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAGnzScvko5PkG7YBy3i%2Fuploads%2Fgit-blob-45e0d56f902440ee51e4526dde77868dfaa43ac3%2F2be38605698bb41881c927171fe751276d354ea0.png?alt=media" alt=""></div>

In this topology, the customer-provided PoE switch supplies power to the gateway’s PoE In port and receives data from the same port. To enable this setup, you need to change the PoE **In** port configuration to LAN.

***

### Change PoE In port configuration to LAN

{% hint style="warning" %}
This configuration is only available on outdoor gateways.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Gateways.**
{% endstep %}

{% step %}
**Select the gateway you want to configure.**
{% endstep %}

{% step %}
**In the top right, click Settings.**
{% endstep %}

{% step %}
**Under Network > Connection, select Local Area Network (LAN).**

<div align="left" data-with-frame="true"><img src="https://1814166542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAGnzScvko5PkG7YBy3i%2Fuploads%2Fgit-blob-530d02c5c3701bd87237fbc9c88a1c2d96e72231%2Faa4919508c82e5db6888019937dc7a782db7c34f.png?alt=media" alt="" width="435"></div>

{% hint style="warning" %}
The PoE IN port on the outdoor gateways is set to WAN by default.
{% endhint %}
{% endstep %}

{% step %}
**Click Apply, then Confirm to save.**
{% 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/connectivity/configuration/power-options-for-outdoor-gateways/use-a-poe-switch-with-outdoor-gateways.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 `build a script that syncs our docs to a CMS` 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.