Ask Your Question

Disable rpcap-interface discovery on startup

asked 2018-09-18 08:46:29 +0000

Basti gravatar image

Hi together,

is there any hidden option to disable the rpcap-interface discovery on Programm startup.

The newest Wiresahrk Version store all known remote interfaces inside the "recent-common" file wich is located "C:\Users\<user>\AppData\Roaming\Wireshark"

After the comment: "######## Recent remote hosts, cannot be altered through command line ########"

The Problem is, that Wireshark search on very Startup for all these rpcap Interfaces which are not reachable anymore and the startup process take so much of time and often the programm breaks and i must restart it again.

I hope there is any advanced configuration to doable this behaviour

thank you, Basti

edit retag flag offensive close merge delete


Has anybody a solutions for this problem?

Basti gravatar imageBasti ( 2018-11-30 14:33:19 +0000 )edit

Stop Wireshark, try deleting the entries from the file, restart Wireshark.

grahamb gravatar imagegrahamb ( 2018-11-30 14:47:28 +0000 )edit


Stop Wireshark, try deleting the entries from the file, restart Wireshark. This works only for the next startup.

If i add a remote interface in the next session it will also be cached in the config file. If i start wireshark then again he try to connect to the cached rpcap ip.

From my understanding this make in the most of scveanrios no sense. So i preferred a config flag to activate/deactivate this behaviour

thanks you Basti

Basti gravatar imageBasti ( 2018-11-30 15:28:29 +0000 )edit

Then you would need to either submit a change to the source that does what you want (see the Submitting Patches page on the Wiki, or you can submit an enhancement request on the Wireshark Bug Tracker.

grahamb gravatar imagegrahamb ( 2018-11-30 16:06:26 +0000 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2022-04-26 10:01:42 +0000

Basti gravatar image

Hey Ho,

since Wireshark version 3.4.x it will not help anymore to mark "recent_common" with write-restriction in the windows filesystem. Now the Wireshark will prompt an error message that the named file is not writable :/

Anybody who wants to fix them? I think a good possibility would be a configuration if Wireshark should store old interfaces yes/no.

Thanks and greetz

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2018-09-18 08:46:29 +0000

Seen: 250 times

Last updated: Sep 18 '18