From: Chris Gorman <chrisjohgorman@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Wifi setup in plan9.ini fails to work, need to run commands by hand
Date: Fri, 25 Nov 2022 16:10:29 -0500 [thread overview]
Message-ID: <CAHVeOW_KBKJbzmx02b4=rF7HfcAXqwhg0orTtF-g=Y-MiAy7Cw@mail.gmail.com> (raw)
In-Reply-To: <CABO6shfHrf-1NaX5cRMyg_nSuLDPD-zpSe1ikkXC+Kq52ZswQA@mail.gmail.com>
On Fri, Nov 25, 2022 at 3:29 PM kemal <kemalinanc8@gmail.com> wrote:
> if i understand correctly, the boot script isn't running aux/wpa...
> maybe we could try moving the wifi card to ether0
>
> ether0=type=iwl essid=ESSID
> wpapsk=PASS
This prevents the server from working properly. I have to connect a
keyboard, monitor and mouse to it in order to copy a working plan9.ini
in place.
> no but it would be helpful to change that mac address so your cpu+auth setup
> continues to work. you can obtain the mac address from /net/etherN/addr
> (N being the interface number).
I'm probably not explaining myself well, sorry. The
ether=989096aad5d5 is the mac address for the wired interface and the
mac address for the wifi is ether=6057181042fd. I would like both to
ask my router for a password via dhcp. Currently, this works for the
wired interface and by hand for the wireless.
For some reason aux/wpa does not ask me for a password when run. I
think my problem may lie with factotum, but I don't know where.
Thank you for your suggestions.
Chris
next prev parent reply other threads:[~2022-11-25 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 16:10 Chris Gorman
2022-11-25 19:38 ` kemal
2022-11-25 20:07 ` Chris Gorman
2022-11-25 20:26 ` kemal
2022-11-25 21:10 ` Chris Gorman [this message]
2022-11-25 21:58 ` kemal
2022-11-25 22:21 ` Chris Gorman
2022-11-25 22:43 ` kemal
2022-11-25 22:48 ` Chris Gorman
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='CAHVeOW_KBKJbzmx02b4=rF7HfcAXqwhg0orTtF-g=Y-MiAy7Cw@mail.gmail.com' \
--to=chrisjohgorman@gmail.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).