SSH interactive is keystrokes. Bulk is SCP and friends. Feel free to spice up the article if you can make it better.
On 10/26/05, Peter Zaitsev <[EMAIL PROTECTED]> wrote: > On Tue, 2005-10-25 at 23:50 -0400, Scott Ullrich wrote: > > http://faq.pfsense.com/index.php?sid=3552〈=en&action=artikel&cat=10&id=56&artlang=en&highlight=ssh%20traffic%20shaper > > Scott, > > I've actually read this (as all FAQ but later forgot, sorry) > > Actually this FAQ raises more questions than it provides answers: > > "It already is, a SSH key is an ACK. If you put ssh in, then bulk will > kill all other ssh traffic (interactive). > > Last update: 2005-10-18 17:29 > Author: Matt Bailey > " > > It is not clear > > - Why SSH key is ACK is it stands for something ? Why is not it named > SSH ? > > To be honest I would think ACK corresponds to IP packets with ACK > flag. > > - So SSH is not in ? ("If you put ssh in...") > > - What is "bulk" > > - Why it would kill all other ssh traffic and what it suppose to mean ? > > > > > > > > On 10/25/05, Peter Zaitsev <[EMAIL PROTECTED]> wrote: > > > On Tue, 2005-10-25 at 19:52 -0500, Bill Marquette wrote: > > > > Any 'altq on' lines? I'll try and duplicate this tonight (or not, > > > > it's already 8PM and I'm still at work). > > > > > > Thanks. It does not seems like there are any. > > > > > > I actually repeated the wizard and now selected one of the traffic > > > shaping features. > > > > > > It looks like you can't simply continue with Wizard to the end without > > > setting any shaping - it will create wrong rules. > > > > > > Also in remote access services I did not find SSH - very surprising > > > omission for FreeBSD based product. There is VNC, RDP but not SSH. > > > > > > > > > > > > > > --Bill > > > > > > > > On 10/25/05, Peter Zaitsev <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > > > > > I'm running 0.89.6 > > > > > > > > > > I tried to experiment with traffic shaping today. I'm to use it for > > > > > collocation so my goal is to avoid long traffic spikes, as this is > > > > > what > > > > > I'll need to pay for. So lets say I have 100MB connection and I want > > > > > to > > > > > cap it at 15Mbit or something. > > > > > > > > > > Anyway at this point I just went via EZ Shaper wizard and only set > > > > > bandwidth leaving all default as rest. The following rules were > > > > > generated: > > > > > > > > > > queue qWANRoot bandwidth 100000Kb priority 6 hfsc { qWANdef, qWANacks > > > > > } > > > > > queue qWANdef bandwidth 1% priority 3 hfsc ( default upperlimit(100% > > > > > 100 90%) linkshare(0% 1000 10%) realtime(10% 1 10%) ) > > > > > queue qLANRoot bandwidth 100000Kb priority 6 hfsc { qLANdef, qLANacks > > > > > } > > > > > queue qLANdef bandwidth 1% priority 3 hfsc ( default upperlimit(100% > > > > > 100 90%) linkshare(0% 1000 10%) realtime(10% 1 10%) ) > > > > > queue qLANacks bandwidth 1% priority 6 hfsc ( upperlimit(80% 1 80%) > > > > > linkshare(0% 1000 10%) realtime(10% 1 10%) ) > > > > > queue qWANacks bandwidth 1% priority 6 hfsc ( upperlimit(80% 1 80%) > > > > > linkshare(0% 1000 10%) realtime(10% 1 10%) ) > > > > > > > > > > > > > > > I get the error loading these rules, basically in every line: > > > > > > > > > > hp: /wizard.php: There were error(s) loading the > > > > > rules: /tmp/rules.debug:17: queue qWANRoot has no > > > > > parent /tmp/rules.debug:17: errors in queue > > > > > definition /tmp/rules.debug:18: queue qWANdef has no > > > > > parent /tmp/rules.debug:18: errors in queue > > > > > definition /tmp/rules.debug:19: queue qLANRoot has no > > > > > parent /tmp/rules.debug:19: errors in queue > > > > > definition /tmp/rules.debug:20: queue qLANdef has no > > > > > parent /tmp/rules.debug:20: errors in queue > > > > > definition /tmp/rules.debug:21: queue qLANacks has no parent /tmp/rul > > > > > > > > > > > > > > > Any help with these ? > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
