Firewall Ports

[alistair]

I'm moving my installation of Sighthound into the DMZ of my home network.

What port(s) and IP(s) do I need to allow so the annoying new "activation" system will work?
Do I need to whitelist anything in addition for update checking?

[ryan]

Hi Alistair,

As with prior versions of the software you shouldn't need to open any ports in your firewall. No traffic is ever initiated to your application from an external source. If you're having any trouble please submit a bug report from within the app at "Help->Report a Problem" and we'll be glad to look into it.

[alistair]

Hi Ryan

I'm blocking all OUTBOUND traffic in the DMZ also (I'm a little bit OCD about perimeter security ).

Sighthound will need to connect outbound to check for updates, and activate the license.... it's this connectivity I need to whitelist.

[ryan]

Ah, gotcha, sorry for the misunderstanding. I assume your software supports wildcard entries? A standard http/https exception for *.sighthound.com should do the trick.

[alistair]

Ah, if only it were that easy . No DNS resolution on firewall rules, frustratingly.
I'll give it a go on 80/443 for 173.230.131.7 (www.sighthound.com) and see if it works....

[ryan]

Hrmm, that's unfortunate. Maybe you can have something post-firewall that will redirect traffic so you can hardcode Junk IPs and later translate into the correct dns resolution? For now you'll want to add 54.84.168.172 as well.