TruView Firewall ports: Difference between revisions

From wiki.comcert.com
Jump to navigation Jump to search
No edit summary
No edit summary
Line 16: Line 16:
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
|-
| style="width: 126px;" | '''role'''
| style="width: 126px;" | '''destination'''
| style="width: 134px;" | '''port'''
| style="width: 134px;" | '''service'''
| style="width: 224px;" | '''service'''
| style="width: 224px;" | '''role'''
|-
|-
| style="width: 126px;" |  
| style="width: 126px;" | tcp/443
| style="width: 134px;" |  
| style="width: 134px;" | https
| style="width: 224px;" |  
| style="width: 224px;" | User Portal
|-
|-
| style="width: 126px;" |  
| style="width: 126px;" | tcp/22
| style="width: 134px;" |  
| style="width: 134px;" | ssh
| style="width: 224px;" |  
| style="width: 224px;" | Management CLI
|}
|}


Line 33: Line 33:
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
|-
| '''role'''
| style="width: 124px;" | '''destination'''
| '''port'''
| style="width: 136px;" | '''service'''
| '''service'''
| style="width: 223px;" | '''role'''
|-
|-
|  
| style="width: 124px;" | udp/53
|  
| style="width: 136px;" | dns
|  
| style="width: 223px;" |  
|-
|-
|  
| style="width: 124px;" | tcp/389,tcp/636
|  
| style="width: 136px;" | ldap
|  
| style="width: 223px;" |  
|-
|-
|  
| style="width: 124px;" | udp/123
|  
| style="width: 136px;" | ntp
|  
| style="width: 223px;" |  
|-
|-
|  
| style="width: 124px;" | udp/161
|  
| style="width: 136px;" | snmp
|  
| style="width: 223px;" |  
|}
|}


Line 58: Line 58:
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
|-
| '''role'''
| '''destination'''
| '''port'''
| style="width: 83px;" | '''service'''
| '''service'''
| style="width: 163px;" | '''role'''
|-
|-
|  
| tcp/443
|  
| style="width: 83px;" | https
|  
| style="width: 163px;" | User Portal
|-
|-
|  
| tcp/22
|  
| style="width: 83px;" | ssh
|  
| style="width: 163px;" | Management CLI
|-
|-
|  
| udp/2055, udp/6343
|  
| style="width: 83px;" | netflow
|  
| style="width: 163px;" |  
|}
|}


Line 79: Line 79:
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
|-
| '''destination'''
| '''service'''
| '''role'''
| '''role'''
| '''port'''
| '''service'''
|-
|-
|  
| udp/53
|  
| dns
|  
|  
|-
|-
|  
| udp/123
|  
| ntp
|  
|  
|-
|-
|  
| udp/161
|  
| snmp
|  
|  
|}
|}

Revision as of 20:20, 18 November 2019

Introduction

Please remember that Pulse, Software nPoint and Hardware nPoint are communication the same way.

In general, nPoint is contacting the nGeniusPULSE Server, not the other way around.

Service Test are executed by the nPoint. Device monitoring is done by nGeniusPULSE server or a Collector.

Even when there's no Service Test running on the nPoint, the nPoint will contact nGeniusPULSE Server every minute to update its configuration.

Solution

TVC inbound

destination service role
tcp/443 https User Portal
tcp/22 ssh Management CLI

TVC outbound

destination service role
udp/53 dns  
tcp/389,tcp/636 ldap  
udp/123 ntp  
udp/161 snmp  

TVF inbound

destination service role
tcp/443 https User Portal
tcp/22 ssh Management CLI
udp/2055, udp/6343 netflow  

TVF outbound

destination service role
udp/53 dns  
udp/123 ntp  
udp/161 snmp