Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

none of the host interfaces are shown #17

Closed
1 task done
habsfanongit opened this issue Feb 26, 2024 · 5 comments
Closed
1 task done

none of the host interfaces are shown #17

habsfanongit opened this issue Feb 26, 2024 · 5 comments

Comments

@habsfanongit
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When I run the compose file, I can only see the container's interfaces, none of the hosts are shown.
Do I need to install or perform any additional configuration to see the host's interfaces?

Expected Behavior

Host's network interfaces to be available to capture traffic from

Steps To Reproduce

  1. using the docker-compsoe file
  2. run docker compose up -d --build --remove-orphans--
    docker compose logs -f wireshark

Environment

- OS: Ubuntu 2204
- How docker service was installed: Used the instructions found on Docker Official Site https://docs.docker.com/engine/install/ubuntu/ and insatlled using apt

CPU architecture

x86-64

Docker creation

---
services:
  wireshark:
    image: lscr.io/linuxserver/wireshark:latest
    container_name: wireshark
    cap_add:
      - NET_ADMIN
    security_opt:
      - seccomp:unconfined #optional
    network_mode: host
    environment:
      - PUID=0
      - PGID=0
      - TZ=Etc/UTC
    volumes:
      - config:/config
    ports:
      - 3000:3000 #optional
      - 3001:3001 #optional
    restart: unless-stopped
volumes:
  config:

Container logs

