I think the problem is pretty simple, vEthernet Adapters from Windows 8 are not managed at all by CIS.
The reproduction is pretty easy, install (enable) Hyper-V, create a External vSwitch (preferably bound to a 2nd physical adapter or the main/only Ethernet adapter is fine as well), create a VW with an OS of your choice and watch what happend, everything from the VM is passing through without a single question from CIS on the Hyper-V server physical host.
In my setup i’ve got two NIC’s from which i’ve dedicated one to the vSwitch and as said, then Windows 8 will swap the manufacturer driver with it’s so called “Ethernet adapter vEthernet” driver or software layer.
On my 2nd NIC though, everything still goes through CIS but on the other one, which gets a physical IP from the DHCP and is shown at the Hyper-V physical host (check vSwitch-ipconfig.png), it’s simply ignored or not seen by CIS.
As you can see (vSwitch-properties1.png), the CIS driver is in fact bound to the virtual adapter, but does not seem to be “catched”.
Here are my versions:
Windows 8 x64
Windows 8 x64 Hyper-V enabled
Hyper-V guest Windows 8 x64
If it’s really needed and will help the community securing things a little deeper i would do as you’ve suggested…
Thanks very much for your issue report. We have moved it to the non-format bugs board for the moment, because too much of the information we normally need to replicate a problem and fix it is missing, or it is not in the format we request.
We realize some people may not have the time to do bug report in standard format, and therefore offer the option of a non-format report instead. But the problem is much more likely to be fixed promptly if you edit your first post to create an issue report which meets all criteria in the Checklist and Format. (You can copy and paste the format from this topic). The general reasons why are summarized in that post, the reasons we ask for specific pieces of information are given in this detailed post.
You can get your report moved to the format verified issues board simply by ensuring that it is correctly formatted and all criteria are met, and PM’ing a mod who is active on the bug board.
I have just ‘come back’ to Comodo after a little break and I find I cannot manage my firewall because of Hyper-V. I don’t have the luxury of 2 Ethernet adapters so that isn’t an option for me. How do I get Comodo to ‘see’ my network with Hyper-V running.
I am running Win8 Pro and the latest 6.0.264710.2708 CIS. I manage a few VMs using Hyper-V and do not want to have to switch to another VM manager.
Can you please check and see if this is fixed with the newest version (version 6.2.282872.2847)? Please let us know whether it is fixed or you are still experiencing the problem.
Also, note that all bug reports in the Non-Format section of the forum, which is where this report currently is, are not looked at by the devs. Thus, if the bug you were experiencing is still not fixed please edit your first post so that it is in the correct format (found here, with all required attachments, so I can forward this to the devs and get this problem fixed.
Can you please check and see if this is fixed with the newest version (version 6.3.294583.2937)? Please let us know whether it is fixed or you are still experiencing the problem.
Also, note that all bug reports in the Non-Format section of the forum, which is where this report currently is, are mainly not looked at by the devs. Thus, if the bug you were experiencing is still not fixed please edit your first post so that it is in the correct format (found here, with all required attachments), so I can forward this to the devs and get this problem fixed.
The devs are not able to replicate this issue. Also, as there has not been a response to my queries, I will assume that this is now fixed and move this to Resolved. If this is not fixed for you please let me know.