Wifi connecting problem. (BookwormPup64 10.0.6)

[nnriyer]

My HP Laptop having BookwormPup64 10.0.6 is not connecting to wifi. The mobile wifi hotspot security is WPA2/WP3.

[dimkr]

Are you sure you're using Vanilla Dpup 10.0.6?

[nnriyer]

Yes Sir. Kernel 6.1.76. (Version 10.0.6) The problem is found while connecting Android 14.

[nnriyer]

Connection name shows Anjaneya\x20?. Why showing \X20 along with Wifi name ?. Also RSN-CCM-P?.

Another good news. I am able to connect through Conman connection manager. No such issues. Other connection options through simple network, fressbee etc not possible.

[dimkr]

Are you sure you're not using BookwormPup64?

[nnriyer]

Installed BookwormPup64 10.0.6

Operating System:
Distro Name BookwormPup64 10.0.6 (x86_64)
Woof-CE Build testing;22250aa6d;2024-03-04 13:57:41 +0000
Woof Version 9
Binary Base debian
Distro Base bookworm
Distro Date Mar 2024
User Session x11
Window Manager JWM v2.4.3
Desktop Start xwin jwm

▶—— /etc/DISTRO_SPECS ——◀

One or more words that identify this distribution:
• DISTRO_NAME='BookwormPup64'

Version number of this distribution:
• DISTRO_VERSION=10.0.6

The distro whose binary packages were used to build this distribution:
• DISTRO_BINARY_COMPAT='debian'

Prefix for some filenames: exs: bookwormsave.2fs, bookworm-8.0.sfs
• DISTRO_FILE_PREFIX='dpupbw64'

The version of the distro whose binary packages were used to build this distro:
• DISTRO_COMPAT_VERSION='bookworm'

The kernel pet package used:
• DISTRO_KERNEL_PET='Huge_Kernel'

Read by /usr/bin to bypass Xorg Wizard at first boot:
• DISTRO_XORG_AUTO='yes'

Subname for online PETs dir. Ex: "slacko14", dir "pet_packages-slacko14", db file "Packages-puppy-slacko14-official":
Note: prior to existence of this variable, online subname was set to $DISTRO_COMPAT_VERSION or via some hack code.
• DISTRO_DB_SUBNAME='bookworm'

• WOOF_VERSION=9

• DISTRO_TARGETARCH='x86_64'

• NO_MULTIARCH_SYMLINK=1

• BUILD_FROM_WOOF='testing;22250aa6d;2024-03-04 13:57:41 +0000'

Puppy default filenames...
Note, the 'SFS' files below are what the 'init' script in initrd.gz searches for,
For the partition, path and actual files loaded, see PUPSFS and ZDRV in /etc/rc.d/PUPSTATE
• DISTRO_BDRVSFS='bdrv_dpupbw64_10.0.6.sfs'

• DISTRO_PUPPYSFS='puppy_dpupbw64_10.0.6.sfs'

• DISTRO_ZDRVSFS='zdrv_dpupbw64_10.0.6.sfs'

• DISTRO_FDRVSFS='fdrv_dpupbw64_10.0.6.sfs'

• DISTRO_ADRVSFS='adrv_dpupbw64_10.0.6.sfs'

• DISTRO_YDRVSFS='ydrv_dpupbw64_10.0.6.sfs'

• DISTRO_PUPPYDATE='Mar 2024'

• DISTRO_ARCHDIR='x86_64-linux-gnu'

▶—— /etc/os-release ——◀

NAME=Puppy
VERSION="10.0.5"
ID=debian
VERSION_ID=10.0.5
PRETTY_NAME="BookwormPup64 10.0.5"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:puppy:puppy_linux:10.0.5"
HOME_URL="http://puppylinux.com/"
SUPPORT_URL="http://www.murga-linux.com/puppy/index.php"
BUG_REPORT_URL="https://github.com/puppylinux-woof-CE/woof-CE"
VERSION_CODENAME=bookworm

[bigpup]

If Conman connection manager is working then your problem is fixed.

It is a new network connection program and is much better than the other ones.

Do not worry about what it is using for the name of the WIFI device.
Those names are nothing but something to identify it.