docker compose logs -f wireshark
wireshark  | [migrations] started
wireshark  | [migrations] no migrations found
wireshark  | ───────────────────────────────────────
wireshark  |
wireshark  |       ██╗     ███████╗██╗ ██████╗
wireshark  |       ██║     ██╔════╝██║██╔═══██╗
wireshark  |       ██║     ███████╗██║██║   ██║
wireshark  |       ██║     ╚════██║██║██║   ██║
wireshark  |       ███████╗███████║██║╚██████╔╝
wireshark  |       ╚══════╝╚══════╝╚═╝ ╚═════╝
wireshark  |
wireshark  |    Brought to you by linuxserver.io
wireshark  | ───────────────────────────────────────
wireshark  |
wireshark  | To support LSIO projects visit:
wireshark  | https://www.linuxserver.io/donate/
wireshark  |
wireshark  | ───────────────────────────────────────
wireshark  | GID/UID
wireshark  | ───────────────────────────────────────
wireshark  |
wireshark  | User UID:    0
wireshark  | User GID:    0
wireshark  | ───────────────────────────────────────
wireshark  |
wireshark  | .+.+..+...+....+...+..+...+.......+...+...+.....+...+....+...+..+..........+......+......+...+......+..+...+.+......+...+.....+.+.....+.........+....+..+........................+.........+...+....+.....+...+...+++++++++++++++++++++++++++++++++++++++*...........+......+.....+++++++++++++++++++++++++++++++++++++++*...+....+..+.+.....+...+.........................+..+...+.+.........+..++++++
wireshark  | .....+..+.........+++++++++++++++++++++++++++++++++++++++*...+......+....+..+++++++++++++++++++++++++++++++++++++++*..................+.......+...+.....+...............+....+.....+......+.......+........+......+...+.......+.....+......+....+......+..+.+.....+......+..........+.........+...........+......+....+.........+..+..........+..+.+..+...............+....+...+...+..+......+.......+..+............+...+.+............+.....+....+.....++++++
wireshark  | -----
wireshark  | [custom-init] No custom files found, skipping...
wireshark  | [ls.io-init] done.
wireshark  |
wireshark  | Xvnc KasmVNC 1.2.0 - built Feb 17 2024 18:44:55
wireshark  | Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
wireshark  | See http://kasmweb.com for information on KasmVNC.
wireshark  | Underlying X server release 12014000, The X.Org Foundation
wireshark  |
wireshark  | The XKEYBOARD keymap compiler (xkbcomp) reports:
wireshark  | > Warning:          Could not resolve keysym XF86CameraAccessEnable
wireshark  | > Warning:          Could not resolve keysym XF86CameraAccessDisable
wireshark  | > Warning:          Could not resolve keysym XF86CameraAccessToggle
wireshark  | > Warning:          Could not resolve keysym XF86NextElement
wireshark  | > Warning:          Could not resolve keysym XF86PreviousElement
wireshark  | > Warning:          Could not resolve keysym XF86AutopilotEngageToggle
wireshark  | > Warning:          Could not resolve keysym XF86MarkWaypoint
wireshark  | > Warning:          Could not resolve keysym XF86Sos
wireshark  | > Warning:          Could not resolve keysym XF86NavChart
wireshark  | > Warning:          Could not resolve keysym XF86FishingChart
wireshark  | > Warning:          Could not resolve keysym XF86SingleRangeRadar
wireshark  | > Warning:          Could not resolve keysym XF86DualRangeRadar
wireshark  | > Warning:          Could not resolve keysym XF86RadarOverlay
wireshark  | > Warning:          Could not resolve keysym XF86TraditionalSonar
wireshark  | > Warning:          Could not resolve keysym XF86ClearvuSonar
wireshark  | > Warning:          Could not resolve keysym XF86SidevuSonar
wireshark  | > Warning:          Could not resolve keysym XF86NavInfo
wireshark  | Errors from xkbcomp are not fatal to the X server
wireshark  | Obt-Message: Xinerama extension is not present on the server
wireshark  |  2024-02-26 10:48:20,917 [INFO] websocket 0: got client connection from 127.0.0.1
wireshark  |  2024-02-26 10:48:20,928 [PRIO] Connections: accepted: @172.20.0.1_1708962500.917958::websocket
wireshark  |  2024-02-26 10:50:16,542 [INFO] websocket 1: got client connection from 127.0.0.1
wireshark  |  2024-02-26 10:50:16,555 [PRIO] Connections: accepted: @172.20.0.1_1708962616.542582::websocket
wireshark  |  2024-02-26 10:56:56,564 [PRIO] Connections: closed: @172.20.0.1_1708962616.542582::websocket (Clean disconnection)
wireshark  |  ** (wireshark:290) 10:57:14.555891 [Capture MESSAGE] -- Capture Start ...
wireshark  |  ** (wireshark:290) 10:57:14.633969 [Capture MESSAGE] -- Capture started
wireshark  |  ** (wireshark:290) 10:57:14.633985 [Capture MESSAGE] -- File: "/tmp/wireshark_eth004RHJ2.pcapng"
wireshark  |  ** (wireshark:290) 10:58:27.472874 [Capture MESSAGE] -- Capture Stop ...
wireshark  |  ** (wireshark:290) 10:58:27.521523 [Capture MESSAGE] -- Capture stopped.
wireshark  |  ** (wireshark:290) 10:58:27.608710 [Capture MESSAGE] -- Capture Start ...
wireshark  |  ** (wireshark:290) 10:58:27.674745 [Capture MESSAGE] -- Capture started
wireshark  |  ** (wireshark:290) 10:58:27.674780 [Capture MESSAGE] -- File: "/tmp/wireshark_eth081TGJ2.pcapng"
wireshark  |  ** (wireshark:290) 10:58:36.786762 [Capture MESSAGE] -- Capture Stop ...
wireshark  |  ** (wireshark:290) 10:58:36.826329 [Capture MESSAGE] -- Capture stopped.
wireshark  |  ** (wireshark:290) 10:58:46.737328 [Capture MESSAGE] -- Capture Start ...
wireshark  |  ** (wireshark:290) 10:58:46.836943 [Capture MESSAGE] -- Capture started
wireshark  |  ** (wireshark:290) 10:58:46.836956 [Capture MESSAGE] -- File: "/tmp/wireshark_any7V79I2.pcapng"
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@LinuxServer-CI
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@thespad
Copy link
Member

thespad commented May 18, 2024

I can't replicate this; using your compose (discarding the ports because they're irrelevant with host networking mode) I can see all the host interfaces:

image

@LinuxServer-CI
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Aug 16, 2024
Copy link

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

3 participants