Puppy Linux Discussion Forum

himajin · Joined: 08 Jul 2008 Posts: 54 Location: JAPAN

For ja_JP.UTF-8
http://qyg01263.googlepages.com/net-setup.mo.ja

Put it /usr/share/locale/ja/LC_MESSAGES/ and rename net-setup. .

11/21 fix buildScanWindow section

PaulBx1 · Joined: 16 Jun 2006 Posts: 2308 Location: Wyoming, USA

Dougal · Posted: Mon 10 Nov 2008, 06:07 Post subject:

NicolasHoTaylor · Posted: Mon 10 Nov 2008, 12:54 Post subject: Old Ralink driver

Puppy 4.11 seems to have the old rt61 driver, not the newer rt61pci. I understand there are some issues with rt61pci, but there's a worse problem with rt61: it doesn't support PCMCIA cards.

Not mine, at least (D-Link DWA-610).

I have to stick to Puppy 4.1, as a result (it has rt61pci). If anyone knows how I could copy the driver from one version to another that might help...

valpy

Information about improving stability of connections with rtl8187 driver for those who still have issues with rtl8187

http://www.murga-linux.com/puppy/viewtopic.php?t=35586

@tempestuous

gyro

Apologies if I've posted this in an inappropriate place.

I've installed Puppy 4.1.1 and sucessfully configured wifi on an EeePC 701 and a Lenovo ThinkPad R61e, no problem.
Click on "Scan", choose my SSID from the list, click on "WPA2", paste my key into "Key" field, click on "Save", click on "Use this profile", then "Auto-dhcp", etc... Everything works. Even after a reboot I am automatically re-connected to my wifi network.

Thanks Dougal.

But may be there are some things that helped my configuration to work so easily:

1) I am lucky enough to have hardware that is supported by working drivers.

2) I do my testing in the same room, and less than 2 metres from the wireless Access Point. This simply means that signal strength is eliminated as a problem.

3) On my wireless Access Point device, I disable "UPnP". I'm not sure why, but I just think Windows and Linux more happily co-network if I do. I know that IP needs only dhcp to configure itself seamlessly. Also gives me confidence that the device is working exactly how I configured it via it's WWW interface.

4) On my wireless Access Point device, I configure it to broadcast my ESSID/SSID. (It's the strong encryption that provides the security.)

5) I know that my key is identical on all devices because I store it in a text file on a USB stick, so I can cut and paste it into all devices, including the "Key" field in the puppy wizard. This provides confidence, even on devices that only display dots or "*" in the key field.

6) On WPA2 I don't use the "s:key" construct, that is supposed to work in WEP. I paste just the plain ASCII string. As long as it's less than 64 characters WPA assumes it's an ASCII key.

7) I don't use a key string that will cause problems on any device. I use a key of 30 random alpha-numeric characters, with no spaces, with a few special characters thrown in. I avoid special characters that can cause problems, e.g. "$" character could be a problem in scripts like the puppy wizard. (Though I think Dougal might have fixed that one now.) For your first key, use just alpha-numeric characters and no spaces, just to be sure that the key can not be a problem. You can change it to a more complex key after it is working.

Hopefully, something in all this will help someone else have a successful experience with wifi and the puppy network wizard.

Alan

Dougal

h4yn0nnym0u5e · Joined: 01 Nov 2008 Posts: 4

imnotrich · Joined: 02 Jun 2006 Posts: 44 Location: Northern California

I'm using a Gateway ML-3109 laptop and Realtek 8185 with Puppy 4.1.1 but am still unable to connect to my home wlan.
Footnote: My son's Kanotix/XP desktop using NDISWRAPPER (also a Realtek 8185) could not see the home network unless I broadcast my SSID. But it's working great for him now.
I was very happy that Puppy 4.1.1 finally detects the Realtek 8185 in my laptop, and it can see my home network! But I am using WPA2 TKIP+AES with a 64 bit hex key and for some reason Puppy will not connect to the router and pull an ip address from the router's dhcp server.
I haven't tried static ip yet but does it really matter? The issue would seem to be that Puppy out of the box does not support this level of encryption.
Is there a patch available, or am I doomed to tinker from the command line?
Heeeeeeeeeeeelp!
I don't get why the 8185 works on one machine, and not the other and I'm afraid to try NDISWRAPPER with puppy because last time it so corrupted my pup save file I had to delete and start from scratch.
Of course, I am a total noob and I am sure it's something really simple that I've overlooked but if anyone has ideas I'm eager to hear from you.
Thanks!
Rich

Dougal

cthisbear · Joined: 29 Jan 2006 Posts: 2943 Location: Sydney Australia

Dougal:

I wish to thank you and tempestuous for all the great work you are
doing. There are others helping out too...Just Greg? etc.
If I have missed anyone....my apologies.
Anyway... thanks to all in the puppy genius factory
for your efforts.

""""""""""

This is one problem I couldn't solve.
I don't have access to this laptop any more though.
Works OK until you allow Vista to stitch it up.
And of course wonder of wonders.....
Network Magic came to the rescue to connect the
encrypted wireless in Windows. A brilliant program.
I hope that Cisco don't stuff it up now that they have
bought it.

http://www.murga-linux.com/puppy/viewtopic.php?t=35962

::::::::::::
In puppy 4.1.1 I have found that the wireless
networking menu works for me most times.
Faster than Windows.

If I can't get things going I try this:

Connect a network cable, setup the network ethernet 0,
test ethernet 0, then click auto dhcp, test for available connections,
type in password... and try to connect.

If I'm successful...I pull out the cable...
redo the setup for wireless.....wlan0 ?
and go through all the steps again. "

Regards...................Chris.