[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 revisionLast revisionBoth sides next revision | ||
| howtos:network_services:running_an_access_point_from_a_slackware_box [2022/11/13 03:28 (UTC)] – [5.4 Socket Status] louigi600 | howtos:network_services:running_an_access_point_from_a_slackware_box [2023/01/20 09:43 (UTC)] – [4.3 DNS and DHCP Servers] fix typos tim | ||
|---|---|---|---|
| Line 199: | Line 199: | ||
| ===== 4.3 DNS and DHCP Servers ===== | ===== 4.3 DNS and DHCP Servers ===== | ||
| Now it's time to start dnsmasq. You can actually leave it running from boot if you like or even run specific servers at your choice. I now run separate dnsmasq instances for each AP so I've abandoned Slackware' | Now it's time to start dnsmasq. You can actually leave it running from boot if you like or even run specific servers at your choice. I now run separate dnsmasq instances for each AP so I've abandoned Slackware' | ||
| - | Configuring it is something you should look into to suit best your networking needs ... let's just look at some of the most common | + | Configuring it is something you should look into to suit best your networking needs ... let's just look at some of the most common |
| Supposing that you want to assign ip addresses belonging to 192.168.0.0/ | Supposing that you want to assign ip addresses belonging to 192.168.0.0/ | ||
| Line 211: | Line 211: | ||
| * dhcp-leasefile=/ | * dhcp-leasefile=/ | ||
| * conf-dir=/ | * conf-dir=/ | ||
| - | The options local and domain allow dnsmasq to tell clients they belong to a domain and in return serve as authoritative for that domain. Some distributions that use NetworkManager will not get local resolution to work unless | + | The options local and domain allow dnsmasq to tell clients they belong to a domain and in return serve as authoritative for that domain. Some distributions that use NetworkManager will not get local resolution to work unless |
| The options except-interface bind-interfaces and listen-address are particularly useful if you want to run more then one instance of dnsmasq. | The options except-interface bind-interfaces and listen-address are particularly useful if you want to run more then one instance of dnsmasq. | ||
| Line 597: | Line 597: | ||
| ===== 5.5 Virtual AP ===== | ===== 5.5 Virtual AP ===== | ||
| - | If your wireless NIC supports it you might like to run multiple virtual APs | + | 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 ====== | ||
