The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click here for more information.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

RN150 Internet access requirements

aaaaaa
By
Level 6

May I know what each Internet connection requirement of RN150 using for? If we use FlexDeploy,  will these connection requirements the same or I can remove some of them?

Internet access (TCP Port 443)

TCP Port 443 outbound to the following:

• orchestration.riscnetworks.com ( 34.192.184.110, 34.192.195.90 )
• initial.riscnetworks.com ( 34.192.43.78, 34.192.198.28 )
• dataup.riscnetworks.com ( 34.192.12.37, 34.192.197.132 )
• app3.riscnetworks.com (34.192.198.73 )
• Backup & Growth ( 34.192.99.153, 34.192.185.36 )
Internet access (UDP Port 123)

UDP Port 123 outbound to the following:

• ntp.riscnetworks.com ( 3.231.5.12, 18.204.38.15 )

(1) Solution

joemigliore
By
Flexera Alumni

Dataup.riscnetworks.com ( 34.192.12.37, 34.192.197.132 ) is not required for the FDP, only the RN150 requires this in the case of SaaS deployments.

Backup & Growth ( 34.192.99.153, 34.192.185.36 )  is not currently utilized by either appliance and can be excluded.

Ntp.riscnetworks.com ( 3.231.5.12, 18.204.38.15 ) is optional on both appliances; you can instead use an internal NTP server by allowing UDP:123 and specifying the NTP server IP address in the Interface section on the dashboard of both appliances.

The remaining URLs are used for things like authentication, device updates, license verification, Command and Control, etc. and are required.

 

 

View solution in original post

(5) Replies

joemigliore
By
Flexera Alumni

Dataup.riscnetworks.com ( 34.192.12.37, 34.192.197.132 ) is not required for the FDP, only the RN150 requires this in the case of SaaS deployments.

Backup & Growth ( 34.192.99.153, 34.192.185.36 )  is not currently utilized by either appliance and can be excluded.

Ntp.riscnetworks.com ( 3.231.5.12, 18.204.38.15 ) is optional on both appliances; you can instead use an internal NTP server by allowing UDP:123 and specifying the NTP server IP address in the Interface section on the dashboard of both appliances.

The remaining URLs are used for things like authentication, device updates, license verification, Command and Control, etc. and are required.

 

 

Hello @joemigliore ,

 

Could you let me know exactly what data will be sent to RISC Network cloud? Ex: authentication data, appliance status,...

 

Thanks,

https://orchestration.riscnetworks.com
- Coarse licensing / entitlement
- User authentication / privilege checks
- Scheduling/pickup of (RN150 data) aggregation jobs
- Reporting success/failure of said aggregation jobs
- Scheduling/pickup of pending user report requests
- Pickup of job to initiate support-level debugging session

 

https://initial.riscnetworks.com
- Initial bootstrap during user activation code entry
- Approximately daily check / download for Debian OS (Security) Updates
- Approximately daily check / download for RISC Application Updates

Hello @joemigliore ,

What's different between app3.riscnetworks.com and app1.riscnetworks.com.

They have the same IP but our proxy filter by domain. Does it any problem if we just filter only app3 for both RN150 and FDP?

 

Thank you

ChrisG
By Level 20 Flexeran
Level 20 Flexeran

app1.riscnetworks.com is used by the FlexDeploy pod server, while app3.riscnetworks.com is used by the RN150 Virtual Appliance.

See the following pages for details of the different connectivity requirements:

 

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)