Wifi-Connect 2017B beta (Deprecated)

Message

gcmartin · #101 Post by **gcmartin** » Tue 28 Jun 2016, 22:00

In exposing the PET for testing, I am unsure of a method of replacing the bin file that wont lead to problems. Can you post a PET without the bin file. I will assume that without that included in the PET, the PET/subsystem will use the internal system's DHCPD. And, as such, the replacement would work in any system, 32/64.

Correct?

stemsee · #102 Post by **stemsee** » Tue 28 Jun 2016, 22:16

That seems correct to me.

Just download the pet posted and use uextract (or what have you) to extract the pet then remove /usr/sbin/dhcpcd binary file from the extracted pet, then rebuild the pet or make an sfs. Maybe run in term 'which dhcpcd' first to see where your existing dhcpcd is.

gcmartin · #103 Post by **gcmartin** » Tue 28 Jun 2016, 22:55

@Stemsee, I am sure you are aware, but might be important.

Some of my distros, i.e. Slacko 32/64 use /usr/sbin/udhcpd. Thus, these do not have a "DHCPD" as is currently in the Wifi-Connect PET for 32bit systems.

What is a proper way to use or test your PET in those systems? Or is there a PET available for those systems?

I ask, because if I remove the /usr/bin/dhcpd from the existing PET, will the Wifi-Connect 2016 functionality work as you expect it in those PUP distros using udhcpd? Thus a PET without the "dhcpd" component will work on all modern PUP distros no matter if they have either dhcpd or udhcpd. Is that correct?

Is a new PET in order?

Thanks in advance.

stemsee · #104 Post by **stemsee** » Wed 29 Jun 2016, 06:19

If your distro uses udhpcd then you can safely install the pet without overwriting udhpcd. My scripts do not use udhpcd if present although I looked at adding the possibilty just needs two variables, one for acquiring ip and one for releasing lease on interface. The switches/options are different for udhcpd and dhcpcd.

Install dhcpcd(5) using ppm or gslapt, or directly download package and install. I do not maintain dhcpcd, I maintain only wifi-connect scripts (wifiprofi, scanner, eduwifi, hotspot, wifi-connect and wifi-connect-2, and oui.txt for random mac address). All scripts have a routine for informing if any dependency is missing, independent of the installer.

stemsee · #105 Post by **stemsee** » Wed 29 Jun 2016, 09:04

Here is a pet with no dhcpcd and renamed, in case the name trips the install.

udhcpd/c is the busybox dhcp server which hasn't had work since 2002. Dhcpcd is an external server which had work up to about 4 years ago, on raspberrypi there is ongoing work here https://github.com/raspberrypi/dhcpcd-6 ... /changelog . Work by RedHat is current.

stemsee · #106 Post by **stemsee** » Wed 29 Jun 2016, 20:57

I see a let-down if the machine doesn't have a wifi-card there is zero functionality for ethernet. So now I will be adding more access for ethernet and usb.

slavvo67 · #107 Post by **slavvo67** » Thu 30 Jun 2016, 15:06

Stemsee:

Does this search for wifi drivers on the hard drive and wrap them? It would be nice to have that kind of functionality for people that can't find Linux drivers for their particular systems.

Kind regards,

Slavvo67

stemsee · #108 Post by **stemsee** » Thu 30 Jun 2016, 17:56

Slavvo

I had a look at how to use ndiswrapper. It seems there are two stages 1) associate the windows wifi driver *.inf with ndiswrapper 2) then use the -D switch to uspecify ndiswrapper as the driver when using wpasupplicant.

To build the module for each system seems to require installing the headers, and compiling ndiswrapper from source. Also requires downloading the windows driver for your wifi card/s and locating it.

I have no way to develope and test such routines as all my wifi cards work on linux.

Actually none of these scripts have the option to test or load other drivers.

If anyone wants to volunteer some tested code, great!

stemsee

gcmartin · #109 Post by **gcmartin** » Thu 30 Jun 2016, 18:26

I can see where system's available drivers would be outside of the scope of this utility. Still the utility has its solid offering for what it does in its mission. Ease!

The driver issue in Puppyland has been a "target" for years with no clear-cut direction. Some developers include all in base ... Some include drivers in zdrv/ydrv/adrv ... Some only include a subset ... Each distro has a reflection of what its developer feel best fro his offering.

This driver problem is consistent across operating systems.

Ease of use, though, and clear guidance in ease of use it what appears, here, leaving driver discovery to the base running system.

stemsee · #110 Post by **stemsee** » Thu 30 Jun 2016, 19:58

In the meantime here is wifi-connect-30

Solves wlan1/2 start/stop bug in wifi-connect-2 menu.

Introduces code that should allow the gui to start when no wifi-card found (not tested by me as machine has two unremoveable cards)

Solves issue when only one AP is found; loop generated 30 entries the same for when only one AP found.

Scanner early menu wouldn't close

stemsee · #111 Post by **stemsee** » Fri 01 Jul 2016, 10:51

NoArch version without dhcpcd binary.

stemsee · #112 Post by **stemsee** » Sat 02 Jul 2016, 11:36

I have managed to code wifi-connect script to successfully connect using udhcpc if dhcpcd is not found. But dhcpcd is preferred if system has both.

I will test some more before adding that code to all scripts.

stemsee · #113 Post by **stemsee** » Sat 02 Jul 2016, 12:55

Ok ... finished testing!

Needs testing on other systems. Feedback essential.

Has dhcpcd i386 binary in.

fake .gz extensions just rename and remove the .gz

stemsee · #114 Post by **stemsee** » Tue 05 Jul 2016, 22:52

Icons updated. Also renamed apps to ; Wifi-Profiles, Wifi-Scanner and Wifi-Eduroam to match Wifi-Connect in Menu.

stemsee · #115 Post by **stemsee** » Mon 25 Jul 2016, 11:57

I have added simple profile management for saved profiles, available when using wifi-profiles app. Option to delete selected profile.

stemsee · #116 Post by **stemsee** » Tue 26 Jul 2016, 07:44

As far as I know, wifi-connect is the only application that can connect your pc to the internet using either udhcpc or dhcpcd, without user intervention.

I have been testing this feature for a couple of weeks now and no issues.

greengeek · #117 Post by **greengeek** » Fri 29 Jul 2016, 04:20

Hi stemsee - I gave this a try on a Slacko 5.6 derivative but it failed to run due to lack of zenity and yad. (Might be worth mentioning those dependencies if not already highlighted somewhere - I may have missed them).

Once the dependencies were added I got to first base but couldn't get scan results (which I assume is step one). Also ended up with two icons in the tray and couldn't terminate them. Will try again and report back with specifics once I know how to disable frisbee on my system - I think it lurks in the background and may interfere.

stemsee · #118 Post by **stemsee** » Fri 29 Jul 2016, 07:38

Wifi-connect should be the first script to use, for creating profiles, it also unblocks interfaces first.
Maybe try

Code: Select all

rfkill unblock all

in term first

I noted the same 'problem' with tray icons.

Thanks for reporting

stemsee · #119 Post by **stemsee** » Wed 31 Aug 2016, 10:32

I intend to rewrite the way the tray menus are handled. Firstly there will only ever be one menu generated from an exported function. All subsequent scripts will use the same comprehensive menu. Infos will be generated also using exported functions with timeouts thus eliminating the need to use Esc to close any dialogue box.

I may also add ndiswrapper functionality. Widi is also a possibility.

stemsee

gcmartin · #120 Post by **gcmartin** » Thu 01 Sep 2016, 05:41

WiDi +1

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Wifi-Connect 2017B beta (Deprecated)