FreshTomato Wiki

User Tools

Site Tools

Trace:
advanced-wlanvifs

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
advanced-wlanvifs [2022/01/21 01:11] – [Virtual Wireless]-clarity, grammar hogwildadvanced-wlanvifs [2022/01/21 01:14] – [Virtual Wireless]-grammar hogwild
Line 1: Line 1:
 ====== Virtual Wireless ====== ====== Virtual Wireless ======
  
-The Virtual Wireless menu allows you to create and modify virtual wireless interfaces for virtual wireless networks. This is useful for creating things like guest networks, and separate networks for IoT (Internet of Things) devices, which are often untrusted in terms of security.+The Virtual Wireless menu allows you to create and modify virtual wireless interfaces for virtual wireless networks. This is useful for creating things like guest networks, (for questionable/unfamiliar users). It's also useful for creating  separate networks for IoT (Internet of Things) devices. IoT devices are often untrusted in terms of security.
  
  \\  \\
Line 26: Line 26:
 For details on Wireless modes, please see the "Wireless Mode" tables on the [[:network|Network]] wiki page. For details on Wireless modes, please see the "Wireless Mode" tables on the [[:network|Network]] wiki page.
  
-**Bridge** -  Allows you to select which LAN bridge this VIF should be assigned+**Bridge** -  Allows you to select to which LAN bridge this VIF should be assigned.
  
-Virtual wireless networks share the same radio as their corresponding main wireless interface. Because of this, for any virtual wireless network you want to enable, you must ensure the corresponding, shared main interface is enabled. For exampe, to enable VIF wl0.1, the main wireless interface wl0 must be enabled. The opposite, is not true. Turning off a corresponding VIF has no effect on the on/off status of the corresponding main interface.+Virtual wireless networks share the same radio as their corresponding main wireless interface. Thus, for any virtual wireless network you want to enable, you must ensure the corresponding, shared main interface is enabled. For example, to enable VIF wl0.1, the main wireless interface wl0 must be enabled. The opposite, is not true. Turning off a corresponding VIF has no effect on the on/off status of the corresponding main interface.
  
-Physical wireless interfaces are listed wl0, wl1, wl2, and so on. An alias (like for physical interfaces) is identified by a period (".") + "reference number" , such as wl0.1, wl0.2 and so forth. For example, in the image above, the virtual network wl0.1 (sharing the 2.4 GHz radio) has SSID name "Guest24". The virtual network wl0.2 (sharing the 5 GHz radio) has SSID name "Guest50".+Physical wireless interfaces are listed as wl0, wl1, wl2, and so on. An alias (like for physical interfaces) is identified by a period (".") and "reference number" , such as wl0.1, wl0.2 and so forth. For example, in the image above, the virtual network wl0.1 (sharing the 2.4 GHz radio) has SSID name "Guest24". The virtual network wl0.2 (sharing the 5 GHz radio) has SSID name "Guest50".
  
 The more virtual interfaces there are, the more possible SSIDs you get and the less throughput is available to each client (though this is hardly noticeable for up to 4-5 virtual SSIDs). The more virtual interfaces there are, the more possible SSIDs you get and the less throughput is available to each client (though this is hardly noticeable for up to 4-5 virtual SSIDs).
advanced-wlanvifs.txt · Last modified: 2023/06/18 23:03 by hogwild

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki