31
How to Install the ISONAS PureIP Reader-controller
Firewall Configuration Recommendations
The reader controllers communicate on port 55533.
If Intrusion Detection and Prevention is enabled, double check the firewall
logs for dropped packets with a source IP that matches a reader-controller
and create bypass rules as needed.
A firewall egress rule allowing the IP’s of the reader-controllers is required.
Note: the devices do not proxy.
Recommendation: Create a group for the reader-controller IPs and apply the
group to a rule to allow 55533 to communicate with
isonaspureaccesscloud.com (IP 52.40.147.42). Both UPD and TCP should be
allowed to pass.
DHCP Configuration
If the reader-controllers are to be left on DHCP it is strongly recommended to
use reservations, so the IP address does not need to be renewed.
Network Configuration
A common best-practice is to place the reader-controllers in a dedicated
subnet
The POE switch should have enough power to run all ports and account for in
rush. (IE. A switch restart which would cause all readers to restart).
Pure IP Reader-Controllers to PureAccess-Manager Software:
Some locations may have a version of PureAccess installed on a local server. The software
package that is designed for such on-site installation is named: PureAccess-Manager.
These installations will require that the reader-controller’s configuration be modified to
direct the reader to connect to the local server’s location.
ISONAS can provide a simple utility, that can be used to redirect the reader-controllers to
the local instance of PureAccess-Manager.
Addressing:
The recommended best-practices is to let the local network’s DHCP service assign the IP
Address to each reader.
As an alternate, you can manually assign the reader’s IP Address. To allow the reader to
successfully reach the host software, the following setting are typically required:
Static IP Address that is valid on the local subnetwork
Proper Subnet Mask
IP Address of the local subnetwork’s gateway.
DNS server’s IP Address
