Thanks, Tomas. Those commands, and the commands that a couple of handy AI bots suggested, all return expected results. The wpasupplicant package was the only package with a networking scent that was updated at the time of the regression so I've reported the following:
Bug#1152058: wpasupplicant: Wifi can't connect after recent forky update Fingers crossed that the bug can be easily found. And fixed. <[email protected]> wrote: > On Sat, Oct 24, 2026 at 03:03:45PM -0700, Bill Wohler wrote: > > My wifi won't connect to my router after I performed my weekly update to my > > forky system. I was able > > to connect after I turned off the MAC filter on my router. > > > > Is something broken with the system, or is my MAC address now being > > randomized and I have to take > > action to make it stop doing that (on my home network). > > You can verify that by issuing "ip link show" > > (setting it would be "ip link set dev <device> address <mac-addr>") > > > I tried setting the network's Identify > Cloned Address to both preserve > > and permanent to no avail. > > Hm. This is probably NetwokManager foo. I'm not familiar with that, > so I'll leave to others to chime in. > > Cheers > -- > t -- Bill Wohler <[email protected]> aka <[email protected]> http://www.newt.com/wohler/, GnuPG ID:610BD9AD
