I want to automate my wlan0 internet connection, the connection
works just fine when I load them from the keyboard.

This is what the wiki said to do, but....

Next, you want to auto load the settings on boot.
Puppy has a file /etc/rc.d/rc.local that can be used to automate
the process. Just add the following values, corresponding to
your system. Using Rox, I added the following to rc.local;

The device (eth1) may be different depending on your card, for some it is ath0 for some wlan0 for some ra0 etc.

You need to know the parameters of your network.
You need to know for example:
- The mode. Mine is 'Managed'
- If the network has security enabled
- You need to know if the WEP key is 'restricted' or 'open'
- You need to know the actual WEP key
- If the access point broadcasts the essid, you need to know the essid of the network.

I prefer to start disabling security and making sure that I can connect, after that I enable security.

Also, something that may seem obvious but we never know: Don't type the comments included in the instructions.

It looks like perhaps you did take the article too literally. I think that you used my article on wiki, which was written for Puppy 1.0.2. It may need to be updated.

The hang on boot is a syntax error somewhere in the command lines that you put in rc.local.

If you look at the article again, I gave a step by step explanation of each command and when each should be used.

You do not need ifconfig wlan0 up in the command sequence, just dhcpcd wlan0.

...and yes, you need to make sure that it works at the command line first, as the article explains.

The most important point is that you need to maker sure that you have an access point. This is where folks are speaking of the card needing open vs. restricted access, as well as if a wep key is needed.

Guys and gals, let me know if I need to change the article for Puppy 1.0.3 and I will do it promptly. I have not tried it totally with the new version of Puppy 1.0.3._________________I love it when a plan comes together

I know it's not encrypted but I live so far out in the sticks I'm not worried.
I'll fix the encription problem later.
I just want to fix the automation problem first.
Loading the driver and connecting to my router.
Also I exed out some of the numbers on the device ID.
I made copies of the module net8180 and put it in different locations hoping it could be found....but no go.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum