Firewall Settings [Basic Edition]
In order to get traffic through the firewalls I need the following information -
Ports Used? (for a single screen-scraper instance)[basic edition]
> External ie (Internet Facing)
>> Whether Inbound / Outbound or bi-directional?
> Internal ie (LAN Only)
>> Whether Inbound / Outbound or bi-directional?
Protocols
> What protocols need to be allowed on each Port?
The documentation I have read so far suggests that the following ports are / or maybe used 8777, 8778, 8779, 9001, & 9005. I can find no information on what protocols are used on each port, nor whether they are uni / bi-directional, and I suspect that 9001 and 9005 do not need to allow traffic to / from the Internet.
For the curious, the need for LAN related info is because the LAN has multiple sites that are connected via broadband using a firewalled VPN.
Any help would be appreciated
Cheers
Tarka
8777 is the port used for
8777 is the port used for proxying pages. it uses the http/https protocols, but ports 80 and 443 (default http/s ports) should be open already, or else you wouldn't be able to get online at all. Assuming you are proxying on the same machine that you are browsing the firewall shouldn't need to be touched for this though as localhost requests aren't blocked by the firewall (at least basic firewalls).
Ports 8778, 8779 are used for running screen-scraper as a server. This feature isn't available in the basic addition so you don't need to worry about them, and they are also by default only allow connections from the local machine, although this can be changed in the screen-scraper.properties file.
9001 is used for screen-scrapers internal database, again only localhost. This shouldn't need to be forwarded through anything.
To sum it up the only ports/protocols that screen-scraper should need open at the lan firewall to scrape websites is the same you would need open to browse websites, http/https on ports 80 and 443 respectively.
I just corrected some bad
I just corrected some bad grammar and unclear information and typos in my colleague's post :)
We love you Ryan Justus.