PeasyWiFi - a reliable WiFi connection manager

[Geoffrey]

Here is my tip for such occasions.

Third last post....

Chris, you can link directly to any post, saves a lot of scrolling.
http://murga-linux.com/puppy/viewtopic. ... 765#810765

[cthisbear]

Geoffrey:

Hey! uncle Geoffrey.
Not happy now.

Been wondering how that happens, I bookmarked it and
will probably try that later.

Actually just re read that and it works. Einstein lives...

Thanks mate....Chris.

[uio]

Hi rcrsn51,

Well, the issue seems to have resolved itself. I'm not sure quite what it was but I think that it was a combination of the fact that the WiFi was weak (at the library for exampe, I had to move the laptop around a bit and then it connected), and perhaps the fact that I was using the same usb on a laptop (Thinkpad T40) and on a desktop computer.

So, all that said, I've been able to use WiFi correctly with the occasional graphical restart. But not enought to warrant, in my opinion, further investigation I think it is WiFi signal strength (or weakness....) induced.

Autostart works nicely (just used it).

Voilà.

uio

[Scooby]

Mucked around a bit with router and saw that I have
AES set for encryption with wpa2.

Now my peasywifi profile has

Code: Select all

proto=WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
}

It has TKIP for value, it still does connect despite the TKIP values

Can I edit TKIP here to AES? and if so should that not be a
an option in GUI in peasywifi?

could you please explain how a profile with AES should look?

[rcrsn51]

could you please explain how a profile with AES should look?

I don't know much about encryption, but I thought that CCMP meant AES.

[Scooby]

yeah you are quite right.

My asus router called it AES so I was confused.
Further reading gives that CCMP is the "correct" naming
of AES encryption in WPA2.

Sorry for bothering you.

This is why standard names are useful

[Pelo]

PeasyWifi 3.4 va bien aussi sur nos classiques puppy 4
good results too with our famous Puppies serie 4
Puplite 5.0 AND HUNGARIAN pUPPY BROWER 431;
Fast boot, impressive speed and wireless stable connection, what people could ask more ?
What a pleasure to run old CDs with PeasyWifi

Caution : no wlan0 , change it to eth0 or eth1, depending on the 'old' Puppy running.

[rcrsn51]

PWF v3.8 is posted on the main page. See the Update note.

[Scooby]

I am commandline jockey so I found it really useful to add bash completion
for peasywifi.

I am running an older version
with wpa profiles in path /etc/network-wizard/wireless/wpa_profiles

Anyway this would work with any path

As you know I like peasywifi and would like to share

if you add to ~/.bashrc this

Code: Select all

_peasywifi()
{
	local cur pwf
    cur=${COMP_WORDS[COMP_CWORD]}
    pwf=$( ls -1 /etc/network-wizard/wireless/wpa_profiles/ )
    COMPREPLY=( $(compgen -W "$pwf" -- $cur) )
}
complete -F _peasywifi peasywifi

Now in a terminal I can do p <tab> and get peasywifi and then
the first letter of my wpa profile file + tab and then hit return to connect.

Not for everyone I guess but for me that doesn't want to have a certain profile set to autostart it's gold

Just wanted to share

[rcrsn51]

PWF v4.1 makes a significant internal change. It removes dhcpcd as the DHCP client program in favour of Busybox udhcpc. Udhcpc is less intrusive and may eliminate connection problems like dropouts. Thank you to Marv for his help with this.

See the main post for details.

[akuma]

estoy probando esta aplicasion necesito saber como activar el Wlan1 ya que me arroja el siguiente mensaje de error


I am testing this application I need to know how to activate the WLAN 1 so and throws me the following error message

[rcrsn51]

Click the Help button at the top and read the basic instructions.

Then click the Config button and change INTERFACE=wlan0 to INTERFACE=wlan1

[akuma]

Click the Help button at the top and read the basic instructions.

Then click the Config button and change INTERFACE=wlan0 to INTERFACE=wlan1

thanks for your help I'll be they test

[zygo]

rcrsn51,

Can you tell me what to do so peasywifi recognises a network card which is visible in ROX as the following items

Code: Select all

/proc/sys/net/ipv4/conf/usb0
/proc/sys/net/ipv4/neigh/usb0
/sys/class/net/usb0
/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/net/usb0

which usb-modeswitch creates when I plug in a 3g dongle (with driver cdc_ether).

SNS in Quirky werewoolf has no problem even though ifconfig doesn't list it.

In Fatdog-Arm, peasywifi and Fatdog connect don't see it. How do I add this usb0?

Peasywifi does list the no-existant eth1. I thought I could point this at usb0 but no.

I don't see usb0 in /dev/.

[rcrsn51]

Click the I/F button. Is the usb0 interface listed? If not, PWF is not going to work for you.

[rcrsn51]

@zygo: No reply? Too bad. This could have been useful information for other community members.

I don't know much about 3g dongles, but I thought that they presented themselves as tty devices, so you had to use modem software.

Is this device presenting itself as an ethernet adapter named usb0? Does it show up in "ifconfig -a"? In that case, open the file /etc/pwf/interaces and change "eth0" to "usb0".

Run PWF. Under the Ethernet tab, configure this usb0 interface. Then do a Reconnect. This assumes that you have configured PWF as your primary network manager.

[zygo]

rcrsn51,

Firstly, I read on another post of some years past that one could make the change to /etc/pwf/interaces that you suggest and it would work but it doesn't. Secondly, this was with PeasyWifi either v3.4 or v3.6 whichever I thought was current at the time of the post.

Your first reply was very effective. When the I/F button returned a window with no list it prompted me to copy the newest SNS files I had to hand (from Barry's quiky-xerus-pi) to the Raspbery Pi. That worked but with a few errors on the command line ad GUI.

I've had a few 3g dongles but this latest one (or 2) presents itself as an ethernet adapter named usb0. In FatDogArm it shows up in "ifconfig" but only after I use the "up" option of ifconfig. It is listed as "wired" in SNS even though it's 3g.

I hope to try your latest PeasyWifi in FatDogArm on the RaspPi soon. Just to be clear, where should I enter "usb0" in /etc/pwf/interaces? The line

Code: Select all

ETH1="eth1"

should become what?

Thanks PeasyWifi has saved my bacon, on WiFi, in the past.

[rcrsn51]

In FatDogArm it shows up in "ifconfig" but only after I use the "up" option of ifconfig. It is listed as "wired" in SNS even though it's 3g.

That's why I suggested the command "ifconfig -a". It will show all interfaces, whether they are up or not.

When the I/F button returned a window with no list it prompted me to copy the newest SNS files I had to hand (from Barry's quiky-xerus-pi) to the Raspbery Pi. That worked but with a few errors on the command line ad GUI.

That was bad advice. Your dongle is not a WiFi adapter, so it won't show under the main I/F button.

Instead, open the file /etc/pwf/interfaces and change:

Code: Select all

ETH1="usb0"

There are several more steps.

1. Restart PWF and open the Ethernet section.
2. Select the new usb0 interface for DHCP and click Configure.
3. Select your current eth0 interface and configure it as Disabled.
4. Click Check. You should see a dummy file named "usb0.dhcp".
5. Click Reconnect.

Be aware that if you are already using SNS as the default connection manager, you may have trouble switching to PWF. There are instructions on the main post for doing this.

I have high confidence that this procedure will work in Puppy, but I cannot comment on the non-Puppy platforms you are using.

----------------------

[Pelo]

peasy Wifi 2.8 was my version until now.. I jump to 4.1 . For keeping connected longer.. Good work again rcrsn51
Sommetime i ask myself why to buy a laptop if my Puppy keeps me linked at home. Devs should think about kernels with no drivers available.

[rcrsn51]

Old Puppies like 431 or 528 need an upgrade to udhcpc. Install the attached PET. This needs testing and feedback.