Ports and Protocols used by Pathfinder CorePro

Updated by Brett Patram

Scope

The Pathfinder CorePro routing appliance, a hardware and software product, uses various ports and protocols during normal operation. This HelpDoc provides a list of the ports and protocols commonly used by this product.

Ports and Protocols

It is not expected that all ports and protocols listed here will be in use. The usage of certain ports is heavily dependent on user configuration in the product

Port (Type)

Protocol

Inbound/Outbound

Used For

80 (TCP)

HTTP, WS

Both

CorePro Web Interface and web sockets

*CorePro listens on this port

*CorePro may connect outbound for websocket or RESTapi connections to other devices like Infinity Intercoms

8000(TCP)

WS

Inbound

CorePro web sockets used with user panels

*In 1.9.X and future 1.10.X this is merged into port 80/443

8001(TCP)

SA Metering

Inbound

Metering data (1.9.x and future 1.10.X)

*External or Internal (webUI only) exposure depending on security settings

*In 1.9.X and future 1.10.X this is merged into port 9501

443 (TCP)

HTTPS, WSS

Both

CoreProSecure Web Interface

*CorePro listens on this port (Requires proper certificate configuration)

*CorePro may connect outbound for websocket or RESTapi connections to other devices like Infinity Intercoms

9600(TCP)

SapV2

Inbound

CorePro API/Protocol

*External or internal only depending on security settings

9602(TCP)

SapV2

Inbound

CorePro API/Protocol TLS Encrypted

*Depending on security settings and properer certificate configuration

9501(TCP)

SA Metering

Inbound

Metering data

*External or Internal (webUI only) exposure depending on security settings

22(TCP)

SSH

Inbound

SSH

*Can be enabled or disabled. Not used for customer access

93(TCP)

LWRP

Both

Livewire Routing Protocol

*CorePro usually connects out to devices on this port.

*CorePro will also act as an LWRP server when its internal GPIO node is enabled

2055,2060 (UDP)

Livewire Multicast GPIO

Outbound 2055

Inbound 2060

Used with multicast group 239.192.255.4 for internal GPIO node if enabled

4001 (UDP)

Livewire Advertisement Protocol

Inbound

Used with multicast group 239.192.255.3, only when CorePro has auto-device discovery enabled

4010(TCP)

LWCP

Outbound

Livewire Control Protocol

*CorePro connects out to devices on this port

20518(TCP)

LWCP - VX Dialect

Outbound

Livewire Control Protocol for Telos VX products

*CorePro connects out to Telos VX products on this port

4040(TCP)

LWCP SS

Outbound

Livewire Control Protocol "SS"

*CorePro connects to to iQx/iQs/Altus/QOR products on this port

514(UDP)

Syslog

Outbound

CorePro syslog writer - if enabled (disabled by default)

Additional inbound and outbound TCP and UDP ports may be used when Device Emulators are created, as these allow the user to specify the desired Listener or Server ports


How did we do?