From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] wifi
Date: Fri, 24 Jan 2020 10:21:53 -0500 [thread overview]
Message-ID: <E7D6AD8B-F1A5-4B1D-B650-CA1582DE938F@stanleylieber.com> (raw)
In-Reply-To: <CAFSF3XMY3VRgH57nd8XT-YV-nmaWbmn3s8KoRsb+LkEYWL8KXw@mail.gmail.com>
On January 24, 2020 5:03:01 AM EST, hiro <23hiro@gmail.com> wrote:
>sl: i'm surprised to hear you have multiple times the same bssid on
>different channels. that sounds non-standard, too and if you can turn
>that off it might help indeed.
sorry, I meant essid.
I had fiber gigabit internet installed, along with a much needed isp-provided wifi repeater. they recommended setting both 2ghz and 5ghz channels in my isp-provided router/ap to the same essid, and the repeater mirrors those essids, for a grand total of three separate channels using the same essid (for some reason the 5ghz channel on the repeater uses the same channel as the 5ghz on the router/ap, but the 2ghz does not). at the other end of my house where 9front is located, signal strength from the router/ap is weak but works, and signal strength from the repeater is strong.
ever since this was all setup, my local 9front (which uses said wifi) has started freezing/dropping incoming rcpu sessions. incoming rcpu -p can only rarely complete a connection at all. rcpu without -p can usually connect, but suffers accordingly. making and sustaining connections to this machine was never a problem before.
seemed logical to start by asking questions only about the recent changes on my network that coincided with the observed trouble. machine's most recent sysupdate is only a few days ago, but I don't recall any recent wifi changes.
sysinfo: http://okturing.com/src/7656/body
obviously, i'm not a wifi expert. maybe i'm barking up the wrong tree.
sl
next prev parent reply other threads:[~2020-01-24 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 18:29 wifi Stanley Lieber
2020-01-23 21:25 ` [9front] wifi hiro
2020-01-23 21:49 ` Stanley Lieber
2020-01-23 21:53 ` Kurt H Maier
2020-01-24 10:03 ` hiro
2020-01-24 15:21 ` Stanley Lieber [this message]
2020-01-24 18:27 ` hiro
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=E7D6AD8B-F1A5-4B1D-B650-CA1582DE938F@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/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 NNTP newsgroup(s).