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