IRF 2.2 and Zonealarm - workaround

IRF 2.1 and previous versions worked fine for me, but I was having trouble getting IRF 2.2 to work with the free Zonealarm 2.1.44 software firewall from www.zonelabs.com. Even though I had IRF specified always be allowed in the Zonealarm programs menu, it still didn't work. (No chat and no races displayed. I am not talking about hosting, just about viewing chat and joining races.) I think it has to do with the IRF random port numbers. I think Zonealarm rejects the messages arriving on the random ports because, well, that's what it does. And the free Zonealarm doesn't have any way of specifying which port numbers should be allowed-- it just goes by application-- unless I haven't found it yet. So I can't specify a couple ports in IRF, then enter the same two ports into Zonealarm. But IRF does work when I lower my Zonealarm internet security from High to Medium. But I didn't want to do this on a permanent basis, so instead I reviewed my Zonealarm logs and found the IRF messages appeared to be coming from: 216.87.208.137 So I went into Zonealarm security/advanced and defined this IP address as local. Then I set my *local* network security to medium (and 216.87.208.137 is the only IP address in my local network). My regular internet security is still High. And this works! Just as long as no one from 216.87.208.137 launches an attack, I'll be fine :-) A couple other comments: 1. I have not tried hosting N4 yet, but as noted in other postings, there is info about this in the IRF 2.2 README file. 2. What port numbers does Zonealarm think IRF is using? If I knew what ports it thinks IRF is using, I could enter these in the IRF Options... Otherwise I'll use this workaround. -- Doug Appleyard "Got us a Dirt Track Date, demolition derby figure 8" -- Southern Culture On The Skids Sent via Deja.com http://www.deja.com/ Before you buy.

Same thing is happening with my LinkSYS router. If I DMZ my machine it will work. The author of IRF needs to publish the IP Port holes we need to punch. Quick :) -Larry "Doug Appleyard" <[email hidden]> wrote in message news:90li8f$7kf$[email hidden]...

Quoted text (54 lines)

> > > IRF 2.1 and previous versions worked fine for me, but > I was having trouble getting IRF 2.2 to work with > the free Zonealarm 2.1.44 software firewall from > www.zonelabs.com. Even though I had IRF > specified always be allowed in the Zonealarm > programs menu, it still didn't work. (No chat and > no races displayed. I am not talking about hosting, > just about viewing chat and joining races.) > > I think it has to do with the IRF random port numbers. > I think Zonealarm rejects the messages arriving on > the random ports because, well, that's what it does. > And the free Zonealarm doesn't have any way of specifying > which port numbers should be allowed-- it just goes > by application-- unless I haven't found it yet. > So I can't specify a couple ports in IRF, then enter the > same two ports into Zonealarm. > > But IRF does work when I lower my Zonealarm internet > security from High to Medium. But I didn't want to do > this on a permanent basis, so instead I reviewed my > Zonealarm logs and found the IRF messages appeared to be > coming from: 216.87.208.137 > > So I went into Zonealarm security/advanced and defined > this IP address as local. Then I set my *local* network > security to medium (and 216.87.208.137 is the only > IP address in my local network). My regular internet > security is still High. And this works! > Just as long as no one from 216.87.208.137 > launches an attack, I'll be fine :-) > > A couple other comments: > > 1. I have not tried hosting N4 yet, but as noted in other > postings, there is info about this in the IRF 2.2 README file. > > 2. What port numbers does Zonealarm think IRF is using? > If I knew what ports it thinks IRF is using, I could > enter these in the IRF Options... Otherwise I'll use > this workaround. > > > -- > Doug Appleyard > > "Got us a Dirt Track Date, demolition derby figure 8" > -- Southern Culture On The Skids > > > Sent via Deja.com http://www.deja.com/ > Before you buy.