F/W settings for nod32EE (v2.70.39)

[Cosmo32]

Good Morning all,
I have migrated from a dial-up connection to a broadband connection. So far my nod32EE is working as sold and is now almost totally invisible, fast, light, and amazingly impossible for me to fathom!

Are there some suggested settings I should do to the SPI FW in my router (d-link dgl-4300)?

I have scanned the FAQs, but I get lost easily in the details.:-[
I would like to make certain that nod32EE has full and unrestricted access to the internet whenever it chooses to "phone home?" ???

It does work OK for now, but I would like to make sure nod32EE has complete freedom for its' business. The previous 9 months have been superb. Not a single "red" warning, and, all local scans are clean. Great programming ESET!;D Really good stuff.8)
Best,
Duncan

[Cosmo32]

bump
Perhaps I placed this post into the wrong forum thread series. Perhaps I really need to post in the 'other firewalls' forum(?)
The "F/W" in the title meant FireWall, not firmware. What I am trying to figure out is are there any nod32 unique settings (ports) I need to be aware of so that nod32 has free, full, non-restricted access through my router's firewall to ESET proper?
Maybe not a big issue because it all seems to work just fine so far. Just wondering. Thank you for any suggestions.

[WSFuser]

Its fine. Your router is already set to allow certain ports (like HTTP).

[Cosmo32]

Thank you WSUser.

That is true. And, if HTTP is that only port I need for local to call home, I suppose my question is/was really a non-question after all.
If that is the only port/pinhole I need to worry about, I am covered ATM. ;D
Really sorry for the noise. Just checking. I am still in /learn/ mode.
I read that there might be bigger fish to fry......later.......

Bubba, you can close this thread if necessary..........