YaST is failing to set up wi-fi (wlan0) interface correctly.
Hi - I have ran into a sudden unexpected failure on Yast2's part in setting up my wi-fi interface that I need help with. I am running OpenSuSE Leap 15.2 on my laptop, x64 bit version. I have had no problems with the wi-fi interface up until yesterday. I have a dual boot system where I can boot up Windows 10 on this laptop also. Windows 10 does NOT have any problems with the wi-fi interface so I can be pretty certain this is not a hardware failure. My problem began with either one of two events, the first being I had just updated my laptop with a bunch of updates, didn't keep track of what was installed, and cannot say for certain that the updates are the culprit. Second, I then attempted to use Yast to set up my wi-fi (wlan0) to use my Android phone as a mobile hotspot. (this is something I very rarely do, but was necessary in order to run a zoom session for a neighborhood meeting) The only thing I did in Yast was to scan for and change the access point so that my laptop would use my mobile phone instead. Everything else remains the same, account user name, password, encryption etc. And it failed! I couldn't figure out why so gave up and tried to reset Yast to use the access point that I normally use in my house, and that too failed in the same way. I got no idea why, I have rechecked all my setting in Yast and nothing else has changed or been touched. I even compared all the Yast settings for the wlan0 interface with another laptop that works, and no differences were found other than hostname. Lots of Googling has enabled me to find a workaround and get the wlan0 interface working, but it is a bit squirrelly and not exactly a repeatable sequence of commands to get the interface working again. FYI I use a dhcpd service to get an IP address for my laptop, but even setting it up with a static IP address still results in Yast not getting the interface to work. The workaround is as follows - After attempting to set up the wlan0 interface with Yast, I execute the following two commands to see if the interface is working and whether I have an IP address -
marcslaptop:/var/log # iwconfig wlan0 wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on marcslaptop:/var/log # ifconfig eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 38:d5:47:31:54:0f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 22 bytes 2640 (2.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22 bytes 2640 (2.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether e4:a7:a0:46:83:e0 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
As you can see, no joy. So my next step is to see if the wlan0 NIC can hear anything -
marcslaptop:/var/log # iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:12:17:A1:B0:10 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=32/70 Signal level=-78 dBm Encryption key:on ESSID:"hamshack" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Master Extra:tsf=000000630301e649 Extra: Last beacon: 3420ms ago IE: Unknown: 000868616D736861636B IE: Unknown: 010882848B962430486C IE: Unknown: 030101 IE: Unknown: 2A0100 IE: Unknown: 2F0100 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: 32040C121860 IE: Unknown: DD06001018020004 Cell 02 - Address: 98:DE:D0:F9:93:CA Channel:6 Frequency:2.437 GHz (Channel 6) Quality=70/70 Signal level=-21 dBm Encryption key:on ESSID:"ChamberlinCupola" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Master Extra:tsf=0000004db69159e4 Extra: Last beacon: 3144ms ago IE: Unknown: 00104368616D6265726C696E4375706F6C61 IE: Unknown: 010882848B962430486C IE: Unknown: 030106 IE: Unknown: 2A0100 IE: Unknown: 2F0100 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: 32040C121860 IE: Unknown: 0B0506001D0000 IE: Unknown: 2D1AFE1917FFFF000001000000000000000000000000000000000000 IE: Unknown: 3D1606051700000000000000000000000000000000000000 IE: Unknown: 7F080400080000000040 IE: Unknown: DD760050F204104A0001101044000102103B00010310470010D96C7EFC2F8938F1EFBD6E5148BFA8121021000754502D4C494E4B10230005415033303010240006313233343536104200033030311054000800060050F2040001101100054150333030100800022008103C0001031049000600372A000120 IE: Unknown: DD090010180206000C0000 IE: Unknown: DD180050F2020101840003A4000027A4000042435E0062322F00 IE: Unknown: 46057208010000 Cell 03 - Address: 88:DC:96:41:72:9F Channel:11 Frequency:2.462 GHz (Channel 11) Quality=70/70 Signal level=-34 dBm Encryption key:on ESSID:"EnGeniusAP" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=0000000cf0f00dbe Extra: Last beacon: 3036ms ago IE: Unknown: 000A456E47656E6975734150 IE: Unknown: 010882848B960C121824 IE: Unknown: 03010B IE: Unknown: 0706555320010B1E IE: Unknown: 2A0100 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: 32043048606C IE: Unknown: 2D1AAD0103FFFF000000000000000000000100000000000000000000 IE: Unknown: 3D160B080400000000000000000000000000000000000000 IE: Unknown: 4A0E14000A002C01C800140005001900 IE: Unknown: 7F080100000000000040 IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00 IE: Unknown: DD0900037F01010000FF7F Cell 04 - Address: BC:30:7D:F6:54:5E Channel:52 Frequency:5.26 GHz (Channel 52) Quality=53/70 Signal level=-57 dBm Encryption key:on ESSID:"DIRECTV_WVB_24100A9C" Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=0000004db6437c22 Extra: Last beacon: 2440ms ago IE: Unknown: 0014444952454354565F5756425F3234313030413943 IE: Unknown: 01088C129824B048606C IE: Unknown: 030134 IE: Unknown: 050B0203000000000000000000 IE: Unknown: 2D1ACE0117FFFFFFFFFEFFFFFFFF1F000001000000000018E6E71900 IE: Unknown: 3D16340D0500000000000000000000000000000000000000 IE: Unknown: DD180050F2020101010003A4000027A4000042435E0062322F00 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: DD0B002686010300DD00000101 IE: Unknown: DD220050F204104A00011010440001011049000600372A00012010490006002686000101 Cell 05 - Address: 98:DE:D0:F9:93:C9 Channel:149 Frequency:5.745 GHz Quality=70/70 Signal level=-31 dBm Encryption key:on ESSID:"ChamberlinCupola_5G" Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=0000000016bac041 Extra: Last beacon: 560ms ago IE: Unknown: 00134368616D6265726C696E4375706F6C615F3547 IE: Unknown: 01088C129824B048606C IE: Unknown: 050400010000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: 0B050000010000 IE: Unknown: 2D1AEF0917FFFF000000000000000000000000000000000000000000 IE: Unknown: 3D16950D0000000000000000000000000000000000000000 IE: Unknown: 7F080400080000000040 IE: Unknown: BF0CB259810FFAFF0000FAFF0000 IE: Unknown: C005019B000000 IE: Unknown: C30402020202 IE: Unknown: DD310050F204104A000110104400010210470010D96C7EFC2F8938F1EFBD6E5148BFA812103C0001031049000600372A000120 IE: Unknown: DD090010180200001C0000 IE: Unknown: DD180050F2020101840003A4000027A400004243BC0062326600 IE: Unknown: 46057208010000
So yes, wlan0 can hear OK, AND AMAZINGLY sometimes this is all that it takes to get wlan0 working which I check by executing -
marcslaptop:/var/log # ifconfig eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 38:d5:47:31:54:0f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 22 bytes 2640 (2.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22 bytes 2640 (2.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.10.10 netmask 255.255.255.0 broadcast 192.168.10.255 inet6 fe80::e6a7:a0ff:fe47:83e0 prefixlen 64 scopeid 0x20<link> ether e4:a7:a0:46:83:e0 txqueuelen 1000 (Ethernet) RX packets 315 bytes 33055 (32.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 136 bytes 39494 (38.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
But if ifconfig does not report that wlan0 got an ip address assigned to it, then I drop a bigger hammer, which so far always works -
marcslaptop:/var/log # ip link set wlan0 up
So why am I now having to execute these manual steps after using Yast to set up wlan0? Can't say that looking through log files has been very helpful either and I am starting to get a bit out of my league here. I just want to be able to rely on Yast to set up my network interfaces. I haven't tried setting eth0 yet, will await for any helpful ideas first, before spinning my wheels with eth0. Thanks as always, in advance, for any help offered, I much appreciate it especially when I have wandered off into some sort of quagmire like this issue that suddenly sprung up on me! Marc C. -- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
Marc Chamberlin wrote:
So why am I now having to execute these manual steps after using Yast to set up wlan0? Can't say that looking through log files has been very helpful either and I am starting to get a bit out of my league here. I just want to be able to rely on Yast to set up my network interfaces. I haven't tried setting eth0 yet, will await for any helpful ideas first, before spinning my wheels with eth0.
Thanks as always, in advance, for any help offered, I much appreciate it especially when I have wandered off into some sort of quagmire like this issue that suddenly sprung up on me! Marc C.
Hi Marc, you are really using YaST to manage your wicked config - essentially a text file: /etc/sysconfig/network/ifcfg-wlan0 Let us the contents of that, maybe obscure the wifi password. I think it might also be useful if you start with 'ifdown wlan0' so we have a known starting point. Then try to activate the network interface with 'ifup wlan0' and let us see what 'ip addr show dev wlan0' says after that. If there is any problem connecting to the access point, 'dmesg' might show some interesting messages. -- Per Jessen, Zürich (19.2°C)
On 9/26/21 1:41 AM, Per Jessen wrote:
Marc Chamberlin wrote:
So why am I now having to execute these manual steps after using Yast to set up wlan0? Can't say that looking through log files has been very helpful either and I am starting to get a bit out of my league here. I just want to be able to rely on Yast to set up my network interfaces. I haven't tried setting eth0 yet, will await for any helpful ideas first, before spinning my wheels with eth0.
Thanks as always, in advance, for any help offered, I much appreciate it especially when I have wandered off into some sort of quagmire like this issue that suddenly sprung up on me! Marc C. Hi Marc,
you are really using YaST to manage your wicked config - essentially a text file:
/etc/sysconfig/network/ifcfg-wlan0
Let us the contents of that, maybe obscure the wifi password.
I think it might also be useful if you start with 'ifdown wlan0' so we have a known starting point. Then try to activate the network interface with 'ifup wlan0' and let us see what 'ip addr show dev wlan0' says after that.
If there is any problem connecting to the access point, 'dmesg' might show some interesting messages.
Thanks Per, and can do -
marcslaptop:/var/log # ifdown wlan0 wlan0 device-ready marcslaptop:/var/log # cat /etc/sysconfig/network/ifcfg-wlan0 MTU='0' BOOTPROTO='dhcp' STARTMODE='auto' ZONE='internal' WIRELESS_ESSID='ChamberlinCupola' WIRELESS_AUTH_MODE='psk' WIRELESS_MODE='managed' WIRELESS_WPA_PSK='xxxxxxxxxxxxxxx' WIRELESS_AP_SCANMODE='0' marcslaptop:/var/log # ifup wlan0 wlan0 setup-in-progress marcslaptop:/var/log # ip addr show dev wlan0 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether e4:a7:a0:46:83:e0 brd ff:ff:ff:ff:ff:ff
The only thing dmesg shows that is related to the wi-fi wlan0 interface is -
[92283.790584] wlan0: deauthenticating from 98:de:d0:f9:93:ca by local choice (Reason: 3=DEAUTH_LEAVING) [92389.805091] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM [92389.979695] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM [92390.060594] iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
The MAC address 98:de:d0:f9:93:ca is for the 'ChamberlinCupola' access point. HTH's to understand what is going on with my wlan0 setup process... Marc -- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
Marc Chamberlin wrote:
Thanks Per, and can do -
marcslaptop:/var/log # ifdown wlan0 wlan0 device-ready marcslaptop:/var/log # cat /etc/sysconfig/network/ifcfg-wlan0 MTU='0' BOOTPROTO='dhcp' STARTMODE='auto' ZONE='internal' WIRELESS_ESSID='ChamberlinCupola' WIRELESS_AUTH_MODE='psk' WIRELESS_MODE='managed' WIRELESS_WPA_PSK='xxxxxxxxxxxxxxx' WIRELESS_AP_SCANMODE='0'
Comparing to one of my systems with wicked and wifi - I have WIRELESS_AP_SCANMODE='1' -- Per Jessen, Zürich (17.8°C)
On Mon, Sep 27, 2021 at 10:14 AM Per Jessen <per@computer.org> wrote:
Marc Chamberlin wrote:
Thanks Per, and can do -
marcslaptop:/var/log # ifdown wlan0 wlan0 device-ready marcslaptop:/var/log # cat /etc/sysconfig/network/ifcfg-wlan0 MTU='0' BOOTPROTO='dhcp' STARTMODE='auto' ZONE='internal' WIRELESS_ESSID='ChamberlinCupola' WIRELESS_AUTH_MODE='psk' WIRELESS_MODE='managed' WIRELESS_WPA_PSK='xxxxxxxxxxxxxxx' WIRELESS_AP_SCANMODE='0'
Comparing to one of my systems with wicked and wifi - I have WIRELESS_AP_SCANMODE='1'
That sounds quite probable. From the man page Mode 0 means the driver performs the scan. Mode 1 means wpa_supplicant takes care of scanning. Mode 2 is basically the same as mode 0 but the access point gets chosen by security policy and SSID. This mode does not support multiple network settings. Default is 1 for most drivers. Usually scanning is controlled by network management programs. I wonder if there are any drivers that perform periodical scans automatically. And even if they do, what is the interval between these scans?
On 9/27/21 1:16 AM, Andrei Borzenkov wrote:
On Mon, Sep 27, 2021 at 10:14 AM Per Jessen <per@computer.org> wrote:
Marc Chamberlin wrote:
Thanks Per, and can do -
marcslaptop:/var/log # ifdown wlan0 wlan0 device-ready marcslaptop:/var/log # cat /etc/sysconfig/network/ifcfg-wlan0 MTU='0' BOOTPROTO='dhcp' STARTMODE='auto' ZONE='internal' WIRELESS_ESSID='ChamberlinCupola' WIRELESS_AUTH_MODE='psk' WIRELESS_MODE='managed' WIRELESS_WPA_PSK='xxxxxxxxxxxxxxx' WIRELESS_AP_SCANMODE='0' Comparing to one of my systems with wicked and wifi - I have WIRELESS_AP_SCANMODE='1'
That sounds quite probable. From the man page
Mode 0 means the driver performs the scan. Mode 1 means wpa_supplicant takes care of scanning. Mode 2 is basically the same as mode 0 but the access point gets chosen by security policy and SSID. This mode does not support multiple network settings. Default is 1 for most drivers.
Usually scanning is controlled by network management programs. I wonder if there are any drivers that perform periodical scans automatically. And even if they do, what is the interval between these scans? Thanks Per, Andrie - Interesting! I set the WIRELESS_AP_SCANMODE='1' on my laptop, in
/etc/sysconfig/network/ifcfg-wlan0 and executed ifdown wlan0 followed by ifup wlan0 and it worked! So I tried it with Yast again and discovered that by default Yast is setting WIRELESS_AP_SCANMODE="0" This is a setting (found in Expert Settings subpanel) for wlan0 edit/setup for the wlan0 interface. I have never messed with it, didn't even know what it's purpose was, but by setting it to 1, that does the trick and Yast will also set up the wlan0 interface properly. So now the questions becomes - Why is Yast always setting WIRELESS_AP_SCANMODE="0" by default? Especially if, as you stated, the default is 1 for most drivers? How do I coerce Yast into setting the WIRELESS_AP_SCANMODE='1' by default and keep that setting persistent? Feels like we are starting to make progress on solving this issue! I will look forward to hearing additional thoughts, Thanks again for your help and insights. Marc... -- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
Marc Chamberlin wrote:
So now the questions becomes - Why is Yast always setting WIRELESS_AP_SCANMODE="0" by default? Especially if, as you stated, the default is 1 for most drivers? How do I coerce Yast into setting the WIRELESS_AP_SCANMODE='1' by default and keep that setting persistent?
I guess we ought to ask where that default value comes from? I compared to my settings on a Nano Pi Neo Air, where the wifi is an AP6212 (IIRC). -- Per Jessen, Zürich (20.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
On 27.09.2021 19:13, Marc Chamberlin wrote:
So now the questions becomes - Why is Yast always setting WIRELESS_AP_SCANMODE="0" by default?
For all I can tell default in YaST is "1", at least when support for this variable was originally introduced and in current code.
Especially if, as you stated, the default is 1 for most drivers? How do I coerce Yast into setting the WIRELESS_AP_SCANMODE='1' by default and keep that setting persistent?
I am not sure I understand it. Do you mean that setting it to "1" is not persistent?
Feels like we are starting to make progress on solving this issue! I will look forward to hearing additional thoughts, Thanks again for your help and insights. Marc...
On 9/27/21 11:51 AM, Andrei Borzenkov wrote:
So now the questions becomes - Why is Yast always setting WIRELESS_AP_SCANMODE="0" by default? For all I can tell default in YaST is "1", at least when support for
On 27.09.2021 19:13, Marc Chamberlin wrote: this variable was originally introduced and in current code.
Especially if, as you stated, the default is 1 for most drivers? How do I coerce Yast into setting the WIRELESS_AP_SCANMODE='1' by default and keep that setting persistent?
I am not sure I understand it. Do you mean that setting it to "1" is not persistent?
Correct Andrie, each time I start up Yast, and go into Network Settings, I find that the WIRELESS_AP_SCANMODE is set to zero (0) which makes it seem like that is the default value, and my having previously set it to one (1) is not persistent. Marc...
Feels like we are starting to make progress on solving this issue! I will look forward to hearing additional thoughts, Thanks again for your help and insights. Marc...
-- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
On 28.09.2021 01:45, Marc Chamberlin wrote:
On 9/27/21 11:51 AM, Andrei Borzenkov wrote:
So now the questions becomes - Why is Yast always setting WIRELESS_AP_SCANMODE="0" by default? For all I can tell default in YaST is "1", at least when support for
On 27.09.2021 19:13, Marc Chamberlin wrote: this variable was originally introduced and in current code.
Especially if, as you stated, the default is 1 for most drivers? How do I coerce Yast into setting the WIRELESS_AP_SCANMODE='1' by default and keep that setting persistent?
I am not sure I understand it. Do you mean that setting it to "1" is not persistent?
Correct Andrie, each time I start up Yast, and go into Network Settings, I find that the WIRELESS_AP_SCANMODE is set to zero (0) which makes it seem like that is the default value, and my having previously set it to one (1) is not persistent.
I can confirm it on 15.2 - editing wireless interface resets scan mode to 0 (new interface defaults to 1). Seeing that Leap 15.2 is near end of support and this problem is no more present in 15.3 I am not sure bug report makes much sense.
Hello, In the Message; Subject : YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <d33a78d1-643e-1300-b5a1-90a390d6cb9e@marcchamberlin.com> Date & Time: Sat, 25 Sep 2021 18:33:15 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: MC> Hi - I have ran into a sudden unexpected failure on Yast2's part in MC> setting up my wi-fi interface that I need help with. I am running [...] MC> marcslaptop:/var/log # ip link set wlan0 up Have you checked /etc/resolve.conf? Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --
On 9/26/21 5:11 PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <d33a78d1-643e-1300-b5a1-90a390d6cb9e@marcchamberlin.com> Date & Time: Sat, 25 Sep 2021 18:33:15 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
MC> Hi - I have ran into a sudden unexpected failure on Yast2's part in MC> setting up my wi-fi interface that I need help with. I am running [...] MC> marcslaptop:/var/log # ip link set wlan0 up
Have you checked /etc/resolve.conf?
Regards.
Thanks Masaru for the suggestion, it was a good idea, but still no joy. resolve.conf looks just fine and hasn't changed on my laptop for a long time. I did double check to make sure my own DNS servers are running, both are and report no issues. Same for my DHCPD server, no issues, nor does it report, in it's log file, that an attempt was made to get an IP address from/for my laptop, when my laptop fails to set up wlan0 properly. What seems odd to me is that just executing -
iwlist wlan0 scan
i.e. simply doing a scan for APs is enough to often setup wlan0 and retrieve an IP address from my DHCPD server! Marc... -- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
Hello, In the Message; Subject : Re: YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <58194721-2c59-2a7f-057e-ed3182f2f464@marcchamberlin.com> Date & Time: Sun, 26 Sep 2021 18:10:38 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MC> Thanks Masaru for the suggestion, it was a good idea, but still no joy. MC> resolve.conf looks just fine and hasn't changed on my laptop for a long MC> time. I did double check to make sure my own DNS servers are running, MC> both are and report no issues. Same for my DHCPD server, no issues, nor MC> does it report, in it's log file, that an attempt was made to get an IP MC> address from/for my laptop, when my laptop fails to set up wlan0 properly. MC> What seems odd to me is that just executing - MC> > iwlist wlan0 scan MC> i.e. simply doing a scan for APs is enough to often setup wlan0 and MC> retrieve an IP address from my DHCPD server! Which service are you using, wicked or NetworkManager? Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
On 9/26/21 6:38 PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <58194721-2c59-2a7f-057e-ed3182f2f464@marcchamberlin.com> Date & Time: Sun, 26 Sep 2021 18:10:38 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
[...] MC> Thanks Masaru for the suggestion, it was a good idea, but still no joy. MC> resolve.conf looks just fine and hasn't changed on my laptop for a long MC> time. I did double check to make sure my own DNS servers are running, MC> both are and report no issues. Same for my DHCPD server, no issues, nor MC> does it report, in it's log file, that an attempt was made to get an IP MC> address from/for my laptop, when my laptop fails to set up wlan0 properly.
MC> What seems odd to me is that just executing - MC> > iwlist wlan0 scan
MC> i.e. simply doing a scan for APs is enough to often setup wlan0 and MC> retrieve an IP address from my DHCPD server!
Which service are you using, wicked or NetworkManager?
Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money." Thanks again Masaru with another good question that I should have stated. I am using Wicked. Marc....
-- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
Hello, In the Message; Subject : Re: YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <f2a6dab5-e184-1186-1f9b-5240b294bc7f@marcchamberlin.com> Date & Time: Sun, 26 Sep 2021 19:58:40 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MC> Thanks again Masaru with another good question that I should have MC> stated. I am using Wicked. Marc.... Thanks. Have you checked the status of mac address randomization in Android? Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'
On 9/26/21 8:28 PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <f2a6dab5-e184-1186-1f9b-5240b294bc7f@marcchamberlin.com> Date & Time: Sun, 26 Sep 2021 19:58:40 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
[...] MC> Thanks again Masaru with another good question that I should have MC> stated. I am using Wicked. Marc....
Thanks.
Have you checked the status of mac address randomization in Android?
Hi Masaru - I think you are starting to ask questions that are above my pay grade! LOL Up until you asked I didn't even know it was possible to randomize mac addresses! My Android phone is a Samsung Galaxy S8 running Android 9. Google searches showed me ways to find and set/reset mac address randomization, but none of those methods seem applicable to my phone. I simply cannot locate a setting anywhere, including in Developer Options, that allows me to change such an ability. My educated guess is to say that my phone is not using or randomizing it's mac address. The reason I say this is that my phone is set up to use dhcp for getting an IP address lease. And my dhcpd server is set up to hand out specific IP addresses, based on their mac address, to different devices on my SOHO network, including my Android phone. So my Android phone is getting the same local network IP address assigned to it every time. I would think that to randomize my Android's mac address would break my dhcpd server's ability to give my Android phone it's very specific IP address, and also occasionally break other IP assignments to other devices on my network. But what do I know, this is getting beyond my ability to grok why randomizing mac address would even be useful. Also, I don't understand why my phone settings would affect my regular ability to connect my OpenSuSE laptop, via wlan0/WiFi, to my normal AP, which is NOT my phone's hotspot. Rather it is a TP-Link WiFi access point / router . Thanks again for taking the time to help me, Masaru, and please bear with me, I am learning new things about WiFi connections as I go along, and some of it is not easy to grok for me... Marc -- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
Hello, In the Message; Subject : YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <d33a78d1-643e-1300-b5a1-90a390d6cb9e@marcchamberlin.com> Date & Time: Sat, 25 Sep 2021 18:33:15 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MC> My problem began with either one of two events, the first being I had MC> just updated my laptop with a bunch of updates, didn't keep track of MC> what was installed, and cannot say for certain that the updates are the MC> culprit. Could you show the result of; $ rpm -qa --last | grep "Fri Sep 24" Regards, and Good Night --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --
Hello, In the Message; Subject : Re: YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <87mtnye0be.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Mon, 27 Sep 2021 20:15:49 +0900 [MN] == Masaru Nomiya <nomiya@galaxy.dti.ne.jp> has written: MN> Hello, MN> In the Message; MN> Subject : YaST is failing to set up wi-fi (wlan0) interface correctly. MN> Message-ID : <d33a78d1-643e-1300-b5a1-90a390d6cb9e@marcchamberlin.com> MN> Date & Time: Sat, 25 Sep 2021 18:33:15 -0700 MN> [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: MN> [...] MC> My problem began with either one of two events, the first being I had MC> just updated my laptop with a bunch of updates, didn't keep track of MC> what was installed, and cannot say for certain that the updates are the MC> culprit. MN> Could you show the result of; MN> $ rpm -qa --last | grep "Fri Sep 24" MN> Regards, and Good Night If you updated on Sep 25, please execute as follows; $ rpm -qa --last | grep "Sat Sep 25" Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'
On 9/27/21 4:39 AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: YaST is failing to set up wi-fi (wlan0) interface correctly. Message-ID : <87mtnye0be.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Mon, 27 Sep 2021 20:15:49 +0900
[MN] == Masaru Nomiya <nomiya@galaxy.dti.ne.jp> has written:
MN> Hello,
MN> In the Message;
MN> Subject : YaST is failing to set up wi-fi (wlan0) interface correctly. MN> Message-ID : <d33a78d1-643e-1300-b5a1-90a390d6cb9e@marcchamberlin.com> MN> Date & Time: Sat, 25 Sep 2021 18:33:15 -0700
MN> [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
MN> [...] MC> My problem began with either one of two events, the first being I had MC> just updated my laptop with a bunch of updates, didn't keep track of MC> what was installed, and cannot say for certain that the updates are the MC> culprit.
MN> Could you show the result of;
MN> $ rpm -qa --last | grep "Fri Sep 24"
MN> Regards, and Good Night
If you updated on Sep 25, please execute as follows;
$ rpm -qa --last | grep "Sat Sep 25"
Regards. Hello again Masaru, I got no results from the queries you suggested so I did a more general query and this is the results -
marcslaptop:/var/log # rpm -qa --last | grep "Fri Sep 24" marcslaptop:/var/log # rpm -qa --last | grep "Sat Sep 25" marcslaptop:/var/log # rpm -qa --last | more xen-libs-4.13.3_04-lp152.2.30.1.x86_64 Wed 22 Sep 2021 01:30:33 PM PDT chromium-93.0.4577.82-lp152.2.125.1.x86_64 Wed 22 Sep 2021 01:30:31 PM PDT x11-video-nvidiaG05-470.74-lp152.44.1.x86_64 Wed 22 Sep 2021 01:29:52 PM PDT nvidia-computeG05-470.74-lp152.44.1.x86_64 Wed 22 Sep 2021 01:28:40 PM PDT nvidia-glG05-470.74-lp152.44.1.x86_64 Wed 22 Sep 2021 01:28:30 PM PDT nvidia-gfxG05-kmp-default-470.74_k5.3.18_lp152.19-lp152.44.1.x86_64 Wed 22 Sep 2021 01:15:58 PM PDT java-11-openjdk-11.0.12.0-lp152.2.18.1.x86_64 Tue 21 Sep 2021 02:20:08 PM PDT java-11-openjdk-headless-11.0.12.0-lp152.2.18.1.x86_64 Tue 21 Sep 2021 02:20:05 PM PDT libsoftokn3-hmac-3.68-lp152.2.10.1.x86_64 Tue 21 Sep 2021 02:19:16 PM PDT mozilla-nss-3.68-lp152.2.10.1.x86_64 Tue 21 Sep 2021 02:19:15 PM PDT xorg-x11-fonts-legacy-7.6-lp152.7.6.1.noarch Tue 21 Sep 2021 02:19:14 PM PDT libsoftokn3-3.68-lp152.2.10.1.x86_64 Tue 21 Sep 2021 02:18:42 PM PDT yast2-country-4.2.23-lp152.2.9.1.x86_64 Tue 21 Sep 2021 02:18:37 PM PDT xorg-x11-fonts-7.6-lp152.7.6.1.noarch Tue 21 Sep 2021 02:18:36 PM PDT mozilla-nss-certs-3.68-lp152.2.10.1.x86_64 Tue 21 Sep 2021 02:18:33 PM PDT yast2-country-data-4.2.23-lp152.2.9.1.x86_64 Tue 21 Sep 2021 02:18:32 PM PDT xorg-x11-fonts-core-7.6-lp152.7.6.1.noarch Tue 21 Sep 2021 02:18:32 PM PDT libfreebl3-hmac-3.68-lp152.2.10.1.x86_64 Tue 21 Sep 2021 02:18:32 PM PDT xorg-x11-fonts-converted-7.6-lp152.7.6.1.noarch Tue 21 Sep 2021 02:18:28 PM PDT mozilla-nspr-4.32-lp152.2.6.1.x86_64 Tue 21 Sep 2021 02:18:22 PM PDT libfreebl3-3.68-lp152.2.10.1.x86_64 Tue 21 Sep 2021 02:18:22 PM PDT libcroco-0_6-3-0.6.13-lp152.2.3.1.x86_64 Tue 21 Sep 2021 02:18:20 PM PDT fonttosfnt-1.1.0-lp152.2.5.1.x86_64 Tue 21 Sep 2021 02:18:20 PM PDT PackageKit-lang-1.1.13-lp152.3.27.1.noarch Sat 18 Sep 2021 09:40:38 AM PDT PackageKit-gtk3-module-1.1.13-lp152.3.27.1.x86_64 Sat 18 Sep 2021 09:40:38 AM PDT PackageKit-gstreamer-plugin-1.1.13-lp152.3.27.1.x86_64 Sat 18 Sep 2021 09:40:38 AM PDT PackageKit-backend-zypp-1.1.13-lp152.3.27.1.x86_64 Sat 18 Sep 2021 09:40:36 AM PDT PackageKit-1.1.13-lp152.3.27.1.x86_64 Sat 18 Sep 2021 09:40:36 AM PDT nvme-cli-1.10-lp152.2.18.1.x86_64 Sat 18 Sep 2021 09:40:35 AM PDT libpackagekit-glib2-18-1.1.13-lp152.3.27.1.x86_64 Sat 18 Sep 2021 09:40:35 AM PDT wireshark-ui-qt-3.4.7-lp152.2.18.1.x86_64 Fri 17 Sep 2021 07:20:40 AM PDT wireshark-3.4.7-lp152.2.18.1.x86_64 Fri 17 Sep 2021 07:20:39 AM PDT libwireshark14-3.4.7-lp152.2.18.1.x86_64 Fri 17 Sep 2021 07:20:37 AM PDT libwiretap11-3.4.7-lp152.2.18.1.x86_64 Fri 17 Sep 2021 07:20:30 AM PDT ghostscript-x11-9.52-lp152.2.7.1.x86_64 Fri 17 Sep 2021 07:20:29 AM PDT yast2-users-4.2.13-lp152.2.6.1.x86_64 Fri 17 Sep 2021 07:20:28 AM PDT libwsutil12-3.4.7-lp152.2.18.1.x86_64 Fri 17 Sep 2021 07:20:28 AM PDT ghostscript-9.52-lp152.2.7.1.x86_64 Fri 17 Sep 2021 07:20:27 AM PDT autoyast2-installation-4.2.55-lp152.2.15.1.noarch Wed 15 Sep 2021 10:59:52 PM PDT yast2-installation-4.2.53-lp152.2.21.1.noarch Wed 15 Sep 2021 10:59:46 PM PDT kernel-default-devel-5.3.18-lp152.92.2.x86_64 Wed 15 Sep 2021 10:59:45 PM PDT yast2-4.2.95-lp152.2.31.1.x86_64 Wed 15 Sep 2021 10:59:40 PM PDT kernel-devel-5.3.18-lp152.92.2.noarch Wed 15 Sep 2021 10:59:39 PM PDT yast2-logs-4.2.95-lp152.2.31.1.x86_64 Wed 15 Sep 2021 10:59:28 PM PDT libcares2-1.17.1+20200724-lp152.2.12.1.x86_64 Wed 15 Sep 2021 10:59:28 PM PDT kernel-macros-5.3.18-lp152.92.2.noarch Wed 15 Sep 2021 10:59:27 PM PDT kernel-default-5.3.18-lp152.92.2.x86_64 Wed 15 Sep 2021 10:58:36 PM PDT cronie-1.5.1-lp152.7.3.1.x86_64 Tue 14 Sep 2021 10:25:13 PM PDT netcfg-11.6-lp152.4.3.1.noarch Tue 14 Sep 2021 10:25:12 PM PDT gcc-7-lp152.5.6.1.x86_64 Tue 14 Sep 2021 10:25:12 PM PDT libaom0-1.0.0-lp152.3.3.1.x86_64 Tue 14 Sep 2021 10:25:11 PM PDT cron-4.2-lp152.7.3.1.x86_64 Tue 14 Sep 2021 10:25:10 PM PDT cpp-7-lp152.5.6.1.x86_64 Tue 14 Sep 2021 10:25:09 PM PDT openssl-1_1-1.1.1d-lp152.7.24.1.x86_64 Sun 12 Sep 2021 09:07:08 PM PDT libopenssl1_1-32bit-1.1.1d-lp152.7.24.1.x86_64 Sun 12 Sep 2021 09:07:06 PM PDT libopenssl1_1-1.1.1d-lp152.7.24.1.x86_64 Sun 12 Sep 2021 09:07:04 PM PDT hwdata-0.351-lp152.2.15.1.noarch Fri 10 Sep 2021 10:01:56 PM PDT ntfs-3g-2021.8.22-lp152.5.3.1.x86_64 Thu 09 Sep 2021 09:28:06 PM PDT ntfsprogs-2021.8.22-lp152.5.3.1.x86_64 Thu 09 Sep 2021 09:28:05 PM PDT libntfs-3g87-2021.8.22-lp152.5.3.1.x86_64 Thu 09 Sep 2021 09:28:04 PM PDT yast2-update-4.2.22-lp152.2.10.1.x86_64 Tue 07 Sep 2021 05:48:16 PM PDT libpcre2-8-0-10.31-lp152.4.3.1.x86_64 Tue 07 Sep 2021 05:48:13 PM PDT libpcre2-16-0-10.31-lp152.4.3.1.x86_64 Tue 07 Sep 2021 05:48:12 PM PDT libesmtp-1.0.6-lp152.4.3.1.x86_64 Tue 07 Sep 2021 05:48:12 PM PDT libxerces-c-3_1-3.1.4-lp152.5.3.1.x86_64 Mon 06 Sep 2021 02:14:47 PM PDT HTHs Marc
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'
-- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
participants (4)
-
Andrei Borzenkov -
Marc Chamberlin -
Masaru Nomiya -
Per Jessen