![]() ![]() I presume that a single process that opens multiple adapters won't get a UAC prompt for every adapter if so, then, if dumpcap were to have a mode where it opened multiple adapters when running in "sparkline mode" - the mode where it's capturing on an interface and supplying packet counts so that the Wireshark main window can draw sparklines for each adapter - rather than, as per that bug, having multiple dumpcaps, one per interface - that would at least reduce the number of UAC prompts. Yes, at least some of this is a Wireshark issue, not an Npcap issue, as per Wireshark bug 15082. But indeed, this change should probably be done in Wireshark rather than npcap. When you start typing, Wireshark will help you autocomplete your filter. For example, type dns and you’ll see only DNS packets. The most basic way to apply a filter is by typing it into the filter box at the top of the window and clicking Apply (or pressing Enter). I think the solution is to start a single elevated process that can then spawn many as required. That’s where Wireshark’s filters come in. Sometimes I want to quickly capture some traffic (because something is happening) and I have to wait lots of time to pass all these UAC Windows one by one, even with keyboard shortcuts it takes time as Windows takes time to display them. Extremely annoying, especially that UAC (unlike sudo) has no timer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |