[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
howtos:network_services:running_an_access_point_from_a_slackware_box [2016/11/18 15:05 (UTC)] – [4.7.3 Other Linux Distributions Wireless Clients] louigi600howtos:network_services:running_an_access_point_from_a_slackware_box [2019/09/01 07:03 (UTC)] – [3.3 Other Software] louigi600
Line 89: Line 89:
   - edit the defconfig file and enable any optional features you need (default is fine for a simple setup)   - edit the defconfig file and enable any optional features you need (default is fine for a simple setup)
   - copy the defconfig file to .config   - copy the defconfig file to .config
 +  - make a softlink for netlink includes (cd /usr/include; ln -s libnl3/netlink .)
   - make   - make
   - make install (or optionally just put in /usr/local/bin just the hostapd binary)   - make install (or optionally just put in /usr/local/bin just the hostapd binary)
Line 399: Line 400:
 It should then be possible to restart rc.inet1 (or just rc.inet1 wlan0_down and rc.inet1 wlan0_up) and the client should associate. It should then be possible to restart rc.inet1 (or just rc.inet1 wlan0_down and rc.inet1 wlan0_up) and the client should associate.
  
-There's also the command line alternative with wpa_cli in this example we'll assume that your client is totalu unconfigured and wpa_supplicant is not running. Wr're going to do everything on the command line:+There's also the command line alternative with wpa_cli in this example we'll assume that your client is totally unconfigured and wpa_supplicant is not running. We're going to do everything on the command line:
  
   # wpa_supplicant -B -W -Dwext -i wlan0 -c /etc/wpa_supplicant.conf   # wpa_supplicant -B -W -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
Line 443: Line 444:
 in it the above snippet would have saved the new network to wpa_supplicant.conf and associated you with it. in it the above snippet would have saved the new network to wpa_supplicant.conf and associated you with it.
  
-Remember that if you're doning that for an AP with no secutity you need to use this:+Remember that if you're associating with an non secured AP you need to use this:
   > set_network 0 ssid "Insecure-WiFi"   > set_network 0 ssid "Insecure-WiFi"
   OK   OK
Line 449: Line 450:
   OK   OK
   >   >
 +
 +
 ==== 4.7.3 Other Linux Distributions Wireless Clients ==== ==== 4.7.3 Other Linux Distributions Wireless Clients ====
 I've tried various other flavor distributions ... most don't use wpa_gui for associating to AP but  some sort of other tool that generally pops up when you click on the icon that notifies the presence of an Access Point. After a few headaches I found that best association success is achieved by forcing setup for hidden AP even if the AP I'm configuring has not the hidden essid. You can always use wpa_cli on the command line if it's shipped with whatever distro you prefer. I've tried various other flavor distributions ... most don't use wpa_gui for associating to AP but  some sort of other tool that generally pops up when you click on the icon that notifies the presence of an Access Point. After a few headaches I found that best association success is achieved by forcing setup for hidden AP even if the AP I'm configuring has not the hidden essid. You can always use wpa_cli on the command line if it's shipped with whatever distro you prefer.

Trace:

howtos:network_services:running_an_access_point_from_a_slackware_box ()