I'll give putty a try.
I have tried this:
https://community.ubnt.com/t5/EdgeMAX/Guest-QOS-or-Bandwidth-limit-per-vlan/td-p/1527542
(mojo_333 / 2014-04-04, 2:36PM post)
- It strikes me as wrong that both UPLOAD and DOWNLOAD have the same source address. Is one supposed to be destination?
- I got the CLI message: traffic-policy shaper DOWNLOAD configuration not complete: missing default class.
- Is the redirect (near the bottom) since shaper cannot apply to inbound?
- Download policy seems to make sense, adds default that was missing above.
- The redirect, again. Is this so you can apply shaper to traffic inbound to eth1?
Am I wanting to do all the shaping on eth1 (WAN)? Or could/should some be on eth0 (LAN).
If eth0, do I apply to eth0 itself, or eth0.2 and eth0.3? If eth0.2 and eth0.3, does that then become 2 traffic-policy each direction (in/out) and are they aware of each other (e.g. HOUSE policy can sense that OFFICE is sucking all the bandwidth it can, so HOUSE sticks to 10% limit, rather than approaching HOUSE ceiling)?
If you use a redirect, that seems to flip the concept of IN to OUT. Does it then affect whether you specify SOURCE or DESTINATION in the MATCH clause, or do those always stay with the true source or destination of the traffic?
By now it's very apparent that I know very little about this stuff. But I want to learn.
Thanks!
Doug