From: unobe@cpan.org
To: 9fans@9fans.net
Subject: Re: [9fans] Prompt for wpapsk during wifi boot
Date: Wed, 14 Jun 2023 10:28:56 -0700 [thread overview]
Message-ID: <2583BECD003EEDE14CC9D2CF2ABAC100@smtp.pobox.com> (raw)
In-Reply-To: <2e32d690b4641591812e246aa6bd7bf6043bf78f.camel@ck-weine.ch>
Quoth Luis <luis@ck-weine.ch>:
> On Wed, 2023-06-14 at 10:30 -0400, Stanley Lieber wrote:
> > not sure what other problems there may be, but make sure essid
> > appears on the same line as ether0.
> >
> > sl
>
> Ok, Thanks. The Problem does persist with essid= on the same line as
> ether0=.
I recall having issues as well with this. My current plan9.ini uses
the bssid= rather than the essid= for the wireless network I'm
connecting to, but I don't think it does anything because in my user's
profile I run a script to connect to wifi *after* I start up factotum:
% cat /bin/wifi/auth
#!/bin/rc
if (~ $ether '')
ether=`{cd /net; ls -d ether*}
for (e in $ether ) {
if (grep -s 'status: need authentication' /net/$e/ifstats) {
essid=`{grep '^essid: ' /net/$e/ifstats | sed 's/essid: //'}
if (grep -s 'essid=.*'^$"essid /mnt/factotum/ctl) {
aux/wpa /net/$e
ip/ipconfig ether /net/$e
}
if not echo 'No factotum key found for essid:'^$"essid >[1=2]
}
}
So the wpapsk= probably didn't work for my situation or I didn't know
how to wield it. If either of those was the case, perhaps I didn't
want to type the password each time and I was okay with waiting for my
profile to be run.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tf639303c48fd1149-M7667a918367e5a13ff8c9353
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-06-14 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 14:18 Luis
2023-06-14 14:30 ` Stanley Lieber
2023-06-14 16:26 ` Luis
2023-06-14 17:28 ` unobe [this message]
2023-06-14 18:35 ` 9johansen via 9fans
2023-06-14 18:38 ` unobe
2023-06-14 18:50 ` Luis
2023-06-14 18:58 ` unobe
2023-06-14 19:02 ` mkf9
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=2583BECD003EEDE14CC9D2CF2ABAC100@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=9fans@9fans.net \
/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).