VectorLinux
September 02, 2014, 03:18:02 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1] 2
  Print  
Author Topic: Connectivity assistance please.  (Read 1647 times)
Locator
Vectorian
****
Posts: 704



« on: December 06, 2013, 09:32:18 pm »

Can anyone out there recommend a WPA supplicant that WON'T keep kicking me off the wireless network (I currently use wext)? and my operating system is Vector Linux 7.0.
Logged
sledgehammer
Vectorian
****
Posts: 1423



« Reply #1 on: December 07, 2013, 12:51:38 am »

Locator,

I would happily recommend my wpa supplicant, as it does not kick me off wireless and I use 7.0.  But I don't know what a wpa supplicant is or where to find it on my system. So if you tell me how, I will forward whatever I am using. Is it on some line in /etc/wpa_supplicant.conf?

Logged

VL7.0 xfce4 Samsung RF511
Locator
Vectorian
****
Posts: 704



« Reply #2 on: December 07, 2013, 05:26:11 am »

Go to Wicd Network Manager and click on the down arrow in the top left, and from the drop-down menu click "Preferences", then click the "Advanced Settings" tab.
Logged
roarde
Vectorian
****
Posts: 528


move the needle


« Reply #3 on: December 07, 2013, 05:15:36 pm »

Are you using wicd to set up the connection you're having trouble with, or some other utility?
Are there other networking connections in use that are not managed by wicd?
As root run:
Code:
/etc/rc,d/rc.wicd stop
/etc/rc.d/rc.wicd start
and try your connection again. Note warnings if any.
Post the output of 'ls -l /etc/rc.d'  and  'ls -l /etc/rc.d/rc.4', please.

To answer the question (semi-)directly, do:
Code:
wpa_supplicant -h | sed -n '/^drivers:/,/^options:/p'
Ability to use the listed drivers has been compiled into your copy of wicd, but that doesn't mean all those drivers have been compiled into the kernel or as modules. Still, if one of them looks familiar, you can try loading it as a module and see if wicd picks it up.

But you'd do better to provide more information and tell more about what is happening.
Logged

Robert
VL STD 7.1 RC2.2.2, icewmvmods
sledgehammer
Vectorian
****
Posts: 1423



« Reply #4 on: December 07, 2013, 06:23:10 pm »

Quote
Go to Wicd Network Manager and click on the down arrow in the top left, and from the drop-down menu click "Preferences", then click the "Advanced Settings" tab.

Well, perhaps this will help.  My down arrow is top right, not top left. It says "wext."
Logged

VL7.0 xfce4 Samsung RF511
bigpaws
Vectorian
****
Posts: 1847


« Reply #5 on: December 07, 2013, 07:04:18 pm »

You could try editing wpa_supplicant.conf directly to prove it is or is not working.

Use man wpa_supplicant.conf on howto use it.


Bigpaws
Logged
Locator
Vectorian
****
Posts: 704



« Reply #6 on: December 07, 2013, 07:10:38 pm »

Quote
Go to Wicd Network Manager and click on the down arrow in the top left, and from the drop-down menu click "Preferences", then click the "Advanced Settings" tab.

Well, perhaps this will help.  My down arrow is top right, not top left. It says "wext."

Sorry about that, I got my left and my right mixed up, and yes - I'm using wext as well
Logged
Locator
Vectorian
****
Posts: 704



« Reply #7 on: December 07, 2013, 07:29:12 pm »

Are you using wicd to set up the connection you're having trouble with, or some other utility?
Are there other networking connections in use that are not managed by wicd?
As root run:
Code:
/etc/rc,d/rc.wicd stop
/etc/rc.d/rc.wicd start
and try your connection again. Note warnings if any.
Post the output of 'ls -l /etc/rc.d'  and  'ls -l /etc/rc.d/rc.4', please.

