[HOW TO] Installing Wireless Networking


Recommended Posts

Introduction

I would like to thank Bliksem who helped getting me connected to the Internet.

This tutorial was written using Blkisem's help, and the help of google. This works with a variety of wireless cards, but for the sake of things I'm going to explain preciesly how I installed this using a Linksys WMP54G Wireless Network Card (V2). I know this looks like a long tutorial because it's as detailed as I can get it (because it's all extremely fresh in my mind).

My Relevant Specs & Info

- Fedora Core 3 (aka Red Hat 12)

- Kernel 2.6.10-1.760 (works with previous kernels, including *.770 and 2.6.11)

- Linksys WMP54G Wireless Network Card (Version 2)

- Username: djmuk (/home/djmuk/) <-- change this to your own login name where appropriate.

Step 1: Downloading & Saving

1.) Download ndiswrapper and the Linksys WinXP Drivers

2.) Do NOT extract anything at this point unless specified

3.) Save the ndiswrapper-[version_number].tar.gz file onto a Floppy, CD-R/RW or DVD+-R/RW (or other storage mediums)

3.) Open up the WinXP Driver's .zip file and save the 2 files (bcmwl5.sys & bcmwl5.inf) onto a Floppy, CD-R/RW or DVD+-R/RW (or other storage mediums)

4.) You should have 3 files on your Floppy, CD-R/RW or DVD+-R/RW (or other storage mediums) [ndiswrapper-1.0.tar.gz, bcmwl5.sys & bcmwl5.inf]

Step 2: Installation (Part 1/2)

1.) Extract the 3 files (ndiswrapper-[version_number].tar.gz, bcmwl5.sys and bcmwl5.inf) to /home/djmuk/

2.) Open up your terminal (Shortcut: F4 - if you're in the /home/djmuk/ folder)

3.) Type: su (super-user)

4.) Type your 'root account' password

5.) Type: tar -zxvf ndis (hit tab to auto-complete file name, and hit enter)

6.) Type: cd ndis (hit tab to auto-complete folder name, and hit enter)

7.) Type: make (hit enter)

8.) Type: make install

Step 3: Verification & Installation (Part 2/2)

1.) Type: ls -l /lib/modules/`uname -r`/misc/ (hit enter). This verifies the installation of the kernel module

2.) Type: whereis ndiswrapper loadndisdriver wlan_radio_averatec_5110hx (hit enter). This verifies the installation of user space utilities

3.) Type: /usr/sbin/ndiswrapper -i /home/djmuk/BCMWL5.INF (Case sensitive, if file: 'BCMWL5.INF' is in capitals in /home/djmuk/ then use capitals here)

4.) Type: ndiswrapper -l <-- That's the letter 'L' by the way (not the number one). This verifies the installation of the Windows driver

5.) Type: /sbin/modprobe ndiswrapper (hit enter)

6.) Type: ndiswrapper -m (hit enter)

7.) Type: /sbin/dhclient wlan0 (This activates the wireless connection - FINALLY!)

ALL DONE!

* There is no encryption being used at the moment. I haven't ventured that far yet ;) (but I will do when I get some sleep)

You should also note, that if you reboot your machine, you might notice there's no Internet connection.

To fix this, when you log in to the system, immediately open up the terminal and type the last command (Step 3: Part 7): (/sbin/dhclient wlan0). I'm sure there's a way to initiate this upon Start Up - but I'm still a n00b at Linux.

I hope this becomes useful for someone :)

Edited by markjensen

Enabling Encryption

Introduction

Alrighty then, Part 2 of this tutorial. The first part has no encryption (meaning, your Wireless Access Point has all security features disabled. Now it's time to enable them (after a few hours of research on google).

I'm going to write this tutorial based upon my own settings (feel free to change them).

My Relevant Specs & Info

- Fedora Core 3 (aka Red Hat 12)

- Kernel 2.6.10-1.760 (works with previous kernels, including *.770 and 2.6.11)

- Linksys WMP54G Wireless Network Card (Version 2)

- Linksys WAP54G Wireless-G Access Point (IP Address example used in browser: 192.168.2.2)

Step 1: Setup and Auto-Start on Reboot

1.) Copy & Paste the text below into a text editor (eg, "gedit"):

# NDIS Wrapper Configuration: Linksys WMP54G
 DEVICE=wlan0
 ONBOOT=yes
 BOOTPROTO=dhcp
 TYPE=Wireless
 MODE=Managed
 SSID="DjmUK_54G"
 CHANNEL=11
 USERCTL=yes
 PEERDNS=no
 KEY=xxxxxxxxx
 RATE=Auto
 NICK=wlan0

2.) Save the file to: /etc/sysconfig/network-scripts/ with the filename: ifcfg-wlan0.

Step 2: Editing File: ifcfg-wlan0

1.) Editing the file. Firstly open up your Access Point into a browser http://192.168.2.2 (I used my WinXP box to do this). The important settings to change (just copy the settings you see in your browser):

- SSID="DjmUK_54G"

This is the name of your wireless network which MUST match your Access Points SSID

- CHANNEL=11

Depends on your location, I use 11 because I'm in Europe

- KEY=XXXXXXXXXX

Take a look at your 'Security Settings', I'm using a 'Security Mode of WEP @ 64-bits / 10 hex digits' (because 128-bit slows down the network). Type in your key here, NOT the passphrase! the generated key. I had four to choose from, so I made sure I was broadcasting the chosen key

- RATE=Auto

You can change this to your actual bandwidth (eg, 54G), but auto is the easiest method that works just fine with me

Step 3: Network Settings and Network Restart

1.) In Fedora, go to "Start > System Settings > Network", and in the DNS Tab:

- Hostname: localhost Unless you're a web server

- Primary DNS: 192.168.1.1 Your Gateway address (your Access Point via a browser will tell you this)

- Secondary DNS:

- Tertiary DNS:

- DNS Search Path:

* I left some fields blank above because I'm not running a web server so I don't need to worry about those.

2.) Restart your network, and you have two options to do this.

-- In 'Terminal' you can type: service network restart

-- Network Configuration (Decativate device, Activate device).

3.) Now test it all. Load up any web page ;)

ALL DONE!

The above works for me, so hopefully it will work for someone else out there and hopefully with little to no modifications.

Kernel Updates Broke My Network Connections

Introduction

Okay, this is my last article on this subject (all this Linux is a nice learning curve, and I'm still learning).

Basically, I just upgraded my kernel (via yums rpm):

From: 2.6.10-1.760

To: 2.6.10-1.770

However, on reboot the Internet was broken. But don't worry, you don't need to go through all these steps again because the hardware is installed and configured correctly.

My Relevant Specs & Info

- Fedora Core 3 (aka Red Hat 12)

- Kernel 2.6.10-1.770 <-- NEW VERSION BABY!

- Linksys WMP54G Wireless Network Card (Version 2)

- Linksys WAP54G Wireless-G Access Point

Step 1: Why Is It Broken?

1.) Because that ndiswrapper module you compiled and installed was for the previous kernel, so you're gonna' have to recompile a new one - and that's all there is to it.

2.) "Step 2: Installation (Part 1/2)" needs to be followed - but not in so much detail, so here goes.

Step 2: Recompiling

Let's say you've kept the ndiswrapper folder in your user space /home/djmuk/ (if not, then go sort it out by un-tar'ing it etc.)

01.) Load up the terminal

02.) Type: su

03.) Type: cd /home/djmuk/ndiswrapper-1.0/ Or wherever you've un-tar'ed the ndiswraper module

04.) Type: make

05.) Type: make install

06.) Type: ndiswrapper -l Note the name of the driver (in my case 'bcmwl5')

07.) Type: ndiswrapper -e bcmwl5 This removes that driver (so watch your spelling)

08.) Type: /usr/sbin/ndiswrapper -i /home/djmuk/BCMWL5.INF reinstalls the driver

09.) Type: ndiswrapper -l Verification

10.) Type: /sbin/modprobe ndiswrapper

11.) Type: ndiswrapper -m

12.) Type: /sbin/dhclient wlan0

13.) Type: service network restart

ALL DONE!

There we go, just a simple case of recompiling the ndiswrapper module for your new kernel, and reinstalling the module. All your previous settings and configurations (including encryption) are still intact.

Edited by markjensen
  • 2 weeks later...

I would like to offer another alternative to using ndiswrapper, called madwifi. I find it is much faster and more convenient especially when theres security keys involved.

It *should* work on any card that uses an atheros chipset.

This worked for me on fedora core 3 770 with a WPC55AG card:

1. get the madwifi drivers and libradies:

http://dl.atrpms.net/production/packages/f...fc3.at.i686.rpm

http://download.atrpms.net/production/pack...fc3.at.i386.rpm

2. install the rpms:

at terminal:

cd /download_location/

