You are not logged in.

#1 2024-02-28 23:15:16

slime
Member
Registered: 2024-02-28
Posts: 2

[SOLVED]Wifi card is stuck 'configuring' and can't connect to internet

Hello, this is my first time asking for help after about a week and a half of playing with my new/first install. It's been slow but sure progress, but I've encountered something I can't seem to get through.

I'm trying to just use systemd-networkd and systemd-resolved for network configuration. I was connected for a few days without issue, but despite my studying I still wasn't 100% confident on how it was working, and today it has broken down on me.

In the beginning I needed to get my broadcom drivers setup, as I'm installing on a Macbook Air 2013. I got the dkms drivers and wpa_supplicant config setup, and the wifi card was visible + routable. However, I was getting temporary name resolution errors when trying to ping google.
I kept poking around trying my best to figure out if I was doing something with resolved incorrectly, but I found nothing. It kept saying that resolved's DNS should work out of the box for most things, but that you can also make a link of the stub-resolv.conf in /etc/ and manually specify DNS servers in /etc/systemd/resolved.conf.d/dns_servers.conf (which I did). Regardless of all of this, nothing would work.

Then, I found a comment that suggested running dhcpcd link_name. After that, I was connected! But, I honestly don't know what made it work afterwards. After analyzing, my conclusion was that it wrote some DNS goodness to my /ect/resolv.conf file and that made everything work smoothly.

Fast forward to now, I just opened my laptop and discovered I wasn't connected. I tried to run dhcpcd link_name again as a fix, but it said there were no ipv6 routers available. So, I decided to try to reset and get connected with just systemd-networkd and systemd-resolved again. I restarted networkd and resolved, made sure dhcpcd wasn't running, overwrote /etc/resolv.conf with the stub-resolv.conf again, and finally rebooted for good measure.

Now, when I look at my network devices, I see that my card is being "configured" indefinitely. Pinging anything besides localhost is impossible, as networks are unreachable now. Here are some files I think would be relevant, and please ask me to post anything else.

I'm trying to solidify my relationship of what's going on here so I can troubleshoot better in the future. From what I see in the status logs, nothing is going awry (the link goes down and up because I was hoping by resetting it, it would start working hahahaha) but I could be wrong; and the stub-resolv.conf isn't supposed to be edited and should be used as is, so I'm at a loss. Can someone maybe help re-word the relationship between these three pieces of software to help me understand?

command results:
networkctl

IDX LINK   TYPE     OPERATIONAL SETUP
  1 lo     loopback carrier     unmanaged
  2 wlp3s0 wlan     degraded    configuring

2 links listed.

cat /etc/systemd/network/25-wireless.network

[Match]
Name=wlp3s0

[Network]
DHCP=yes
IgnoreCarrierLoss=3s

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 34:36:3b:85:b1:70 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3636:3bff:fe85:b170/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever

network -a status (just output for this link though)

● 2: wlp3s0
                   Link File: /usr/lib/systemd/network/99-default.link
                Network File: /etc/systemd/network/25-wireless.network
                       State: degraded (configuring)
                Online state: online
                        Type: wlan
                        Path: pci-0000:03:00.0
                      Driver: wl0
                      Vendor: Broadcom Inc. and subsidiaries
                       Model: BCM4360 802.11ac Dual Band Wireless Network Adapter
            Hardware Address: 34:36:3b:85:b1:70 (Apple, Inc.)
                         MTU: 1500 (min: 68, max: 1500)
                       QDisc: fq_codel
IPv6 Address Generation Mode: eui64
          Wi-Fi access point: (null) (00:00:00:00:00:00)
    Number of Queues (Tx/Rx): 1/1
                     Address: fe80::3636:3bff:fe85:b170
           Activation Policy: up
         Required For Online: yes
           DHCP6 Client DUID: DUID-EN/Vendor:0000ab11eca31d2315a09006

Feb 28 16:10:21 air systemd-networkd[258]: wlp3s0: Configuring with /etc/systemd/network/25-wireless.network.
Feb 28 16:10:21 air systemd-networkd[258]: wlp3s0: Link UP
Feb 28 16:10:21 air systemd-networkd[258]: wlp3s0: Gained carrier
Feb 28 16:10:23 air systemd-networkd[258]: wlp3s0: Gained IPv6LL
Feb 28 16:13:56 air systemd-networkd[258]: wlp3s0: Link DOWN
Feb 28 16:13:56 air systemd-networkd[258]: wlp3s0: Lost carrier
Feb 28 16:13:59 air systemd-networkd[258]: wlp3s0: DHCPv6 lease lost
Feb 28 16:15:45 air systemd-networkd[258]: wlp3s0: Link UP
Feb 28 16:15:45 air systemd-networkd[258]: wlp3s0: Gained carrier
Feb 28 16:15:47 air systemd-networkd[258]: wlp3s0: Gained IPv6LL

systemctl status systemd-networkd

● systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
     Active: active (running) since Wed 2024-02-28 18:46:07 EST; 6min ago
TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
             man:org.freedesktop.network1(5)
   Main PID: 255 (systemd-network)
     Status: "Processing requests..."
      Tasks: 1 (limit: 4560)
   FD Store: 0 (limit: 512)
     Memory: 3.3M (peak: 3.7M)
        CPU: 110ms
     CGroup: /system.slice/systemd-networkd.service
             └─255 /usr/lib/systemd/systemd-networkd

Feb 28 18:46:07 air systemd[1]: Starting Network Configuration...
Feb 28 18:46:07 air systemd-networkd[255]: lo: Link UP
Feb 28 18:46:07 air systemd-networkd[255]: lo: Gained carrier
Feb 28 18:46:07 air systemd-networkd[255]: Enumeration completed
Feb 28 18:46:07 air systemd[1]: Started Network Configuration.
Feb 28 18:46:08 air systemd-networkd[255]: wlan0: Interface name change detected, renamed to wlp3s0.
Feb 28 18:46:08 air systemd-networkd[255]: wlp3s0: Configuring with /etc/systemd/network/25-wireless.network.
Feb 28 18:46:08 air systemd-networkd[255]: wlp3s0: Link UP
Feb 28 18:46:08 air systemd-networkd[255]: wlp3s0: Gained carrier
Feb 28 18:46:09 air systemd-networkd[255]: wlp3s0: Gained IPv6LL

Thank you so much in advance for your help! This forum has already been of great assistance to get me this far.

EDIT:
I figured it out, I can't believe I didn't see this earlier!
I decided to look at the list of network managers again and realized that systemd-networkd does not have wireless authentication... Duh! When I restarted my laptop I had failed to run wpa_supplicant again, and my wifi card said it was being "configured" because it was waiting on me to authenticate it. Lesson learned, I'll need that command to run upon boot!

Last edited by slime (2024-02-29 00:09:50)

Offline

Board footer

Powered by FluxBB