August 23, 2019, 09:38:50 PM
Welcome, Guest. Please login or register
News: Stay up to date with everything that's happening at http://twitter.digitalsignage.com

MediaSignage support forum



Author Topic: Firewall explicit rules  (Read 48198 times)

jerrymattias

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Firewall explicit rules
« on: March 07, 2016, 06:13:26 AM »
Hi Community,
Can someone explain why the 172.31.X.X  private IP range is on the explicit firewall rule list? I'm not a network wiz but it what sense it 172 being used by the system for Communication between signage player client and the media cloud communication? The support chat could not explain other that they got the list from the developers but refeered to the forum.

This is the explicit rules IP list given by the chat:

*.signage.me
84.109.103.198
84.109.0.182
54.213.5.133
54.213.47.132
54.213.45.90
54.213.3.30
54.213.160.84
54.213.160.58
54.213.159.84
54.213.152.120
54.213.130.252
54.213.120.28
54.213.120.51
54.200.84.221
54.200.235.59
54.200.133.40
54.200.109.147
54.230.6.143
172.31.47.220
172.31.44.127
172.31.42.127
172.31.41.111
172.31.40.54
172.31.40.254
172.31.40.233
172.31.39.200
172.31.37.99
172.31.37.87
172.31.37.86
172.31.37.117
172.31.36.79
172.31.35.3


Thanks/

Mattias
« Last Edit: March 07, 2016, 06:18:24 AM by admin »

admin

  • Administrator
  • Hero Member
  • *****
  • Posts: 4962
  • Karma: +35/-8
    • View Profile
Re: Firewall explicit rules
« Reply #1 on: March 07, 2016, 06:27:31 AM »
Hi,

Yes, you can remove the 172.X.X.X ip range as those are private ip address ranges.  Will update the support team as well.

 

Carbonate design by Bloc
variant: carbon
SMF 2.0.12 | SMF © 2016, Simple Machines