32-bit Jammy & SPup won't connect to hidden wifi. Bionic & Fossa Pups will.

[amethyst]

I've downloaded the latest 32-bit Jammy and SPup to check them out and both do not connect my hidden wifi connection after setup. I do not have this problem with Bionic and Fossa Pups.

[amethyst]

Okay, so I extracted the Network Wizard package used by Bionic, repackaged it and loaded it as an adrv. It now works for me in Jammy. There seems to be problems with the latest Network Wizard shipped with the newest Puppys.

[rockedge]

@amethyst Just saw a beautiful polished example of amethyst. Really amazing depth of color. (my birthday is in February)

This problem is in the Network Wizard on the 32 bit versions of Jammy or also the 64 bit? Also observed in other newer Puppy's?

[amethyst]

@amethyst Just saw a beautiful polished example of amethyst. Really amazing depth of color. (my birthday is in February)

This problem is in the Network Wizard on the 32 bit versions of Jammy or also the 64 bit? Also observed in other newer Puppy's?

Checked the very latest 32-bits Jammy and SPup. Both have issues. The script has changed...

[bigpup]

Will you give specific details on what does not work?
You do this?
You see this?

With that specific information.

I can make a issues report at Woof-CE, where the changes to Network Wizard was done.
https://github.com/puppylinux-woof-CE/woof-CE

[amethyst]

Will you give specific details on what does not work?
You do this?
You see this?

With that specific information.

I can make a issues report at Woof-CE, where the changes to Network Wizard was done.
https://github.com/puppylinux-woof-CE/woof-CE

The changers of the code should compare the previous script with this one to see where they went wrong. I see nothing different in setting up of the hidden connection but it just doesn't connect. Anyways - I'm using the older script instead which works. BTW - There is also something wrong with PPM in Jammy 32-bit but I don't have time now.

[peebee]

Was last changed in Sep 2022 by @rerwin :
https://github.com/puppylinux-woof-CE/w ... ork_wizard

Commits on Sep 6, 2022
Merge pull request #3370 from rserwin1/network_connect_20220901

@01micko
01micko committed on Sep 6, 2022
Copy the full SHA
View commit details
View at this point in the history
Browse the repository at this point in the history
Commits on Sep 4, 2022
use WAYLAND_DISPLAY to detect graphical sessions

@dimkr
dimkr committed on Sep 4, 2022
Copy the full SHA
View commit details
View at this point in the history
Browse the repository at this point in the history
Commits on Sep 3, 2022
network-wizard 2.2.1: improve probability of a valid IP address, etc.

@rserwin1
rserwin1 committed on Sep 3, 2022
Copy the full SHA
View commit details
View at this point in the history
Browse the repository at this point in the history
Commits on Apr 25, 2021
network-wizard 2.2: Display corrected progress windows, fixes, etc.

@rserwin1
rserwin1 committed on Apr 25, 2021
Copy the full SHA
View commit details
View at this point in the history
Browse the repository at this point in the history
Commits on Jan 28, 2021
combobox is missing in GTK 3, switch to comboboxtext

@dimkr
dimkr committed on Jan 28, 2021
Copy the full SHA
View commit details
View at this point in the history
Browse the repository at this point in the history
Commits on Apr 20, 2020
net-setup.sh: Restore proper /dev/null indirection

@rserwin1
rserwin1 committed on Apr 20, 2020
Copy the full SHA
View commit details
View at this point in the history
Browse the repository at this point in the history
Commits on Apr 19, 2020
network_connect: Increase wait for link detection; replace if/iwconfi…

@rserwin1
rserwin1 committed on Apr 19, 2020
Copy the full SHA
View commit details
View at this point in the history
Browse the repository at this point in the history
Commits on Jul 6, 2019
[global] &>/dev/null = >/dev/null 2>&1

@wdlkmpx
wdlkmpx committed on Jul 6, 2019

[dimkr]

I can make a issues report at Woof-CE, where the changes to Network Wizard was done.
https://github.com/puppylinux-woof-CE/woof-CE

You can open issues for the network wizard, PPM and other unmaintained things in woof-CE. The question is, who is going to address them and when.

[amethyst]

I can make a issues report at Woof-CE, where the changes to Network Wizard was done.
https://github.com/puppylinux-woof-CE/woof-CE

You can open issues for the network wizard, PPM and other unmaintained things in woof-CE. The question is, who is going to address them and when.

Why change something that works and have been working correctly for ages? Use the older script.

[rockedge]

Why change something that works and have been working correctly for ages? Use the older script

.

Can't always. Conditions outside of the script change and the code must be altered to match.

I will put this on the huge stack of the "To Do" tasks near the top and reluctantly look it over to appease the Gods.

When did the PPM work even near 100%?? I can't recall a time there was no report on PPM failures.

First things first...compare the scripts and try to reproduce the problem.

[amethyst]

Why change something that works and have been working correctly for ages? Use the older script

