On 12/30/2017 12:22 PM, Ilario Gelmetti wrote:
On 12/30/2017 06:02 PM, Patricio Gibbs wrote:
In Caimito we want to reduce our use of Internet
bandwidth, at least for
a few weeks until we can get a higher bandwidth connection.
1) block certain URLs, such as YouTube,
2) throttle traffic.
Maybe only during peak traffic hours.
For reducing the bandwidth (and decreasing congestion) you can try
installing and configuring qos-scripts
There's also a web interface packaged as luci-app-qos
That's useful! I see there's also Smart Queue Management (SQM), which is
another type of QoS that's incompatible with luci-app-qos:
I wonder which one is more useful for our network. They both sound
relevant for the way we want to regulate access to our network -- one
queue for people who contribute to the network, and a slower queue for
people who don't.
A problem you will face, I suppose, it's which
network interface to
select in configuration. You can try indicating the one used as WAN.
looking around more, I found a page about using the firewall, and that
sounds the easiest for blocking access to particular websites:
rest of Internet
Modem/Router in Cabin
| Cabin residents
There's 5 Mb/s 2 Mb/s DSL connection with 1:8 sharing (compartición) at
the cabin, and when the connection gets slow there, sometimes the owner
unplugs our cable from the modem/router to see if his download goes
faster. We want to calm down that guy so he stops unplugging our
connection! If we show him that we're blocking YouTube, that might be
enough for him.
Maybe we can make a traffic queue for YouTube that slows it down without
blocking it, but I think that might make the congestion worse at the
cabin, because YouTube would send data at full speed to the
modem/router, across the Ubiquiti antennas, and then get slowed down
when it gets to our LibreMesh gateway router in Caimito. So maybe it
would congest the modem/router? Maybe it would congest the buffer in the
LibreMesh router, but surely QoS and SQM doesn't work that way. Anyone know?
Let us know!
PS the bonus feature of having the system activated via email sounds complex
Looking through LEDE packages for "trigger" and "email", I see a few
things that might be part of a solution... but maybe it's easier to
trigger it through pushing a button on a webpage instead of sending an
lime-users mailing list