9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Unsubscribe
Date: Fri, 2 Oct 2015 12:50:22 +0200	[thread overview]
Message-ID: <aec2616be99127e2d548ff749bcf3577@felloff.net> (raw)
In-Reply-To: <CAN4ARwTtbd3xfeaHDTo7=xXCNwFk7Eg6LB4vGAsA7zHzAoozEw@mail.gmail.com>

>> If I try authenticating with `aux/wpa -1 -s itsatrap -p

we do support wpa2, i see no reason why we would need to
force us to wpa1. i'd suggest the following setup to
debug this:

make a rio window, run cat /dev/kprint in it so we get kernel
debug output.

in another window, do bind '#l1' /net, then enable debugging
of the kernel wifi stack with: echo debug > /net/ether1/clone
you should see "#l1: debug 1" print in the kernel print window.

then run: aux/wpa -p -d -s itsatreap /net/ether1, this will
prompt for the password first. if you have the key already 
in factotum, you can leave out the -p option.

the -1 and -2 options are not really needed anymore as the
kernel puts the rsne element from the beacon in the status
file which allows wpa to figure out what protocol is used.

anyway, i'm interested in seeing the full kernel prints from
the first window and the debug output of aux/wpa.


  parent reply	other threads:[~2015-10-02 10:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  7:03 Unsubscribe Brian Vito
2015-10-02  7:11 ` [9front] Unsubscribe David Lind
2015-10-02  7:27   ` Unsubscribe Brian Vito
2015-10-02 10:50   ` cinap_lenrek [this message]
2015-10-02 14:34     ` [9front] Unsubscribe David Lind
     [not found] <B0DA0ABD-6EE9-4574-8404-23AA5E8EFDE0.ref@yahoo.com>
2022-10-17 10:08 ` Boris Ashkinazi
  -- strict thread matches above, loose matches on Subject: below --
2022-10-17  5:49 [9front] unsubscribe Rickard Bremer
2014-05-04 10:48 unsubscribe juef
2014-05-04 14:36 ` [9front] unsubscribe Kurt H Maier
2014-05-04 14:43   ` tony

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aec2616be99127e2d548ff749bcf3577@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.org \


* 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).