Differences

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

--- bwlimit [2025/05/08 16:40] – [Default Class for LAN1 (br1)] -Condense 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.
  \\

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools