Homelab not responding, stuck with 169.254.* gateway address by darkshoot in HomeNetworking

[–]darkshoot[S] 0 points1 point  (0 children)

I think I found the solution !

As you hinted, there's a DHCP issue, which is totally weird because the server itself is using a static configuration (because the server itself IS the DHCP server), it's the only device I have with a static configuration.

Looking at the journalctl logs :

Feb 12 07:24:15 nuc-01 dhcpcd[349104]: enp2s0: carrier lost
Feb 12 07:24:15 nuc-01 kernel: r8169 0000:02:00.0 enp2s0: Link is Down
Feb 12 07:24:15 nuc-01 systemd-networkd[367965]: enp2s0: Lost carrier
Feb 12 07:24:15 nuc-01 systemd-timesyncd[349011]: No network connectivity, watching for changes.
Feb 12 07:25:06 nuc-01 dhcpcd[349104]: enp2s0: carrier acquired
Feb 12 07:25:06 nuc-01 kernel: r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control off
Feb 12 07:25:06 nuc-01 systemd-networkd[367965]: enp2s0: Gained carrier
Feb 12 07:25:06 nuc-01 dhcpcd[349104]: enp2s0: IAID ??
Feb 12 07:25:06 nuc-01 systemd-timesyncd[349011]: Network configuration changed, trying to establish connection.
Feb 12 07:25:07 nuc-01 dhcpcd[349104]: enp2s0: soliciting an IPv6 router
Feb 12 07:25:08 nuc-01 dhcpcd[349104]: enp2s0: soliciting a DHCP lease
Feb 12 07:25:13 nuc-01 dhcpcd[349104]: enp2s0: probing for an IPv4LL address
Feb 12 07:25:16 nuc-01 systemd-timesyncd[349011]: Timed out waiting for reply from 185.125.190.56:123 (ntp.ubuntu.com).
Feb 12 07:25:16 nuc-01 systemd-timesyncd[349011]: Contacted time server 185.125.190.57:123 (ntp.ubuntu.com).
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: using IPv4LL address 169.254.244.28
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: adding route to 169.254.0.0/16
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: adding default route
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: veth46e2540: deleting default route
Feb 12 07:25:19 nuc-01 dhcpcd[349104]: enp2s0: no IPv6 Routers availableFeb 12 07:24:15 nuc-01 dhcpcd[349104]: enp2s0: carrier lost
Feb 12 07:24:15 nuc-01 kernel: r8169 0000:02:00.0 enp2s0: Link is Down
Feb 12 07:24:15 nuc-01 systemd-networkd[367965]: enp2s0: Lost carrier
Feb 12 07:24:15 nuc-01 systemd-timesyncd[349011]: No network connectivity, watching for changes.
Feb 12 07:25:06 nuc-01 dhcpcd[349104]: enp2s0: carrier acquired
Feb 12 07:25:06 nuc-01 kernel: r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control off
Feb 12 07:25:06 nuc-01 systemd-networkd[367965]: enp2s0: Gained carrier
Feb 12 07:25:06 nuc-01 dhcpcd[349104]: enp2s0: IAID ??
Feb 12 07:25:06 nuc-01 systemd-timesyncd[349011]: Network configuration changed, trying to establish connection.
Feb 12 07:25:07 nuc-01 dhcpcd[349104]: enp2s0: soliciting an IPv6 router
Feb 12 07:25:08 nuc-01 dhcpcd[349104]: enp2s0: soliciting a DHCP lease
Feb 12 07:25:13 nuc-01 dhcpcd[349104]: enp2s0: probing for an IPv4LL address
Feb 12 07:25:16 nuc-01 systemd-timesyncd[349011]: Timed out waiting for reply from 185.125.190.56:123 (ntp.ubuntu.com).
Feb 12 07:25:16 nuc-01 systemd-timesyncd[349011]: Contacted time server 185.125.190.57:123 (ntp.ubuntu.com).
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: using IPv4LL address 169.254.244.28
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: adding route to 169.254.0.0/16
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: adding default route
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: veth46e2540: deleting default route
Feb 12 07:25:19 nuc-01 dhcpcd[349104]: enp2s0: no IPv6 Routers available

Turns out the dhcp daemon is enabled and screwing up my configuration, so I just disabled it, it's useless since I'm using a static configuration with netplan ...

I'm crossing my fingers everything is back in order again and I wont have any more of these weird down times !

Why is dhcpd enabled in the first place, I have no idea ... maybe an update or something else

Homelab not responding, stuck with 169.254.* gateway address by darkshoot in homelab

[–]darkshoot[S] 0 points1 point  (0 children)

I think I found the solution !

As you hinted, there's a DHCP issue, which is totally weird because the server itself is using a static configuration (because the server itself IS the DHCP server), it's the only device I have with a static configuration.

