Differences

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

--- advanced_scenarios [2023/09/25 00:16] – [Scenario 3: Mixed Dual WAN (Ethernet and WiFi)] hogwild
+++ advanced_scenarios [2024/11/12 03:12] (current) – [Scenario 2: WiFi for Site-to-Site Connectivity] -clarity, condense hogwild
@@ Line 1: / Line 1: @@
 ====== Advanced Scenarios ======
-===== Advanced Wireless only Operations =====
+===== Advanced Wireless-Only Operations =====
 In most cases, a traditional consumer router works best in only one scenario. It connects your wired/wireless LAN clients to an Internet provider via a single physical WAN port on the router. In FreshTomato, this concept has been abstracted. Each physical or wireless router interface can be customized to work as WAN or LAN interface. This allows for some creative scenarios. Let's discuss some common examples.
@@ Line 61: / Line 61: @@
  \\
-However, this is not always possible. Both Wireless Ethernet Bridge and Media Bridge modes allow you to extend the LAN from one building to another. However, if you have a large number of clients, and end-to-end LAN connectivity isn't a prerequisite, you might want to use Wireless Client mode. Doing so will stop broadcast packets, from crossing the WiFi link, or at least reduce them to a minimum. Of course, intra-LAN communication over the single wireless link is limited in capacity, but works well enough for low-bandwidth traffic. Setting the two wireless LANs to the same SSID usename/password will allows clients to roam freely between buildings, retaining WiFi connectivity at both sites.
+However, this is not always possible. Both Wireless Ethernet Bridge and Media Bridge modes allow you to extend the LAN from one building to another.
+If you have a large number of clients, and end-to-end LAN connectivity isn't a prerequisite, you might consider using Wireless Client mode. Doing so will stop broadcast packets from crossing the WiFi link, or at least reduce them to a minimum. Of course, intra-LAN (within the LAN) communication over that one wireless link will have limited capacity, but it will work well enough for low-bandwidth traffic. Setting the two wireless LANs to the same SSID username/password will allows clients to roam freely between buildings, retaining WiFi connectivity at both sites.
  \\
@@ Line 87: / Line 89: @@
-==== Scenario 4 ====
+==== Scenario 4: Pure WiFi Dual WAN ====
-**Pure WiFi DualWAN**
+ \\
+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.
+ \\
+The Solution:
+ \\ {{:pasted:20220215-171344.png}}
+ \\
-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, stree-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.
-Solution:\\
-{{:pasted:20220215-171344.png}}
 ==== Scenario 5: WiFi6 Integration ====
@@ Line 104: / Line 114: @@
 The Solution:
- \\ \\ {{:pasted:20220215-102621.png}}
+ \\ {{:pasted:20220215-102621.png}}
  \\
@@ Line 111: / Line 121: @@
 ===== 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