PeasyWiFi - a reliable WiFi connection manager

[James186282]

This is a more general question but I think you will probably have the answer. Why are most ips gotten from dhcp servers? What I mean is what is wrong with using static ip addresses? I think its logical for some WiFi hotspot but if your using a small network? Wouldn't it be a little but faster that way? Just an update if I didn't say it. My Mother in law and my wife are set up on peasyWiFi. My mother in law is very pleased. Her son is also pleased. He tried to fix things and was getting frustrated. My wife tried it but something wasn't right. I got it to work by digging up all the wpa_supplicant .conf files I could find and deleting them. One thing I wish is that people use the same directories. I'm wearing out pfind. Anyway. I suspect one of the other WiFi managers was still starting up. I didn't have time to look more into it but thats what I saw.

[rcrsn51]

what is wrong with using static ip addresses?

Nothing. If you have a small network and can keep track of who has what IP address, it is a LOT faster to connect. But as soon as you hook up a different computer or install a different Puppy or run Windows, you have to set up another static configuration. DHCP does all of this automatically for you.

I got it to work by digging up all the wpa_supplicant .conf files I could find and deleting them.

In PWF, click Profile > Check. This opens the folder /etc/pwf/wifi where PWF keeps its .conf files.

I suspect one of the other WiFi managers was still starting up.

If you see a bunch of popup messages like "wlan0 down", this is another network manager stomping on your PWF connection. This is why I prefer a clean Puppy install before starting to use PWF. See the last paragraph of my previous post regarding dhcpcd.

[rcrsn51]

The version number is still 3.1, but there are some improvements to the code behind the Details and Duplicates buttons.

[rcrsn51]

PWF v3.2 changes the way that multiple SSIDs are handled. Read here.

[rcrsn51]

This is still v3.2, but with a few minor changes.

1. The Abort button works better. It should now kill a slow/stalled connection in one or two clicks. Previously, it took several clicks.

2. The Show All Cells list is now sorted by signal quality.

[Pelo]

I believe we can now trash Pwireless. Peasywifi does it everywhere, even where wireless connexion was not so easy. (free Wifi from the city)
My computer can go with me outside, when it's a sunny afternoon.
And inside too, because i lost my phone plug
v 3.2 ????? ! i shall see that later.
Info sent to France here. well arrived They are sleepy...

[rcrsn51]

PWF v3.3 has several improvements. See the update note on the main page, especially concerning the use of TIMEOUT=0.

[Scooby]

PWF v3.3 has several updates.

2. The Ethernet section has a new Reconnect button.

I'm happy for the return of this feature

In version 3.3 does

Code: Select all

peasywifi eth0 &

in a startup script work at boot?

[rcrsn51]

I'm happy for the return of this feature

Yes, I should have done that long ago.

In version 3.3 does

Code: Select all

peasywifi eth0 &

in a startup script work at boot?

No. the only legal command line argument is a profile name. How do you want to use it? At bootup, your Ethernet ports should be enabled by default.

[Scooby]

No. the only legal command line argument is a profile name. How do you want to use it? At bootup, your Ethernet ports should be enabled by default.

Yep at boot up
I aint running a regular puppy but the puppy cuz alphaos
so using a modded peasywifi(version 2.7) with the aforementioned feature

My ethernet is not enabled by default

Bought a router anyway so now I use wifi

[rcrsn51]

My ethernet is not enabled by default

In a standard Puppy setup, this happens through /etc/rc.d/rc.network. The PWF instructions explain how to change it so PWF manages the Ethernet ports at bootup. You would need to find the equivalent procedure in alphaOS.

[rcrsn51]

Some notes about WiFi drivers:

Puppy has always been good at supplying drivers for WiFi adapters. Look here at all the work by tempestuous to support WiFi in Lucid.

Since around k3.4 (Slacko56-4G), most WiFi drivers have been part of the mainstream kernel and work OOTB in Puppy. One exception is the 8188eu, which is now in Tahrpup k3.14.

