SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to get the WiFi working under Slackware64 14.1 and iwconfig returns the following:
wlan0 IEEE 802.11bgn ESSID:"TRENDnet652"
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
However the key keyword generated a warning and encryption is not set. Can someone help me to get this problem resolved? Thanks.
I am trying to get the WiFi working under Slackware64 14.1 and iwconfig returns the following:
wlan0 IEEE 802.11bgn ESSID:"TRENDnet652"
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
However the key keyword generated a warning and encryption is not set. Can someone help me to get this problem resolved? Thanks.
The WiFi is known to work with the same router (TRENDnet652 ) and same computer under Windows 8.1.
Still I would recommend wicd or networkmanager (wicd even has a great curses interface, and networkmanager probably will in the next Slackware release).
Still I would recommend wicd or networkmanager (wicd even has a great curses interface, and networkmanager probably will in the next Slackware release).
I didn't find either wicd or networkmanager. Maybe a PATH thing, I'll look into it. These are accessible from console interface?
---------- Post added 04-06-15 at 10:23 AM ----------
Quote:
Originally Posted by allend
The use of rc.wireless is now deprecated. For the full chapter and verse on what you are trying to do, I suggest this
I'm trying to set up the WiFi first with iwconfig, then once it's working I can move the proper entries to rc.net1. I'm a bit confused about the index e.g., [4] and why it never seems to be [0] or [1]
To clarify the situation, I have a cable modem feeding internet to a router at home. I have my desktop in another room connected via WiFi.
Last edited by rdx; 04-06-2015 at 10:33 AM.
Reason: added
wicd is in slackware/extra while networkmanager is in by default (as NetworkManager, nm*)
wicd i know has a curses interface, idk about NM
NM has a gtk interface called nm-applet
that said, if you have a stable connection you don't need either of those
WEP is easy to set up, and goes something like this
Code:
ifconfig wlan0 up
iwconfig wlan0 essid name key s:key channel chan_num
#channel number is optional to make sure it's the right AP, BSSID would be better though
killall -9 dhcpcd
dhcpcd wlan0
WPA requires making a /etc/wpa_supplicant.conf and starting the supplicant, that i never did
and that's the basics of what rc.inet1 comes down to
PS iwconfig has a successor called iw that i find does the same thing by using more words
iwconfig should work for the foreseeable future
NetworkManager has 'nmcli' as a curses interface. The problem with nmcli is that it cannot use the secrets required for wireless with WPA2. The nm-applet interface is required for that.
wicd has the much nicer curses interface 'wicd-client', but cannot be used with USB modems.
Back in the days that I was doing wireless connections, I tried wicd (this was before 14.0 when NetworkManager was included). Unless I just couldn't figure it out, it would never connect to the wireless soon enough to mount my network share drives during startup (this was a media center pc that relied on those network drives). I ended up switching to just having rc.inet1 manage my connection. It may be a bit difficult the first time, but once you get the handle of it, it is relatively easy (although, certainly not on par with GUI interfaces with NetworkManager or wicd). Also, if this is a laptop and has the potential to connect to new networks frequently, it may be beneficial to go with the GUI options, since it is much quicker to add a network that way. That being said, if I remember correctly, this is what you would need to do to connect to a WPA network using just rc.inet1 and wpa_supplicant (I assume you aren't using WEP, because you reallyshouldn't be).
But the slackbook wiki has fairly detailed information on getting rc.inet1.conf and wpa_supplicant set up. Make sure you read the section about WPA2 to get your wpa_supplicant set up properly.
Just for the record, NetworkManager is part of the standard Slackware install since 14.0
I am baffled by this because I do not find NetworkManager. Using KDE I can go into system setup and find a number of config paged but they don't seem to address the parameters I'm trying to get at. There is a tray icon which says Network Management and when I click it, it says "NetworkManager is not running. Please start it." But I am not finding it.
You would need to make /etc/rc.d/rc.networkmanager executable and run it before you can use the applet in KDE. If you don't have that file, then you didn't install NetworkManager (which is part of a full installation). To make it executable and start the service, as root, run:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.