su

rpm -i madwifi-kmdl-2.6.10-1.770_FC3-0.9.4.12-15.rhfc3.at.i686.rpm

rpm -i madwifi-0.9.4.12-15.rhfc3.at.i386.rpm

cd /sbin

./modprobe ath_pci

3. configure your card the way you want it:

most configurations can use the built-in network config utility:

-open it up, and click to create a new device config.

-select you options for ip, dhcp, etc

-select "managed" mode

-select any othe config you need, like WEP key, if you use one.

-save

-restart "network" from applications>system settings>server settings>services

if you use a WEP key in an open system, i have found that the built in configurator has problems since it specifies "restricted" as the authentication mode, so you can do this:

-go to a terminal:

su

cd /sbin

./ifconfig ath0 up

./iwconfig ath0 key open [1] 7E0355BA7E

./dhclient ath0

you can stick all this stuff in a script or something if you want.

This config gives me fast authentication and good speed (it correctly uses 54Mb/s when available)

Here is a nice guide on how to get ndiswrapper working with *all* linux distros \

You must have the wireless tools installed

1: extract tar (kernel 2.4.* or lower needs ndiswrapper .12)

2: cd /path/to/ndiswrapper/source

3: make

4: su

5. make install

6. modprobe nidwrapper

7. ndiswrapper -i /path/to/win/driver

8. ndiswrapper -l [check that hardware is present]

9. iwconfig (make sure you see the card)

10. ndiswrapper -m

11. iwlist wlan0 scan (shows wireless networks (essid))

12. iwconfig wlan0 mode [network mode usually] managed

13. Then run dhcpcd wlan0

key [encription key] 48143525698

essid [network name] DLink

so you might have

iwconfig wlan0 mode managed

iwconfig wlan0 key 4812534656

iwconfig wlan0 essid DLink

How to get ndiswrapper working on startup:

There are many ways but theres nothing that exact. Different Distros have their way, but you can make a script in /etc/rc.d/rc.wlan0 and then have a some file call it

My /etc/rc.d/wlan0 looks like

#!/bin/sh
#/etc/rc.d/wlan0
echo "Starting Wireless Networking....."
modprobe ndiswrapper
sleep 1
iwconfig wlan0 mode Managed
iwconfig wlan0 essid DLink
sleep 1
dhcpcd wlan0
echo "Wireless Networking Started!"

At this time I'm working on remaking my script work better like to search for a network before it sets the essid etc...

Hope you found this useful

Didn't I already do this :huh:

Slightly more detailed and specifically for FC3, but reports show that it works on a lot of distros out there:

[HOW TO] Fedora 3: Installing Wireless Networking

Well, we now have two tutorials - if one doesn't work then the other's bound to :rolleyes:

  DjmUK said:
Didn't I already do this :huh:

Slightly more detailed and specifically for FC3, but reports show that it works on a lot of distros out there:

[HOW TO] Fedora 3: Installing Wireless Networking

Well, we now have two tutorials - if one doesn't work then the other's bound to  :rolleyes:

585656664[/snapback]

Well kinda mine short a sweet

and it tells how to load the connection at startup using a script important to gentoo, slack, arch, maybe debian

Both of those procedures could be useful, and since they augment and compliment each other, let me merge them into one larger thread for people to go to when they are looking for a guide. (Y)

  wicker_man said:
Nice guide, thanks a lot. Shame though we have to go through all this - a regular user won't be able to handle that  :no:

585689939[/snapback]

Well it's all about the 1st, 5th & 6th posts. The 2nd & 3rd are optional extras. Just follow either #1, #5 or #6 and that's all you'll need to get online (as long as basic security isn't an issue).

  Jayzee said:
What about WPA encryption settings!? This guide bases on WEP encryption, which anybody can crack within 5 hours..  :pinch:

585690394[/snapback]

Some drivers are supported by wpa-supplicant, which is configured through a separate config file.

  Jayzee said:
What about WPA encryption settings!? This guide bases on WEP encryption, which anybody can crack within 5 hours..  :pinch:

585690394[/snapback]

WPA - hmm, never looked into that. I've always gone with WEP (because I know how to), but I'll have to look into WPA encryption sometime, once I've researched into 'which is more secure'.

  tsukikage said:
I would like to offer another alternative to using ndiswrapper, called madwifi.  I find it is much faster and more convenient especially when theres security keys involved.

It *should* work on any card that uses an atheros chipset.

This worked for me on fedora core 3 770 with a WPC55AG card:

