Skip to content
  • There are no suggestions because the search field is empty.

PourMyBeer Network Requirements

IP Scheme, Firewall, Wired Network Structure, Whitelists

The PourMyBev LAN is deployed in a configuration that requires minimum setup. However; in some cases our customers choose to use a “Self Managed” (SM) or “Third Party Service
Provider” (TPSP) to configure, manage, and maintain their system’s security protocols. PourMyBev recommends the following requirements when setting up the LAN through an SM or TPSP.

IP Scheme


● PourMyBev operates on the 192.168.2.101 - 254 network. Make sure this range is reserved for Pour My Beer.
● The Server is designated 192.168.2.254
● The Charger client(s) are designated to count backwards from .254 (example, 192.168.2.253 for Charger 1)
● The UI Clients are designated 192.168.2.101
● Subnet 255.255.255.0 for the entire network

Firewalls & Whitelist


All ports must be open for unrestricted access as defined in the table below. Please ensure these are applied to both UDP and TCP protocols.

Source            (IP or FQDN)

Destination                  (IP or FQDN)

Port Protocol Direction Description / Purpose
localhost / PourMyBev
Server
  80, 443 TCP/UDP outbound PourMyBeer Server needs access to
internet
TeamViewer

master*.teamviewer.com

router*.teamviewer.com

5938 TCP+UDP, 443 TCP, 80 TCP

TCP/UDP

outbound TeamViewer needed for
remote support
PourMyBev POS Integration FTP 50.19.192.181 20, 21, 22 TCP inbound / outbound FTP file hosting
endpoint for POS
integration setup,
monitoring, and automated upgrades
PourMyBev POS Integration  40.122.110.154  80, 443 TCP inbound / outbound POS Integration Support & Monitoring 
PourMyBev POS Integration  40.117.34.242 9200 TCP outbound Elastic Search cloud data
storage to backup card
info POS integration
PourMyBev BKG Reporting Portal

bkg.isogentdev.com

bkg.pourmybeer.com

216.24.158.183

80, 443 TCP outbound Client web based reporting portal
localhost / PourMyBev
Server IP
smtp.gmail.com 465 TCP outbound Optional keg management email alerts
localhost / PourMyBev
Server IP
business.untappd.com 80, 443 TCP outbound Client web based reporting portal

 

Wired Network Structure

The PourMyBev system runs off its own dedicated LAN (Local Area Network). The following Cat6 Runs must be made before scheduling your PourMyBev installation.

From Switch to each beer screen: 1 per screen
From Switch to each check-in station: 1 per check-in unit (aka charger)
From Switch to PourMyBev server: 1 Total
Ethernet from customer supplied router to PourMyBev server: 1 total

This is a closed loop system, meaning all runs are separate from the Point of Sale system. 
All runs must be terminated, tested, and labeled Cat6 with MaleRJ45 ends and wired according to TIA/EIA-568B. 

In the event a patch panel is used at your location the customer is responsible for all Cat6 data connections between the patch panel and the screens, check-in terminals, and server.

Network-1

 

Physically separated Local Area Network (LAN)
PourMyBev recommends the PourMyBev Network should be on it’s own segregated network and does NOT share any connections with any other LANS or VLANS. In an ideal deployment, the Server, Chargers, Switch, and UI Screen Clients should all be on the same LAN.
Non-PourMyBev devices should not be riding on this network.


Virtual Local Area Network (VLAN)
In the event the PourMyBev Network cannot be segregated from “other” networks we specify the following requirements.
● VLAN setup for PourMyBev separate from all other networks.
● VLAN should have the scheme 192.168.2.101 - 254
● A minimum of 1 Ethernet port matched to this VLAN for every IP device on the network.
● PourMyBev devices ONLY on this network

Internet Requirements

PourMyBev requires a hard-line ethernet connection at the location of the PourMyBev Server. Internet speeds should be a minimum of 100 Mbps download and 100 Mbps upload.

In addition to the above, it is recommended if at all possible to give prioritization (QoS) to PourMyBev network traffic. Your guest wireless network should also be capped or throttled to prevent your bandwidth from being completely used up during peak times with customers streaming. For high volume locations, a backup ISP connection if available as a failover will keep operations running if the primary connection fails. 


Self Managed & Third Party Service Provider Network Checklist

Wired Network Yes No
All Network cabling is at least CAT6.    
All Network cabling ends are terminated according to the TIA/EIA-568B
wiring standard.
   
All Clients on the PourMyBev LAN have at least one Network drop per
client.
   
All Network Cables have been Identified and labeled.    
All Network Cables have been tested and confirmed to be working.    
At least one Ethernet port for the PourMyBev LAN.    
Wireless Network    
Upload speeds of at least 100 mb/s.    
Download speeds of at least 100 mb/s.    
IP Schema    
The range of 192.168.2.101 - 254 has been reserved for PourMyBev.    
If using a different range, has this reserved range been communicated to the PourMyBev Installation Coordinator?    
Firewalls & Whitelisting    
The router is providing unrestricted outbound access to ports 80 & 443?    
The router is providing unrestricted outbound access to ports 465, 5938,
9200?
   
The router is providing unrestricted inbound & outbound access to ports 20, 21, and 22?