Differences

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

--- bwlimit [2025/05/08 16:43] – [Bandwidth Limiter] hogwild
+++ bwlimit [2025/11/15 18:41] (current) – [Bandwidth Limiter Notes and Troubleshooting] -Changed: "releases" to "r" hogwild
@@ 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 256: / Line 256: @@
   - 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 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.
+  - Bandwidth Limiter should reboot the WAN interface only when \\ Captive Portal is enabled. However, with r2020.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 r2022.1.
  \\

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools