From: KeithG <ys3al35l@gmail.com>
To: iwd@lists.linux.dev
Subject: wifi disconnects periodically
Date: Fri, 26 May 2023 07:56:50 -0500 [thread overview]
Message-ID: <CAG17S_Nrg_PCVFR1UZLROME+TuKy5_3N=JgfBkLF2cpZaiaTVw@mail.gmail.com> (raw)
I recently changed from Arch Linux on my Pis to now using RaspiOS
bullseye. I have noticed that, periodically, I get a disconnect from
my AP. I am not completely certain that this is it, but the journal
shows this at the time I think it lost connection:
May 26 07:23:47 kitchenrune dbus-daemon[308]: [system] Activating via
systemd: service name='org.freedesktop.timedate1'
unit='dbus-org.freedesktop.timedate1.service' requested by ':1.49134'>
May 26 07:23:47 kitchenrune systemd[1]: Starting Time & Date Service...
May 26 07:23:48 kitchenrune dbus-daemon[308]: [system] Successfully
activated service 'org.freedesktop.timedate1'
May 26 07:23:48 kitchenrune systemd[1]: Started Time & Date Service.
May 26 07:23:48 kitchenrune systemd-resolved[13100]: Failed to emit
notification about changed property CurrentDNSServer: Transport
endpoint is not connected
May 26 07:23:48 kitchenrune systemd[1]: Stopping Network Name Resolution...
May 26 07:23:48 kitchenrune systemd[1]: systemd-resolved.service: Succeeded.
May 26 07:23:48 kitchenrune systemd[1]: Stopped Network Name Resolution.
May 26 07:23:48 kitchenrune systemd[1]: Starting Network Name Resolution...
May 26 07:23:48 kitchenrune systemd-resolved[17192]: Positive Trust Anchors:
May 26 07:23:48 kitchenrune systemd-resolved[17192]: . IN DS 20326 8 2
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
May 26 07:23:48 kitchenrune systemd-resolved[17192]: Negative trust
anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa
18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.a>
May 26 07:23:48 kitchenrune systemd-resolved[17192]: Using system
hostname 'kitchenrune'.
May 26 07:23:48 kitchenrune systemd[1]: Started Network Name Resolution.
May 26 07:24:18 kitchenrune systemd[1]: systemd-timedated.service: Succeeded.
May 26 07:25:44 kitchenrune iwd[313]: wiphy_estimate_data_rate() failed
May 26 07:25:44 kitchenrune iwd[313]: wiphy_estimate_data_rate() failed
May 26 07:25:44 kitchenrune iwd[313]: wiphy_estimate_data_rate() failed
May 26 07:28:01 kitchenrune kernel: nfs: server 192.168.2.253 not
responding, timed out
(and I cannot connect to my NFS share)
I am running a custom built iwd version 2.4 and ell 0.56 with custom
built connman 1.41
What was going on when it lost connection:
I was listening to an internet stream and it stopped playing. When it
did, I was no longer able to ping nor ssh into the pi. I was able to
get it to reconnect to my local LAN by restarting the AP radio on the
router.
I am not aware of this happening like this before. Any ideas on what I
can check?
Keith
next reply other threads:[~2023-05-26 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 12:56 KeithG [this message]
2023-05-26 14:12 ` wifi disconnects periodically James Prestwood
2023-05-26 15:03 ` KeithG
2023-05-26 15:04 ` James Prestwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG17S_Nrg_PCVFR1UZLROME+TuKy5_3N=JgfBkLF2cpZaiaTVw@mail.gmail.com' \
--to=ys3al35l@gmail.com \
--cc=iwd@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).