-
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.
Clarification to those about to read this Guide
1. This method provides the most low level method to establish your network connection. It is the least common denominator. It does not use any reference to the /etc/network/interfaces file, as this file requires a method that is more high level.
2. If you are interested in making modifications to your /etc/network/interfaces guide to establish your connection, possibly Weiman01's guide covering this topic would be more applicable to your situation: http://ubuntuforums.org/showthread.php?t=318539. This method however uses processes that are more high level. If editing or use of the /etc/network/interfaces file fails, I would recommend reading the guide provided below, as it is "lower level".
Unencrypted/ WEP / WPA (PSK and EAP-TLS) 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:
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>.
Attention All Users: Please Read
****All users of Atheros or Intel Chipsets (ipw****) -- Although lshw may list your interface as wmaster0 or wifi0 -- PLEASE NOTE this refers to the actual assigned interface name to the device, HOWEVER you interact through an assigned VIRTUAL INTERFACE!!!. Your will NEVER USE wmaster0 or wifi0 as the device name. If you type iwconfig, this may give you information on the assigned virtual interface used to access the physical device. -- BOTTOM LINE -- You will never use wmaster0 or wifi0 as the interface name, rather some other interface such as wlan0 of eth1. Please check ifconfig or iwconfig for cross referencing!!
***Please note -- as there exist exceptions to every rule, an exception applies to Atheros chipset employing the madwifi kernel module. Atheros cards are typically identified as wifi0. This is the physical logical name of the device. When working with madwif modules however, one or more virtual interfaces are made for every actual device. All configurations must be completed using the virutal interface device rather than the actual interface to the device. In most cases, Atheros chipsets will need to use the ath0 interface rather than the wifi0 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:
Code:
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>
__________________________________________________ __________________________
WEP Connection
You must have either your 64bit or 128 bit HEX Key or the ASCII Equivalent of your HEX Key.
Code:
sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <interface> essid "ESSID_IN_QUOTES"
sudo iwconfig <interface> key HEX_KEY <<<-------- If using ASCII Equivalent, this is s:ASCII_KEY (please make note of the prefix s:)
****Additional Comand that may be needed -- sudo iwconfig <interface> key open <<<----See note below
sudo iwconfig <interface> mode Managed
sudo dhclient <interface>
***The security mode may be open or restricted, and its meaning depends on the card used. With most cards, in open mode no authentication is used and the card may also accept non-encrypted sessions, whereas in restricted mode only encrypted sessions are accepted and the card will use authentication if available.
__________________________________________________ __________________________
WPA Connection - WPA-PSK or WPA2-PSK (PSK=Pre-Shared Key) or WPA-EAP-TLS
For uses of Ra-based chipsets: rt61, rt73, rt2500 please skip directly to the WPA Section entitled WPA with Ra based chipsets
Requirements: In most cases the wpa_supplicant package is required in order to connect via WPA. If you have a working ethernet or unencrypted/WEP wireless connection, this package may be installed via:
Code:
sudo aptitude install wpasupplicant
If only wireless is available, I would recommend that an unencrypted connection first by established and tested first before directly proceeding to make a WPA connection. WPA adds another layer of complexity.
WPA-PSK - Covers WPA(1) and WPA(2)
1. Creation of /etc/wpa_supplicant.conf file
At command line:
Code:
gksu gedit /etc/wpa_supplicant.conf
Inside the file add the following for WPA(1):
Code:
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="ESSID_IN_QUOTES"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="ASCII PSK Password in Quotes"
pairwise=TKIP
group=TKIP
}
For WPA(2) (see this thread: http://ubuntuforums.org/showthread.php?t=607410):
Code:
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="ESSID_IN_QUOTES"
psk="ASCII PSK Password in Quotes"
key_mgmt=WPA-PSK
proto=RSN WPA
pairwise=CCMP TKIP
group=CCMP TKIP
}
***Word of caution -- In some cases I have found WPA(2) to have different settings than the above. Some Broadcom cards use the pairwise/group TKIP cipher for WPA2 rather than CCMP. I would suggest all initially use WPA(1) and then later convert to WPA2 since some variations to the above may be needed
**WPA2 capabilities must also be built-into the driver set used with your hardware. If using ndiswrapper with an old windows driver, the driver may not contain code for wpa2.
2. Connect via command line
Code:
sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo wpa_supplicant -D<****see footer below***> -i<interface> -c/etc/wpa_supplicant.conf -dd
***Note that starting with the -dd flag will create a lot of debuggin output.
If you choose to use the -dd flag to troubleshoot your connection, you must
open up a separate terminal and type the rest of the commands listed below in a
separate terminal window. You can also replace the -dd flag with the -B flag to
send the process to the background, avoiding the need to open up a separate
terminal window (however no debugging output will be generated)
sudo dhclient <interface>
***footer
The value listed here is dependent on the driver you have installed. Typing man wpa_supplicant at command line will give you the full gamut of choices however most recent versions of wpa_supplicant only recognize wext as the appropriate value (Despite all the information on the internet). If you would like to verify what drivers besides wext your installed version of wpa_supplicant recognizes, type at the command line:
wpa_supplicant -l
And look specifically at the section called drivers:
Here is what my stock wpa_supplicant lists for its drivers:
drivers:
wext = Linux wireless extensions (generic)
atmel = ATMEL AT76C5XXx (USB, PCMCIA)
wired = wpa_supplicant wired Ethernet driver
Other drivers can be compiled into wpa_supplicant if you compile wpa_supplicant, however please not that in recent kernel versions this is unnecessary. wext will work for ndiswrapper, madwifi, intel, etc.
WPA-PSK with Ra Based Chipsets
Ra cards do not require the wpa_supplicant package to use WPA. Here is how to connect from the command line with these cards:
References: http://ubuntuforums.org/showthread.p...=serial+monkey, http://rt2x00.serialmonkey.com/wiki/...owto#Using_WPA
WPA-PSK(1)
Code:
sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <inteface> essid "ESSID_IN_QUOTES"
sudo iwpriv <interface> set AuthMode=WPAPSK
sudo iwpriv <interface> set EncrypType=TKIP
sudo iwpriv <interface> set WPAPSK="YOUR_WPA_PSK_KEY"
sudo dhclient <interface>
For WPA-PSK(2), I have no working configuration yet. If someone would like to help me refine these instructions for WPA2 with Ra-based chipsets, I would appreciate your help!
WPA EAP-TLS
Information Provided Referenced from http://www.codealias.info/technotes/...x_client_setup
Thanks to CodeAlias for Providing Information
1. Prepare TLS Certificates
EAP-TLS requires client TLS certificates to be installed in the system. You need to ask the administrators in your institution to provide you your own TLS certificate.
In the most common cases, your admin will issue you a .p12 file and a password.
We need to create three files from this .p12 certificate
These files are cacert.pem, cert.pem and key.pem (The names may vary). Assuming that your certificate file name is example.p12, run the following :
Code:
openssl pkcs12 -in example.p12 -out cacert.pem -cacerts -nokeys
openssl pkcs12 -in example.p12 -out cert.pem -clcerts -nokeys
openssl pkcs12 -in example.p12 -out key.pem -nocerts
Put the three generated files somewhere in the file system of your wireless device (e.g /etc/certs)
2. Configuration of the wpa_supplicant.conf file
Edit the wpa_supplicant configuration file (e.g. /etc/wpa_supplicant.conf), ant put the following:
Code:
network={
ssid="ESSID_IN_QUOTES"
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TLS
identity="XXXXX@yourdomain.com"
ca_cert="/etc/certs/cacert.pem"
client_cert="/etc/certs/cert.pem"
private_key="/etc/certs/key.pem"
private_key_passwd="YOUR-PASSWORD"
}
---“YOUR-PASSWORD” is the password provided by your administrator when your received your .p12 certificate
3. Connect via the command line
Code:
sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo wpa_supplicant -D<****see footer below***> -i<interface> -c/etc/wpa_supplicant.conf -dd
***Note that starting with the -dd flag will create a lot of debuggin output.
If you choose to use the -dd flag to troubleshoot your connection, you must
open up a separate terminal and type the rest of the commands listed below in a
separate terminal window. You can also replace the -dd flag with the -B flag to
send the process to the background, avoiding the need to open up a separate
terminal window (however no debugging output will be generated)
sudo dhclient <interface>
***footer
The value listed here is dependent on the driver you have installed. Typing man wpa_supplicant at command line will give you the full gamut of choices however most recent versions of wpa_supplicant only recognize wext as the appropriate value (Despite all the information on the internet). If you would like to verify what drivers besides wext your installed version of wpa_supplicant recognizes, type at the command line:
wpa_supplicant -l
And look specifically at the section called drivers:
Here is what my stock wpa_supplicant lists for its drivers:
drivers:
wext = Linux wireless extensions (generic)
atmel = ATMEL AT76C5XXx (USB, PCMCIA)
wired = wpa_supplicant wired Ethernet driver
Other drivers can be compiled into wpa_supplicant if you compile wpa_supplicant, however please not that in recent kernel versions this is unnecessary. wext will work for ndiswrapper, madwifi, intel, etc.
__________________________________________________ __________________________
A successful connection in all cases will similarly result in: (Example Provided Below):
Code:
user@computer:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/wlan0/00:12:17:35:17:10
Sending on LPF/wlan0/00:12:17:35:17:10
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.101 -- renewal in 299133 seconds.
The computer in this example has received an IP address of 192.168.1.101
__________________________________________________ __________________________
Users of RTL 8180, RTL8185, RTL 8187 using the built in native r8187 / r818x drivers
By default the r8187 and r818x drivers are blacklisted due to a know bug. These drivers are usuable however with a twist to the above methods
If you want to try using these drivers, please load the kernel modules:
Code:
sudo modprobe r818x
sudo modprobe r8187
These drivers require a bogus or extra letter be suffixed to the essid name in order for these drivers to work
For example if your are trying to connect to a router with essid=Router, at he command line you would type essid=Routerx. Notice the extra x or bogus character. I have provided an example using the unencrypted connection procedure below, however this extra character needs to be used if attempting to connect to all network types (unencrypted/ WEP / WPA)
Code:
sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> up
sudo iwconfig <interface> essid "Routerx"
sudo iwconfig <interface> mode Managed
sudo dhclient <interface>
If these drivers work for you, and you would like these drivers to load automatically at startup for you, avoiding to have to type sudo modprobe everytime, please edit your blacklist file:
Code:
gksu gedit /etc/modprobe.d/blacklist
And comment out (or prefix the following lines with a # sign). You want the following lines to appear as below:
Code:
#blacklist r8187
#blacklist r818x
__________________________________________________ __________________________
Static IP Addresses
Im going to give an example of how to configure your interface using a static IP address using an unencrypted wireless connection. The two lines highlighted below however can be used with WEP and WPA connections. Values in italics must be customized to meet your particular situation
Code:
sudo ifconfig <interface> down
sudo dhclient -r <interface>
sudo ifconfig <interface> 192.168.1.100 netmask 255.255.255.0 up
sudo route add default gw 192.168.1.1
sudo iwconfig <interface> essid "ESSID_IN_QUOTES"
sudo iwconfig <interface> mode Managed
If when using static IP addresses you are getting a problem with name resolution, you will have to specifiy specific dns (domain name servers) in order to translate URLs to IP addresses. Unfortunately there is not an easy way to configure this from the command line. This requires that you edit the /etc/resolv.conf file and manually enter the domain name server(s) you want to use. In many cases users can specifiy their router, their internet service providers dns servers, or use opendns (or use all three). Up to three nameservers can be specified.
Code:
sudo gedit /etc/resolv.conf
and add the nameservers you want to use, one to a line, in the following format.
Code:
nameserver <nameserver>
***Spaceboy909 has also reported that when using this technique with static IP addresses, network manager has to be uninstalled because it keeps trying to reset the connection. In order to uninstall networkmanager:
In Ubuntu:
Code:
sudo aptitude uninstall network-manager-gnome
In Kbuntu:
Code:
sudo aptitude uninstall knetworkmanager
__________________________________________________ _________________________
Setting the Wireless Interface to Connect at Boot ***Courtesy of Maricaibo
If you are successful in bringing up the Interface Manually, the commands may be placed inside the /etc/rc.local file to run the commands at boot, and establish a wireless connection. There is no GUI to give visual confirmation of the connection. The user should type ifconfig at the command line to verify an IP address has indeed been granted by the router.
The process of adding the commands to the /etc/rc.local file is documented below (this connects to an unencrypted network -- to connect to a WEP or WPA encrypted network, some modifications as used above will need to be added):
Code:
gksu gedit /etc/rc.local
This opens up the file in the gedit utility and allows you to make changes and save the file
Code:
ifconfig <wired network connection interface> down
ifconfig <wireless network connection interface> down
dhclient -r <wireless_interface>
iwconfig <wireless_interface> essid <router name>
iwconfig <wireless_interface> mode Managed
ifconfig <wireless_interface> up
dhclient <wireless_interface>
Be sure this text goes into the /etc/rc.local file BEFORE the line reading "exit 0".
Save and close the /etc/rc.local file.
Open up a Terminal window (the shell) and type in:
Code:
sudo chmod +x /etc/rc.local
This command turns the rc.local file into an executable that will run at startup. Here's an example of what the /etc/rc.local file should contain. Your device names may be different:
Code:
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
ifconfig eth0 down
ifconfig wlan0 down
dhclient -r wlan0
iwconfig wlan0 essid "ESSID_IN_QUOTES"
iwconfig wlan0 mode Managed
ifconfig wlan0 up
dhclient wlan0
exit 0
NOTE: The first line in the rc.local file downs your wired connection, so if for some reason you need the wired connection back just open up a Terminal window (shell) and type:
sudo <wired_interface> up
sudo dhclient <wired_interface>
__________________________________________________ __________________________
Useful Commands
ifconfig - lists IP address (similar to ipconfig in Windows)
iwlist scan - shows wireless networks that are available in the area along with basic encryption information
lshw -C network - Shows interface and driver associated with each networking device
lspci -nn - Shows hardware connected to the pci bus
lsusb - Shows USB connected hardware
lshw -C usb - Additional info on USB related hardware (good for USB dongles)
cat /etc/modprobe.d/blacklist - List modules that will not be loaded by the Operating System at boot time
lsmod - lists currently loaded kernel modules. (Example usage - lsmod | grep ndiswrapper)
route -n - Lists kernel IP routing table -- Good for troubleshooting problems with the gateway (netstat -rn = equivalent command)
sudo route add default gw 192.168.1.1 - Example of how to set the default gateway to 192.168.1.1
sudo route del default gw 192.168.1.1 - Example of how to delete the default gateway setting
sudo modprobe ***** - Loads the kernel module **** . (Example usage - sudo modprobe ndiswrapper, sudo modprobe r818x, sudo modprobe ath_pci)
sudo modprobe -r **** - Unloades the kernel module ****. (Example usage - sudo modprobe -r ndiswrapper)
sudo ifup/ifdown <interface> - Brings up/down the interface and clears the routing table for the specified interface
sudo ifconfig <interface> up/down - Brings up/down the interface for the specified interface
sudo dhclient <interface> - Request IP address from DNS server for specified interface
sudo dhclient -r <interface> - Release IP address associated with specified interface
sudo iptables -L - Lists firewall rules
dmesg | more - Lists boot log -- good for troubleshooting problems with modules/drivers not being loaded
uname -r - Displays kernel version
/etc/iftab (Feisty and pre-releases (Edgy, etc)) - /etc/udev/rules.d/70-persistent-net.rules (Gutsy) - File which assigns logical names (eth0, wlan0, etc) to MAC addresses
cat /etc/resolv.conf - Lists DNS servers associated with network connections (Network Manager)
/etc/dhcp3/dhclient.conf - File which sets or modifies dns (domain name servers) settings
__________________________________________________ __________________________
WPA_SUPPLICANT.CONF - Good Description and Explanations of All Available Options that can be Placed with the wpa_supplicant.conf file
http://hostap.epitest.fi/cgi-bin/vie...?revision=HEAD
__________________________________________________ __________________________
References for Specific Wireless Chipsets - Please see Link if Your Specific Chipset is Not Working with Above Tutorial's Instructions
Official Broadcom site for bcm43xx firmware - http://linuxwireless.org/en/users/Drivers/b43
Broadcom 64bit Drivers for Use with Ndiswrapper - http://www.linuxant.com/driverloader/drivers.php
Broadcom Guid for Ubuntu Hardy/Intrepid and Ibex -- A very informative sight! - http://linuxfans.betaserver.org/inde...ides&Itemid=61 - Author Ayuthia
Ra chipsets - Serial Monkey Drivers - rt2500, rt73, rt61, rt2570 drivers - http://ubuntuforums.org/showthread.p...=serial+monkey - Author diepruis
rt2500 chipsets with the Serial Monkey rt2500 CVS driver - http://ubuntuforums.org/showthread.p...ghlight=rt2500 - Author zoiks
Ralink RT2860 (m)PCI(e) (RT2760/RT2790/RT2860/RT2890) - http://ubuntuforums.org/showthread.php?t=1045703 - Author Fass
Rutilt - A Network Manager Like GUI for Ra Chipsets - http://ubuntuforums.org/showthread.p...ghlight=rutilt - Author sulilogs
Ndiswrapper Official Compatibility Reference - http://linuxfans.betaserver.org/ndis_drivers/toc.html - Author Ayuthia (Borrowed from the Ex-Official Ndiswrapper Site)
Ndiswrapper installation for Broadcom chipsets - http://ubuntuforums.org/showthread.php?t=475963 - Author Jamie Jackson
Ndiswrapper General Installation Guide - SVN, Troubleshooting Tips (My Personal Guide) - http://ubuntuforums.org/showthread.php?t=574501 - Author KevDog
Madwifi website for certain Atheros Chipsets - http://madwifi.org/ -- If your Atheros chipset is listed on this website - it should work out of the box with installation of the linux restricted drivers package for your kernel version
Atheros 5006eg Chipset work-around - Card apparently listed as 5007eg - http://ubuntuforums.org/showpost.php...5&postcount=14 - Author ugm6hr
Does your madwifi connection keep dropping??? Possible solution -- http://ubuntuforums.org/showthread.php?t=540101 = Author robnz/tranalbert
Realtek win98 driver - http://www.majorgeeks.com/Realtek_RT...0XP_d5165.html - For use with ndiswrapper if native r818x, r8187 driver is buggy
Realtek win98 driver installation - http://ubuntuforums.org/showthread.p...highlight=8187 - Author Panurge
Realtek - Installation with Native Driver - http://ubuntuforums.org/showthread.php?t=567505
Realtek 8187B Native Patch for Realtek 818x USB Devices -- Relevant only to rtl8187B USB wireless devices - Toshiba Laptops - http://www.datanorth.net/~cuervo/rtl8187b/ - Author Cuervo
__________________________________________________ __________________________
Wireless Security
WPA with EAP-TLS - http://www.codealias.info/technotes/...x_client_setup
__________________________________________________ __________________________
Other Interesting Sites
Control Programs Kept in Swap vs Memory - http://ubuntuforums.org/showpost.php...&postcount=150
If your Wireless Freezes after Suspend/Resume - Check here - http://ubuntuforums.org/showpost.php...7&postcount=12 - Author Harty83
DNS related problems?? - Configuration for OpenDNS servers - http://ubuntuforums.org/showthread.php?t=543659 - Author noob12
Turn off/Disable IPv6 - http://ubuntuforums.org/showthread.php?t=282034 - Author handy
General Linux Page Discussing Network Setups - Default Gateways - http://linux-ip.net/html/basic-changing.html
Log Files -- Your Friend to Debug almost anything on your System - https://help.ubuntu.com/community/Li...f98267e009db55
Using OpenVPN to bridge networks - http://ubuntuforums.org/showthread.php?t=752127 - Author SpaceTeddy
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Excellent post! Worked as advertised! I had been using the NetworkManager but all of a sudden, it stopped wanting to connect to my wireless. These instructions got me connected once again. Thanks a lot!!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
After upgrading to gutsy my WIFI broke after the first reboot. The output from the first command is:
Code:
darren@BeggarBox:~$ sudo lshw -C network
*-network
description: Network controller
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0b:00.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=ipw3945 latency=0 module=ipw3945
...
Notice it is not given a logical name. How do I set it back to being eth1? /etc/iftab seems to be the best option, but I dont know the mac address. Any ideas?
It doesn't seem like /etc/iftab is used anymore, back to square one....
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Beggar
Interesting situation you present, cant say that Ive ever seen your situation before .. so its kind of neat. What does
dmesg
say after you boot. Anything about the interface. Does
ifconfig
lend any clues.
My forte is not with the ipw drivers. I think noob12 is much better in this area than I.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
My wireless (eth1) has gone upon the latest "partial upgrade" of the gutsy preview I've been using for a couple of weeks.
~$ dmesg|grep ipw2200
[ 18.384000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmprq
[ 18.384000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 18.628000] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
[ 18.872000] ipw2200: Unable to load ucode: -62
[ 18.872000] ipw2200: Unable to load firmware: -62
[ 18.872000] ipw2200: failed to register network device
[ 18.872000] ipw2200: probe of 0000:02:01.0 failed with error -5
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
If you have an older kernel version installed (ie you upgraded from feisty), press the ESC key when booting to enter the grub menu and see if you can use the ipw driver in an older kernel version. One other option, although its pretty drastic would be to compile your own vanilla kernel. I think (not certain), that the ipw drives are included by default, but confirm this. The masterkernel thread is a good place to start in the forums.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Mine loads fine, but then I found this little gem a few lines down.
Code:
[ 16.088000] ipw3945: Radio Frequency Kill Switch is On:
[ 16.088000] Kill switch must be turned off for wireless networking to work.
Might be hard for me to turn my kill switch off however, considering I don't have one...
----
Scratch that, I didnt notice it, but since the gutsy upgrade my function keys work. Apparently right after the upgrade I used fn-f2 instead of ctrl-f2, fn-f2 is my computers wifi killswitch.
Boy do I feel stupid. I only spent 5+ hours trying to fix that. Hard to debug something you dont think works suddenly getting fixed on you...
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
kevdog
If you have an older kernel version installed (ie you upgraded from feisty), press the ESC key when booting to enter the grub menu and see if you can use the ipw driver in an older kernel version...
Luck would have it, I just removed the older kernels yesterday. Have rebooted a couple of times since then with everything working fine. But ran the latest updates (some sort of a partial upgrade) just today, and that did the wireless in.
Oh well, gonna have another look. Thanks for your suggestions.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Hi,
Just wanted to say thanks for the post, kevdog.
I just followed your advice to connect to my girlfriend's WRT54G v8 with WPA1. It was working under Windows, but not (K)ubuntu. The only oddity I found is that I have to use the wext driver instead of ipw when running wpa_supplicant, even though I have an Intel 2915 card in my laptop. I found that out by reading the output of wpa_supplicant with the -Dipw option.
Thanks again!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Hmm, I guess you are right
wext is for any generic linux driver.
ipw is for the intel ipw 2100 and 2200 driver.
Good thing you read the man pages since this part of configuring the wpa_supplicant.conf file can be a little tricky
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
I installed Mepis 6.5.02 on my Dell Inspiron 1721 last week. I gave Vista the boot and Mepis installed real easy and connected to my Linksys router w/no issues. Today, I downloaded Kubuntu 7.10 and tried to set it up to dual boot. I ran into some problems and finally threw my hands up and just installed it over Mepis. I couldn't get connected to the wireless router. Then I tried Mepis again and was able to dual boot both Kubuntu and mepis (happy days!), however, now I can't connect to the wireless on Mepis. Right now I am connected wired into the access point.
I ran you scripts and here is what I saw....
iwconfig wlan0 essid Gameserver
root@1[/]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sit0 no wireless extensions.
root@1[/]# ifconfig wlan0 down
root@1[/]# dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on LPF/wlan0/00:1c:26:91:c7:ec
Sending on LPF/wlan0/00:1c:26:91:c7:ec
Sending on Socket/fallback
root@1[/]# ifconfig wlan0 up
root@1[/]# ifconfig wlan0 essid "Gameserver"
essid: Unknown host
ifconfig: `--help' gives usage information.
root@1[/]# iwconfig wlan0 essid "Gameserver"
root@1[/]# iwconfig wlan0 mode Managed
root@1[/]# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on LPF/wlan0/00:1c:26:91:c7:ec
Sending on LPF/wlan0/00:1c:26:91:c7:ec
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
root@1[/]#
Please help!!!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
What does
iwlist scan show
Make sure you take down your wired interface when trying to connect, such as
sudo ifconfig eth0 down
Also can you post
lshw -C network
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Here you go!
root@2[eleni]# sudo ifconfig eth0 down
root@2[eleni]# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:13:46:1F:A4:3E
ESSID:"default"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:1A:70:F6:C6:99
ESSID:"Gameserver"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:93/100 Signal level:-36 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
root@2[eleni]# lshw -C network
*-network
description: Wireless interface
product: Dell Wireless 1390 WLAN Mini-PCI Card
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0b:00.0
logical name: wlan0
version: 01
serial: 00:1c:26:91:c7:ec
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper driverversion=1.38 firmware=Broadcom,10/12/2006, 4.100.15.5 link=no multicast=yes wireless=IEEE 802.11g
resources: iomemory:fe8fc000-fe8fffff irq:19
*-network DISABLED
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@03:00.0
logical name: eth0
version: 02
serial: 00:1c:23:8a:f6:f8
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=b44 driverversion=0.97 link=no multicast=yes
resources: iomemory:fe5fe000-fe5fffff irq:22
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
What driver are you using bcmwl5??
Once the eth0 interface is down, can you repeat the unencrypted manual commands for wlan0 and see what happens??
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
Beggar
After upgrading to gutsy my WIFI broke after the first reboot. The output from the first command is:
Code:
darren@BeggarBox:~$ sudo lshw -C network
*-network
description: Network controller
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0b:00.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=ipw3945 latency=0 module=ipw3945
...
Notice it is not given a logical name. How do I set it back to being eth1? /etc/iftab seems to be the best option, but I dont know the mac address. Any ideas?
It doesn't seem like /etc/iftab is used anymore, back to square one....
I remarked out # the last line in /etc/udev/rules.d/70-persistent-net.rules, rebooted and wireless started working. Seems upgrade replaced iftab but then setup rules.d with two interface names for the same mac address...
Here the files before I remarked out the redundant entry in rules.d
/etc/iftab
Code:
# This file is no longer used and has been automatically replaced.
# See /etc/udev/rules.d/70-persistent-net.rules for more information.
#
# This file assigns persistent names to network interfaces.
# See iftab(5) for syntax.
##eth0 mac 00:09:5d:15:60:23 arp 1
#wlan0 mac 00:19:D2:BB:50:59 arp 1
/etc/udev/rules.d/70-persistent-net.rules
Code:
# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.
# Converted from /etc/iftab on upgrade
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:09:5d:15:60:23", ATTRS{type}=="1", NAME="eth0"
# Converted from /etc/iftab on upgrade
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:19:D2:BB:50:59", ATTRS{type}=="1", NAME="wlan0"
# PCI device 0x8086:0x4222 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:19:d2:bb:50:59", NAME="eth1"
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Same error!
root@1[/]# ifconfig wlan0 up
root@1[/]# iwconfig wlan0 essid "Gameserver"
root@1[/]# iwconfig wlan0 mode Managed
root@1[/]# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on LPF/wlan0/00:1c:26:91:c7:ec
Sending on LPF/wlan0/00:1c:26:91:c7:ec
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
How do I find what the driver is?
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Look in the /etc/ndiswrapper folder. There should be a subdirectory, and inside this subdirectory I believe is contained the driver.
Are you broadcasting the essid on the router? No MAC filtering on the router correct??
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
What are the steps to connect to a network with hidden ESSID (WEP) using command line?
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
The commands are the same, however Im not sure if this will work. Its something about the drivers and Linux. So basically Im saying is that Im not certain ubuntu can connect to any router with hidden ssid broadcast.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
eleni@1[~]$ cd /etc
eleni@1[etc]$ cd ndis*
eleni@1[ndiswrapper]$ ls
bcmwl5 lsbcmnds
The SSID is being broadcasted. Not sure about MAC filtering. I see a MAC address for the Router Lan settings and another for the Router Wan settings. Encryption is WEP. I can get to the point where it asks me for the key. I put it in and it gets to 28% complete and fails. I have tried connected to some unprotected wireless networks and the same thing happens. 28% and quits. My sound doesn't work either and that was working before I did the dual boot setup.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Where are you getting the 28% stuff -- From the command line Im not familar with that output at all.
What is in the lscmnds subfoler??
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
There is an icon in the tray where you can click to connect to a wireless network. When I tell it to connect it starts connecting until it gets to 28% and then fails. It does this on any wireless network, not just my router.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
followed all the directions step by step, but I'm still getting "No DHCPOFFERS received."
*posted a thread on my question instead -> http://ubuntuforums.org/showthread.p...80#post3592180
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
No icon is involved in these instructions -- if your having a problem with the icon, these instuctions are not for you!
I see that you are getting no dhcp offers. What is the sgnal strength reported for your router for
iwlist scan
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Code:
Quality:76/100 Signal level:-47dBm Noise level:-96 dBm
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
I am not using the icon with these instructions. It won't connect when I follow the instructions. When I use the GUI to manually set addresses, DNS, and Gateway or if I set it to automatic, there is a Icon to click to see available wireless networks. I can see the network, but when it tries to connect it only gets to 28%.
Here is the scan
wlan0 Scan completed :
Cell 01 - Address: 00:13:46:1F:A4:3E
ESSID:"default"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:4/100 Signal level:-93 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:1A:70:F6:C6:99
ESSID:"Gameserver"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:93/100 Signal level:-36 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
I wish I could help you guys more, since it seems like you guys are doing everything right. Ive seen random problems like this before, and its always something I would never think to do that would fix it -- like uninstall a different package, or disable ipv6. Try disabling ipv6, not sure if this is going to help. Ive also seen some cards struggle with 64 bit wep (some driver problem) so I dont know if you are effected by this. Have you tried ascii based wep authentication:
sudo iwconfig wlan0 key s:ASCII
With WEP, are you using the first hex key??
You can set your key index with the following command:
sudo iwconfig wlan0 key [1] XXXXXXX (or s:ASCII) key [1]
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
dude i love you, you're now my best friend in the world!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Kevdog
Here's one for you.
I have two identical network cards. (ipw3945)
One is working A-OK.
The other is showing up in the system, but with no logical name, and no mac address. I've checked the wireless switches, bios settings for the card - and it is enabled...
Here's what I get for "lshw -C network"
*-network
description: Network controller
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0b:00.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list
configuration: driver=ipw3945 latency=0 module=ipw3945
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: eth1
version: 02
serial: 00:1b:77:60:79:85
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw3945 driverversion=1.2.2mp.ubuntu1 firmware=14.2 1:0 () ip=10.10.1.9 latency=0 module=ipw3945 multicast=yes wireless=IEEE 802.11g
Obviously - the bottom one is working, top is not.
Where would I even start to get a logical name assigned to this. Querying "dmesg" doesn't give me anything interesting (errors) about this card.
I've tried other forums, threads, and this is the closest one I could find relevent. ANY help at all is appreciated.
Thanks.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Just some random thoughts
Do you need two wireless cards running at the same time?? Ok I guess I could think of some situations this might be needed but just a thought.
If the working wireless card is removed, does the other card work.
Ive used two different wireless cards plugged into two separate pcmcia slots before, (atheros and broadcom), however I didnt use them at the same time. I brought one interface down and the other up. Your situation is slightly different since your not even getting an interface name assigned.
I guess first step is to verify the first card actually works.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
kevdog
Just some random thoughts
Do you need two wireless cards running at the same time?? Ok I guess I could think of some situations this might be needed but just a thought.
If the working wireless card is removed, does the other card work.
Ive used two different wireless cards plugged into two separate pcmcia slots before, (atheros and broadcom), however I didnt use them at the same time. I brought one interface down and the other up. Your situation is slightly different since your not even getting an interface name assigned.
I guess first step is to verify the first card actually works.
The card actually works - I've used both by themselves in the same install with no problems. However, once there are two cards present, only one works.
As far as the need - if I don't want to buy another card, for what I'm trying to do/play with, yeah, this situation I need two.
Thanks for responding, you're the first in about a million posts all over the place - any ideas on where to start after verifying the card functions correctly?
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Are these two pcmcia slots?? Just wondering if one slot is given priority over the other.
Couple things to try, say you got the same scenario as you presented above, what if you bring the interface down, modprobe -r the ipw module, then modprobe the ipw module, then check with lshw -C network? Which card is assigned the interface name. What if you switch the cards?
How many times in lsmod | grep ipw is the ipw driver listed?
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
kevdog
Are these two pcmcia slots?? Just wondering if one slot is given priority over the other.
Couple things to try, say you got the same scenario as you presented above, what if you bring the interface down, modprobe -r the ipw module, then modprobe the ipw module, then check with lshw -C network? Which card is assigned the interface name. What if you switch the cards?
How many times in lsmod | grep ipw is the ipw driver listed?
These are two mini-pci express cards (Intel 3945abg) - I'm getting the feeling slot 2 is getting priority. If I switch the cards, it seems to follow that slot. It's the first slot I'm having problems with.
I've verified this slot works however, because, in the windows side of this install - it works flawlessly - except, I have no use for two cards in windows.
Under "lsmod" i've only got the driver coming up once.
When I "modprobe -r ipw3945" then "lshw" - both cards show up as unclaimed network controllers.
When I "modprobe ipw3945" - both cards show up again, the second one w/ the logical name/mac/etc... the other, with just the same basic info. This is the same as it was before.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Im just shooting from the hip here b/c I googled around and found nothing similar to your problem except my experience (which isnt exactly similar). However just wondering if there are windows xp drivers available for your device. Here is what Im thinking. Im not sure if you are hardware limited and only one device is going to work at a time, or its more a driver issue where two devices cant use the same driver at once. I just dont know. What if however we could make one device use the native ipw driver and the other ndiswrapper. Im not sure if this would work.
Here is what I was thinking however
Most likely the card not show is interface eth0
The card in slot two is interface eth1
You could probably confirm this by taking out the card in slot 2 and just using slot 1 and see if the device is assigned eth0.
You could then probably add some aliases in /etc/modules like the following:
alias eth0 ndiswrapper
alias eth1 ipw3945
Here is a reference although I dont if I completely understand everything:
http://linux.about.com/od/lkm_howto/a/hwtlkm06t03.htm
One last random thought
What if you just type
sudo ifconfig eth0 up
What happens??
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
kevdog
Im just shooting from the hip here b/c I googled around and found nothing similar to your problem except my experience (which isnt exactly similar). However just wondering if there are windows xp drivers available for your device. Here is what Im thinking. Im not sure if you are hardware limited and only one device is going to work at a time, or its more a driver issue where two devices cant use the same driver at once. I just dont know. What if however we could make one device use the native ipw driver and the other ndiswrapper. Im not sure if this would work.
Here is what I was thinking however
Most likely the card not show is interface eth0
The card in slot two is interface eth1
You could probably confirm this by taking out the card in slot 2 and just using slot 1 and see if the device is assigned eth0.
You could then probably add some aliases in /etc/modules like the following:
alias eth0 ndiswrapper
alias eth1 ipw3945
Here is a reference although I dont if I completely understand everything:
http://linux.about.com/od/lkm_howto/a/hwtlkm06t03.htm
One last random thought
What if you just type
sudo ifconfig eth0 up
What happens??
The ndiswrapper route is a no-go. That limits what I'm trying to do with the card. (Monitoring mode/injection/etc...). You may have hit it on the head w/ the two cards not being able to use the same driver, though I'm not proficient enough to know/find out.
As far as eth0 is concerned - that's actually the integrated broadcom nic and hasn't given me any problems.
Looks like I may be buying a PCMCIA card or another mini-pci express card for this setup. That sucks.
Thanks for your help though!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
What if you just type
sudo ifconfig eth2 up
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
kevdog
What if you just type
sudo ifconfig eth2 up
eth2 doesn't exist.
the exact error is "eth2: ERROR while getting interface flags: No such device"
interesting thing though - i disabled one of the mini-pci e slots completely in the bios (the one that was working flawlessly) and the other card came up immediately, except in the system it had it as "eth3" , there was no eth1 or eth2. worked and everything.
if i could get the second card assigned a logical name, while the first card was working, i'd be able to troubleshoot if from there. i'm wondering if this is some sort of bug with 2 cards using the same driver, you wouldn't think so, but i'm not familiar enough with the way hardware interfaces with drives under linux.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Thats why I wanted you to use ndiswrapper -- only for testing purposes. Im not sure if you can use the same driver twice, however it would seem logical that if one was using ndiswrapper and the other ipw and for some reason both network cards worked in this scenario, that it would tell me that it was most likely a driver or configuration problem rather than a hardware problem. Again Im not exactly sure how the kernel interacts and assigns drivers (or duplicate copies of a driver). Im just trying to rule some things out.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Kevdog, wanted to let you know this worked for me in Gutsy using NDISWrapper 1.47 with a Broadcom 43xx on a Dell Inspiron 8500. So it looks like it's an issue with Gutsy's Network manager or something. I was also glad to see someone mention the change to iftab for Gutsy, I did see that previously as well. Any idea if Network Manager can be backdated to Feisty's or if there's a configuration fix for it somewhere? If not, at least I know it CAN work, nice job.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Hello, i have been looking around
i have a dv2000 hp laptop with an AMD and the 64bit version of Gutsy
My wireless network has WPA it works
After i go thru a lot of hoops
boot up, change the settings on my wireless ssid and password, click ok (they are already stored)
change them back
and the network manager does it thing and activates the connection
i dont know why i dont get an IP at the moment of boot up, if i go to wired connection everything works as supposed
i have a broadcom 43xx driver
any ideas?... all i can think of is that unfortunatly my card is not trying to fetch an IP from the router
i have tried static ip as well and it doesnt work
pls help!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
You got to give me more details like how you are setting up your wpa connection. This post is really only concerned with setting up manual connections, and not with problems with network manager. I know a lot about network manager, but to delve into it here in this particular post would be a little off topic.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Kevdog, I am hoping you are still around and can help me with this:
My wifi card has the logical address of wifi0, but the iwlist scan is performed by ath0? Is this why I'm not getting any connection? And what about the wifi0: unknown hardware address type 801 error in the dhclient command?
Please help me sever the cable!
devo@devo-desktop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Ethernet interface
product: SiS900 PCI Fast Ethernet
vendor: Silicon Integrated Systems [SiS]
physical id: 4
bus info: pci@0000:00:04.0
logical name: eth0
version: 90
serial: 00:14:85:14:9f:fc
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sis900 driverversion=v1.08.10 Apr. 2 2006 ip=192.168.1.44 latency=64 maxlatency=11 mingnt=52 module=sis900 multicast=yes
*-network:1
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: c
bus info: pci@0000:00:0c.0
logical name: wifi0
version: 01
serial: 00:18:e7:2e:60:50
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g
devo@devo-desktop:~$ sudo iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wifi0 Interface doesn't support scanning.
ath0 Scan completed :
Cell 01 - Address: 00:E0:98:CC:54:D7
ESSID:"ThrasherNet"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=17/70 Signal level=-78 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Cell 02 - Address: 00:09:5B:ED:5D:B2
ESSID:"NETGEAR"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=6/70 Signal level=-89 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:ath_ie=dd0900037f01010006ff7f
Cell 03 - Address: 00:18:39:3F:17:5F
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=19/70 Signal level=-76 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Cell 04 - Address: 00:12:0E:40:DC:B6
ESSID:"06B408648877"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=158/70 Signal level=-193 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
devo@devo-desktop:~$ sudo dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:18:e7:2e:60:50
Sending on LPF/ath0/00:18:e7:2e:60:50
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Your using the madwifi drivers. According to the madwifi specs it creates a virtual interface for each device. The device is wifi0, the virtual interface is ath0. All command line is directed toward the virtual interface, not the physical device itself. You need to probably specifiy a specific essid on the command line before the dhclient command. All though you mentioned the error with wifi0, where is the output that showed this error?
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
where would I put the essid in the command? wifi0 error listed below.
devo@devo-desktop:~$ sudo dhclient ath0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:18:e7:2e:60:50
Sending on LPF/ath0/00:18:e7:2e:60:50
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Look at the original post (first page). It will tell you where to put the essid. If that error persists, it could be a problem.
Post
lshw -C network
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
I just ran trough the entire exercise again. Output below. I'm sure it has something to do with the unknown hardware 801 error after sudo dhclient -r ath1, but I don't know what to do about it. Is there a way I can start from scratch? maybe something wonky in a configuration file?
devo@devo-desktop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Ethernet interface
product: SiS900 PCI Fast Ethernet
vendor: Silicon Integrated Systems [SiS]
physical id: 4
bus info: pci@0000:00:04.0
logical name: eth0
version: 90
serial: 00:14:85:14:9f:fc
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sis900 driverversion=v1.08.10 Apr. 2 2006 ip=192.168.1.44 latency=64 maxlatency=11 mingnt=52 module=sis900 multicast=yes
*-network:1
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: c
bus info: pci@0000:00:0c.0
logical name: wifi0
version: 01
serial: 00:18:e7:2e:60:50
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g
devo@devo-desktop:~$ iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wifi0 Interface doesn't support scanning.
ath1 Scan completed :
Cell 01 - Address: 00:E0:98:CC:54:D7
ESSID:"ThrasherNet"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=13/70 Signal level=-82 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Cell 02 - Address: 00:09:5B:ED:5D:B2
ESSID:"NETGEAR"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=209/70 Signal level=-142 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:ath_ie=dd0900037f01010006ff7f
Cell 03 - Address: 00:18:39:3F:17:5F
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=0/70 Signal level=-95 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
devo@devo-desktop:~$ sudo ifconfig eth0 down
devo@devo-desktop:~$ sudo ifconfig ath1 down
devo@devo-desktop:~$ sudo dhclient -r ath1
There is already a pid file /var/run/dhclient.pid with pid 7271
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath1/00:18:e7:2e:60:50
Sending on LPF/ath1/00:18:e7:2e:60:50
Sending on Socket/fallback
devo@devo-desktop:~$ sudo ifconfig ath1 up
devo@devo-desktop:~$ sudo iwconfig ath1 essid "ThrasherNet"
devo@devo-desktop:~$ sudo iwconfig ath1 key 526d2c6b426a42646f3f382058
devo@devo-desktop:~$ sudo iwconfig ath1 mode managed
devo@devo-desktop:~$ sudo dhclient ath1
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath1/00:18:e7:2e:60:50
Sending on LPF/ath1/00:18:e7:2e:60:50
Sending on Socket/fallback
DHCPDISCOVER on ath1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath1 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Check your system logs (there is a reference in the reference section in the original post) to see if you find anything
dmesg | more
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Well, there is this:
[ 39.235637] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 39.319034] ath_hal: module license 'Proprietary' taints kernel.
[ 39.319859] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[ 39.547523] wlan: 0.8.4.2 (0.9.3.2)
[ 39.567685] ath_pci: 0.9.4.5 (0.9.3.2)
[ 39.567748] ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 21
[ 40.236346] ath_rate_sample: 1.2 (0.9.3.2)
[ 40.236900] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[ 40.236906] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[ 40.236916] wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[ 40.236923] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
[ 40.236927] wifi0: mac 7.9 phy 4.5 radio 5.6
[ 40.236933] wifi0: Use hw queue 1 for WME_AC_BE traffic
[ 40.236935] wifi0: Use hw queue 0 for WME_AC_BK traffic
[ 40.236937] wifi0: Use hw queue 2 for WME_AC_VI traffic
[ 40.236939] wifi0: Use hw queue 3 for WME_AC_VO traffic
[ 40.236941] wifi0: Use hw queue 8 for CAB traffic
[ 40.236943] wifi0: Use hw queue 9 for beacons
[ 40.306535] wifi0: Atheros 5212: mem=0xe8000000, irq=21
Then a lot of stuff like this:
[ 1683.492931] Unknown OutputIN= OUT=ath1 SRC=169.254.5.129 DST=192.168.1.1 LEN=80 TOS=0x00 PREC=0x00 TTL=64 ID=13146 DF PROTO=UDP SPT=32780 DPT=53
LEN=60
[ 1689.336286] Unknown OutputIN= OUT=ath1 SRC=192.168.1.44 DST=205.188.9.53 LEN=112 TOS=0x00 PREC=0x00 TTL=64 ID=9813 DF PROTO=TCP SPT=56667 DPT=519
0 WINDOW=29957 RES=0x00 ACK PSH URGP=0
[ 1712.238621] eth0: Media Link On 100mbps full-duplex
[ 1719.782730] eth0: no IPv6 routers present
[ 1820.302925] Inbound IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:12:f0:a3:29:4a:08:00 SRC=192.168.1.47 DST=192.168.1.255 LEN=237 TOS=0x00 PREC=0x00 TTL=
128 ID=541 PROTO=UDP SPT=138 DPT=138 LEN=217
[ 1826.247646] ath1: no IPv6 routers present
[ 2085.655551] ath1: no IPv6 routers present
[ 2225.572919] Unknown OutputIN= OUT=ath1 SRC=192.168.1.44 DST=207.46.106.20 LEN=70 TOS=0x00 PREC=0x00 TTL=64 ID=41815 DF PROTO=TCP SPT=32997 DPT=18
63 WINDOW=13936 RES=0x00 ACK PSH URGP=0
[ 2231.415242] Unknown OutputIN= OUT=ath1 SRC=169.254.5.129 DST=192.168.1.1 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=19331 DF PROTO=UDP SPT=32780 DPT=53
LEN=43
Any of that say anything to you?
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Are you running wired and wireless at the same time??
Can you post
ifconfig
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
devo@devo-desktop:~$ ifconfig
ath1 Link encap:Ethernet HWaddr 00:18:E7:2E:60:50
inet6 addr: fe80::218:e7ff:fe2e:6050/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr 00:14:85:14:9F:FC
inet addr:192.168.1.44 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::214:85ff:fe14:9ffc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22085 errors:0 dropped:0 overruns:0 frame:0
TX packets:21338 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14910385 (14.2 MB) TX bytes:3101423 (2.9 MB)
Interrupt:20 Base address:0xc800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:66 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5176 (5.0 KB) TX bytes:5176 (5.0 KB)
wifi0 Link encap:UNSPEC HWaddr 00-18-E7-2E-60-50-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:65942 errors:0 dropped:0 overruns:0 frame:62139
TX packets:3557 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:5605636 (5.3 MB) TX bytes:180947 (176.7 KB)
Interrupt:21
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Did you bring the wired interface down prior to trying to bring up the wireless interface?
sudo ifconfig eth0 down
sudo ifconfig ath1 up
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
This is a great guide. Very nice work. I'll definitely be using this later to figure out a few issues of my own.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Kevdog. Thank you. This was so much easier than trying to find the right gui that worked. The last time I installed a *buntu on my laptop I struggled for a couple days trying to figure out why I couldn't connect to wireless networks and it ended up being a gui problem. Nice guide.=D>
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
If you can do it from the command line, you dont ever have to worry what happens if suddenly network manager acts up (which it does), or if you take your laptop elsewhere and it cant connect through the GUI -- but it did at home. Again, the command line gives you the basic knowledge to get a connection when other methods are failing -- its a very reliable if not the ultimate fallback!!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
I have no issues with establishing/maintaining connection on unprotected networks (like at school), but WEP just isn't working. The last step yields the following message, "No DHCPOFFERS received. No working leases in persistent database - sleeping."
Now I know the network is up because I can scan for it and see it with the pre installed gui. Any idea what's going on?
Thanks,
Griff
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
64 or 128 bit wep?? Are you using hexidecimal or ascii? If hexidecimal did you set the key index correctly?? (man iwconfig gives examples how to do this)
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
It's 128 hex and I believe I did it correctly. I'll double check.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
kevdog
If hexidecimal did you set the key index correctly??
I'm not sure what you mean by index, but according to the man page all I should need to do is:
Code:
sudo iwconfig eth0 key 11111111111111111111111111
right?
edit: I saw the entry about index but from what it says I don't think it applies to me
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
yes thats the right formati, you need to make sure then that key is 25 (24??) characters is in length and that its key index 1 on the router.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
I went through the steps, but I'm still unable to pull an IP. Any help would be appreciated.
Here's what I end up getting:
Quote:
$ sudo dhclient eth1
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit
http://www.isc.org/sw/dhcp/
Listening on LPF/eth1/00:12:17:9d:8a:ee
Sending on LPF/eth1/00:12:17:9d:8a:ee
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
All right, it was key 1 on the router and I enforced the key to index [1] on my card, but the outcome is the same as before.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
Griff
All right, it was key 1 on the router and I enforced the key to index [1] on my card, but the outcome is the same as before.
looks like we're in the same boat right now, Griff.
did you bring your ether connection down before you tried enabling your wifi connection?
Just a thought, perhaps that could be holding you back, as I read it in a previous page.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Now, does it matter if the ESSID contains spaces? Does it matter if the WPA is a passphrase? (both within the quotation marks tho)
Now, this is what I'm (also) getting
Listening on LPF/eth1/00:19:7e:b3:2c:89
Sending on LPF/eth1/00:19:7e:b3:2c:89
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
using ndiswrapper-1.47 installed on a clean gusty as detailed in
http://ubuntuforums.org/showthread.p...hlight=bcm43xx
network name was found after this installation but i never got connected to it. also switching back to wired connection never works immediately, it might just take some time but usually i switch it on and off a couple of times from Administration/Network before anything happens
now did I use this command correctly?
sudo wpa_supplicant -w -Dwext -ieth1 -c/etc/wpa_supplicant.conf
it does not result in anything, I had to terminate
And here's some more info
*-network DISABLED
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:0b:00.0
logical name: eth1
version: 01
serial: 00:19:7e:b3:2c:89
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.47+Broadcom,10/12/2006, 4.100. latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11g
Thanks, this is wrecking my head, being a beginner doesn't help!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Here is your problem:
*-network DISABLED
So if you have a wired connection, bring down the wired interface, and then bring up the wireless interface:
sudo ifconfig eth0 down
sudo ifconfig eth1 up
Recheck lshw -C network to confirm you do not have a disabled statement.
No spaces in essid --- spaces = BIG PROBLEMS!
Try an unencrypted connection before using wpa.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
kevdog
Here is your problem:
*-network DISABLED
So if you have a wired connection, bring down the wired interface, and then bring up the wireless interface:
sudo ifconfig eth0 down
sudo ifconfig eth1 up
Recheck lshw -C network to confirm you do not have a disabled statement.
No spaces in essid --- spaces = BIG PROBLEMS!
Try an unencrypted connection before using wpa.
ah yeah well that was only disabled when I copied that report, thats not the problem here
but apparently "get your own broadband, ****!"-essid has to be changed, bah. been having problems logging into the router and its a common one to our house so just wanted to try and get it working without service disrupts but thats an another story altogether and will have to have a look at it now then...
thanks!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
I'm having the *exact* same problem as d_thrasher, right down to the outputs above, error messages and logical names, and yes I've checked that my wired is down and there's no NETWORK DISABLED on my ath0/wifi0 device.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Ubuntiac
Can you post the results of lshw -C network and iwlist scan?
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Quote:
Originally Posted by
kevdog
Can you post the results of lshw -C network and iwlist scan?
lshw -C network:
Code:
*-network DISABLED
description: Ethernet interface
product: 82566DC Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 02
serial: 00:19:d1:88:59:b4
capacity: 1GB/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.20-k2-NAPI firmware=1.1-0 latency=0 link=no module=e1000 multicast=yes port=twisted pair
*-network
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: 0
bus info: pci@0000:07:00.0
logical name: wifi0
version: 01
serial: 00:18:e7:27:12:5f
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.4.5 (0.9.3.2) latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g
iwlist scan:
Code:
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wifi0 Interface doesn't support scanning.
and just for good measure, lspci:
Code:
00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82P965/G965 PCI Express Root Port (rev 02)
00:03.0 Communication controller: Intel Corporation 82P965/G965 HECI Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801H (ICH8 Family) 2 port SATA IDE Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600 GT (rev a1)
03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6101 single-port PATA133 interface (rev b1)
07:00.0 Ethernet controller: Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
07:01.0 RAID bus controller: Silicon Image, Inc. PCI0680 Ultra ATA-133 Host Controller (rev 02)
07:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
Strange thing is that it seemed to work fine before the recent network-manager update, and now it still seems to work *sometimes*. If I don't use it for a few hours though it just seems to drop out and not even a computer restart gets it back. Oh, and for the record, my Atheros card usually supports scanning, just fine!
Thanks in advance for any ideas!
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
You are using the madwifi drivers which usually are very reliable. B/c of the way madwifi works, it creates virutal interfaces (usually ath0) for your physical card located at wifi0.
I used to have a problem with my broadcom card doing something similar to what you describe. Short of rebooting, the only thing I found would work was to create a script that would bring down the interface, unload the driver module, reload the driver module, and then bring up the interface. Although definitely not an ideal solution it would at least save me a reboot.
Since you state that sometimes your atheros card work, see if it scan (iwlist scan) using ath0. I dont think wif0 is truly the interface to work through.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
Thanks for this process - wirless now works if I type in these commands.
Now - sorry for a total noob question (I am one - a noob that is)
How do I set things up so I don't have to type the command sequence everytime I start my PC? I assume I can put them into some sort of script file and have it auto run at start up? What if I want to make it flexible for different networks?
Or is there anything I can do to make the GUI work (It detects the SSID from the wirless, but repeatedly asks me to put in the WEP Key, and gets no further, although it did work once.)
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
I know in Kubuntu (or any KDE distro) you just put the script in a text file in ~/.kde/autostart, make sure the file name ends in .sh, rick click on it and check "executable" under the permissions tab. I'm sure there's something similar in gnome.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
If the manual commands are working for you on the command line, then Im not sure why network manager is not working.
A couple of things
WICD is an alternative to network manager. You might try this. I know that at its heart it works similar to the command line, but is very fancy and provides a GUI, tray icon, etc.
You can always write a script file that you either launch manually or when you log in. You could get really fancy with the script file, or keep it rather basic. Seems in my situation the more I jazz up the script file, I decrease the chances it will actually work. Usually I just scan for available networks with iwlist scan, and then wrote a script and call it with:
network_connect NETWORK_NAME
NETWORK_NAME in the script is variable $1, so everything pretty much connects. Simple but it works.
-
Re: How To: Troubleshoot your Wireless Network Connection - Connecting at Command Li
"wicd" gave me a headache last week. the install unloaded NetworkManager then failed to complete. I couldn't successfully reload NM after that, so I was forced to upgrade from Feisty to Gutsy before I planned.