Opened 8 years ago

Closed 8 years ago

Last modified 6 years ago

#8138 closed bug (invalid)

Intel pro wireless not connecting to wpa-psk wireless network

Reported by: lalit Owned by: axeld
Priority: normal Milestone: R1
Component: Network & Internet/Wireless Version: R1/alpha3
Keywords: 2200BG Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

My laptop with wireless card Intel pro wireless 2200BG not connecting to wpa-psk wireless network. I tried with "ifconfig /dev/net/iprowifi2200/0 join SSID mypassword" and also with the "wireless_networks" file located in /boot/common/settings/network/, but the card gets the wrong IP addresses (my router is in DHCP mode). Find the attached screen shots.

Attachments (4)

sky setting.PNG (40.6 KB) - added by lalit 8 years ago.
Settings on my router
wifi.png (91.2 KB) - added by lalit 8 years ago.
It's detecting the networks.
error.png (80.9 KB) - added by lalit 8 years ago.
Getting the error when trying to connect from list.
syslog (485.5 KB) - added by lalit 7 years ago.
syslog

Download all attachments as: .zip

Change History (16)

Changed 8 years ago by lalit

Attachment: sky setting.PNG added

Settings on my router

Changed 8 years ago by lalit

Attachment: wifi.png added

It's detecting the networks.

Changed 8 years ago by lalit

Attachment: error.png added

Getting the error when trying to connect from list.

comment:1 in reply to:  description Changed 8 years ago by mmlr

That looks like you simply didn't install the wpa_supplicant optional package. In that case access to the network is denied, hence the "operation not allowed" error message. Granted it could be made more obvious, but the need for it will go away as soon as the supplicant is included in the default image (which I might simply do in the state it is now, as it is usable).

comment:2 Changed 8 years ago by Disreali

This sounds very similar to ticket:7081

comment:3 Changed 8 years ago by lalit

I did installed the optional package using the command "~> installoptionalpackage wpa_supplicant". I tried to connect to wep setting, it accepted the passoword but not connected. It is a dhcp setup and it is picking up the wrong ipaddress. Not asking for password while connecting through menu.

The following is my optional package list:

~> installoptionalpackage -l

Optional Packages that have been installed: APR APR-util BeBook BePDF Bzip CCache CDRecord CVS Curl Development DevelopmentBase DevelopmentMin Expat Fastdep Git ICU LibIconv LibXML2 MandatoryPackages Mercurial Nano Neon OpenSSH OpenSSL P7zip PCRE Paladin Pe Perl Python SQLite Sed Subversion Tar TimGMSoundFont TrackerNewTemplates Vision WQY-MicroHei WebPositive Welcome WonderBrush XZ-Utils Yasm

Installable Optional Packages: abi-compliance-checker armyknife bazaar beae beam behappy beoscompatibility bezillabrowser burnitnow clockwerk clucene cmake developmentjava doxygen friss gettext gperf groff keymapswitcher libevent liblayout libmng libxslt links lua man netsurf ocaml opensound rsync ruby taglib transmission vim allegrolibs box2d fribidi lcms libart_lgpl libmad libmikmod libmodplug libpaper physfs sdllibs xiphlibs

comment:4 Changed 8 years ago by diver

Alpha3 didn't have wpa_supplicant as optional package. You need to install recent nightly to have it, or obtain wpa_supplicant package built for A3.

comment:5 in reply to:  4 Changed 8 years ago by anevilyak

Resolution: invalid
Status: newclosed

Replying to diver:

Alpha3 didn't have wpa_supplicant as optional package. You need to install recent nightly to have it, or obtain wpa_supplicant package built for A3.

Was about to say the same. I don't think wpa_supplicant will work on A3 either way since getting it working involved fixing some lower level bugs in the kernel and/or network stack. Closing as invalid.

comment:6 Changed 7 years ago by lalit

This is still a problem in recent nightly build. It is accepting password. But assigning wrong ip addresses.

comment:7 Changed 7 years ago by diver

Please attach your syslog and ifconfig output.

Changed 7 years ago by lalit

Attachment: syslog added

syslog

comment:8 Changed 7 years ago by lalit

Here is the ifconfig:

~> ifconfig
loop    Hardware type: Local Loopback, Address: none
        inet addr: 127.0.0.1, Mask: 255.0.0.0
        inet6 addr: ::1, Prefix Length: 128
        MTU: 16384, Metric: 0, up loopback link
        Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Collisions: 0

/dev/net/3com/0
        Hardware type: Ethernet, Address: 00:0b:db:02:56:7c
        inet addr: 192.168.0.4, Bcast: 192.168.0.255, Mask: 255.255.255.0
        inet6 addr: fe80::20b:dbff:fe02:567c, Bcast: ffff:ffff:ffff:ffff::, Prefix Length: 64
        MTU: 1500, Metric: 0, up broadcast auto-configured
        Receive: 8 packets, 0 errors, 1504 bytes, 0 mcasts, 0 dropped
        Transmit: 7 packets, 0 errors, 1410 bytes, 0 mcasts, 0 dropped
        Collisions: 0

/dev/net/iprowifi2200/0
        Hardware type: Ethernet, Address: 00:12:f0:92:f2:e3
        inet addr: 169.254.0.97, Bcast: 169.254.255.255, Mask: 255.255.0.0
        inet6 addr: fe80::212:f0ff:fe92:f2e3, Bcast: ffff:ffff:ffff:ffff::, Prefix Length: 64
        MTU: 1500, Metric: 0, up broadcast auto-configured
        Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Transmit: 2 packets, 7 errors, 594 bytes, 0 mcasts, 0 dropped
        Collisions: 0
Last edited 7 years ago by diver (previous) (diff)

comment:9 Changed 7 years ago by diver

Does it work if you assign ip address manually?

comment:10 Changed 7 years ago by lalit

No it doesn't work. I tried using static ip, it is not changing the ip addresses.

comment:11 Changed 7 years ago by diver

You can try to restart net_server in Terminal so that you can see some additional debug output:

hey net_server quit
/system/servers/net_server

Then try to connect to your network and set static ip (using ifconfig maybe?)

comment:12 Changed 6 years ago by diver

Is this still an issue?

Note: See TracTickets for help on using tickets.