Tag Info

Hot answers tagged

3

You can use netstat -Wplunt to get a list of every process listening on TCP or UDP ports. This will list a bit more than you want to know about. You can ignore all of the ports bound to ::1 or 127.0.0.1 since those are only accessible to the server itself. The rest are possibly reachable from outside. How to test the firewall rules is a separate question. I ...


3

Yes. Wireshark operates "before" firewall and sees all the packets that the network card receives. Then the packets get filtered by the firewall running on the PC.


2

An older post, but still worth adding to. It seems that in Windows Server 2012, this item simply means "allow packets from other subnets". At least that is the behavior I have observed. We have two offices connected with an IPSec VPN. The VPN connects the two routers, so as far as the Windows computers are concerned, it's simply traffic between two different ...


2

We did this with a game server. We eventually changed it for a plugin on pfsense, but we didn't notice any performance degradation with a few thousand ip blocks in the windows firewall. Blocking based upon ip is one of the most rudimentary tasks a firewall can do. Besides the management overhead (you already have a script for that), I wouldn't see any reason ...


1

Even if our scenarios are different, I would like to share: I have a small VPS (1 CPU, 256MB RAM) running a few services on Linux, and the firewall have thousands of rules denying whole blocks of adresses, spanning whole countries, and I haven't seen any slowdown. I think it's less demanding on the server to simply drop lots of packets than letting them go ...



Only top voted, non community-wiki answers of a minimum length are eligible