To answer the question (semi-)directly, do:
Code:
wpa_supplicant -h | sed -n '/^drivers:/,/^options:/p'
Ability to use the listed drivers has been compiled into your copy of wicd, but that doesn't mean all those drivers have been compiled into the kernel or as modules. Still, if one of them looks familiar, you can try loading it as a module and see if wicd picks it up.

But you'd do better to provide more information and tell more about what is happening.


root:# ls -l /etc/rc.d
total 472
-rw-r--r-- 1 root root   832 May 14  2007 README.functions
-rwxr-xr-x 1 root root   845 Sep 28  2006 diamond*
-rwxr-xr-x 1 root root 12147 Sep 28  2006 functions*
-rwxr-xr-x 1 root root  3180 Sep 28  2006 functions-display*
-rwxr-xr-x 1 root root  2944 Sep 28  2006 functions-network*
-rwxr-xr-x 1 root root  4690 Sep 28  2006 functions-service*
drwxr-xr-x 3 root root  4096 Dec  3 10:19 init.d/
lrwxrwxrwx 1 root root     4 Dec  1 16:48 rc.0 -> rc.6*
-rwxr-xr-x 1 root root   893 Sep 28  2006 rc.4*
-rwxr-xr-x 1 root root  6184 Jul  5  2010 rc.6*
-rwxr-xr-x 1 root root  2941 Sep 28  2006 rc.A*
-rwxr-xr-x 1 root root  8670 Oct  8  2011 rc.K*
-rwxr-xr-x 1 root root  7013 Aug 10  2011 rc.M*
-rwxr-xr-x 1 root root 15014 Oct  6  2011 rc.S*
-rwxr-xr-x 1 root root  2347 Aug 10  2011 rc.X*
-rw-r--r-- 1 root root   816 Nov  5  2007 rc.acpi
-rwxr-xr-x 1 root root   466 Nov  5  2004 rc.acpid*
-rwxr-xr-x 1 root root  2771 Feb  9  2011 rc.alsa*
-rwxr-xr-x 1 root root   746 Sep 28  2006 rc.apm*
-rw-r--r-- 1 root root  2784 Mar  5  2010 rc.autofs
-rwxr-xr-x 1 root root   429 Sep 28  2006 rc.autologin*
-rwxr-xr-x 1 root root  1569 Aug 30  2011 rc.avahidaemon*
-rwxr-xr-x 1 root root  1627 Aug 30  2011 rc.avahidnsconfd*
-rw-r--r-- 1 root root  3378 Jun 24  2010 rc.bind
-rw-r--r-- 1 root root   497 Mar 30  2011 rc.bluetooth
-rw-r--r-- 1 root root   393 Dec  3 10:19 rc.bluetooth.new
-rwxr-x--- 1 root root   690 Sep 13  2007 rc.bootsplash*
-rw-r--r-- 1 root root  9052 Sep 28  2006 rc.cdrom
-rw-r--r-- 1 root root  4852 Mar  3  2011 rc.cgconfig
-rw-r--r-- 1 root root  3397 Mar  3  2011 rc.cgred
-rwxr-xr-x 1 root root   572 Mar 17  2011 rc.consolekit*
-rw-r--r-- 1 root root  4318 Jan 22  2011 rc.cups
-rw-r--r-- 1 root root   512 Sep 28  2006 rc.dnsmasq
-rwxr-xr-x 1 root root   124 Sep 28  2006 rc.fc-cache*
-rwxr-xr-x 1 root root  1695 Aug  5  2011 rc.firewall*
-rwxr-xr-x 1 root root   119 May 30  2004 rc.font*
-rwxr-xr-- 1 root root  1893 Oct  1  2007 rc.fuse*
-rw-r--r-- 1 root root   906 Nov 16  2010 rc.hald
-rw-r--r-- 1 root root  1585 Sep 28  2006 rc.hotplug
-rwxr-xr-x 1 root root   565 Sep 28  2006 rc.inet1*
-rw-r--r-- 1 root root  3759 Sep 20  2006 rc.inet1.conf
-rw------- 1 root root  4752 Aug 25  2009 rc.inet1.conf.new
-rwxr-xr-x 1 root root  9600 Aug 26  2009 rc.inet1.new*
-rw-r--r-- 1 root root   474 Sep 28  2006 rc.inet2
-rwxr-xr-x 1 root root  4847 Sep 17  2007 rc.inet2.new*
-rwxr-xr-x 1 root root   497 Sep 11  2003 rc.inetd*
-rw-r--r-- 1 root root  2062 Sep 28  2006 rc.ip_forward
-rw-r--r-- 1 root root  2684 Dec  3  2008 rc.ip_forward.new
-rwxr-xr-x 1 root root   450 Sep 28  2006 rc.keymap*
-rwxr-xr-x 1 root root  1032 Feb  8  2011 rc.local*
-rwxr-xr-x 1 root root  1740 Feb 27  2011 rc.messagebus*
-rwxr-xr-x 1 root root 23594 Jul  5  2010 rc.modules*
-rwxr-xr-x 1 root root   384 Jul  5  2010 rc.network*
-rwxr-xr-x 1 root root  1669 Oct 21  2011 rc.networkmanager*
-rwxr-xr-x 1 root root  2444 May 31  2007 rc.nfsd*
-rwxr-xr-x 1 root root  2449 Mar 21  2011 rc.nfsd.new*
-rw-r--r-- 1 root root  1148 Sep 28  2006 rc.parallel
-rw-r--r-- 1 root root   916 Sep 28  2006 rc.paranoid
-rw-r--r-- 1 root root  1722 Mar 16  2007 rc.pcmcia
-rwxr-xr-x 1 root root   215 Sep 28  2006 rc.pnp*
-rwxr-xr-x 1 root root  1336 Sep 28  2006 rc.route*
-rw-r--r-- 1 root root  1402 May 17  2007 rc.rpc
-rw-r--r-- 1 root root   791 Sep  7  2011 rc.samba
-rw-r--r-- 1 root root  1169 May 27  2006 rc.saslauthd
-rwxr-xr-x 1 root root   967 Sep 28  2006 rc.scanluns*
-rw-r--r-- 1 root root  2895 Sep 28  2006 rc.serial
-rw-r--r-- 1 root root   895 Jun 18  2007 rc.snmpd
-rwxr-xr-x 1 root root  1600 Feb  7  2011 rc.sshd*
-rwxr-xr-x 1 root root   860 Sep 28  2006 rc.syslog*
-rw-r--r-- 1 root root  1016 Apr 25  2010 rc.sysstat
-rwxr-xr-x 1 root root  1740 Sep 28  2006 rc.sysvinit*
-rwxr-xr-x 1 root root  1316 Jul  5  2010 rc.text*
-rw-r--r-- 1 root root   750 Jun 22  2011 rc.timidity
-rw-r--r-- 1 root root   545 Dec  3 17:10 rc.timidity.new
-rw-r--r-- 1 root root   340 Sep 28  2006 rc.tmpfs
-rw-r--r-- 1 root root  5058 Dec 13  2010 rc.udev
-rwxr-xr-x 1 root root  3085 Jul  5  2010 rc.vlinit*
-rwxr-xr-x 1 root root  1087 Sep 26  2011 rc.wicd*
-rw-r--r-- 1 root root  5637 Sep 28  2006 rc.wireless
-rw------- 1 root root  7320 May 19  2007 rc.wireless.conf
-rw-r--r-- 1 root root 12835 Nov 28  2010 rc.wireless.new
drwxr-xr-x 2 root root  4096 May 14  2007 rc0.d/
drwxr-xr-x 2 root root  4096 May 14  2007 rc1.d/
drwxr-xr-x 2 root root  4096 Dec  1 16:48 rc2.d/
drwxr-xr-x 2 root root  4096 Dec  1 16:48 rc3.d/
drwxr-xr-x 2 root root  4096 Dec  1 16:57 rc4.d/
drwxr-xr-x 2 root root  4096 Dec  1 16:48 rc5.d/
drwxr-xr-x 2 root root  4096 May 14  2007 rc6.d/
lrwxrwxrwx 1 root root     5 Dec  1 16:48 rc7.d -> rc4.d/
lrwxrwxrwx 1 root root     5 Dec  1 16:48 rc8.d -> rc5.d/
-rwxr-xr-x 1 root root  6208 Sep 28  2006 service*

