Pwireless2 (Version 1.0)

Configuration wizards, scanners, remote desktop, etc.
Message
Author
ahm
Posts: 1
Joined: Sun 28 Mar 2010, 14:26

Bug in Pwireless2 Beta 2.9 Scanned AP Display

#201 Post by ahm »

First of all, Pwireless2 is great. Much better than the old Network Wizard. I use Browser Linux on my Asus netbook and Pwireless2 makes connecting easy. At least that was the case. I recently got a new router - a Netgear WGR614v10 - just a basic G router really. Imagine my surprise when my Ubuntu laptop, my Windows 7 netbook and my old HP XP laptop would see and connect to my AP but my little Asus netbook with Browser Linux 362 wouldn't. What I found most amusing was that it would see all the many APs that exist in my condo complex but not mine. Quite baffling. After some futzing around with router settings I finally went to the code for Pwireless2. In the directory where the scripts are located I found "get_scan_results". Here wpa_cli is used to get a list of APs and then that list is filtered and sent to the main program for display. One part of the pipeline is:

Code: Select all

egrep ^[0123456789]
which essentially gets rid of the line of text put out by the wpa_cli command. The only problem with this is that not every wireless AP MAC starts with a number. Mine starts with a "c03f" which is assigned to Netgear. I "fixed" the problem by just adding a "c" to the expression. Again, Pwireless2 is a great little program for Puppy Linux. Keep at it.

User avatar
technosaurus
Posts: 4853
Joined: Mon 19 May 2008, 01:24
Location: Blue Springs, MO
Contact:

#202 Post by technosaurus »

should it then be [a-f0-9] ??? to cover all hex values
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].

User avatar
drongo
Posts: 374
Joined: Sat 10 Dec 2005, 23:35
Location: UK

hex values

#203 Post by drongo »

Yes, MAC addresses can contain any hex value, as can WEP and WPA passwords!

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#204 Post by jemimah »

Yep, my bad. I'll fix that for the next version.

User avatar
scrappy
Posts: 12
Joined: Tue 30 Mar 2010, 09:10

#205 Post by scrappy »

hello all, i am new on this forum and i am using puppy linux 4.3.1 beta 2 startdust. This version uses the pwireless2 program.

I have a toshiba laptop with a realtek 8192 wifi card and have installed the linux driver for it : r8192se_pci-14.0115.2010-k2.6.30.5.pet.

I have an internet connection but it is verry poor. The speed is so slow that a programm like pidgin loses its connection verry often. I have tryed this laptop on a cable and that worked perfect, lan card was nicely picked up by puppy.

ndiswrapper i no solution because i have tryed different window drivers and had no succes at all.

Can someone help me ?? My knolledge on linux is poor so please be patient with me :-)

ps, i am sorry if this post is posted on the wronge tread.

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#206 Post by jemimah »

That driver is still "experimental," so you may be stuck waiting until a stable driver is developed.

If it's only the wpa-supplicant support that's flaky, you might find that the traditional network wizard works better for you.

You can try posting in the hardware forum and see if anyone else has had success with that card.

User avatar
scrappy
Posts: 12
Joined: Tue 30 Mar 2010, 09:10

#207 Post by scrappy »

jemimah wrote:That driver is still "experimental," so you may be stuck waiting until a stable driver is developed.

If it's only the wpa-supplicant support that's flaky, you might find that the traditional network wizard works better for you.

You can try posting in the hardware forum and see if anyone else has had success with that card.
....thx for the rappid reply. I will try the traditional network wizzard and see if that helps. I have looked around on this forum but didn't find any usefull info other than the posted linux driver. Will try the hardware forum if this doesn't work.....

thx again jemimah

User avatar
scrappy
Posts: 12
Joined: Tue 30 Mar 2010, 09:10

#208 Post by scrappy »

Sorry to say that the traditional wizzard had no effect at all, it doesn't see any interface at all. Will try to get some info on the hardware form.

husker_pick
Posts: 6
Joined: Wed 07 Apr 2010, 06:36

#209 Post by husker_pick »

I found Pwireless2 when checking out different puplets (Wolfpup) and it said no wireless adapters found. It worked in 4.3.1 and other Distros like Zenwalk. Trying to find a very simple mother-in-law distro for an ancient slow notebook.

I have a very old orinoco pcmcia Lucent Wavelan Silver 802.11b card that shows up as eth0 in iwconfig.

YOUR ADVICE BELOW SOLVED THE PROBLEM. (After deleting profiles and disabeling rc.network per above posts)

