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

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)

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

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

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)

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

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

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

    • Studio MDHR reveals Cuphead sequel and an 8-bit platformer spin-off by Pulasthi Ariyasinghe Studio MDHR has been rather silent about its next major gaming project since the release of Cuphead back in 2017. However, that ended today during the Summer Game Fest presentation, with the studio revealing not one but two project announcements. First, the studio confirmed that it is currently in the middle of developing a brand-new Cuphead game, bringing back the iconic characters for another adventure. Just like the last game, this is slated to be a fully hand-animated endeavor. This also means there isn't a release date attached to it yet. “Craftsmanship is at the heart of everything we do here at Studio MDHR,” says co-founder Chad Moldenhauer. “When it came time to peel back the curtain and share a little bit about what we’ve been up to, we couldn’t imagine a more fun way to do so than with today’s Special Bulletin. The studio is working on this new Cuphead with help from Toronto’s Stop Motion Department and Continue Agency. At the same time, Studio MDHR also revealed that another part of the team has been working on a different Cuphead installment. Dubbed the Mighty Cuphead Adventure, this is taking a different art direction to the original. "In true Studio MDHR fashion, this game goes beyond just taking inspiration from the classics of the 1980s… it is actually built with technology of the era," the studio explained. "That's right: Mighty Cuphead Adventure is programmed in assembly language and designed with the exacting specifications of the Sega Master System home gaming console in mind." Aside from releasing on PC and modern consoles, Mighty Cuphead Adventure will even be playable on the 1985-released Sega Master System. A release date has not been announced just yet.
    • Any decent ITSM will A) have a web form that allows a user to raise a ticket, if you're writing an email you can write a ticket. B) Monitor a mailbox and auto-generate tickets based on inbound mails for those users that really can't get their heads around the concept that if you have an issue you go to support.mycompany.com and fill in the box. From your description you're having users email the desk, and then having a human read each one and manually raise a ticket on behalf of the user.
    • Microsoft PC Manager 3.21.6.0 (Offline Installer) by Razvan Serea With Microsoft PC Manager, users can easily perform basic computer maintenance and enhance the speed of their devices with just one click. This app offers a range of features, including disk cleanup, startup app management, virus scanning, Windows Update checks, process monitoring, and storage management. Microsoft PC Manager key features: Storage Manager- easily uninstall infrequently used apps, manage large files, perform a cleanup, and set up Storage Sense to automatically clear temporary files. Health Checkup feature -scans for potential problems, viruses, and startup programs to turn off. It helps you identify unnecessary items to remove, optimizing your system's performance. Pop-up Management - block pop-up windows from appearing in apps. Windows Update - scans your system for any pending updates. Startup Apps - enable or disable startup apps on your PC, allowing you to optimize your system's startup performance. Browser Protection - rest assured that harmful programs cannot alter your default browser. Also enables you to change your default browser. Process Management - allows you to conveniently terminate any active process, ensuring optimal system performance and resource utilization. Anti-virus protection - Fully integrated with Windows Security. Safeguard your PC anytime. Quick Steps: Download Microsoft PC Manager Offline Installer (APPX/MSIX) with Adguard Adguard serves as a third-party online service, offering a user-friendly method for directly downloading appx, appxbundle, and msixbundle files from the Microsoft Store. Official download links will be generated for both the app's various versions and its dependency packages. How to download Microsoft PC Manager Offline Installer (APPX/MSIX) 1. Initially, you must find the app URL within the Microsoft Store. Access the Microsoft Store via your browser and search for "Microsoft PC Manager". Once located, copy the app URL, which includes the product ID, either from the address bar or from the provided link below. https://apps.microsoft.com/detail/9PM860492SZD 2. Now paste the app URL into the designated area, then click the check mark button to produce a direct download link. 3. To download, right-click the relevant link and select “Save link as…” from your browser's menu. Occasionally, Microsoft Edge may flag the download as insecure. In such cases, consider utilizing alternative browsers such as Google Chrome or Firefox to successfully complete the download. Microsoft PC Manager is a completely free tool optimized exclusively for use on Windows 10 (19042.0 and above) and Windows 11. Download: Microsoft PC Manager 3.21.6.0 | from Microsoft Store View: Microsoft PC Manager Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • I've never even heard of this browser before seeing this article. How does it differ from other browsers?
    • Fixing things? Have you ever tried linux? Everything works out of the box nowadays in most common hardware. This includes Wifi and Bluetooth. If anything, if they return back to windows is because they haven't found an equivalent program which often used on windows.
  • Recent Achievements

    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      485
    2. 2
      PsYcHoKiLLa
      272
    3. 3
      Skyfrog
      78
    4. 4
      Steven P.
      65
    5. 5
      FloatingFatMan
      61
  • Tell a friend

    Love Neowin? Tell a friend!