Interfaces shows wrong wlan0 state

[denk-mal]

Versions

• Core version is v6.0.4 (Latest: v6.0.4)
• Web version is v6.0.1 (Latest: v6.0.1)
• FTL version is v6.0.3 (Latest: v6.0.3)

Platform

• OS and version: Debian 12 (bookworm)

• Platform: std x64 PC

Expected behavior

State of wlan0 should be shown as down but is shown as up

Actual behavior / bug

instead of

ip addr show wlan0
wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 1c:c1:0c:xx:xx:xx brd ff:ff:ff:ff:ff:ff

Steps to reproduce

Steps to reproduce the behavior:

1. deactivate wlan0
2. Go to Tools -> Interfaces
3. show status of wlan0 on console ip addr show wlan0
4. See error

[DL6ER]

What is the wlan0 related output of

pihole api network/interfaces

?

Feel free to replace MAC/IP address information with, e.g., XX. Please just make sure it is clear what you obfuscated.

[denk-mal]

{
  "name": "wlan0",
  "speed": null,
  "type": "ether",
  "flags": [
    "broadcast",
    "multicast"
  ],
  "state": "down",
  "carrier": true,
  "proto_down": false,
  "address": "01:23:45:67:89:ab",
  "broadcast": "ff:ff:ff:ff:ff:ff",
  "perm_address": "01:23:45:67:89:ab",
  "stats": {
    "rx_bytes": {
      "value": 0,
      "unit": ""
    },
    "tx_bytes": {
      "value": 0,
      "unit": ""
    },
    "bits": 64
  }
},

[yubiuser]

I think this line should check for state, not carrier

https://github.com/pi-hole/web/blob/25441178f7dcc365c5a553a86b23eeed0573938f/scripts/js/interfaces.js#L35

[denk-mal]

I belive there is a little bit more to do because interface.carrier is a boolean (true/false) while interface.state is a string ("up"/"down")
EDIT: ...and lo has state 'UNKNOWN'

[DL6ER]

Please try again on branch development:

sudo pihole checkout web development

[denk-mal]

wlan0 is marked correcly as 'down' now - in green (docker0 is marked as 'down' in red). Vice versa would be better IMHO but this is a design thing and up to you.

[DL6ER]

wlan0 state is "down" but carrier is true -> hence green. It is not Pi-hole's "fault" that a disconnected WiFi module is advertised with carrier = true I'd say here :-)

docker0 state is "down" and carrier is false -> red color. Does it mean you have no docker container running right now?

[denk-mal]

wlan0 state is "down" but carrier is true -> hence green. It is not Pi-hole's "fault" that a disconnected WiFi module is advertised with carrier = true I'd say here :-)

Full Ack

docker0 state is "down" and carrier is false -> red color. Does it mean you have no docker container running right now?

This is a miracle on my server because I have a lot of container up and running but ip addr show docker0 results in

6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 12:da:95:65:ad:cb brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

[rdwebdesign]

docker0 DOWN doesn't mean you don't have containers running.

The docker0 interface is used only when you start a container using the default bridge network (without specifying another bridge network).
When all containers are using user-defined bridge networks (or host network), docker0 will be down.

[denk-mal]

I know this known behavior and on my server most of the container - but not all container - using a custom network maintained from the traefik instance. One is working in host mode (dlna) and one is working on the default bridge (docker0). But honestly it is working so I would not claim about docker0 as marked 'down'. And it is not a fault of pihole so who cares, I don't.

[DL6ER]

I will mark this issue as "fixed in next release" as we have a few changes in development of the web component that style the interfaces better. It is good to know that the data we show is not wrong, though :-)

[DL6ER]

The next version of FTL has been released. Please update and run

pihole checkout master

to get back on-track. The fix/feature branch you switched to will not receive any further updates.

Thanks for helping us to make Pi-hole better for us all!

If you have any issues, please either reopen this ticket or (preferably) create a new ticket describing the issues in further detail and only reference this ticket. This will help us to help you best.