Is the device providing the WIFI signal not very old?
If yes.
It most likely has some of the newer abilities, and is identified by these features.

What is the difference between WPA and RSN?
RSN is more comprehensive and includes support for AES (Advanced Encryption Standard), which is available only on the latest WLAN hardware. WPA uses existing technology such as IEEE 802.1x, EAP, TKIP and RADIUS.

The other older connection programs are still being provided for maybe very old hardware support and why not.
Some people like using them instead of Conman.
They do offer some options Conman does not.

Conman is a simple get connected program, that does a lot of things automatically.
About all that is offered is what WIFI signal to use and the passphrase to connect.

If both devices you are using for WIFI have ability to use RSN and can auto select to use it.
Conman could have actually used RSN for the connection.

[nnriyer]

ConnMan is connecting wifi instantly whereas other options are not connecting to my Wfi network due to reasons beyond my knowledge. May be due to encryption or other technical issues. Seems that I can manage wifi connection with ConnMan Network Manager.

[rcrsn51]

@nnriyer What kind of network is this? A home network? An enterprise network like a university or business?

Or are you connecting to a cellphone hotspot? You mention WPA3 above. You may need a special wpa_supplicant.conf setup to manage this.

It would be useful for Puppy to understand what's happening here. Just saying "Connman works, so use it instead" is not helpful.

[nnriyer]

Sir, connection from Mobile Hotspot having Android 14. Following security available in Android Mobile Moto 54G

WPA3-Personal
WPA2/WPA3-Perasonal
WPA2-Personal
None.

I think, Android 14, security setting is strong. I feel, i got connected to WPA2 in Android 12. I

[rcrsn51]

It sounds like the issue is WPA3 and you need a modified wpa_supplicant config file. This is easy to do in PeasyWiFi. I don't know how to do it in the other Puppy connection tools.

[rerwin]

It sounds like the issue is WPA3 and you need a modified wpa_supplicant config file. This is easy to do in PeasyWiFi. I don't know how to do it in the other Puppy connection tools.

rcrsn51,

If/when you get WPA3 working in PeasyWiFi, I can implement it in the Puppy tools. Thanks for considering the modification. I hope nnriyer can help us test the mods.

Richard

[rcrsn51]

If/when you get WPA3 working in PeasyWiFi, I can implement it in the Puppy tools. Thanks for considering the modification. I hope nnriyer can help us test the mods.

There's lots of info online about how to modify a wpa_supplicant.conf file for WPA3. It's just a couple of changes to the WPA2 file. But I don't have access to a WPA3 network to test it and there appear to be several minor variations.

I don't know which Puppy connection managers give the user access to the wpa_supplicant.conf file so they can change it manually on the fly.

[bigpup]

ConnMan is connecting wifi instantly whereas other options are not connecting to my Wfi network due to reasons beyond my knowledge. May be due to encryption or other technical issues. Seems that I can manage wifi connection with ConnMan Network Manager.

The other connection programs require some selections to be made by you.
They can be confusing, the very first time you use them.
The Network Wizard, is all a bunch of selections you have to make, to get connected, and it is very confusing, the first time using it.

As you have seen, Conman is simple to use.

[rcrsn51]

I don't know which Puppy connection managers give the user access to the wpa_supplicant.conf file so they can change it manually on the fly.

Is there no way to do this? It would be nice to test these new wpa3 methods.

[rerwin]

rcrsn51,

In Network Wizard, the wpa_supplicant profiles are in:
/etc/network-wizard/wireless/wpa_profiles/xx:xx:xx:xx:xx:xx.WPA2.conf.

In SNS, the profiles are in:
/etc/simple_network_setup/wpa_supplicant.conf-(SSID)-xx:xx:xx:xx:xx:xx

Those might be something to modify and then reboot.

Richard

[rcrsn51]

Then here are two versions for nnriyer to test:

#pure wpa3 network
network={
ssid="your_ssid"
sae_password="your_password"
key_mgmt=SAE
ieee80211w=2
}

#mixed network
network={
ssid="your_ssid"
psk="your_password"
key_mgmt=WPA-PSK-SHA256
ieee80211w=2
}