[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 [2022/06/11 08:30 (UTC)] – [8 Setting up on an Embedded Device] louigi600 | howtos:network_services:running_an_access_point_from_a_slackware_box [2022/11/13 04:21 (UTC)] – [5.5 Virtual AP] louigi600 | ||
|---|---|---|---|
| Line 22: | Line 22: | ||
| Ok there is still some Wireless NICs that support hardware master mode but that's 3 against all the rest I'm not going to bother going into any detail with those 3 exceptions, google is your friend if you want to insist in the hardware master mode way. | Ok there is still some Wireless NICs that support hardware master mode but that's 3 against all the rest I'm not going to bother going into any detail with those 3 exceptions, google is your friend if you want to insist in the hardware master mode way. | ||
| + | |||
| + | |||
| + | Should you want to have Virtual Access Poits (more than one AP on a single physical wireless NIC) you will want to look at the section "valid interface combinations" | ||
| + | Here's the output from two cards : | ||
| + | |||
| + | [root@nuc8i5 ~]# for Phy in $(iw dev |grep ^phy); do echo " | ||
| + | phy#1 | ||
| + | valid interface combinations: | ||
| + | * #{ AP, mesh point } <= 8, | ||
| + | total <= 8, #channels <= 1 | ||
| + | phy#0 | ||
| + | valid interface combinations: | ||
| + | * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1, | ||
| + | total <= 3, #channels <= 2 | ||
| + | [root@nuc8i5 ~]# | ||
| + | | ||
| + | The first one would allow more than on vAP (up to a maximum of 8) but they all got to be on the same channel. | ||
| + | The second one would allow for one AP and one managed client to be used at the same time even of different channels but the total number of live APs need to be no more than one. | ||
| ====== 3 Software Requirements ====== | ====== 3 Software Requirements ====== | ||
| Line 577: | Line 595: | ||
| Please note the above script only works on 2.6 kernels or above. This probably also applies to socklist. | Please note the above script only works on 2.6 kernels or above. This probably also applies to socklist. | ||
| + | |||
| + | ===== 5.5 Virtual AP ===== | ||
| + | If your wireless NIC supports it you might like to run multiple virtual APs. As mentioned in Chapter 2 to be able to do this | ||
| + | you will need the "valid interface combinations" | ||
| + | If this is the case then you can add virtual AP like this | ||
| + | |||
| + | iw phy0 interface add vap0 type __ap | ||
| + | or | ||
| + | iw wlan0 interface add vap0 type __ap | ||
| + | | ||
| + | this will create a new virtual AP, arbitrarily called vap0 on which you will need to activate a separate instance of hostapd as explained in Chapter 4. | ||
| + | Incidentally the type can be any of of these (as long as your wireless NIC supports them): | ||
| + | |||
| + | * monitor | ||
| + | * managed | ||
| + | * wds | ||
| + | * mesh | ||
| + | * ibss | ||
| + | * __ap | ||
| + | |||
| + | |||
| + | if you subsequentlt want to remove the virtual AP toy can terminate the hostapd running on it, optionally put the nick in down state and then tell iw you want to delete the virtual device: | ||
| + | |||
| + | iw vap0 del | ||
| + | | ||
| ====== 6 Remote Administration ====== | ====== 6 Remote Administration ====== | ||
