> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-outside-emv/appendices/d-shell-branded-sites.md).

# D Shell Branded Sites

## Gilbarco Local Area Network Configuration

The LAN needs to be configured for Gilbarco CRIND. In the Gilbarco configuration, the Commander is the CLIENT and the Gilbarco CRIND is the SERVER. The Outdoor EMV DCR IP traffic must be routed from Commander through the network IP of 192.168.31.31. Depending on which device specific IP configuration is selected for the site. Device Specific network routes might need to be added.

{% hint style="danger" %} <img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FrLxiG7aos35lVjPFBygQ%2Fimage.png?alt=media&amp;token=e58fb688-2c37-4e28-a09a-5d6cff3d1a0e" alt="" data-size="line"> For Shell branded sites with two routers MNSP, see Shell Verifone Zone settings below. Follow the Isolated Payment NIC steps for Shell Single MNSP option.
{% endhint %}

### Isolated Payment NIC

1. In Configuration Client, navigate to Initial Setup > Local Area Network Configuration.
2. Select Isolated Payment NIC in Device Specific IP Configuration.
3. Verify if "Default Route" parameter is checked. If the parameter is checked then, continue to the next steps. If not checked, then skip to EPS Global Configuration Section.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FiLkrVpclR744jPULtuw2%2Fimage.png?alt=media&amp;token=ceb26de4-ea33-4ac1-8bd3-892561843dca" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Using the IP address entered in the EMV Parameter in DCR configuration, add a network destination route with the 4th octet (last) set to ZERO. i.e. 10.5.55.0. This should cover all the IP ranges from 10.5.55.1 through10.5.55.255.
{% endhint %}

If Default Route is checked, then add New Route Config to the Device Specific Routes per site.

* Route Type: Network
* EMV Parameter IP Address (Forecourt > DCR > DCR Position Attributes) with the 4th octet set to 0.
* Gateway: 192.168.31.31
* Netmask: 255.255.255.0

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FgNqaTAhTH2benLBiytQB%2Fimage.png?alt=media&amp;token=9505ea0a-ee8f-4ee9-9901-2edfb3bc5c78" alt=""><figcaption></figcaption></figure>

Save the configuration changes and reboot the site controller.

### Verifone Zone (Shell - Two router MNSP LAN Settings)

Verify if "Default Route" parameter is checked. If the parameter is checked then continue to next step.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/c13WTOhRPKqVrEvQUiMG/Unknown%20image)

## Wayne Local Area Network Configuration

{% hint style="info" %}
Verify Gateway IP addresses have been setup for EMV and the MNSP (Switch) Vendor has pushed the correct rules and polices.
{% endhint %}

The LAN is required to be configured for Wayne CAT. In the Wayne configuration, the Commander is the SERVER and the Wayne CAT is the CLIENT. The Outdoor EMV DCR IP traffic must be routed from the Commander through the Network IP Address 192.168.31.31. Depending on which Device Specific IP Configuration is selected for the site, Device Specific Network Routes may need to be added.

{% hint style="warning" %} <img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FylHtPyNXIW04kHWrWvdv%2Fimage.png?alt=media&amp;token=99e86615-c83a-4319-b4e4-655397688c7f" alt="" data-size="line"> For Shell branded sites with two routers MNSP, see Shell Verifone Zone settings below. Follow the Isolated Payment NIC steps for the Shell Single MNSP option.
{% endhint %}

### Isolated Payment NIC

1. In Configuration Client, navigate to Initial Setup > Local Area Network Configuration.
2. Click on Isolated Payment NIC in the Device Specific IP Configuration.
3. Verify if the "Default Route" parameter is checked. If the parameter is checked, then continue with the next steps. If not checked, then skip to the EPS Global Configuration Section.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FAcfrbYFjOJtDQm4XYoUU%2Fimage.png?alt=media&amp;token=52d28d76-9478-40aa-9bec-e4d730b1c7c9" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Using the Wayne DCR IP addresses, add a Network Destination Route with the 4th octet (last) set to ZERO. i.e. if the DCR IP addresses were 172.29.1.1. to 172.29.1.10, then the IP address used for this route would be 172.29.1.0.
{% endhint %}

If the Default Route is checked, then add New Route Config to the Device Specific Routes per site.

1. Route Type: Network
2. Enter in the IP address used for the DCRs with the last octet set to 0. See the note above for more details.
3. Gateway: 192.168.31.31
4. Netmask: 255.255.255.0

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/MuJi9zAdFmJDxzjfFndt/Unknown%20image)

Click Save and then reboot the Commander.

### Verifone Zone (Shell - Two router MNSP LAN Settings)

Verify if the "Default Route" parameter is checked. If the parameter is checked, then continue with the next section.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FT4D9PaQQUy3N92g0sPf8%2Fimage.png?alt=media&amp;token=2d23f2b0-e789-4210-95dc-ddbec336cac2" alt=""><figcaption></figcaption></figure>


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-outside-emv/appendices/d-shell-branded-sites.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.
