Hip Tracker Update: FIREWALLED

chris · Mon Feb 21, 2005 11:26 pm

Hello everyone,

To make it easier to understand if you have opened the correct ports, or if you are firewalled, I modified the code to display "FIREWALLED" when you look at the list of seeds/leechers if you have not opened the correct ports.

Check portforward.com for details on how to get things sorted out and functioning properly.

If you notice any other glitches on the site, or have suggestions for improvement, please let me know.

Thanks!

kgray · Tue Feb 22, 2005 5:11 pm

I am using a firewall (Zone Alarm). I went to the site Chris mentioned above about enabling ports, and it shows how to do it with ZoneAlarm Pro (no mention of regular ZoneAlarm).

Does anyone know how to open ports on regular Zone Alarm (the free version)?

Thanks,
Kevin

PurposelessPlay · Tue Feb 22, 2005 7:52 pm

If I remember correctly from previous discussions of this, you can't forward ports in the free ZA. Sorry.

kelman66 · Wed Mar 02, 2005 10:57 pm

I have always had great ul and dl and never a problem connecting to ports 6881 etc....but all of a sudden, i am now 'firewalled'. I have done nothing to change this. I have noticed others showing up as firewalled for a week or two now, but I have been fine until yesterday.

Norton Internet Security settings are unchanged.

chris · Thu Mar 03, 2005 7:27 am

I only changed the code to display "FIREWALLED" instead of "-----" if a user is behind a firewall; no settings were modified. I imagine that people are just taking note of the word "FIREWALLED" more than the five dahes that used to be displayed.

kelman66 · Thu Mar 03, 2005 11:51 am

the only problem is that I have no download or upload speed. Until three days ago, it was great

chris · Thu Mar 03, 2005 11:56 am

Something has happened, and I don't know what it is. I'll look into it this weekend, and try to reinstall some of the software.

kelman66 · Thu Mar 03, 2005 9:47 pm

thanks dude.
you rock

chris · Fri Mar 04, 2005 8:31 am

I think that I fixed it... at least temporarily. Cancel all of your current torrents, and try to reconnect. It should be working properly again.

As I said, this is a temporary fix, and I will delve into it more this weekend.

kelman66 · Fri Mar 04, 2005 10:37 am

thanks Chris, it appears that I now have some throughput, so whatever you tried, it has at least some limited success.