1. get the madwifi drivers and libradies:

http://dl.atrpms.net/production/packages/f...fc3.at.i686.rpm

http://download.atrpms.net/production/pack...fc3.at.i386.rpm

2. install the rpms:

at terminal:

cd /download_location/

su

rpm -i madwifi-kmdl-2.6.10-1.770_FC3-0.9.4.12-15.rhfc3.at.i686.rpm

rpm -i madwifi-0.9.4.12-15.rhfc3.at.i386.rpm

cd /sbin

./modprobe ath_pci

3. configure your card the way you want it:

most configurations can use the built-in network config utility:

-open it up, and click to create a new device config.

-select you options for ip, dhcp, etc

-select "managed" mode

-select any othe config you need, like WEP key, if you use one.

-save

-restart "network" from applications>system settings>server settings>services

if you use a WEP key in an open system, i have found that the built in configurator has problems since it specifies "restricted" as the authentication mode, so you can do this:

-go to a terminal:

su

cd /sbin

./ifconfig ath0 up

./iwconfig ath0 key open [1] 7E0355BA7E

./dhclient ath0

you can stick all this stuff in a script or something if you want.

This config gives me fast authentication and good speed (it correctly uses 54Mb/s when available)

585637315[/snapback]

Thank you so much for this. This made my wireless work flawlessly on my Toshiba laptop! GREAT JOB!

  • 4 weeks later...
  • 4 weeks later...

One thing that ive never figured out ( until recently )how to get working was WPA Supplicant with NDIS Wrapper to load automatically on boot.

Open up the interfaces file in

/etc/network/interfaces

Make sure you have these lines in there

auto wlan0
iface wlan0 inet dhcp
pre-up /usr/sbin/wpa_supplicant -Bw -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant.conf
post-down killall -q wpa_supplicant

Just thought I'd add that, would have made my life soo much freaking easier if I knew how to set that up from the start.

  • 1 month later...

I think I figured out how to get my WLAN working, but not set for automatic startup and was setup with the native drivers instead of ndiswrapper. I noted that quite a few WLAN cards include the Linux drivers, but arc4 and/or crc32 are required. Those crypto modules can be found in /lib/modules/(your kernel version)/kernel/crypto. But if only I could find out how to get it to work for automatic startup and find a GUI WLAN monitor, I'd be all set and then, I'd be able to post a HOWTO on that.

DjmUK:

I'm having a problem with Part 7 on Step 2 of the first post of this topic. I'm extremely new to Linux and have Fedora Core 4. I'm trying to get my Linux card to work on this thing. I do an lspci and come up with the following (just for the sake of having posted as much info as possible)

  Quote
00:0a.0 Network controller: Broadcom Corporation BCM4306 802.11 b/g Wireless LAN Controller (rev03)

So I go to do this install on my nix box and get to this part

  Quote
[root@localhost ndiswrapper-1.2]#

and type in the word 'make' to get something along the following output (I had to write it down seeing as how I have no net connection).

  Quote
make -C driver

make [1]: Entering directory /root/Desktop/ndiswrapper-1.2/driver'

Can't find kernel sources in /lib/modules/2.6.11-1.1369_FC4/build;

give the path to kernel sources with KSRC=<path> argument to make

make[1]: *** [prereq_check] Error 1

make[1]: Leaving directory '/root/Desktop/ndiswrapper-1.2/driver'

make: ***[all]Error 2

[root@localhost ndiswrapper-1.2]#

