Puppy Linux Discussion Forum

[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]

Ok, thank you!

[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.)

[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

[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.

[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

[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.

[01micko]

[jemimah]

Yup looks good.

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

[01micko]

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

[gerry]

@Jemima- I'm using the beta version, how do I upgrade to 1.0? Just install the new one and overwrite the beta, or uninstall/reinstall, or....

thanks- gerry

[jemimah]

Uninstall the old version, then install the new version.

[gerry]

Been using PWireless2 for a few days on my Acer Aspire One, first on Puppy 431, then Fluppy 003. Works beautifully- until today. Neither Puppy would detect any networks. I tried reconfiguring again and again, deleting old profiles here and there, tried live usb without a save file- nada.

So I woke Windows XP from it's hibernation, to check that the computer itself was ok, and that worked. Gave Puppy 431 a last chance before I wiped it and re-re-re-re-installed Ubuntu NBR, and it made it's wireless connection on boot-up with no intervention. Haven't tried Fluppy yet, but I expect it to work. EDIT: yes, it does.

So....if your Puppy won't see any wireless networks, just run Windows XP to straighten things out.

gerry

[gyro]

Just downloaded Pwireless2, and tried to use it, to configure a second ethernet interface.
Situation:
eth0, auto dhcp, UP, connected to Internet.
eth1, not configured.

Trying to achieve, eth1 configured as 192.168.3.1/24, nothing more.
Gateway for machine is already defined, so should not be specified again.
DNS servers are already defined.

Run Pwireless2, select "DHCP" tab. Three interfaces are listed, lo, eth0, and eth1.
I click on eth1, then unset the "auto" box so static boxes become available.
Enter 192.168.3.1 and 255.255.255.0, leave rest blank.
Pwireless2 complains with "invalid gateway" error message, does nothing.

Run network wizard, specify only IP address and network mask, no problem, done and dusted.

gyro

[jemimah]