Try running /etc/init.d/Pwireless2 (from command line or clicking it should work) and see if that fixes it. If it does, you should be able to move it to /root/Startup and it should get run from there.

Thanks so much for a good wireless gui for puppy maybe this should be the default launch location.

pick
EDIT P.S. You're getting very close to wicd!

player_one
Posts: 8
Joined: Thu 16 Apr 2009, 22:36

Pwireless2 and fluppy

#210 Post by player_one »

Hello Jemimah, one of our users (italianpuppy.org) is experiencing problems with Pwireless2 in puppy 4.3.1 (doesn't find any wireless connection), while on fluppy with the same notebook it works fine. So I was wondering: is there any difference between the 2 Pwireless2? Maybe the one on fluppy is the most updated? Thanks.

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#211 Post by jemimah »

Yes there are a few updates in Fluppy that aren't in this version. It's probably time to update the pet. :)

player_one
Posts: 8
Joined: Thu 16 Apr 2009, 22:36

#212 Post by player_one »

Ok, thank you!

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#213 Post by jemimah »

I've posted an update. Most of the changes are minor bugfixes and enhancements.

I no longer consider this Beta, so enjoy!

(Keep in mind I only test on 4.3 so other Puplets may need to repackage it if it init.d scripts work in a different way or something.)

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#214 Post by 01micko »

Hi jemimah,

Couple of questions..

1) I plan to re-package this up for Lucid Puppy.. do you think it necessary to recompile wpa_supplicant and wpa_cli against the ubuntu libs for compatibility? If so, can you post your configure file please? Also the Lupu kernel is recompiled against gcc-4.4.3. Would that make a difference?

2) what about dhcpcd? It's already there, but in Lupu, there is a symlink in /usr/local/sbin/dhcpcd to /usr/sbin/dhcpcd. Can I use those and just add the extra stuff you have in /lib/dhcpcd/ ?

Thanks for this cool app, my wife's machine has been running an early beta for about four months or so without a problem.

Cheers
Puppy Linux Blog - contact me for access

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#215 Post by jemimah »

You can probably use the native wpa_supplicant and dhcpcd as long a they are sufficiently recent (which I'm sure they are in LuPu). I only include binaries in the pet because in a lot of Puplets these are too old, and upgrading breaks the Network Wizard.

I'm attaching the .config for wpa_supplicant.

You can edit /usr/local/Pwireless2/config to tell it which wpa-supplicant and dhcpcd to use.

Let me know if you have any difficulty.
Attachments
.config.gz
(5.14 KiB) Downloaded 897 times

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#216 Post by 01micko »

OK, thanks for speedy response :)

Shall edit /usr/local/Pwireless2/config per your advice. The wpa_* execs are in /sbin in Lupu. ... dhcpcd should be ok as the symlink is already there on /usr/local/sbin.

These files are the extras in /lib/dhcpcd
  • 99-dhcpup
    99-down
    99-ifup
    99-release
    99-stop
    99-timeout
    99-up
I'll add those as well and let you know how it goes.

Cheers
Puppy Linux Blog - contact me for access

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#217 Post by jemimah »

One thing to check for is if your wpa_supplicant supports the -f option to write the log to a file. I think that's not on by default, but it is rather useful, and Pwireless2 needs it.

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#218 Post by 01micko »

Code: Select all

# wpa_supplicant -h    
wpa_supplicant v0.6.9
Copyright (c) 2003-2009, Jouni Malinen <j@w1.fi> and contributors

This program is free software. You can distribute it and/or modify it
under the terms of the GNU General Public License version 2.

Alternatively, this software may be distributed under the terms of the
BSD license. See README and COPYING for more details.

This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)

usage:
  wpa_supplicant [-BddhKLqqstuvW] [-P<pid file>] [-g<global ctrl>] \
        -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] [-p<driver_param>] \
        [-b<br_ifname>] [-f<debug file>] \
        [-N -i<ifname> -c<conf> [-C<ctrl>] [-D<driver>] \
        [-p<driver_param>] [-b<br_ifname>] ...]

drivers:
  wext = Linux wireless extensions (generic)
  nl80211 = Linux nl80211/cfg80211
  atmel = ATMEL AT76C5XXx (USB, PCMCIA)
  wired = wpa_supplicant wired Ethernet driver
