Re: Wireless on an Acer Aspire 3610
Juanjavier Martínez wrote:
Downloaded and installed windows driver for ACER Aspire 3610
So far I successfully installed and got running ndiswrapper, acer_acpi
and played "enabled : 1" > /proc/acpi/acer/wireless"
So driver and wireless are now working flawless...see [0]
Then I type `iwlist wlan0 scan' and get
wlan0 Scan completed :
Cell 01 - Address: 00:14:F8:51:11:40
>>ESSID:"ASUNCION"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:0/100 Signal level:-80 dBm Noise level:-256
dBm
Encryption key:off
Bit Rate:1 Mb/s
(...)
Bit Rate:48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:0A:73:FD:90:12
>>ESSID:"WebSTAR"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:0/100 Signal level:-85 dBm Noise level:-256
dBm
Encryption key:on
Bit Rate:1 Mb/s
(...)
Bit Rate:54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202
Cell 03 - Address: 00:30:BD:FD:AF:B0
>>ESSID:"ANCE"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:0/100 Signal level:-87 dBm Noise level:-256
dBm
Encryption key:on
Bit Rate:1 Mb/s
(...)
Bit Rate:48 Mb/s
Extra:bcn_int=100
Extra:atim=0
So I assume we've got three wireless networks available here: ASUNCION,
WebSTAR and ANCE.
How could I connect to one of them...? Or at least to the first one, which
is the only one that has got the `Encryption Key: off'. Chances are that
with Encryption Key: on
things become harder....but I am not sure of this...as I am still a
Debian Wireless newbie....
Are you entitled to access the "ASUNCION" network, or is that just a
random access point which you detect in your neighborhood? Even though
no encryption key is used, the access point could still reject all
connections by unauthorized users, for example based on the MAC address
(a unique hardware identifier) of their wireless network card. Make sure
that the access point is set up to accept connections from your laptop.
*Checked out* `man iwlist' and `man iwconfig', which are not very
specific about logging onto a remote network.
*Checked out* [1] as well, but it assumes you have got a wireless
router, which is not my case.
Besides, no matter I type `iwconfig wlan0 essid <mynetworkname>' I get
upon doing `iwconfig wlan0': IEEE 802.11g ESSID:off/any.
"iwconfig wlan0" should show "associated" and the hardware address of
the access point. If it does not then the signal might simply be too
weak. "iwlist scan" will also include access points which are of no
practical use since the link quality is too low. I have no experience
with your hardware, but I would be worried about the "Quality: 0/100"
reading.
I know I am probably only a step to get it...but still need some help,
maybe pointing good
documentation relating to it....
In short: I am unable to get an IP address:
dhclient wlan0
Listening on LPF/wlan0/00.14:a4:25:bd:3b
Sending on LPF/wlan0/00.14:a4:25:bd:3b
Sending on Socket/fallback/fallback-net
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database.
You are doing the right thing. The manual of "iwconfig" does not say
much about logging on because it should not be any big deal if the link
is good enough and the access point accepts you. In fact the card should
automatically associate with the nearest access point if its signal is
strong enough. You only need to specify the ESSID if more than one good
access point is detected and you do not like the one that your wireless
driver has picked out. Afterwards "dhclient wlan0" should indeed be
enough unless the access point's dhcp server regards you as an
unauthorized "intruder".
Regards,
Florian
Reply to: