Stan Hoeppner wrote:
Wayne <linuxtwo@gmail.com> put forth on 1/1/2010 8:56 AM: http://www.intergate.com/~huntbrittany/linux/WICD.info.gz If that data is accurate... 1. Your wired ethernet card is using 192.168.1.11 2. Your Atheros card is being assigned 192.168.1.3
The wired NIC is first in the binding order and thus first in the routing table. Your packets for the local subnet will never go out the Atheros card, but the wired NIC. Have you done any testing by hard disabling all network devices in the system except the Atheros card?
Just tried that and can't get a positive response out of dhclient. No offers. Remember though I am not using wicd right now. I am trying to do without the managers. This way I I don't get any system freeze up's and sadly no dhcp offers either.
That iwconfig was 'after' I removed wicd from the system. Guess that I should not have included that as it was not related to the other data. You were right, I am giving you a moving target to troubleshoot and that ain't good.http://www.intergate.com/~huntbrittany/linux/WICD.info.gz shows 4 network devices, 3 of which are actively sending/receiving packets, one of which is on the same subnet as the wireless device you can't seem to get working. Additionally the Atheros shows 0/70 link quality and a S/N of 1:1. It can't be connected to the AP with those numbers--they can't be any worse. The driver shows no association, and that makes sense looking at those RF numbers. Curiously, given the transceiver can't discern anything from the AP RF signals, you still managed to get a dhcp ack with an assignment of 192.1681.3. How is that possible when you don't even have a radio link to the AP?
Is all of the data shown in WICD.info.gz from the same point in time?
Yes All except the last reference to iwconfig.OK, I will go back to the wicd setup and then put ALL of the data you requested from 'that' setup into a new WICD file. I will then STAY at that setup for at least a day or two.
Sorry for the bother. Wayne