Error by extcap pipe

[hgoncal2]

So i've been trying to solve this for a couple hours now,read every doc surrounding this issue,still can't seem to figure out how to solve it,or why it's happening.

So,the web UI works fine

First problem starts when in wireshark none of my containers show up

Of course pressing the "refresh" button doesn't do anything. Can't seem to find out why this is happening,since all my containers show up in the web UI.
Secondly,in the web UI,after trying to open up wireshark by clicking on the icon,and get this error.

I've installed the cshargextcap plugin,and i'm running the edgeshark docker compose project.
Is there anything i'm missing?
Wireshark version 4.0.6

[thediveo]

Hi there, thank you very much for providing such useful details and sorry to hear you are having issues! Your third screenshot with the error message indicates that there seems to be a problem in your general system setup: "localhost" does not directly resolve to 127.0.0.1 (and ::1) as it is common, and using /etc/hosts, but instead your system tries to contact a DNS server (which it shouldn't in thise case) at 1.1.1.2, and this fails.

Can you try navigating to the Edgeshark ui using http://127.0.0.1:5001 instead and see if capturing then works?

As this is a system setup I've never seen, can you share some details about it? I've only seen a similar setup yesterday from a colleague, this is an Apple system, right?

Do you use a Linux Wireshark or an "Apple" Wireshark? I'm suspecting things going south when mixing the Linux plugin with the Apple Wireshark. Unfortunately, I don't have any Apple system at hand to test and maybe develop, so I'm reliant on PRs here.

[Silvanoc]

@thediveo looking at the paths of the 2nd screenshot, I'd say it's a Windows system, not a MacOS one.

[hgoncal2]

Sorry for not saying it in the beggining,yes it's windows + some wsl things.
I've tried your suggestion of using 127.0.0.1 and now it works!

The web UI wireshark thing also works fine. Weird how "localhost" was mapping to that address,even though my hosts file looks right
On wsl:

And on windows:

[thediveo]

no worries, I mislead myself 😁 ... and I now have feedback from the first WSL2 user on top of that.

localhost should map to 127.0.0.1, ::1, but there seems to be something special in case of WSL2.

So this works for you, correct? Great! I will close this issue as "has workaround" and document this. Feel free to reopen or create a new issue if you hit this again or something else.

[thediveo]

I've finally managed to install WSL2, or rather install it twice, as the first install was broken for whatever reason. I've applied the fix in microsoft/WSL#5420 to avoid having /etc/resolv.conf getting recreated all the time and set static upstream DNS servers. This way, "localhost" works for me. Somehow your installation seems to maybe suffer from similar resolver configuration issues...?

[hgoncal2]

I've finally managed to install WSL2, or rather install it twice, as the first install was broken for whatever reason. I've applied the fix in microsoft/WSL#5420 to avoid having /etc/resolv.conf getting recreated all the time and set static upstream DNS servers. This way, "localhost" works for me. Somehow your installation seems to maybe suffer from similar resolver configuration issues...?

Sorry for the late reply.I've tried the fix you've described and still doesn't work with "localhost".
This is my resolv.conf file

And i'm getting the same errors as described in the OP.

I should add i also tried it in windows,without anything WSL, and localhost still doesn't work,so i don't think it's WSL related.

[thediveo]

One thing I noticed is in case of Docker Desktop you'll need to deinstall any previous Docker installation, as Docker Desktop integrates its own files into your distro. This took me some time to diagnose why this didn't work; but you seem to face a different issue with your WSL2 setup -- so just noting that just in case.