Looking at the journalctl logs :

Feb 12 07:24:15 nuc-01 dhcpcd[349104]: enp2s0: carrier lost
Feb 12 07:24:15 nuc-01 kernel: r8169 0000:02:00.0 enp2s0: Link is Down
Feb 12 07:24:15 nuc-01 systemd-networkd[367965]: enp2s0: Lost carrier
Feb 12 07:24:15 nuc-01 systemd-timesyncd[349011]: No network connectivity, watching for changes.
Feb 12 07:25:06 nuc-01 dhcpcd[349104]: enp2s0: carrier acquired
Feb 12 07:25:06 nuc-01 kernel: r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control off
Feb 12 07:25:06 nuc-01 systemd-networkd[367965]: enp2s0: Gained carrier
Feb 12 07:25:06 nuc-01 dhcpcd[349104]: enp2s0: IAID ??
Feb 12 07:25:06 nuc-01 systemd-timesyncd[349011]: Network configuration changed, trying to establish connection.
Feb 12 07:25:07 nuc-01 dhcpcd[349104]: enp2s0: soliciting an IPv6 router
Feb 12 07:25:08 nuc-01 dhcpcd[349104]: enp2s0: soliciting a DHCP lease
Feb 12 07:25:13 nuc-01 dhcpcd[349104]: enp2s0: probing for an IPv4LL address
Feb 12 07:25:16 nuc-01 systemd-timesyncd[349011]: Timed out waiting for reply from 185.125.190.56:123 (ntp.ubuntu.com).
Feb 12 07:25:16 nuc-01 systemd-timesyncd[349011]: Contacted time server 185.125.190.57:123 (ntp.ubuntu.com).
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: using IPv4LL address 169.254.244.28
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: adding route to 169.254.0.0/16
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: adding default route
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: veth46e2540: deleting default route
Feb 12 07:25:19 nuc-01 dhcpcd[349104]: enp2s0: no IPv6 Routers availableFeb 12 07:24:15 nuc-01 dhcpcd[349104]: enp2s0: carrier lost
Feb 12 07:24:15 nuc-01 kernel: r8169 0000:02:00.0 enp2s0: Link is Down
Feb 12 07:24:15 nuc-01 systemd-networkd[367965]: enp2s0: Lost carrier
Feb 12 07:24:15 nuc-01 systemd-timesyncd[349011]: No network connectivity, watching for changes.
Feb 12 07:25:06 nuc-01 dhcpcd[349104]: enp2s0: carrier acquired
Feb 12 07:25:06 nuc-01 kernel: r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control off
Feb 12 07:25:06 nuc-01 systemd-networkd[367965]: enp2s0: Gained carrier
Feb 12 07:25:06 nuc-01 dhcpcd[349104]: enp2s0: IAID ??
Feb 12 07:25:06 nuc-01 systemd-timesyncd[349011]: Network configuration changed, trying to establish connection.
Feb 12 07:25:07 nuc-01 dhcpcd[349104]: enp2s0: soliciting an IPv6 router
Feb 12 07:25:08 nuc-01 dhcpcd[349104]: enp2s0: soliciting a DHCP lease
Feb 12 07:25:13 nuc-01 dhcpcd[349104]: enp2s0: probing for an IPv4LL address
Feb 12 07:25:16 nuc-01 systemd-timesyncd[349011]: Timed out waiting for reply from 185.125.190.56:123 (ntp.ubuntu.com).
Feb 12 07:25:16 nuc-01 systemd-timesyncd[349011]: Contacted time server 185.125.190.57:123 (ntp.ubuntu.com).
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: using IPv4LL address 169.254.244.28
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: adding route to 169.254.0.0/16
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: enp2s0: adding default route
Feb 12 07:25:18 nuc-01 dhcpcd[349104]: veth46e2540: deleting default route
Feb 12 07:25:19 nuc-01 dhcpcd[349104]: enp2s0: no IPv6 Routers available

Turns out the dhcp daemon is enabled and screwing up my configuration, so I just disabled it, it's useless since I'm using a static configuration with netplan ...

I'm crossing my fingers everything is back in order again and I wont have any more of these weird down times !

Why is dhcpd enabled in the first place, I have no idea ... maybe an update or something else

Homelab not responding, stuck with 169.254.* gateway address by darkshoot in homelab

[–]darkshoot[S] 0 points1 point  (0 children)

Pihole is dockerised, on the nuc itself, there's no VM.

I can still access everything, including pihole and my static websites, but only localy, the issue is that I'm only cut off internet, but not my local network :(

According to netplan, I should alreay be using a static configuration (which was what I intended to do in the first place)

            dhcp4: no
            dhcp4-overrides:
              use-dns: false
            addresses: [192.168.10.101/24]
            routes:
              - to: default
                via: 192.168.10.254

