From: Josh Pritsker <email@example.com>
Subject: Re: [9front] WPA2 on 7260
Date: Tue, 15 Nov 2022 17:42:33 +0000 [thread overview]
Message-ID: <2cNGULSiqAYhDKvy2NHc_EsRpuqtZAsNN1RuofYQJIp_YwrNMLtcokl-rRrj8MEYyuFAb1OSjUsz4EETfMmHZFjQF3Q5gHKq3Epuxih4cJ4firstname.lastname@example.org> (raw)
Sorry, which log are you asking for?
With the default WPA it doesn't ask for a password, then fails once I try to `ipconfig ether /net/ether1`
~ Joshua Pritsker
Sent with Proton Mail secure email.
------- Original Message -------
On Monday, November 14th, 2022 at 11:15 PM, <email@example.com> wrote:
> Quoth Josh Pritsker firstname.lastname@example.org:
> > Hello,
> > I've been trying to get 9front working on a Sony Vaio P. I got an Intel AC7260 for WiFi. Everything seems to work fine, but I can't connect to my WPA2 home network. However, I can connect to the open network from a local coffee shop.
> > When I run `aux/wpa -p2 -s 'WiFi-Network' /net/ether1`, after a second I get an error of `aux/wpa: write auth: missing node`
> > `-d` gives `rsne:` and then a long hex string before the missing node error
> > Putting ether1 in debug mode gives me `wifictl: auth` and then the same hex string when the error occurs
> > Adding the password ahead of time with factotum and using only `-2`, I get `can't flush queue 0: flushq: timeout` in the kernel console when adding, and then `ipconfig: no success with DHCP` when trying to initiate it.
> > Has anyone had a similar issue or does anyone have any suggestions for how to address this?
> > Thanks,
> > ~ Joshua Pritsker
> can you put in a full paste of the log?
> have you tried with the default wpa? (no -2)?
next prev parent reply other threads:[~2022-11-15 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 15:01 Josh Pritsker
2022-11-15 4:15 ` ori
2022-11-15 17:42 ` Josh Pritsker [this message]
2022-11-15 22:21 ` Josh Pritsker
2022-11-21 12:21 ` hiro
2022-11-23 15:55 ` kemal
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).