Re: Wireless Woes U7.04 and D-Lnk WDA-1320
David Vincent <dvincent <at> sleepdeprived.ca>
2007-07-01 05:03:25 GMT
Pete Holsberg wrote:
Pete Holsberg keyed the following on 6/30/2007 4:41 PM:
I bought a new PCI wireless card for it's Atheros chipset and
reinstalled Ubuntu 7.04,
Got a message about restricted drivers; it recognized my adapter! 
Tried to configure the adapter with the Network Tools/Manager and
while I was able to select one of the ESSIDs it saw and add the WEP
password, I was unable to use any network tools (ping, traceroute,
etc.)
When I tried iwconfig, ath0 had no ESSID or nickname and when I tried
to give it one, the connand failed!!
What is going on here???
<blush> Forgot to use sudo!
OK, now it has a nickname, an ESSID and an AP, but IU still cannot ping,
etc.!!
I've got the same problem, using Network Manager I cannot connect to
WEP networks. The solution is to go into the network properties, and
deselect "Roaming Mode" on the wireless adapter. Then you can type in
the network name, WEP key, and tell it to use DHCP etc. A reboot
should have you back up properly. (On some machines this works right
away but on others Network Manger just won't let go of the card...)
If anyone can give us a better solution involving installing some
packages or tweaking another file that would be great! :)
I find Network Manager great for WPA networks and open networks as well
as VPNs, but I hate having to unlock the keyring after a reboot etc.
for my network to connect so I went to using a static config in my
/etc/network/interfaces. This unfortunately breaks the best feature of
Network Manager - the intelligence to use a wired connection when one
is plugged in and switch to wireless when unplugged or told to do so.
Anyone know of a fix for that?
-d
<div>
Pete Holsberg wrote:
<blockquote cite="mid4686C6F0.1070306 <at> pobox.com" type="cite">
Pete Holsberg keyed the following on 6/30/2007 4:41 PM:
<blockquote type="cite">
I bought a new PCI wireless card for it's Atheros chipset and
reinstalled Ubuntu 7.04,
Got a message about restricted drivers; it recognized my adapter!
Tried to configure the adapter with the Network Tools/Manager and
while I was able to select one of the ESSIDs it saw and add the WEP
password, I was unable to use any network tools (ping, traceroute,
etc.)
When I tried iwconfig, ath0 had no ESSID or nickname and when I tried
to give it one, the connand failed!!
What is going on here???
</blockquote>
<blush> Forgot to use sudo!
OK, now it has a nickname, an ESSID and an AP, but IU still cannot ping,
etc.!!
</blockquote>
<br>
I've got the same problem, using Network Manager I cannot connect to
WEP networks. The solution is to go into the network properties, and
deselect "Roaming Mode" on the wireless adapter. Then you can type in
the network name, WEP key, and tell it to use DHCP etc. A reboot
should have you back up properly. (On some machines this works right
away but on others Network Manger just won't let go of the card...)<br><br>
If anyone can give us a better solution involving installing some
packages or tweaking another file that would be great! :)<br><br>
I find Network Manager great for WPA networks and open networks as well
as VPNs, but I hate having to unlock the keyring after a reboot etc.
for my network to connect so I went to using a static config in my
/etc/network/interfaces. This unfortunately breaks the best feature of
Network Manager - the intelligence to use a wired connection when one
is plugged in and switch to wireless when unplugged or told to do so.<br><br>
Anyone know of a fix for that?<br><br>
-d<br>
</div>
RSS Feed