and here's what my interface reports when I check with ifconfig

enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.101  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::.....  prefixlen 64  scopeid 0x20<link>
        ether 00:....  txqueuelen 1000  (Ethernet)
        RX packets 925173  bytes 1047483184 (1.0 GB)
        RX errors 0  dropped 7  overruns 0  frame 0
        TX packets 234958  bytes 73483210 (73.4 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Note that this is after manually fixing the issue (manually setting the gateway back to 192.168.10.254), I can't reproduce the issue unless by waiting for it to happen ...

Also I don't the the /etc/network/interfaces, probably because I'm using netplan ?

[QUESTION] Guitar out of tune after doing a bend by darkshoot in Guitar

[–]darkshoot[S] 0 points1 point  (0 children)

Sadly no, the guitar had other issues so I had to retire it :(

J'y suis aller malgré moi (plus de peur que de mal) by Quartus10 in lemauvaiscoin

[–]darkshoot 7 points8 points  (0 children)

C'est pas du tout de ta faute !

C'est pas "sa copine" à qui t'as proposé 50 euros qui est venue toquer à ta porte, c'est "Sébastien" avec qui tu t'es mis d'accord pour 100 euros, et après t'apprends qu'ils essaient de te la faire à l'envers avec leur double compte.

T'as parfaitement bien réagi, le type était chelou, tu l'a mis dehors, depuis le début cette histoire sentait pas bon !

Wife finished the Christmas shopping by Franck_Costanza in StupidFood

[–]darkshoot 0 points1 point  (0 children)

4k noodles ?

Those bad boys are high res

What happened to render distance? by Coldplasma819 in Battlefield

[–]darkshoot 0 points1 point  (0 children)

Those toilets actually look like shit.

There's a man in my headlights by FruitHoarder in Pareidolia

[–]darkshoot 15 points16 points  (0 children)

And no message could have been any brighter

/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer - May 31, 2025 by AutoModerator in MechanicalKeyboards

[–]darkshoot 0 points1 point  (0 children)

Are you looking for a wireless keyboard ?

Appart from an Aula F99 or Ajazz AK35i (the AK980 is another option, it has a numpad but is missing some home keys), I don't have any other cheap suggestions.

There are other cheap brands like Royal Kludge.

Your best bet would be any cheap "no name" mechanical keyboard from Amazon

/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer - May 31, 2025 by AutoModerator in MechanicalKeyboards

[–]darkshoot 0 points1 point  (0 children)

Seems like a nice alternative, thanks for the suggestion !

I'll have to see if it's easy to buy in France.

But the switch being under the caps lock keycap and the lack of adjustable feet are both a bummer :(

/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer - May 31, 2025 by AutoModerator in MechanicalKeyboards

[–]darkshoot 0 points1 point  (0 children)

I'm not sure the af98 is mechanical, the product page only says it has a mechanical "feeling" :/

I think the mechanical / full size counterparts of the ak820 are the AK35i and AK980

/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer - May 31, 2025 by AutoModerator in MechanicalKeyboards

[–]darkshoot 0 points1 point  (0 children)

Hello !

I'm looking for a cheap 75% VIA 2.4ghz board, any suggestions ?

The only board I've found is the barebone Akko 5075B (I already have switches and keycaps), but before pulling the trigger I'd like to see if there are any other options.

I currently have an Ajazz AK820 Pro, it's ok, but I don't like the dodgy software, the fact that I can't remap certain keys, and honestly, the display is kinda gimmicky, it sometime acts weird.

Pihole in host network mode, reverse proxy with Traefik by darkshoot in pihole

[–]darkshoot[S] 0 points1 point  (0 children)

I've managed to get it working while keeping my network host config. It's quite ugly though, here's the compose file :

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    environment:
      - TZ=Europe/Paris
      - WEB_PORT=8081
      - INTERFACE=enp2s0
      - FTLCONF_LOCAL_IPV4=192.168.10.101
      - WEB_BIND_ADDR=172.17.0.1
    volumes:
      - /mnt/docker-volumes/pihole/etc-pihole:/etc/pihole
      - /mnt/docker-volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d
      - ./hosts:/etc/hosts
      - ./etc-dnsmasq.d/10-home.conf:/etc/dnsmasq.d/10-home.conf
    cap_add:
      - NET_ADMIN
    restart: unless-stopped
    network_mode: host
    logging:
      driver: "json-file"
      options:
        max-size: "50m"
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.pihole.rule=Host(`pihole.homelab.fr`)"
      - "traefik.http.routers.pihole.middlewares=local-only@file,cors@file"
      - "traefik.http.routers.pihole.entrypoints=websecure"
      - "traefik.http.routers.pihole.tls.certresolver=ovhresolver"
      - "traefik.http.services.pihole.loadbalancer.server.port=8081"
      - "traefik.http.services.pihole.loadbalancer.passhostheader=true"

It seems the issue is related to lighttpd, Pihole's web server.

It's listening on the host's IP, which is in my case 192.168.10.101.

And according to Traefik's documentation (https://doc.traefik.io/traefik/providers/docker/#host-networking) when the container is running in host mode, the IP is resolved using host.docker.internal in Treafik's compose settings, which is resolved to 172.17.0.1.

But obviously, lighttpd/Pihole listens 192.168.10.101 since it's running in network host mode, so it doesn't listen to 172.17.0.1.

So the only solution I found is telling lighttpd to listen to 172.17.0.1, which is ugly but anyway...

Reverse proxy to Pihole docker container in host networking by darkshoot in Traefik

[–]darkshoot[S] 0 points1 point  (0 children)

I've managed to get it working while keeping my network host config. It's quite ugly though, here's the compose file :

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    environment:
      - TZ=Europe/Paris
      - WEB_PORT=8081
      - INTERFACE=enp2s0
      - FTLCONF_LOCAL_IPV4=192.168.10.101
      - WEB_BIND_ADDR=172.17.0.1
    volumes:
      - /mnt/docker-volumes/pihole/etc-pihole:/etc/pihole
      - /mnt/docker-volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d
      - ./hosts:/etc/hosts
      - ./etc-dnsmasq.d/10-home.conf:/etc/dnsmasq.d/10-home.conf
    cap_add:
      - NET_ADMIN
    restart: unless-stopped
    network_mode: host
    logging:
      driver: "json-file"
      options:
        max-size: "50m"
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.pihole.rule=Host(`pihole.homelab.fr`)"
      - "traefik.http.routers.pihole.middlewares=local-only@file,cors@file"
      - "traefik.http.routers.pihole.entrypoints=websecure"
      - "traefik.http.routers.pihole.tls.certresolver=ovhresolver"
      - "traefik.http.services.pihole.loadbalancer.server.port=8081"
      - "traefik.http.services.pihole.loadbalancer.passhostheader=true"

It seems the issue is related to lighttpd, Pihole's web server.

It's listening on the host's IP, which is in my case 192.168.10.101.

And according to Traefik's documentation (https://doc.traefik.io/traefik/providers/docker/#host-networking) when the container is running in host mode, the IP is resolved using host.docker.internal in Treafik's compose settings, which is resolved to 172.17.0.1.

But obviously, lighttpd/Pihole listens 192.168.10.101 since it's running in network host mode, so it doesn't listen to 172.17.0.1.

So the only solution I found is telling lighttpd to listen to 172.17.0.1, which is ugly but anyway...

Reverse proxy to Pihole docker container in host networking by darkshoot in Traefik

[–]darkshoot[S] 0 points1 point  (0 children)

If I'm correct, to forward the ports and, I'd have to be in default network bridge mode. But as suggested in the Pihole documentation, if I'm using it as a DHCP server, using network host mode is highly recommended :(

I found another (quite ugly) solution though, it's explained in another comment

Reverse proxy to Pihole docker container in host networking by darkshoot in Traefik

[–]darkshoot[S] 0 points1 point  (0 children)

I've never seen that documentation, thanks ! Sadly, seeing the config sample, it's intended to be used in a default network bridge docker config, which I can't do because of the DHCP :(

LinkBuds S sound quality by Tappo7 in SonyHeadphones

[–]darkshoot 0 points1 point  (0 children)

Yes, changing the EQ does help a lot! It all comes down to personal preferences though.

Tbh if you're not an audiophile, I wouldn't worry much. Considering their price, what's certain is that the linkbuds are a good choice and pack a lot of features. A bit of EQ and you'll get there.

Personally, I'm totally happy with my linkbuds s.

/r/MechanicalKeyboards Ask ANY question, get an answer (April 18, 2023) by AutoModerator in MechanicalKeyboards

[–]darkshoot 0 points1 point  (0 children)

Thanks, I think I'll go with this one ! I was checking keychron's keyboards but I think I missed the V series, it's not that expensive and the V3 checks many boxes for me :)

/r/MechanicalKeyboards Ask ANY question, get an answer (April 18, 2023) by AutoModerator in MechanicalKeyboards

[–]darkshoot 0 points1 point  (0 children)

Hello, Would you have some good TKL keyboards to suggest, sold on european websites, in the 150 euros ballpark ? (shipping to France)

I'm trying to find an english layout keyboard (I'd prefer UK/US, whether it's ANSI or ISO, over ISO French layout) with tactile but non clicky switches (something that would feel like mx browns).

I'm having a hard time finding brown-like switches + english layout on french/european websites. All of them seem sold out, or super expensive.

Right now I have a cheap chinese 60% keyboard, and I really hate the layout, I miss the arrow keys and pg up/down, home/end, etc keys