[SOLVED] Dlink so close , but .............

[rokytnji]

This is the command lines I picked up from googling but am scared to use them yet.
Posts

How To: Manual Network Configuration without the need for Network Manager
In setting up their wireless connection for the first time, Im discovering many individuals having problems connecting through Network Manager or other GUI wireless connection tools. In fact my Network Manager is intermittently buggy, connecting sometimes and not others. This guide benefits all users in case the GUI tools are not working, and is useful for testing a wireless connection during initial installation of wireless drivers since it provides for good debugging output.

Unencrypted/ WEP / WPA connections will be covered in this guide.
This guide is for anyone attempting to establish a network connection manually at the command line.

Pre-requisites
1. Properly installed network driver -- This guide can be used to troubleshoot driver installation to see if it is properly functioning
2. The ESSID of your router must be broadcasted and not hidden
3. Knowlege of your wireless cards driver (please see Prerequisite #4 to determine driver). Those using the r8187/r818x driver please see the end of the guide
4. Knowledge of your wireless card's Interface Name - The user must know the proper interface of the wireless connection (wlan0, eth1, rausb1, etc). To discover this information, at command line type:

Code:

lshw -C network

There may be multiple interfaces listed, however look under the section appropriate to your wireless device for the line labeled logical name. Here is an example:

Code:

*-network
description: Wireless interface
product: BCM4306 802.11b/g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 0
bus info: pci@06:00.0
logical name: wlan0
version: 03
serial: 00:12:17:35:17:10
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+lsbcmnds driverversion=1.48rc1+Cisco-Linksys ,LLC.,02/1 ip=192.168.1.101 latency=64 multicast=yes wireless=IEEE 802.11g
resources: iomemory:3c000000-3c001fff irq:11

In the example above the interface name is wlan0. I will refer to the interface name throughout the rest of this guide as <interface>.

For people first setting up their connection, please note that the above also lists the driver used for the network card. In the example above, the driver used is ndiswrapper. If your network device comes back UNCLAIMED or there is no driver listed, then you have not correctly installed the driver for your device. You must review the procedures for installation of your wireless driver.

For those wanting to use static IP addresses, please see section at bottom of guide regarding configuration for static IP addresses

__________________________________________________ __________________________
Unencrypted Connection

All commands typed at the command line:

sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <interface> essid "ESSID_IN_QUOTES"
sudo iwconfig <interface> mode Managed
sudo dhclient <interface>

I think interface for me is either eth o or eth 1. I am not sure.

[gruven]

Ok, I have successfully eliminated network-manager from my ubuntu computer, and I now use /etc/network/interfaces to configure my card.

If network manager is flaky with your card (as it looks like it is) then you may try this.

What I did was put my settings in /etc/network/interfaces and then disabled network-manager. When I saw that it worked, I just un-installed network-manager. That way, my network connection works when the machine boots up instead of me having to login.

You can try this if you want, and it will probably be successful, and you will learn a lot about linux wireless, but it won't be easy for you because it is trial-and-error to get it configured right.

Personally, I wouldn't download the file and install it because I can get it working for you without that I hope.

[gruven]

Your wireless card is eth1, and those commands will work. The easy way is to just disable network-manager for the time being (right click it and close it) and then try the commands. You will have to sudo the commands, remember.

[rokytnji]

huh???????? gave that answer before i saw your second post

[rokytnji]

Will that kill my land line connection when I delete network manager?

[rokytnji]

Right clicking it doesn't give an option to close it. Do I just unclick enable wireless and get the samwe results?

[rokytnji]

Getting no where with wireless disabled in device manager. terminal is giving me this.

harry@harry-laptop:~$ sudo ifconfig eth1 down
[sudo] password for harry:
harry@harry-laptop:~$ sudo dhclient -r eth1
There is already a pid file /var/run/dhclient.pid with pid 9517
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit ISC DHCP

Listening on LPF/eth1/00:15:00:10:0a:ce
Sending on LPF/eth1/00:15:00:10:0a:ce
Sending on Socket/fallback
harry@harry-laptop:~$ sudo ifconfig eth1 up
harry@harry-laptop:~$ sudo iwconfig eth1 "essid"
Error for wireless request "Set ESSID" (8B1A) :
too few arguments.
harry@harry-laptop:~$ sudo iwconfig eth1 "essid"
Error for wireless request "Set ESSID" (8B1A) :
too few arguments.
harry@harry-laptop:~$ sudo iwconfig eth1 "ESSID"
Error for wireless request "Set ESSID" (8B1A) :
too few arguments.
harry@harry-laptop:~$

[rokytnji]

ARRRRRRRRRRRRGH my ass needs a break.my eyes are shot and my brain is numb. Will try again tommorrow.

[gruven]

Instead of "essid" type this:

sudo iwconfig eth1 essid harrybelkin

[waterhead]

You guys need to slow down and stop and take a breather!

Your wireless won't completely work until you install the needed firmware for it. It uses the ipw2200 kernel driver, and firmware can be downloaded from here:
Intel&#174; PRO/Wireless 2200BG Driver Firmware
I'm not sure which version you need, but I'd start with the newest. After unpackng it, copy the contents to the /lib/firmware folder, as root or use sudo.