.

Can't always. Conditions outside of the script change and the code must be altered to match.

I will put this on the huge stack of the "To Do" tasks near the top and reluctantly look it over to appease the Gods.

When did the PPM work even near 100%?? I can't recall a time there was no report on PPM failures.

First things first...compare the scripts and try to reproduce the problem.

I'm encountering strange things when installing pets, things I've never experienced before. Same pets have been installed on older pups. Example: Install two of the pets, works. Install another pet, now one of the pets I've already installed automatically uninstalls and remove itself from menu and so on. Really, really strange behaviour. Some pets say it's installed (confirmation at install) but it's not installed. It's a mess.

[rockedge]

@amethyst I will go with Jammy32 to begin to wade into the process of reproducing some errors.

How is the hidden network setup that fails to connect?

Can you list some of the PET's that I should work with to replicate the behavior you're experiencing?

[amethyst]

@amethyst I will go with Jammy32 to begin to wade into the process of reproducing some errors.

How is the hidden network setup that fails to connect?

Can you list some of the PET's that I should work with to replicate the behavior you're experiencing?

I've installed the pets of my utilities I have shared here. I have the utility suite installed and the Powertimeout one. Seem to have issues with my Packkage remover and package extractor pets. None of my pets present issues with other Puppys. As a test i"ve just checked to install my package extractor pet. Now the latter is installed but the Powertimeout has automatically removed itself (uninstalled all by itself). You can only set up the hidden network with Dougals. You first need to scan the available networks, which step works. You then setup the particulars for the hidden network you want to use. Here is where I've spotted a change between the scripts. The older ones show the selected hidden connection as 0x (which is correct) which you then change with your user particulars and password. The newer script shows nothing. You then proceed with the setup but the newer script ultimately does not connect.

[rockedge]

@amethyst,

I just built a JammyPup32 with the official designation upupjj+d-22.04.iso on local machine setup successfully using woof-CE updated to the very latest commits. (I'm pretty sure....)

Now running on a 32bit QEMU VM hosted by a F96-CE_4, it looks ready for some testing and breakage detection. I will start off on a VM to see what happens with various installs in this environment.

Screenshot(48).jpg (23.64 KiB) Viewed 493 times

[rerwin]

I've downloaded the latest 32-bit Jammy and SPup to check them out and both do not connect my hidden wifi connection after setup. I do not have this problem with Bionic and Fossa Pups.

@amethyst (and others),
Sorry to take so long to respond to your problem with a hidden network.

I infer from your report that setup connects but rebooting fails to detect the network. Right?

A difference between the Bionic netwiz version 2.1 and 2.2.1 is that the latter recognizes hidden networks that appear as
\x00\x00\x00\x00\x00\x00\x00\x00
in addition to those appearing as null or <hidden>. The added code checks for \x00 and forces the SSID value to null, so later logic should see the null value, as before.

My hidden network SSID is hex zeroes (\x00...) in the scan but '(hidden ESSID)' in netwiz) and connects as expected both during setup and upon reboot. I could not test with a null-indicated hidden network, although I see them in my neighborhood.

Because the Help page does not address hidden networks, we seem to be "on our own" to figure out how to deal with them. In my update for "\x00" SSIDs, I assumed that the user is expected to provide it along with the security key (passcode). My way of setting up a connection is to:

• Scan and select the first SSID identified as hidden, which I assume is the strongest, and click OK.

• Click on "WPA2" to show the "Shared key" input field.

• Ensure that "Hidden SSID" is checked, unchecking "Broadcast SSID" if necessary.

• Enter a new profile name, the actual SSID and the passcode.

• Click "Save".

• Click "Use this profile".

I then see the message "Puppy was able to find a live network.". Once I click on "Auto DHCP", get a successful connection, save the configuration and reboot, the connection occurs as expected.

How have you been setting up a connection to a/your hidden network? If it is different from the above, that may be why netwiz appears to fail.

I have seen advice somewhere about using \x00\x00\x00\x00\x00\x00\x00\x00 as the SSID, but that does not seem to work even on older netwiz versions (Bionic's 2.1).

I am curious to see what the scan shows you as SSIDs for hidden networks. Assuming the interface is wlan0, please try either of these command strings:

Code: Select all

iwlist wlan0 scan | grep -E 'Cell |ESSID:'
iw wlan0 scan | grep -E '^BSS |SSID:|signal:'

(If you post the results, please substitute for your actual SSID if it appears -- mine sometimes does!)

Thanks to your report, I discovered a bug exposed when I try to use a blank SSID.

BTW, the latest SNS (3.3.1) also supports hidden SSIDs. Please consider trying it.

Richard

[amethyst]

@rerwin
Thanks for your response. I'm using the older version instead which works fine. Not bothered to struggle again with the newer version(s). I've started up Fossa64CE which uses conman by default. That setup was very easy and quick. Works well.