search

jeanstien / grimwepa

Automatically exported from code.google.com/p/grimwepa
0 stars 1 forks source link

Signon once key is found #18

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Clicked keytank
2. Selected Access Point
3. Click Sign on
4. Selected interface (wlan0 in my case )

What is the expected output? What do you see instead?
Connect to the selected ap with key that is found

See attached screen shot > unable to connect; out of range / invalid password?

What version of the product are you using? On what operating system?
BT4 LiveDVD 4 Final

alpha 6

Please provide any additional information below.

I noticed that is hasn't worked since it was implemented

Original issue reported on code.google.com by ondro...@gmail.com on 10 Jun 2010 at 12:00

Attachments:

GoogleCodeExporter commented 9 years ago 
Ondrovic,

Thanks for the bug report. I haven't had much feedback on this.

On my Backtrack4 install, I have networking start when the computer starts. I 
had a feeling that people using BT4 who don't start networking might have 
issues with the signon feature.

Question: is networking enabled? I could have grimwepa run this command before 
attempting to connect:
/etc/init.d/networking start

Could you try running this command, and THEN trying the grimwepa signon?
If that doesn't solve the issue, then I'm not sure what will.

Thanks again for testing, and for the bug report!!

Original comment by der...@gmail.com on 10 Jun 2010 at 2:36

GoogleCodeExporter commented 9 years ago 
yes I had to enable it in order to download grimwepa for the live dvd I will 
play around with it some more tomorrow and give you a shout after.

I will try issuing the command instead of using the services start networking 
and see what happens

Original comment by ondro...@gmail.com on 10 Jun 2010 at 2:43

GoogleCodeExporter commented 9 years ago 
no dice on the /etc/init.d/networking start here is the output screen shot of 
the sign on

Here is the results of the /etc/init.d/networking start

[code]
root@bt:~# /etc/init.d/networking start
Configuring network interfaces...Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:0c:29:5a:cf:e2
Sending on   LPF/eth0/00:0c:29:5a:cf:e2
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 172.16.74.128 from 172.16.74.254
DHCPREQUEST of 172.16.74.128 on eth0 to 255.255.255.255 port 67
DHCPACK of 172.16.74.128 from 172.16.74.254
bound to 172.16.74.128 -- renewal in 868 seconds.
if-up.d/mountnfs[eth0]: waiting for interface eth1 before doing NFS mounts
if-up.d/mountnfs[eth0]: waiting for interface eth2 before doing NFS mounts
if-up.d/mountnfs[eth0]: waiting for interface ath0 before doing NFS mounts
if-up.d/mountnfs[eth0]: waiting for interface wlan0 before doing NFS mounts
eth1: ERROR while getting interface flags: No such device
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth1.
eth2: ERROR while getting interface flags: No such device
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
ath0: ERROR while getting interface flags: No such device
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:d1:49:98:30
Sending on   LPF/wlan0/00:14:d1:49:98:30
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
if-up.d/mountnfs[wlan0]: waiting for interface eth1 before doing NFS mounts
if-up.d/mountnfs[wlan0]: waiting for interface eth2 before doing NFS mounts
if-up.d/mountnfs[wlan0]: waiting for interface ath0 before doing NFS mounts
done.
[/code]

Original comment by ondro...@gmail.com on 10 Jun 2010 at 3:40

Attachments:

GoogleCodeExporter commented 9 years ago 
I can confirm this same issue in my case.

Thanks

Original comment by Vgr....@gmail.com on 12 Jun 2010 at 6:24