root:# ls -l /etc/rc.d/rc.4
-rwxr-xr-x 1 root root 893 Sep 28  2006 /etc/rc.d/rc.4*
Logged
roarde
Vectorian
****
Posts: 528


move the needle


« Reply #8 on: December 07, 2013, 08:21:01 pm »

Post output (3 separate commands):
ps -C wicd -C NetworkManager
ifconfig
iwconfig

and also, sorry for my mistake above. How about
ls -l /etc/rc.d/rc4.d
Logged

Robert
VL STD 7.1 RC2.2.2, icewmvmods
Locator
Vectorian
****
Posts: 704



« Reply #9 on: December 08, 2013, 12:04:07 pm »

doctor:$ ps -C wicd -C NetworkManager
  PID TTY          TIME CMD
 2646 ?        00:00:26 wicd
vector:/~
doctor:$ ifconfig
lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1460 (1.4 Kb)  TX bytes:1460 (1.4 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:25:9C:A5:D7:01 
          inet addr:192.168.0.101  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:155087 errors:0 dropped:14375 overruns:0 frame:0
          TX packets:62920 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:86372701 (82.3 Mb)  TX bytes:10521904 (10.0 Mb)

vector:/~
doctor:$ iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"dlink" 
          Mode:Managed  Frequency:2.412 GHz  Access Point: C8:D3:A3:53:FB:D2   
          Bit Rate=18 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=43/70  Signal level=-67 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:60  Invalid misc:58   Missed beacon:0
Logged
roarde
Vectorian
****
Posts: 528


move the needle


« Reply #10 on: December 08, 2013, 12:24:38 pm »

@Locator:  Are you still having trouble? What happens?

I see that the wireless card's power management is set up, which usually means that this is a card for which wext works particularly well. In any case, unless there's a reason not to, use wext as it's by far the most actively developed of the drivers.
Logged

Robert
VL STD 7.1 RC2.2.2, icewmvmods
Locator
Vectorian
****
Posts: 704



« Reply #11 on: December 08, 2013, 01:23:26 pm »

What happens is that I keep getting kicked off the network - and we just decently got a brand new router (DLink, to be more exact). I don't know if this has anything to do with it, but the wireless network adapter that I an using plugs into a USB port.
Logged
retired1af
Packager
Vectorian
****
Posts: 1259



« Reply #12 on: December 08, 2013, 03:06:54 pm »

Kicked off how? No signal? Ran out of IP addresses? What?

Generally, if the wireless device is connected, the only reason you'd be getting kicked off the network is if you were suffering signal loss or there was an issue with the router itself.

How far are you from the router? Are you using 802.11g or n?
Logged

ASUS K73 Intel i3 Dual Core 2.3GHz
nightflier
Administrator
Vectorian
*****
Posts: 4022



« Reply #13 on: December 08, 2013, 03:13:33 pm »

Any time you change anything; hardware, software or settings, it can affect how things operate. The new router and your old USB dongle may just not get along that well.

A few (many) years back, I remember spending $200 on an IBM branded modem. It was the hottest thing around, and I would routinely connect to my ISP at 53k. Then I moved. In the new apartment I could get no more than 28.8k out of it, usually less. Replaced it with a $20 no-name brand and I was back up to higher speeds again.
Logged
overthere
Vectorian
****
Posts: 1274



« Reply #14 on: December 08, 2013, 04:04:43 pm »

Some of the dlinks have a mixed setting in addition to g or n
Logged

Everything Is Relative
Pages: [1] 2
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!