Someone please tell me what this means? Why am I getting an error?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Showing people how to self host their own media is harmful, according to YouTube by David Uzondu YouTube has taken down a video from tech creator Jeff Geerling that demonstrated how to use LibreELEC, a lightweight operating system for turning devices into media centers, on a Raspberry Pi 5 for 4K video playback. The video, titled "I replaced my Apple TV—with a Raspberry Pi", originally published in May 2024, was removed in June 2025 under YouTube's "Harmful or dangerous content" policy. According to the violation notice, YouTube claimed the video showed "how to get unauthorized or free access to audio or audiovisual content, software, subscription services, or games that usually require payment." Image via Jeff Geerling Geerling strongly refuted YouTube's claims. He stated clearly, "I purposefully avoid demonstrating any of the tools that are popularly used to circumvent purchasing movie, TV, and other media content." He also emphasized that his own Network Attached Storage, or NAS, contains only legally acquired content. This isn't Geerling's first run-in with YouTube over self-hosted media tools. Last October, his tutorial titled "Better than Disney+: Jellyfin on my NAS" was hit with a similar strike for showing how to set up Jellyfin, an open source media server for organizing and streaming personal media. That strike was quickly overturned after an appeal. But this time, YouTube rejected his appeal, even though the LibreELEC video had been live for over a year, had racked up over half a million views, and contained no promotion of anything illegal. This whole thing feels a lot like what happened with youtube-dl. It's a simple command-line tool for downloading videos, used by tons of people for perfectly legal reasons like saving public domain content or backing up their own uploads. But that didn't stop the RIAA from hitting it with a DMCA takedown on GitHub, calling it a piracy tool. The community pushed back hard, and eventually it was brought back, thanks in part to support from groups like the Electronic Frontier Foundation who pointed out that not everything that can be misused is automatically bad. Side note, the youtube-dl project appears to be unmaintained (the last release was in 2021), if you're looking for an alternative, consider its very popular fork, yt-dlp. After the appeal was rejected, YouTube required Geerling to complete "policy training" to avoid a more serious, permanent strike on his channel. He eventually gave in and took the training. Anyways, if you're interested, he has uploaded the removed LibreELEC video to Internet Archive for anyone to watch.
    • Thanks to Herr Musk being a total poison pill, they can't even give those pieces of scrap away.  They can't even ship them to the UK/EU because they're completely illegal over here.  
    • Intel vs AMD? Microsoft seemingly has a clear recommendation for Windows 11 Pro PC upgrade by Sayan Sen Microsoft and its partners are now quite actively and regularly promoting the upgrade to Windows 11. Asus, for example, recently published blog posts about the "mandatory Windows 11 upgrade" that is coming as the Windows 11 end of support date nears. Microsoft itself, from time to time, urges users to upgrade to its newest OS. Back in February 2024, Microsoft released an advert highlighting the best things about Windows 11 over Windows 10. Later, in June in the same year, the tech giant busted "myths and misconceptions" surrounding a Windows 11 upgrade. And towards the end of 2024, in December, Microsoft put up a blog post outlining the gaming features a user enjoys on 11 if they were to upgrade from Windows 10. While technically there is nothing wrong with a company promoting its own product, sometimes these campaigns make little sense and they fall flat. For example, in January earlier this year, Microsoft shared a blog post headlined "Free Upgrade to Windows 11 (For a Limited Time Only)" which did not make sense as it offered little information about it being a "free upgrade," and it was rightfully, later taken down. The company is back again with a new commercial about Windows 11. This time it is aimed mainly at IT professionals and enterprises as the advert talks about upgrading to Windows 11 Pro from Windows 10. This landed a few days after Microsoft released a new backup tool for organizations for such a purpose. What is interesting is that the company is promoting Intel's vPro processors and there is no mention of AMD's Ryzen PRO parts. The commercial is posted on the Windows official YouTube channel and has been titled "Right side of risk | Windows 11 Pro and Intel". The video description says, "Windows 10 support ends October 14. Stay on the right side of risk—upgrade now to the power of Windows 11 Pro PCs with Intel vPro®." AMD does have a support article about the subject headlined "Support Your Customers’ Move to Windows 11, With AMD Ryzen™ PRO Processors" and you can find it here. This is not the first time Microsoft has promoted Intel CPUs over AMD ones. Back in 2021, the company also put up a full page explaining how users should "look for the Intel EVO badge" on a new device before making a purchase decision because such PCs are "verified wonderful" which was a bit of an odd language. Like the limited upgrade time article, the page above was taken down after we reported on it (can be viewed via the archive) and replaced with something else. The new commercial was published about a couple of days ago, and it is possible that Microsoft may have a dedicated AMD advert too in the pipeline scheduled for a later release, and that would only be fair if both companies get a similar treatment.
    • Don’t blame web developers for the downfall of Firefox. 😂
  • Recent Achievements

    • Week One Done
      luxoxfurniture earned a badge
      Week One Done
    • First Post
      Uranus_enjoyer earned a badge
      First Post
    • Week One Done
      Uranus_enjoyer earned a badge
      Week One Done
    • Week One Done
      jfam earned a badge
      Week One Done
    • First Post
      survivor303 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      435
    2. 2
      +FloatingFatMan
      238
    3. 3
      snowy owl
      213
    4. 4
      ATLien_0
      211
    5. 5
      Xenon
      155
  • Tell a friend

    Love Neowin? Tell a friend!