Some new chipsets made by MediaTek are appearing on the market in devices like the TP-LINK TL-WN727N-v4. Mediatek is the parent company of Ralink, so they are using Ralink Linux drivers, but with names like mt7601Usta.ko. These can be compiled in Puppy.

Although we would all prefer to use open-source drivers, there may be situations where the Windows WiFi driver is more powerful or stable. It is a simple procedure in PWF to set up ndiswrapper and test your adapter both ways.

[Pelo]

i) temporarily disable all encryption at your wifi router, and see if your wifi device will connect in this unencrypted state.
users don't forget that !
Peasy wifi installed to-day on upup raring. Nothing to say, perfect !
Rcrsn, I appreciate a lot having your help about wireless. some forums are not very enthousiates about wireless. Heureusement i manage not so bad with english. Merci pour ton travail.
Français, go and see there translation about PeasyWifi francophonie forum

[step]

...
Since around k3.4 (Slacko56-4G), most WiFi drivers have been part of the mainstream kernel and work OOTB in Puppy. One exception is the 8188eu, which is now in Tahrpup k3.14.
...
Although we would all prefer to use open-source drivers, there may be situations where the Windows WiFi driver is more powerful or stable. It is a simple procedure in PWF to set up ndiswrapper and test your adapter both ways.

I'm still testing my TP-LINK 725N adapter. Now I want to test it with its Windows driver using PWF. Do I need to blacklist the 8188e module in Tahrpup before I can configure the Windows driver with PWF?

[rcrsn51]

Now I want to test it with its Windows driver using PWF. Do I need to blacklist the 8188e module in Tahrpup

Probably. Follow the instructions for setting up ndiswrapper and reboot.

Check Status. If your 8188eu still appears as the kernel module, blacklist it and reboot.

[step]

Now I want to test it with its Windows driver using PWF. Do I need to blacklist the 8188e module in Tahrpup

Probably. Follow the instructions for setting up ndiswrapper and reboot.

Check Status. If your 8188eu still appears as the kernel module, blacklist it and reboot.

Not working here. I downloaded the windows driver, installed it with SWF, rebooted and blacklisted 8188eu, rebooted again. No connection. peasywifi_auto is now two lines:

modproble ndiswrapper
peasywifi SSID

when I run modprobe ndiswrapper from a terminal I get:

modprobe: ERROR: could not insert 'ndiswrapper': Exec format error

I'm running a frugal no-PAE Tahrpup 6.0 with service pack 1.

[rcrsn51]

Ndiswrapper in Tahrpup needs some patches. Read here, especially for the non-PAE version.

I have tested an 8188eu adapter with ndiswrapper in Tahrpup and it works fine.

[step]

Ndiswrapper in Tahrpup needs some patches...

Thanks for the pointer. I patched ndiswrapper and was able to make the Windows driver work with PWF. However, connection quality remains marginal with this adapter, so I'll trash it.
I really like PWF, it works very well, has many features - password encryption, yes! - and it's simple to use for the technically inclined. Thank you for PWF. Happy new year!

[rcrsn51]

However, connection quality remains marginal with this adapter, so I'll trash it.

Agreed. These little micro adapters are cute but they're not really practical.

However, I also own a TP-LINK TL-WN822N with external antennae and it's not that great in Linux either.

[Scooby]

I like peasywifi

I ported version 2.7 to alphaos and wanted to do the same for 3.3

I have a question/feature request and I am not sure this is a
issue in puppy linux, If it is not I can hack around it myself

My 3.3 version is still not working properly but when reviewing code
of "new" notebook with label "Ethernet" I see you are hardcoding
eth0. On my system it is called enp4s0

Any chance you can put that as a variable in config file?

something like

Code: Select all

...
export OPTION=""
export STATIC=""
export GATEWAY=""
export ETH_INTERFACE0=eth0
export ETH_INTERFACE1=eth1