Firewall ports: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
== Solution == | == Solution == | ||
Please remember that Pulse, Software nPoint and Hardware nPoint are | Please remember that Pulse, Software nPoint and Hardware nPoint are communication the same way. | ||
=== Inbound nGeniusPULSE server === | === Inbound nGeniusPULSE server === | ||
| Line 10: | Line 10: | ||
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;" | {| border="1" cellpadding="1" cellspacing="1" style="width: 500px;" | ||
|- | |- | ||
! scope="col" | destination | ! scope="col" | destination | ||
! scope="col" | service | ! scope="col" | service | ||
! scope="col" | role | ! scope="col" | role | ||
| Line 49: | Line 49: | ||
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;" | {| border="1" cellpadding="1" cellspacing="1" style="width: 500px;" | ||
|- | |- | ||
! scope="col" | destination | ! scope="col" | destination | ||
! scope="col" | service | ! scope="col" | service | ||
! scope="col" | role | ! scope="col" | role | ||
| Line 67: | Line 67: | ||
|- | |- | ||
| ip protocol #1 | | ip protocol #1 type 0 and 8 | ||
| icmp | | icmp echo request/reply | ||
| ping monitorred devices | | ping monitorred devices | ||
|} | |} | ||
| Line 76: | Line 76: | ||
| | ||
Inbound nPoint | === Inbound nPoint === | ||
| {| border="1" cellpadding="1" cellspacing="1" style="width: 500px;" | ||
|- | |||
! scope="col" | destination | |||
! scope="col" | service | |||
! scope="col" | role | |||
|- | |||
| | |||
| | |||
| | |||
|- | |||
| | |||
| | |||
| | |||
|} | |||
=== === | |||
=== Outbound nPoint === | |||
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;" | |||
|- | |||
! scope="col" | destination | |||
! scope="col" | service | |||
! scope="col" | role | |||
|- | |||
| | |||
| | |||
| | |||
|- | |||
| | |||
| | |||
| | |||
|} | |||
(*) outbound services are depending on the features that are in use. | (*) outbound services are depending on the features that are in use. | ||
Revision as of 15:28, 21 July 2018
Introduction
Solution
Please remember that Pulse, Software nPoint and Hardware nPoint are communication the same way.
Inbound nGeniusPULSE server
| destination | service | role |
|---|---|---|
| tcp/8443 | https | communication with nGeniusONE |
| tcp/443 | https |
secure web UI communication with nPoint |
| tcp/80 | http | web UI |
| udp/514 | syslog | syslog receiver |
| tcp/22 | ssh | CLI |
| udp/123 | ntp | network time server |
Outbound nGeniusPULSE server*
| destination | service | role |
|---|---|---|
| udp/123 | ntp | network time synchronozation |
| udp/161 | snmp | snmp |
| tcp/443 | https |
communication with virtual center and wireless controller |
| ip protocol #1 type 0 and 8 | icmp echo request/reply | ping monitorred devices |
(*) outbound services are depending on the features that are in use.
Inbound nPoint
| destination | service | role |
|---|---|---|
Outbound nPoint
| destination | service | role |
|---|---|---|
(*) outbound services are depending on the features that are in use.