Windows 10: Firewall: How can i allow a programm to communicate only in LAN (IP range)?

Since i tried a virtual machine i have 2 IP adresses that some programms use. I use RemoteMouse (iOS App) to control my PC and since VM (and 2 IP adresses, default and new virtual switch) the use becomes laggy. I see in Ressourcemonitor it is using/listening/sending on the two networks, 192.168.188.0 and 172.17.194.31. How can i limit the communication to the 192 network? Deactivating the default switch (172 network) will activate itself on the next Windows boot. I tried inbound and outbound rules, it still communicates on both networks and i can‘t choose in firewall not to use the 2nd network adapter, i can set IP ranges. How i do it so communication is only allowed in the 192 network?

submitted by /u/FireStarter1337
[link] [comments]

:)

 

How do I create Firewall rule that allows LAN and blocks internet?

Firewall rules are always vague and unclear to me. What would help is someone telling me exactly what to put in each box.

Does "remote" mean everything but my LAN PC's and router?

Does Local mean "only" my router and pc's?

If I make an allow rule and choose only LAN under interface type, does it block everything else?

My PC's have fixed ip's, if I make an allow rule and put the ip of the other pc in it, does it block everything but that ip?

My LAN is 3 pc's and a printer with fixed ips, 2 hard wired 2 wifi (the printer is wifi) and DHCP for the game console and mobiles devices all hooked to my Cisco EA2700 and it hooks to my modem.

PS This is just a random allow rule I selected for a screenshot.

 

How to block any incomming and outgoing ip traffic for given ip ranges with Windows 10 Firewall?

Hello

I want to block any tcp/ip communication between my Ii-System and some ip ranges. The reason is, that I like to use Edge, which has a google core now, and I do not want my computer system to communicate with google at all.

I already wrote a program, which extracts all ip ranges, I would like to block. I would like to use the standard windows firewall.

Just adding a blocking rule for those ip ranges with all ports, applications and protocols did not work sufficiently. Even if I switch of all outgoing rules, by default, anything should be blocked, I can still connect to the internet and visit google pages.
But I do not want to send any ip package to one of those blocked ranges at all. And I do not want to respond to any request send from an ip address within those ranges.

Which order of rules is used within the windows firewall? If something is forbidden by one rule and allowed by another, which rule has priority? Is there a debugging possibility with more details than the log, where the decision for ip packages can be monitored?

Remark: I do not want to discuss my decision to block google out of my life, I just want to know, how to block the communication to any given ip range.

Thanks a lot for your help!

 

How do I create Firewall rule that allows LAN and blocks internet?

Firewall rules are not complex, but the way they described is confusing. My explanation may be just as confusing...

Remote = anything outside of the system at hand, including other systems within the same LAN.
Local = the local network, including other PCs, printers switches, routers, etc., within the same subnet
Interface type LAN = the interface where the firewall rule will be applied to

You do have a broadband router (Cisco), that's good and having your system software firewall isn't that important. Unless you'd want to control application access, both in and outbound.

In my view, local LAN based in and outbound access should be allowed. At least, that's what I do. The WFC rule is to fold for this purpose, since the bidirectional access (in and outbound for your system) requires two rules:





You can allow all programs, that will allow all programs to access the local subnet. Alternatively you can browse to the program that you'd want to allow access through the firewall.

The "LocalSubnet" is not in the dropdown menu, select "Custom Address" and type in "LocalSubnet". Create two of this rules, one for the "Inbound" the "Outbound" access. Alternatively, you could just select "No Filtering" in the "Profiles" tab for testing purposes: