Hello all, I'm trying to set up a wifi card on my cpu+auth+fileserver in 9front. My typical use is to drawterm into the machine. I currently have the machine connected to a hub via ethernet, but I wanted to load the wifi connection on my network too. I have the following configuration in plan9.ini ether1=type=iwl essid=ESSID wpapsk=PASSWORD debug=1 I have also tried this out on seperate lines in plan9.ini as ori@eigenstate.org suggested to me in an email on the 9fans list. ether1=type=iwl essid=ESSID wpapsk=PASSWORD Neither work. I get the following from /dev/kmesg Plan 9 HPET: fed00000 8086a701 14 MHz 124 holes free 0x00021000 0x00058000 225280 0x00059000 0x0009d000 278528 0x00100000 0x00110000 65536 0x0063a000 0x7ffff000 2140950528 2141519872 bytes free cpu0: 3277MHz GenuineIntel Xeon5000-series (AX 000306C3 CX 77FAFBFF DX BFEBFBFF) LAPIC: fee00000 0xfffffe80fee00000 ELCR: 0000 cpu0: lapic clock at 99MHz cpu1: 3277MHz GenuineIntel Xeon5000-series (AX 000306C3 CX 77FAFBFF DX BFEBFBFF) cpu2: 3277MHz GenuineIntel Xeon5000-series (AX 000306C3 CX 77FAFBFF DX BFEBFBFF) cpu3: 3277MHz GenuineIntel Xeon5000-series (AX 000306C3 CX 77FAFBFF DX BFEBFBFF) pcienable PCI.2.0.0: pcr 0->2 #l1: iwl: 54Mbps port 0xF7C00000 irq 255 ea 000000000000 i217: bad eeprom checksum - 0x3aba; ignored #l0: i217: 1000Mbps port 0xF7D00000 irq 255 ea 989096aad5d5 #S/sdE: ich: sata-II with 2 ports #A0: hda mem f7d30000 irq 255 #A0: codec #0, vendor 10ec0280, rev 00100003 usbehci: 0x8086 0x8c2d: port f7d3c000 size 1024 irq 255 usbehci: 0x8086 0x8c26: port f7d3b000 size 1024 irq 255 usbxhci: 0x8086 0x8c31: port f7d20000 size 65536 irq 255 15745M memory: 2048M kernel data, 13696M user, 14946M swap bootfs: Thu Nov 24 20:06:15 GMT 2022 fingerprint: 6b4e0269e85ddab1d0684ac783785c8b5edd2c54 i217: phy2 oui 0x5500 #l1: firmware: iwm-7265-17, rev 11, build 3216344376, size [3] 18000+30000 + [3] 18000+30000 + 0 #l1: debug: 1 #l1: rxon: bssid ffffffffffff, aid 0, channel 5, rxfilter 5c, rxflags 40008005 sdE0: LLBA 1,000,215,216 sectors HS512QE V0414A0 100108002809 [newdrive] sdE1: LBA 0 sectors TSSTcorp DVD-ROM SN-108FB D100 S13P6YCF7000QM [newdrive] #l1: rxon: bssid ffffffffffff, aid 0, channel 10, rxfilter 5c, rxflags 40008005 #l1: rxon: bssid ffffffffffff, aid 0, channel 2, rxfilter 5c, rxflags 40008005 current fs is "main" 11 uids read, 6 groups used 63-bit cwfs as of Mon Oct 31 12:02:25 2022 last boot Fri Nov 25 10:26:09 2022 #l1: rxon: bssid ffffffffffff, aid 0, channel 7, rxfilter 5c, rxflags 40008005 #l1: rxon: bssid ffffffffffff, aid 0, channel 12, rxfilter 5c, rxflags 40008005 #l1: rxon: bssid ffffffffffff, aid 0, channel 4, rxfilter 5c, rxflags 40008005 #l1: rxon: bssid ffffffffffff, aid 0, channel 9, rxfilter 5c, rxflags 40008005 #l1: rxon: bssid ffffffffffff, aid 0, channel 1, rxfilter 5c, rxflags 40008005 #l1: got probe from 0cac8a04ffd5 #l1: status 0cac8a04ffd5: 000000002570 000000002570: <nil> -> connecting (from pc=0xffffffff801be837) #l1: rxon: bssid 0cac8a04ffd5, aid 0, channel 1, rxfilter 5c, rxflags 40008015 #l1: got auth from 0cac8a04ffd5 #l1: status 0cac8a04ffd5: 000000002580 000000000010: connecting -> need authentication (from pc=0xffffffff801be679) ipconfig: recvra6: no router advs after 3 sols on /net/ether0 2 keys read in AES format init: starting /bin/rc ada# cpu% I can't tell the problem from the log, but I believe the problem is related to the wpapsk password not being recognised properly. Perhaps someone with more experience can tell me what's missing. On the upside, I can get the card recognised and initialized with the following commands I got off the 9fans list. As I am already connected via ethernet, I drawterm in and run ... bind -a '#l1' /net echo 'key proto=wpapsk essid=ESSID !password=PASSWORD' >> /mnt/factotum/ctl aux/wpa -2p -s ESSID /net/ether1 ip/ipconfig ether /net/ether1 This brings the card up and then I can then use it. If anyone has any hints on what to do to get this working on boot, please let me know. Thanks in advance, Chris
hi, may you try this in plan9.ini? ether1=type=iwl essid=ESSID wpapsk=PASS
Hi Kemal,
I just tried it and the network card fails to initialize. I can copy
/dev/kmesg again if it might help, but the messages appear to be the
same as before. My guess is that it's related to ...
#l1: status 0cac8a04ffd5: 000000002580 000000000010: connecting ->
need authentication (from pc=0xffffffff801be679)
Even though I've supplied authentication via wpapsk=PASS. Perhaps my
networking setup is broken somewhere?
As a long shot, could it be because of my /lib/ndb/local? My
modifications to it are...
auth=ada authdom=cgnet
ipnet=cgnet ip=192.168.2.0 ipmask=255.255.255.0
ipgw=192.168.2.1
dns=192.168.2.1
auth=ada
dnsdom=cgnet
fs=ada
sys=ada ether=989096aad5d5
I have no entry for the wifi mac in /lib/ndb/local, could this be the problem?
Thanks for the suggestion,
Best,
Chris
On Fri, Nov 25, 2022 at 2:41 PM kemal <kemalinanc8@gmail.com> wrote:
>
> hi, may you try this in plan9.ini?
>
> ether1=type=iwl essid=ESSID
> wpapsk=PASS
> I just tried it and the network card fails to initialize. I can copy > /dev/kmesg again if it might help, but the messages appear to be the > same as before. My guess is that it's related to ... > > #l1: status 0cac8a04ffd5: 000000002580 000000000010: connecting -> > need authentication (from pc=0xffffffff801be679) > > Even though I've supplied authentication via wpapsk=PASS. Perhaps my > networking setup is broken somewhere? 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 > sys=ada ether=989096aad5d5 > > I have no entry for the wifi mac in /lib/ndb/local, could this be the problem? > > Thanks for the suggestion, 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).
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
> I'm probably not explaining myself well, sorry. no worries. > 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. oh i see. but if you're going to connect to the same network with wireless, what is the point of wireless?
On Fri, Nov 25, 2022 at 5:01 PM kemal <kemalinanc8@gmail.com> wrote:
>
> > I'm probably not explaining myself well, sorry.
> no worries.
> > 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.
> oh i see. but if you're going to connect to the same network with wireless,
> what is the point of wireless?
You bring up a good point. I mainly wanted to get it to work because
I originally planned to use it wirelessly and bought a wifi card for
it. There is no good reason to use it wirelessly and given the speed
difference between wireless and wired, a very good reason not to.
Anyway it is not a big deal for me if it doesn't work as I will get
along without it by using the wired network connection.
Thanks for your time, and if you have other suggestions I welcome them.
Best,
Chris
> Thanks for your time, and if you have other suggestions I welcome them.
no problem! the rest of your configuration seems fine.
On Fri, Nov 25, 2022 at 5:46 PM kemal <kemalinanc8@gmail.com> wrote:
>
> > Thanks for your time, and if you have other suggestions I welcome them.
> no problem! the rest of your configuration seems fine.
Thanks Kemal.
Chris