Unable to connect to WEP wireless network (Puppy 1.07)

[Finbar]

Hi,

Total newbie to Linux, but have managed to get Puppy Linux Version 1.0.7 up and running as a 'dual boot' on my Compaq Armada 3500 (W98SE, 128 MB RAM).

My first attempt has resulted in a great system that boots quickly and thoroughly enjoyable to use!

Installed my Belkin F5D7010 wireless card using ndiswrapper, but, whilst I know that intenet access is ok (hopped on an unsecured wireless network in error using the 'autoconnect' option - sorry! )

However, my BT Broadband is WEP enabled, and despite putting all the relevant details in the WAG profile options - nothing doing - no connection

I have put in the wireless card & access point MAC addresses, input WEP password, gateway, frequency and channel - even tried specifying an IP address - but no joy

I have two other PC's linked up and do not like the thought of an unsecured network (for reason outlined above!)

Looking at the forum I notice that wireless networks do seem to cause a few issues. This forum is great with a depth of information that is a godsend to newbies like me. I am hoping to learn more about Puppy Linux and contribute back to this forum as I go!

If anyone can assist it will be appreciated

Many thanks

Kevin

[HairyWill]

There's been a lot of work done on wireless. Try using the latest version of puppy 2.14 and see how that works.

[mwestlund]

I'm making a WEP connection to my Wifi router just fine with Puppy 2.13 and 2.14 with my Netgear 511 PCI card. I'd suggest using the profiles in RutilT on the Network menu to make it easier on yourself. best wishes. -Mark

[Finbar]

Thank you for the replies to date - appreciated

Upgraded to Puppy Linux 2.14, but ndiswrapper doesn't like the bcmwl5.inf file anymore!

Have seen many comments on the Broadcom chipset that they can cause some issues, so if anyone has any further suggestions they will be appreciated!

Thanks

[rarsa]

Upgraded to Puppy Linux 2.14, but ndiswrapper doesn't like the bcmwl5.inf file anymore!

That's odd, there was a related bug before 2.14 but it was fixed for 2.14. I have two computers with that chipset and use ndiswrapper.

Even more. You (and me) should be using the native driver for that chipset. It is included in 2.14 but the firmware is missing. Tempestuous created a service pack to add some missing firmware, search for it.

[Finbar]

OK - one very happy Puppy Linux user here!

Big thank you to rarsa, mwestlund & HairyWill for their help.

In short - upgraded Puppy 1.017 to 2.14

Obtained Tempestuous' service pack with the bc43xx firmware by searching this forum.

Installed the .pet file and used the RutilT utility to get connected.

Am typing this response with a big smile on my face

Now on to learn some more about Puppy Linux!

Thanks again for your help

[rarsa]

Installed the .pet file and used the RutilT utility to get connected.

I will preemtivelly answer your next question:

If you want the network to automatically connect after booting, use the network wizard to configure the interface and then select to save for next boot.