Author Topic: Network manager issues...  (Read 4544 times)

geo

  • Newbie
  • *
  • Posts: 2
    • View Profile
on: November 17, 2012, 12:16:50 PM
Hello everyone!

I am running backbox 3 on a hp pavilion laptop with 2 gigs of ram and a x64 processor.

I am having issues with network manager connecting me very slow, asking for re-authentication of the password multiple times and resetting my spoofed mac. I understand the mac is because they want me to enter a spoofed mac in network manager however this keeps it from logging on the network completely. I would switch to Wicd but that one drops me constantly and is a headache as well.

Does anyone know if when doing it through shell I will need to specify anything for the encryption on the password? I did some browsing and found a few ways of doing it through shell. My laptop is at my friends house at the moment but I wanted to make sure I was on the right track before I go over and commence to disappoint upon execution.

Here is what I have gathered online:

(Logged in as root so no sudo for me)

iwlist wlan0 s

iwconfig wlan0 essid (my access point) key (password)  (will i need to specify hex for wep and regular password for wpa some way in this line?)

dhclient (says this is to get the static ip, doesnt display it as a console command however so will google)

So yeah if anyone can shed light on how to consistently connect to my AP through shell given I have the password key regardless of encryption that would be of help. Also if anyone has had a similar issue with network manager and knows a possible workaround to stabilize it.

Thank you for any help!





r083rt

  • Guest
Reply #1 on: November 17, 2012, 02:28:56 PM
ok well let me break this bad boy down  ;D

first off we need to have your wifi card model if you look at your first paragraph

I am having issues with network manager connecting me very slow, asking for re-authentication of the password multiple times and resetting my spoofed mac. I understand the mac is because they want me to enter a spoofed mac in network manager however this keeps it from logging on the network completely. I would switch to Wicd but that one drops me constantly and is a headache as well.

what does this says  about your card  ? also if you have both wicd install and network manager are both running at startup your card will not connect properly
regardless if your card has the right drivers etc etc


question why the shell  do you use the shell to connection to lan as well ?? don't get me wrong all aircrack is done in shell and connection but for a standard just connect hmm Im curious !! .. what are you doing or trying to achieve is it that you are just trying to do it by shell because network manger is not working for you ??

1 ) get your card model and check if the drivers come standard with linux wireless drivers or do you need to get them and compile them
1 ) can you connect to any access point with network manager # or is it just keep dropping i.e asking for re-auth { forget shell for the time being }
2 ) what is the status of rfkill ## things like this are just checks Not because this is what the problem is
3 ) iwconfig power  .. ## depending on your card power saving mode can cause problems with connection
4 ) signal strength
5 ) this AP is it yours, a company, etc etc

connection to wifi through shell you can do it off the cuff or if you can you can create a mywireless.sh and put your info and if you wanted create a start up script put the info into it and do update-rc.d wifi defaults


scanning AP
Code: [Select]
iwlist wlan0 scan | grep -e 'ESSID' -e 'Channel:' | sed 'N;s/\n/\t/'
you can use tr and some awk to clean it up if you want a bit more organized i.e strengh ,encryption on/off etc etc

connecting
Code: [Select]
iwconfig wlan0 essid {Network} key {Pasword}
dhclient wlan0

iwconfig will use hex as default if you want to use ASCII put 's:' before your the password

setup a static ip with dhcient.conf

Quote
So yeah if anyone can shed light on how to consistently connect to my AP through shell given I have the password key regardless of encryption that would be of help. Also if anyone has had a similar issue with network manager and knows a possible workaround to stabilize it.


again your card needs to be 100% compatible ,drivers,firmware etc etc ... and then back to the creating the script ..
« Last Edit: November 17, 2012, 05:35:37 PM by r083rt »



weVeg

  • Hero Member
  • *****
  • Posts: 737
    • View Profile
Reply #2 on: November 17, 2012, 02:36:32 PM
You are a little confused, if you have wep encryption iwconfig is enough, otherwise with wpa you need play with wpa_supplicant, dhclient doesn't give you a static but dynamic address, for static you need to use ifconfig IP netmask YOURNETMASK, the better way is to edit /etc/network/interfaces . You have also to configure the route with something like: route add default gw IPGATEWAY and edit  /etc/resolv.conf for DNS.
I can't understand why you spoof your MAC if you are inside your own network, btw macchanger is the way!
If you install wicd, you have to remove network-manager from the rc.

edit: I didn't see robert reply, follow his instruction, he know what he do!
« Last Edit: November 17, 2012, 02:42:52 PM by weVeg »

una voce libera è sempre liberatrice
under_r00t


r083rt

  • Guest
Reply #3 on: November 17, 2012, 02:50:43 PM
some great points weVeg ..

I got a little confused of what he is doing and what is trying to achieve

Quote
If you install wicd, you have to remove network-manager from the rc.

I seen that but though surely he doesn't have both installed and if wicd is running in the background while your running network-manger
that is a recipe for disaster

USE either one or the other NOT both I would recommend Network-Manager

you can have two installed but only one running but the question is have two there is no need for it

but again even having two and only one running it may still cause a problem
« Last Edit: November 17, 2012, 03:08:17 PM by r083rt »



weVeg

  • Hero Member
  • *****
  • Posts: 737
    • View Profile
Reply #4 on: November 17, 2012, 02:58:39 PM
either just one or the other NOT both use I would recommend Network-Manager

Last time I've installed wicd, it doesn't remove network-manager and after a few day of "non sense" address and panic networking I've seen that N-M still running in background. So, choose one and only one, as brobert ;) suggest you!

una voce libera è sempre liberatrice
under_r00t


r083rt

  • Guest
Reply #5 on: November 17, 2012, 03:06:20 PM
100% correct Ive seen some people  SAY just install either network-manger or wicd and the one you install will remove the other this is completely  Wrong

Even after removing wicd or network-manager always check there is no startup files still operational  :)
« Last Edit: November 17, 2012, 03:08:57 PM by r083rt »



pwnd2pwnr

  • Newbie
  • *
  • Posts: 5
    • View Profile
Reply #6 on: December 18, 2012, 03:21:44 PM
100% correct Ive seen some people  SAY just install either network-manger or wicd and the one you install will remove the other this is completely  Wrong

Even after removing wicd or network-manager always check there is no startup files still operational  :)

I think that would collapse any distro; it is like a tug of war between one team... my 2 cents :)