Firewall ports: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 93: | Line 93: | ||
|} | |} | ||
| |||
=== Outbound nPoint* === | === Outbound nPoint* === | ||
Line 106: | Line 106: | ||
| https | | https | ||
| communication with nPoint | | communication with nPoint | ||
|} | |} | ||
Revision as of 15:32, 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 |
---|---|---|
tcp/80 | http | web UI |
tcp/22 | ssh | CLI when enabled |
Outbound nPoint*
destination | service | role |
---|---|---|
tcp/443 | https | communication with nPoint |
(*) outbound services are heavily depending on the Service Test that are configured on nGeniusPULSE.