Hi all...
The initial discovery of this issue began in ScottyK's thread, "Security for Traveling?" but rather than hijack his thread, I decided to start a new one.
I originally thought this was an issue in iptables, however, as I've discovered, ShieldsUP! reports the same problem while running Windows as well: The port "domain Domain Name Server" is open (red) when it didn't used to be. The rest are "closed" or blue in color. Both iptables and Windows firewall report the same thing. So my question is: I have Qwest DSL and I connect directly to the modem that Qwest issued. Is there some firewall layer the modem or perhaps Qwest is providing on their end that is affecting packets before they reach the firewalls on my computer? I'm not understanding this at all.
I am hoping to get some input from you guys before I call Qwest about it. If both iptables and Windows firewall (and in the past, 3rd party firewalls) report the same thing, I can't see this as being an issue with my system...or is it?
Regards...
The initial discovery of this issue began in ScottyK's thread, "Security for Traveling?" but rather than hijack his thread, I decided to start a new one.
I originally thought this was an issue in iptables, however, as I've discovered, ShieldsUP! reports the same problem while running Windows as well: The port "domain Domain Name Server" is open (red) when it didn't used to be. The rest are "closed" or blue in color. Both iptables and Windows firewall report the same thing. So my question is: I have Qwest DSL and I connect directly to the modem that Qwest issued. Is there some firewall layer the modem or perhaps Qwest is providing on their end that is affecting packets before they reach the firewalls on my computer? I'm not understanding this at all.
I am hoping to get some input from you guys before I call Qwest about it. If both iptables and Windows firewall (and in the past, 3rd party firewalls) report the same thing, I can't see this as being an issue with my system...or is it?
Regards...
Comment