What are the update ports?
fakhir (I-Blocklist - General Manager):
port 80 is used for HTTP
port 443 is used for HTTPS
I-Blocklist uses many different servers to host the lists.
I am not sure if those are update connections but it is possible.
port 80 is used for HTTP
port 443 is used for HTTPS
I-Blocklist uses many different servers to host the lists.
I am not sure if those are update connections but it is possible.
posted on 08/28/2010 at 06:14PM
purrcy:
I have two addresses that are prominent in my firewall log at startup: those two that are listed above, which I assume are updating my blocklists. Another address that appears quite often is ool-45792716.dyn.optonline.net; This is an address that pploader wanted to access, and which I haven't figured the purpose of. Oh, and projects.sourceforge.net is a startup address which I think is PG2 calling home for an update. Otherwise, my firewall log at startup is pretty quiet. The only other addresses that appear are for DNS (I think): junior.dexdo.net, perfora.net, and dns2.supremecenter50.com; The surprising thing about these "DNS" addresses is that they access port 80. My OS X doesn't seem to be using port 53 for DNS, which I don't understand. Another pploader address is angetenar.lunarpages.com, which also uses port 80.
All of this gets to the question, "Can I trust enough the addresses that pploader wants to access to put them into My Allow list? I have this paranoid tendency to want to block all port 80 communication, since I use xerosurf.com, and port 443, to do almost all my internet surfing.
So, is there some kind of policy rule that one should apply when blocking an address, or allowing an address?
I have two addresses that are prominent in my firewall log at startup: those two that are listed above, which I assume are updating my blocklists. Another address that appears quite often is ool-45792716.dyn.optonline.net; This is an address that pploader wanted to access, and which I haven't figured the purpose of. Oh, and projects.sourceforge.net is a startup address which I think is PG2 calling home for an update. Otherwise, my firewall log at startup is pretty quiet. The only other addresses that appear are for DNS (I think): junior.dexdo.net, perfora.net, and dns2.supremecenter50.com; The surprising thing about these "DNS" addresses is that they access port 80. My OS X doesn't seem to be using port 53 for DNS, which I don't understand. Another pploader address is angetenar.lunarpages.com, which also uses port 80.
All of this gets to the question, "Can I trust enough the addresses that pploader wants to access to put them into My Allow list? I have this paranoid tendency to want to block all port 80 communication, since I use xerosurf.com, and port 443, to do almost all my internet surfing.
So, is there some kind of policy rule that one should apply when blocking an address, or allowing an address?
posted on 08/29/2010 at 05:22PM
fakhir (I-Blocklist - General Manager):
ool-45792716.dyn.optonline.net
That is the main I-Blocklist update server.
After you connect to the main I-Blocklist server you will get redirected to one or more other servers to download the lists.
You should be safe allowing all connections to/from PeerGuardian.
ool-45792716.dyn.optonline.net
That is the main I-Blocklist update server.
After you connect to the main I-Blocklist server you will get redirected to one or more other servers to download the lists.
You should be safe allowing all connections to/from PeerGuardian.
posted on 08/29/2010 at 09:07PM
Hi,
I'm noticing communications on my firewall log to b9.87.364a.static.theplanet.com:443 and to 3c.b9.354a.static.theplanet.com:80. I believe that these are to update my blocklists. I'm wondering why the differences in ports. I try to avoid port 80, as much as I can, in favor of port 443. Can you tell me what's going on?