Is there any way to restrict network access for a Windows VM using KVM other than a couple of applications (Windows explorer and Firefox)? I don’t want to get into configuring the Windows firewall and would like to do this using KVM/other linux utilities on the host machine if possible As I thought, it is unlikely that I will be able to do this from the KVM side of things. Would anyone have an idea of how I could script this for subsequent Windows VMs?
I see, it’s simply disallowing everything except a specific port on that IP.
Considering that it will likely be a base Windows install, I don’t think other applications will be able to hijack that specific port so swiftly. With that said, can I possibly only allow traffic to and fro from the proxy through my firewall? Assuming that I’ll be running an HTTP proxy, I should be able to (in theory) inspect traffic too, although I don’t know how far that will take me.
With that said, can I possibly only allow traffic to and fro from the proxy through my firewall?
Yes. That is what I suggested. If you configure the firewall to only allow traffic to/from the specific IP and port combination of your proxy, other traffic will be blocked.
I should be able to (in theory) inspect traffic too, although I don’t know how far that will take me.
You can do content filtering via a proxy like that, yes. A similar sort of configuration is used on school computers to do things like block adult content, with varying degrees of success. Some ad-blocking techniques work on similar principles.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I see, it’s simply disallowing everything except a specific port on that IP.
Considering that it will likely be a base Windows install, I don’t think other applications will be able to hijack that specific port so swiftly. With that said, can I possibly only allow traffic to and fro from the proxy through my firewall? Assuming that I’ll be running an HTTP proxy, I should be able to (in theory) inspect traffic too, although I don’t know how far that will take me.
Yes. That is what I suggested. If you configure the firewall to only allow traffic to/from the specific IP and port combination of your proxy, other traffic will be blocked.
You can do content filtering via a proxy like that, yes. A similar sort of configuration is used on school computers to do things like block adult content, with varying degrees of success. Some ad-blocking techniques work on similar principles.
I was wondering if I could label the traffic to and from the proxy, and not have to rely on ports for filtering
You can whitelist both the proxy and the ip, blacklist everything else.
I see. Thanks!