options:
  -b = optional bridge interface name
  -B = run daemon in the background
  -c = Configuration file
  -C = ctrl_interface parameter (only used if -c is not)
  -i = interface name
  -d = increase debugging verbosity (-dd even more)
  -D = driver name (can be multiple drivers: nl80211,wext)
  -f = log output to debug file instead of stdout
  -g = global ctrl_interface
  -K = include keys (passwords, etc.) in debug output
  -s = log output to syslog instead of stdout
  -t = include timestamp in debug messages
  -h = show this help text
  -L = show license (GPL and BSD)
  -p = driver parameters
  -P = PID file
  -q = decrease debugging verbosity (-qq even less)
  -u = enable DBus control interface
  -v = show version
  -W = wait for a control interface monitor before starting
  -N = start describing new interface
example:
  wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
# 
Looks ok I think

Thanks
Puppy Linux Blog - contact me for access

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#219 Post by jemimah »

Yup looks good.

I had an extra Pwireless2.old script in /etc/init.d. I have removed it and uploaded a fixed pet.

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#220 Post by 01micko »

Well it works, :D but there is a bug in the Lupu /etc/rc.d/rc.sysinit script :(

Code: Select all

#100227 choose default network tool...
NETCHOICE='other' #100304
DEFAULTCONNECT="`cat /usr/local/bin/defaultconnect | tail -n 1 | tr -s " " | cut -f 2 -d " "`"
[ "`grep 'gprs' /usr/local/bin/defaultconnect`" != "" ] && DEFAULTCONNECT='pgprs-connect'
[ "$DEFAULTCONNECT" = "gkdial" ] && DEFAULTCONNECT="pupdial" #for older pups.
case $DEFAULTCONNECT in
 Pwireless2)
  NETCHOICE='Pwireless2'
 ;;
 net-setup.sh)
  NETCHOICE='net-setup.sh'
 ;;
 net_wiz_classic)
  NETCHOICE='net_wiz_classic'
 ;;
 sns)
  NETCHOICE='sns'
 ;;
 *) #try determine which tool was used to setup networking...
  if [ -s /etc/simple_network_setup/connections ];then #100306
   NETCHOICE='sns'
  else
   CHECKOLDWIZ="`ls -1 /etc/*[0-9]mode 2>/dev/null`" #ex: eth0mode, wlan0mode.
   if [ "$CHECKOLDWIZ" != "" -a -d /usr/local/net_setup ];then
    NETCHOICE='net_wiz_classic'
   else
    CHECKNEWWIZ="`ls -1 /etc/network-wizard/network/interfaces 2>/dev/null`"
    if [ "$CHECKNEWWIZ" != "" ];then
     NETCHOICE='net-setup.sh'
    else
     [ -f /usr/local/Pwireless2/interface ] && NETCHOICE='Pwireless2' #100304
    fi
   fi
  fi
 ;;
esac
[ -f /etc/init.d/Pwireless2 ] && chmod 644 /etc/init.d/Pwireless2 #prevent jemimah's script from running. 100304 100513
I tried Pwireless2 pfix=ram and rebooted, but the permissions on /etc/init.d/Pwireless2 were 644 ... why? ....So I dug up where they get changed. That's all well and good if you chose something beforehand, but probably not good for Pwireless2. I think this is the same script in Quirky.

So, what did I do? Yeah, one of my gross hacks :roll:

Code: Select all

set -x

if [ -f /usr/local/Pwireless2/interface ];then echo true
	else chmod 755 /etc/init.d/Pwireless2 2>/dev/null
	exec /etc/init.d/Pwireless2
fi

. /usr/local/Pwireless2/config

WIFI_IF=`cat /usr/local/Pwireless2/interface`

[ -z $WIFI_IF ] && exit




gtrayicon --activate="/usr/local/Pwireless2/connect" --activate-icon=/usr/share/pixmaps/network-offline.png --deactivate="/usr/local/Pwireless2/disconnect" --deactivate-icon=/usr/share/pixmaps/network-transmit-receive.png --menu-file=/usr/local/Pwireless2/network.menu --tooltip='Click to connect or disconnect Pwireless2'&
$WPA_CLI -i $WIFI_IF status|grep COMPLETED 
if [[ $? == 0 ]] ; then
	sleep 1
        killall -SIGCONT gtrayicon
	$DHCPCD -n $WIFI_IF
	exit
fi

pidof dhcpcd
if [[ $? != 0  ]] ; then
	/usr/local/Pwireless2/start-dhcp
fi
Far from perfect, but will do for me until woof is fixed.

Thanks for all your help.

Cheers
Puppy Linux Blog - contact me for access

Post Reply