Re: bandwidth for bkbits.net (good news)

From: Larry McVoy (lm_at_bitmover.com)
Date: 08/30/03

  • Next message: Marcelo Tosatti: "Re: /proc/ioports overrun patch"
    Date:	Sat, 30 Aug 2003 08:03:11 -0700
    To: linux-kernel@vger.kernel.org
    
    

    On Fri, Aug 29, 2003 at 06:29:49PM -0700, Larry McVoy wrote:
    > We've avoiding turning on that feature in the past because we share the
    > T1 line that bkbits.net lives on with all the rest of bitmover and we are
    > partialy a distributed company. We do VOIP phones and when you guys clone
    > a repo our phones don't work - that makes us look bad during a sales call.

    Many people have sent me mail saying that we should be using traffic
    shaping to fix this problem. We are using it and we can't seem to make
    it work. Our theory is that we have a network like

     ----- [ ISP ] ====== internet ======== [ ISP ] ----

    wherein "-" means our skinny T1 or DSL and "=" means some fat internet
    connection on the backbone.

    We can shape all we want on our ends but if the internet is blasting us
    then our skinny pipe gets full and our shaping doesn't work. We really
    need to have the ISP do the shaping so they can squelch the traffic
    before it gets to our pipe.

    If there is someone out there who (a) is running VOIP over the public net
    to a pile of different end points (T1 on both ends tends to work, T1 to DSL
    or cable modem tends to get harder) and (b) has figured out traffic shaping
    that works I'd love to know about it.

    But just saying QoS/wondershaper doesn't help much (though the thought is
    appreciated), we've tried that already.

    Thanks.

    -- 
    ---
    Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Marcelo Tosatti: "Re: /proc/ioports overrun patch"