[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.
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| howtos:network_services:running_an_access_point_from_a_slackware_box [2016/11/18 15:04 (UTC)] – [4.7.2 Slackware Wireless Clients] louigi600 | howtos:network_services:running_an_access_point_from_a_slackware_box [2016/11/18 15:14 (UTC)] – [4.7.2 Slackware Wireless Clients] louigi600 | ||
|---|---|---|---|
| Line 449: | Line 449: | ||
| 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. | + | 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. |
