Revel Networking Guidelines

By Troy | Updated


Revel provides its clients a pre-configured, turn-key system which includes a router, switches, access points, etc. in addition to the Point of Sale stations and their peripherals.

Revel understands that, in some situations, our clients may already operate a network and it makes sense for them to leverage that infrastructure for their Revel Point of Sale system.

While Revel cannot directly support these custom configurations, we do want to see our clients succeed by leveraging their own infrastructure or by working with a third party infrastructure provider. This document outlines how to configure a network suitable for Revel’s Point of Sale in a way that facilitates simple and reliable operation.



The network should be provisioned as a /24 subnet and not use VLAN tagging. While larger or classless subnets may work, it is strongly recommended to use a Class C network. Configure your network to have its first usable IP address to be its default router address. There should be one network provisioned per establishment.

Reserve a portion of your IP address range for DHCP clients. These can be used for access points and computers used to perform troubleshooting. During normal operations, there should be no non-essential devices on the network.

All devices and peripherals, including iPads and printers, should be statically configured and not use DHCP where it can be avoided. For devices that do not support static configuration, use DHCP reservations.

Here is the configuration Revel uses when configuring networks for its clients:

Typical Revel Network Configuration


Netmask (/24)

Default Router

DNS Servers,

DHCP Range -

The IP addresses of all network devices in the establishment must correspond with what is registered in the Revel Back End for those devices.


There must be no restriction to communication between devices on the Revel network. Avoid any use of traffic shaping, Quality of Service (QoS), or other services that may inspect or alter traffic on the local network.

All communication with the Revel Back End originates from within the local network, so no access is needed into the network from the Internet.

Wireless access points should be configured in bridge mode, and not employ any network address translation (NAT), tunneling, or VLAN tagging. The SSID should be hidden and use WPA2 encryption. Revel recommends using the 5GHz band with a 20MHz channel width to ensure fast and robust connections. Wireless devices should have a signal-to-noise (SNR) ratio of 25dB or better for optimal transmission.

Revel recommends at least 1.5 megabits/sec dedicated bandwidth, both upload and download. For 3-5 terminals, 6 megabits/sec is recommended.

The network should be wired with Category 5E or better network cabling. Do not secure cables with staples or tight tie-straps. Velcro straps can secure cables without damaging them, while allowing for changes later.

Summary of Connectivity Requirements


Inbound: None.
Outbound: Unfiltered Internet access.
Avoid VLAN tagging, traffic shaping, non-essential network devices.

Wired LAN

Category 5E or better cabling.
Do not crimp or damage cabling.
Clearly label Ethernet ports used for Revel.

Wireless LAN (802.11)

Hidden SSID. Prefer 5GHz, 20MHz width. Use WPA2 encryption.

Internet Bandwidth

1-2 terminals: minimum 1.5Mbit/sec up and down. 3-5 terminals: minimum 6.0Mbit/sec up and down.

Restrictive Networks

There may be cases where you are required to restrict outbound network traffic. The following table of services, protocols and ports, and IP addresses can be used as a guide when formulating your firewall configuration.

Proceed with caution, as blocking outbound connections can interfere with the operation of your Point of Sale.

Core Functionality


Protocol (Port)

Host / IP Addresses

Domain Name Lookups


Time Synchronization

NTP (UDP 123)

Email delivery of Receipts and Invoices

SMTP (TCP 3535)

Revel Back End

HTTPS (TCP 443) (Primary) (Secondary) (Alternate Site)

Revel Identity Service


Crash Reporting, Support


RevelGuard Services

HTTPS (TCP 443) (may change)

TCP 1668 (may change)

TCP 8000 (may change)

iPad Communication

TCP 52387

POS to KDS, CDS stations

UDP 52388

KDS, CDS to POS stations

  • RevelGuard monitor service hostname may change as it is provisioned.
  • These port numbers are the default but they can by changed in the management console.

Third-party Integrations:


Protocol (Port)

Host / IP Addresses





See Stripe IP Addresses




Providing a basic network configuration reference for your on-site manager can help reduce errors when replacing or adding devices to the network. End users of the Revel Point of Sale should first consult with their on-site manager or IT staff before making any changes, including iPad configuration or moving Ethernet cables from one port to another. Where Revel is installed in multi-tenant facilities, be sure to clearly label which Ethernet ports are configured for Revel.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Want to request a new feature? Click here!
Still have questions? Contact our friendly Support team