Differences

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

--- bwlimit [2025/01/22 18:00] – [Bandwidth Limiter Notes and Troubleshooting] hogwild
+++ bwlimit [2025/05/08 16:45] (current) – [Bandwidth Limiter for LAN (br0)] -Condense hogwild
@@ Line 7: / Line 7: @@
 Confusingly, Bandwidth Limiter shares a few settings with QoS. When Bandwidth Limiter is enabled, QoS should be disabled, and vice versa. If both are enabled, they will conflict with each other and neither will work.
-Bandwidth Limiter may not work if you enable some IPv6 service types that use tunelling, such as 6in4. Their encryption is incompatible with Bandwidth Limiter.
+Bandwidth Limiter may not work if you enable some IPv6 service types that use tunneling, such as 6in4. Their encryption is incompatible with it.
  \\
@@ Line 23: / Line 23: @@
 Your menu may have different options, depending on the hardware.
-An easy way to find the "guilty" clients using too much bandwidth is to check the //IP Traffic///[[ipt-graphs|View Graphs]] menu. There, a pie chart clearly indicates the bandwidth used by each address. If you're unsure whether the guilty client is active now, check its history using the Last 24 Hours, Weekly or Monthly menus.
+An easy way to find the clients using too much bandwidth is to check the //IP Traffic///[[ipt-graphs|View Graphs]] menu. There, a pie chart clearly indicates the bandwidth used by each address. If you're unsure whether the guilty client is active now, check its history using the Last 24 Hours, Weekly or Monthly menus.
@@ Line 87: / Line 87: @@
  \\
-This field is shared. //You can only enter one address in a row at a time.// See NOTE below.
+This field is shared. //You can enter only one address in a row at a time.// See NOTE below.
 There's a quicker, easier way to enter individual IP/MAC Addresses. In [[status-devices|Device List]], click on [bwlimit] for each client to limit. You'll then be taken back to the Bandwidth Limiter menu to enter settings for that address.
-IP addresses entered should be specified using a static IP, or DHCP Reservation. If you don't, clients might be assigned a different IP address each time. Bandwidth Limiter won't not work with clients whose addresses changed from what you first configured. Entering MAC addresses instead will avoid that problem, since generally, they don't change.
+IP addresses entered should be specified using a static IP, or DHCP Reservation. Otherwise, clients might be assigned a different IP address each time. Bandwidth Limiter won't not work with clients whose addresses changed from what you first configured. Entering MAC addresses instead will avoid that problem, since generally, they don't change.
  \\
@@ Line 109: / Line 109: @@
 **Priority:** sets the position of the bandwidth rule (relative to other clients) in the netfilter module.
-FreshTomato has five priority settings. The higher the setting, the more preference will be given to that client's allocated bandwidth, relative to other clients. Higher priority clients will also experience lower latency, but only as a side effect of being earlier than other clients in netfilter's priority list.
+FreshTomato has five priority settings. The higher the setting, the more preference given to that client's allocated bandwidth, relative to other clients. Higher priority clients will also experience lower latency, but only as a side effect of being earlier than other clients in netfilter's priority list.
  \\
@@ Line 193: / Line 193: @@
 ===== Default Class for LAN1 (br1) =====
-As said above, settings here are analogous to the Default Class for LAN0 (br0) section above, but instead apply to clients on VLAN1 [ also known as LAN1/(bridge 1) ] .
+As above, settings here are analogous to the Default Class for LAN0 (br0) section above, but instead apply to clients on VLAN1 [ also known as LAN1/(bridge 1) ] .
-The same principles apply here as with the **Default Class for LAN (br0) **section, but to the LAN known as: LAN1/(br1). These settings will be explained again here for your convenience.
+The same principles apply as with the **Default Class for LAN (br0) **section, but to the LAN known as: LAN1/(br1). These settings will be explained again here for your convenience.
-Clients with a compatible static IP could still gain network access. FreshTomato needs a way to ensure clients not inlcuded in the [[dhcp_reservation|DHCP Reservation]] list are also categorized for bandwidth limiting. The **Default Class for unlisted MAC / IP's in LAN (br1)** function does this. It lets you set the default Class (bandwidth priority) for MAC or IP addresses on the main LAN for clients not listed in the DHCP Reservation// //table. It will ensure Bandwidth Limiter manages the bandwidth of static clients. These settings apply to the main LAN (bridge 1).
+Clients with a compatible static IP could still gain network access. FreshTomato needs a way to ensure clients not included in the [[dhcp_reservation|DHCP Reservation]] list are also categorized for bandwidth limiting. The **Default Class for unlisted MAC / IP's in LAN (br1)** function does this. It lets you set the default Class (bandwidth priority) for MAC or IP addresses on the main LAN for clients not listed in the DHCP Reservation// //table. It will ensure Bandwidth Limiter manages the bandwidth of static clients. These settings apply to the main LAN (bridge 1).
  \\
@@ Line 207: / Line 207: @@
 **Download rate:** the minimum download speed allocated to a client when other listed clients are downloading.
-The column total for all clients on the list should not exceed total “Download Bandwidth.” If the amount exceeds “Download Bandwidth”, entered data will serve no purpose when all network clients are downloading data.
+The column total for all listed clients should not exceed total “Download Bandwidth.” If the amount exceeds “Download Bandwidth”, entered data will serve no purpose when all clients are downloading.
 \\ {{::bandwidth_limiter-default_class_for_lan_br1_-2024.1.png?402}}
@@ Line 254: / Line 254: @@
  \\
-  - If Bandwidth Limiter is enabled, QoS should be disabled, and vice\\ versa. If both are enabled, they will conflict and neither will work.
+  - If Bandwidth Limiter is enabled, QoS should be disabled, and vice\\ versa. If both are enabled, they will conflict and neither will work. \\ \\
-  - Bandwidth Limiter won't work with some IPv6 service types enabled, \\ such as //6in4//. They use tunneling protocols that are incompatible with it.
+  - Bandwidth Limiter won't work with some IPv6 service types enabled, \\ such as //6in4//. They use tunneling protocols that are incompatible with it. \\ \\
   - Bandwidth Limiter should reboot the WAN interface only when \\ Captive Portal is enabled. However, with releases 2020.8 and earlier, \\ Bandwidth Limiter rebooted the WAN interface even when Captive Portal \\ was disabled. The router dropped the Internet connection until \\ the WAN interface was reinitialized and the WAN connection renegotiated. \\ This problem was fixed in release 2022.1.

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools