Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 20 Sep 2017, 05:27
All times are UTC - 4
 Forum index » Advanced Topics » Hardware » Networking » Wireless
PeasyWiFi - a reliable WiFi connection manager
Post new topic   Reply to topic View previous topic :: View next topic
Page 16 of 16 [235 Posts]   Goto page: Previous 1, 2, 3, ..., 14, 15, 16
Author Message
Marv


Joined: 04 May 2005
Posts: 857
Location: SW Wisconsin

PostPosted: Mon 17 Jul 2017, 12:09    Post subject:  

rcrsn51 wrote:
PWF v4.3 adds a new "quick-connect" function to the Profile page.

Some wireless access points, like WiFi-Direct printers, have the annoying habit of changing their SSID, forcing you to make a new profile with each change. Now you can join the AP just by clicking the Connect button and entering the WPA2 passphrase.

You can also use this feature for a one-time connection to a secure network.


Got it! Downloaded and installed on my newest, a core i5-2520M with an Qualcomm Atheros AR9287 Wireless Network Adapter using the ath9k driver. Running LxPupSc 17.07.23 for now. No hitches, no glitches. Took it down to the bike commons to check the new 'quick connect with password, no profile' feature and it works perfectly. The last of my Pentium M stable of laptops have retired and I'm vetting three new to me Fujitsus, two i5 based and one core 2 duo convertible tablet. PWF for all!

Thank you,

Edited: LxPupSc version number corrected

_________________
Pups currently in kennel Very Happy X-slacko 4.3 and X-tahr 2.0 for my users; LxPupSc and LxPupXenial for me. All good pups indeed, and all running browsers, office etc. solely from SFS.
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1821
Location: Maine, USA

PostPosted: Sat 29 Jul 2017, 14:43    Post subject:  

rcrsn51,
Although I have not been following this thread about PeasyWiFi, I looked more closely on 8/27 and am impressed by what you have done. I note that you have been keeping up with the changes I have made to the networking wizard and its friends.

I think the connectwizard components need to accommodate PeasyWiFi, so have updated the 8/27 release (20170727) to add some compatibility, announced here:
http://www.murga-linux.com/puppy/viewtopic.php?p=962134#962134
The significant change, for PeasyWiFi, is that the /etc/rc.d/rc.network script is now associated only with the network wizard. So, the network_default_connect script can start the rc.network.pwf script wherever it resides.

If PeasyWiFi is installed and has a profile defined, network_default_connect (in 20170729) now looks for "rc.network" in /usr/local/peasywifi, in case you decide to move it there. If not there, a link will be placed there pointing to /etc/rc.d/rc.network.pwf, during boot-up.

Since PWF 4.3 does not contain the call to identify itself to connectwizard, it should be installed before any other network manager is used or set as default. PeasyWiFi can be set as the default manager, but need not be.

PeasyWiFi can benefit from the recent network_connect improvements if a few simple but tedious changes are made to it. I am willing to make those changes, with your permission. The changes I propose are:
    - Add PeasyWiFi identification to connectwizard, which will then stop any other running network manager and its connection.
    Code:
    which connectwizard_exec &>/dev/null && connectwizard_exec peasywifi
    - Make the gtkdialog dialog names unique to PeasyWiFi by changing "DIALOG" to "PEASYWIFI_DIALOG", so they can be found and killed when another network manager starts.
    - Make the Xdialog processes include '--wmclass "peasywifi"', so they can be found and killed when another network manager starts. That also specifies an icon to be used for the Xdialog window; I suggest adding a link, /usr/share/pixmaps/peasywifi.png, pointing to peasywifi-48.png (or -24 if necessary).
    - Consider adding code to rc.network.pwf to support disconnecting a connection, to cleanly shut down a connection the "PeasyWiFi way." That would allow disconnection from the networking tray icon, as well as for switching away from using PeasyWiFi.
If you need anything further from me, to integrate PeasyWiFi into the mainstream, please tell me. I am open to adding PeasyWiFi as a choice in the connectwizard networking dialog, if and whenever you are ready for that.
Richard
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11580
Location: Stratford, Ontario

PostPosted: Sun 30 Jul 2017, 15:24    Post subject:  

PWF's most recent post-install script registers itself in /usr/local/bin/defaultconnect and deletes /root/.connectwizardrc.

So in network_default_connect, the value of CURRENT_EXEC and NETCHOICE should be "peasywifi".

PWF puts its rc.network in /etc/rc.d - moving it elsewhere would be problematic in several ways. So line 58 could just be
Code:
 peasywifi) /etc/rc.d/rc.network & ;;


This setup should maintain backwards compatibility.

BTW, I don't understand the role of lines 26-43. Also, why is frisbee not included in the final case structure?
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1821
Location: Maine, USA

PostPosted: Mon 31 Jul 2017, 16:06    Post subject: Integrating PeasyWiFi into Puppy  

rcrsn51,
Thanks for getting back to me about this.

rcrsn51 wrote:
PWF's most recent post-install script registers itself in /usr/local/bin/defaultconnect and deletes /root/.connectwizardrc.
The new "network connect" version submitted to woofCE and posted elsewhere uses the defaultconnect value only as a last resort. The current manager name is kept in .connectwizardrc, independent of the default. So, deleting it defeats the purpose of the effort to keep managers from inadvertently interfering with each other. Now, SNS, netwiz and frisbee use the "_exec" service to identify themselves as current and ensure that the previously running manager is cleaned up after, in case it has dialog windows displaying.

Quote:
So in network_default_connect, the value of CURRENT_EXEC and NETCHOICE should be "peasywifi".
That is what I am using.

Quote:
PWF puts its rc.network in /etc/rc.d - moving it elsewhere would be problematic in several ways. So line 58 could just be
Code:
 peasywifi) /etc/rc.d/rc.network & ;;

This setup should maintain backwards compatibility.
This is where PWF violates the practice of keeping program names (or their path names) unique, so that an unfamiliar troubleshooter can know what programs are running and where to find them. Script /etc/rc.d/rc.network is part of the Network Wizard, but has been used in Puppy even without a connection having been defined through net-setup.sh. Now, Barry has replaced that "outside" use of rc.network with the simpler rc.network_eth. With netwiz now in its own package, it can be omitted altogether from a distro. That would impact PWF, which should be independent of other managers. Ideally, and consistent with the other managers, netwiz should reside in /usr/local/network_wizard -- and I am not ruling out doing that.

Other than requiring some straightforward coding changes, how is it problematic to make it both forward and backward compatible? PWF can use the presence of connectwizard_exec as the indicator of the operating environment. Instead of replacing rc.network with the .pwf file, simply replace it with a link to the rc.network(.pwf) script in PWF's directory. But you wouldn't need to do any of that if "_exec" is present.

Quote:
BTW, I don't understand the role of lines 26-43.
That case structure handles the case when no default manager has been set, making a best guess given what it finds in the way of connections but using frisbee only if it is "active".

Quote:
Also, why is frisbee not included in the final case structure?
It is handled by the "*)" case, because its /etc/init.d script detects whether it is active (the current manager) and initializes if it is.

I hope this "eases your mind" about integrating PWF into Puppy, in a backward compatible way.
Richard
Back to top
View user's profile Send private message 
jd7654

Joined: 06 Apr 2015
Posts: 236

PostPosted: Wed 09 Aug 2017, 15:08    Post subject:  

Haven't used PeasyWifi before, only now saw its use in DebLive-Stretch from Fred's mklive-stretch builder.

The connection seems simple and works, but does not survive a reboot and come up working.
Where is it supposed to store config, and does that work in Debian Dog and the DebLive-Stretch?
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11580
Location: Stratford, Ontario

PostPosted: Wed 09 Aug 2017, 15:22    Post subject:  

jd7654 wrote:
The connection seems simple and works, but does not survive a reboot and come up working.

Details please.

Quote:
Where is it supposed to store config, and does that work in Debian Dog and the DebLive-Stretch?


Did you make a connection profile under the Profiles tab? Did you try clicking the Check button? At the next session, did your profile appear in the Profiles drop-down list in the main screen?

The version of PWF in Stretch needs some symlinks:

Code:
ln -sf /usr/bin/leafpad /usr/local/bin/defaulttexteditor
ln -sf /usr/bin/pcmanfm /usr/local/bin/rox
ln -sf /path/to/your/browser /usr/local/bin/defaultbrowser
Back to top
View user's profile Send private message 
jd7654

Joined: 06 Apr 2015
Posts: 236

PostPosted: Wed 09 Aug 2017, 16:40    Post subject:  

rcrsn51 wrote:
Details please.

Did you make a connection profile under the Profiles tab? Did you try clicking the Check button? At the next session, did your profile appear in the Profiles drop-down list in the main screen?

The version of PWF in Stretch needs some symlinks:

Code:
ln -sf /usr/bin/leafpad /usr/local/bin/defaulttexteditor
ln -sf /usr/bin/pcmanfm /usr/local/bin/rox
ln -sf /path/to/your/browser /usr/local/bin/defaultbrowser


I initially clicked config and it did nothing, the symlinks fixed that.
Tried connecting from Profile/Scan/Connect and that worked, but that doesn't populate config..
Made a profile but didn't work, but that was my error as I had WPA instead of WPA2 selected.

So I can use the saved config now and I see it in /etc/pwf/wifi, but can connection come up active automatically on boot like in Puppy sns, or have to launch pwf and connect each time?
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11580
Location: Stratford, Ontario

PostPosted: Wed 09 Aug 2017, 16:52    Post subject:  

jd7654 wrote:
but can connection come up active automatically on boot like in Puppy sns,

Look under the Auto tab.
Back to top
View user's profile Send private message 
jd7654

Joined: 06 Apr 2015
Posts: 236

PostPosted: Wed 09 Aug 2017, 17:05    Post subject:  

rcrsn51 wrote:
jd7654 wrote:
but can connection come up active automatically on boot like in Puppy sns,

Look under the Auto tab.


Auto worked, thanks. <slapping forehead>
Back to top
View user's profile Send private message 
OscarTalks


Joined: 05 Feb 2012
Posts: 1591
Location: London, England

PostPosted: Fri 25 Aug 2017, 15:06    Post subject:  

Thanks for PeasyWiFi.
Version 4.5 is working well for me.
This is my experimental Stretch Pup remaster based on the billtoo version.
Installed (frugal) in an old Dell Optiplex SFF with Edimax WiFi adapter which uses rt2800usb module.

The other network tools (SNS and DougalWiz) were proving unreliable, especially after reboot. Gave PeasyWiFi a try including the Auto feature and results have been flawless so far. I've been able to switch to VPN and back to my own normal IP. The tray icon changes (and changes back again) when I do this.

Earlier Puppies such as Wheezy and Slacko 5.7 are OK on this same hardware using the standard network tools, so not sure what has changed in Stretch. Anyway, PWF offers a solution.

_________________
Oscar in England

Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 16 of 16 [235 Posts]   Goto page: Previous 1, 2, 3, ..., 14, 15, 16
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware » Networking » Wireless
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0755s ][ Queries: 15 (0.0150s) ][ GZIP on ]