Regarding questions #2, see secstore(1) http://p9f.org/magic/man2html/1/secstore On Wed, Mar 22, 2023, 3:04 AM Yury Chumak wrote: > Thank you for last response.. > ..Finally issue was resolved through a comprehensive mutual > configuration of various local network services =)) Main thing that it > was not a hardware issue or incompability with 9front.. > > There is some more questions.. > 1. How to down network interface correctly?? In order to switch from > one essid to another without reboot.. > 2. Also found that factotum doesn't save added keys and they are lost > after reboot. What is not configured?? How to decide and which way to > look?? > > вт, 21 мар. 2023 г. в 16:13, Jacob Moody : > > > > On 3/21/23 05:24, Yury Chumak wrote: > > > Same situation with the same wifi-card. > > > % pci -v > > > > I don't believe the situation is the same. > > You are unable to associate with the access point, > > which was not the same issue as our other friend here. > > > > > ... > > > 3.0.0: net 02.80.00 8086/08b1 4 0:a3100004 8192 > > > Intel Corporation Wireless 7260 > > > > > > Firmware added and kernel rebuilded. Command: > > > % aux/wpa -p2 -s vega3 /net/ether1 > > > > > > asking password, returns '!' and exits. But next command ip/ipconfig > returns: > > > > > > ipconfig: no success with DHCP > > > > > > DHCP is ok. It works good with other devices. DHCP-logs on server side > > > have not requests with wifi-card mac-address. > > > Trying to connect to mobile phone configured as hotspot takes the same > > > result - no success with DHCP. > > > Manual configuring: > > > % ip/ipconfig -g 192.168.7.1 ether /net/ether1 192.168.7.23 > 255.255.255.0 > > > > > > also not solve the situaton - ip/ping says about lost packets.. > > > % cat /net/ether1/ifstats > > > essid: vega3 > > > bssid: 045ea4e8e2ac > > > status: unassociated > > > channel: 06 > > > brsne: ..... > > > ..... > > > ..big list of available wifi-networks > > > > > > Tried also configure hotspot as open network, without authorization - > > > same result, doesn't connect. > > > > > > What could be the problem?? > > > > > > > > > The issue is stated in the ifstats output: > > > status: unassociated > > > > This is the failure mode I would expect if your wpa password was > incorrect. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T9b33abcfc0b8784b-Mde1ff56938d30b38caa14d27 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription