mirozitnansky

@fyodor this issue is still not resolved, as I understand it. Even with version Ncap 1.1, there is still no way to capture packets going through windows bridged physical adapters,...

I just checked on version 1.55, behaviour is still the same on _windows bridge_ adapter.

Ok I'll try as you suggested. Also I noticed same behavior, when I am running virtual machine (in [virtual box](https://www.virtualbox.org/)) which has bridge adapter configured/attached, with IP from LAN router...

Ok I've tested it. Before bridge configuration device list contained 2 physical devices ``` 9. \Device\NPF_{03D160CC-12F2-47E2-AFA5-53AA9818BBA9} (Ethernet 2) 10. \Device\NPF_{9F95C33F-13C7-45C9-B225-2BABBE8D7863} (Ethernet) ``` After bridge configuration, these 2 are missing, 1...

Is it possible to test this modifying installed c:\Program Files\Npcap\npcap.inf directly? If so, is restart or any other kind of "refresh" required?

Hello @felixif, already tried that, after installing https://github.com/PowerShell/Win32-OpenSSH/releases/tag/v9.2.0.0p1-Beta on node machine, node is created but creating instance fails with error ```[2023-04-12T13:26:06.914+0200] [Payara 6.2023.3] [INFO] [] [javax.enterprise.system.core] [tid: _ThreadID=379 _ThreadName=admin-thread-pool::admin-listener(13)] [timeMillis:...

My error is already identified and reported https://github.com/payara/Payara/issues/3700#issuecomment-1456047960

Hello @felixif , any comments on this issue? Do you plan to fix it, or will DCOM be removed from payara?

Maybe I have suggestion for _create-service_ functionality here. If it's not appropriate place, I can move it to other place. _Create-service_ command creates default configuration in {domain1}Service.xml. This contains basic...