Manipulating Firewall Settings

Forums › Microsoft Windows › Manipulating Firewall Settings

Rickles

2938 posts

Uber Geek

Trusted

#289282 25-Aug-2021 12:54

I'm setting up a demonstration showing the global DDoS map (using Netscout site), and how even Windows Security blocks unauthorised incoming connections.

I can show the Firewall logs easily, and can turn Logging On and OFF using a Netsh Command Line that I've made workable using a .BAT file. This
saves me going through the process of opening Firewall and changing each manually.

What I'd like to do is have Command Lines to enable/disable incoming connections, so that the log can proliferate (for a very short time on a closed network) with any
nasties knocking on the door.

What I cannot find is a Command Line to do this, so any help would be appreciated.

michaelmurfy

meow
13256 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#2766487 25-Aug-2021 13:02

Your answer is Powershell: https://docs.microsoft.com/en-us/powershell/module/netsecurity/new-netfirewallrule?view=windowsserver2019-ps

BAT / CMD scripts are last century :)

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

Rickles

2938 posts

Uber Geek

Trusted

#2766514 25-Aug-2021 14:24

>BAT / CMD scripts are last century :)<

That is no way to treat your elders who started out using pencils to mark-sense punch cards, and read all 668 pages of the DOS 5.0 Manual 😜

Lias

5589 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#2766525 25-Aug-2021 14:54

Rickles:

>BAT / CMD scripts are last century :)<

That is no way to treat your elders who started out using pencils to mark-sense punch cards, and read all 668 pages of the DOS 5.0 Manual 😜

He's not wrong however (and I say this as someone who's first PC was an XT)

I'm a geek, a gamer, a dad, a Quic user, and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it. If you use my Quic signup you can also use the code R570394EKGIZ8 for free setup.

Rickles

2938 posts

Uber Geek

Trusted

#2766528 25-Aug-2021 15:01

>He's not wrong however<

Probably so, but far too esoteric for my understanding I'm afraid.

michaelmurfy

meow
13256 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#2766536 25-Aug-2021 15:11

Rickles:

That is no way to treat your elders who started out using pencils to mark-sense punch cards, and read all 668 pages of the DOS 5.0 Manual 😜

Don't get me wrong - I still have a deployment script, in production, that is a *.bat script. I've been meaning to migrate it to powershell but it still works :)

But Powershell is far, far more powerful than the batch scripts of the past.

zespri

414 posts

Ultimate Geek

Lifetime subscriber

#2766563 25-Aug-2021 15:58

Rickles:

>He's not wrong however<

Probably so, but far too esoteric for my understanding I'm afraid.

Seriously, in the context being discussed this just a different interface to the same thing (internal firewall api object model), the article Michael linked and the neighbours give a good description of how to use these command. In both cases it's still a simple script, only with PowerShell you get more flexibility and more support (that is it's much easier to google). I would advise you to try - it may not be as bad as you think. If something is unclear as you start looking at it we might be able to help.