Differences

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

--- advanced_scenarios [2023/09/25 00:17] – [Scenario 4] -condense, formatting hogwild
+++ advanced_scenarios [2023/09/25 00:32] (current) – [Advanced Scenarios Notes] -formatting-bullet Notes points hogwild
@@ Line 91: / Line 91: @@
  \\
-This is a Dual WAN Wireless Client mode scenario. Say, for example you have a Dual/Tri-band router and have access to two different WiFi Services (say public, street-based Wifi and a generous neighbour). You could configure wl0 as a wireless client for the public Internet and wl1 as a wireless client towards your neighbour's network. Then, if you have a Dual band model, you're left only with physical connectivity for your LAN.  However, if you had a Tri-band model, you'd still have room to create a local SSID. Remember that Dual band models always have one 2.4GHz interface and one 5GHz interface. Tri-band models always have one 2.4GHz interface and two 5GHz interfaces. Consider this carefully during your planning, as some devices are likely to be 2.4GHz only. Another possible option is to add a second local device (FreshTomato or otherwise) to handle LAN WiFi.
+This is a Dual WAN Wireless Client mode scenario. Say, for example you have a Dual/Tri-band router and have access to two different WiFi Services (say public, street-based Wifi and a generous neighbour). You could configure wl0 as a wireless client for the public Internet and wl1 as a wireless client towards your neighbour's network. Then, if you have a Dual band model, you're left only with physical connectivity for your LAN.  However, if you had a Tri-band model, you'd still have room to create a local SSID. Remember that Dual band models always have one 2.4GHz interface and one 5GHz interface. Tri-band models always have one 2.4GHz interface and two 5GHz interfaces. Consider this carefully during your planning, as some devices are likely to be 2.4GHz only. Another option would be to add a second local device (FreshTomato or otherwise) to handle LAN WiFi.
  \\
@@ Line 97: / Line 97: @@
 The Solution:
- \\ \\ {{:pasted:20220215-171344.png}}
+ \\ {{:pasted:20220215-171344.png}}
  \\
@@ Line 112: / Line 112: @@
 The Solution:
- \\ \\ {{:pasted:20220215-102621.png}}
+ \\ {{:pasted:20220215-102621.png}}
  \\
@@ Line 119: / Line 119: @@
 ===== Advanced Scenarios Notes =====
-WDS is a relatively old protocol to establish direct wireless connectivity between APs where the usage of a physical calble is not possible. As of 2022, using WDS is not recommended however it cans still help in some peculiar scenarios. WDS also is vendor-dependent and might not benefit from the full intra-device airtime bandwidth. Also please remember that currently trunking over WDS is not supported, this means that to extend a SSID/VLAN from AP1 to AP2 would work only for e.g. br0. If you were to extend the secondary SSID/VLAN you would need to use a secondary radio (e.g. 5GHz). So 1 WDS link = 1 VLAN (max).
+  * WDS is a relatively old protocol to establish direct wireless connectivity between APs where the usage of a physical cable isn't possible. While the use of WDS is unrecommended since 2022, WDS can still be helpful in certain, less common scenarios.
+  * WDS is vendor-dependent, and might not benefit from the full intra-device airtime bandwidth.
+  * Finally, remember that currently, trunking over WDS is not supported. Thus, to extend an SSID/VLAN from AP1 to AP2 would work only for one bridge (such as "br0"). If you wanted to extend the secondary SSID/VLAN, you would need to use a secondary radio (such as 5GHz interface). \\ In other words, 1 WDS link = 1 VLAN (max).

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools