1 | initial version |
WinPCap, which has been obsolete for a number of years, was never very good with VPN's.
npcap should be used in its "native mode", if that doesn't support your interface (use wireshark or tshark from the command line with -D
to list the interfaces), then that should be reported as an npcap issue here.
A final option is to try to capture using the built in capture tools that produce an ETL file and then convert the file to pcapng using etl2pcapng. More info on the tools here and here.
2 | No.2 Revision |
WinPCap, which has been obsolete for a number of years, was never very good with VPN's.
npcap should be used in its "native mode", if that doesn't support your interface (use wireshark or tshark from the command line with -D
to list the interfaces), then that should be reported as an npcap issue here.
A final option is to try to capture using the built in capture tools that produce an ETL file and then convert the file to pcapng using etl2pcapng. More info on the tools here and here.