All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ problems :-(
Date: Tue, 06 Jan 2004 21:43:33 +0000	[thread overview]
Message-ID: <04010621433300.00693@amd> (raw)
In-Reply-To: <1045377672.20040104004813@yahoo.co.uk>

On Sunday 04 January 2004  5:33 pm, Roy wrote:
> > I have read about people having lots of problems with IMQ. So I just
>
> wanted to
>
> > try it and see how stable it is on my box. I gather it could actually
> > be problems with the Kernel and not the IMQ code??
>
> That is possible but prpbably not because of bug in kernel I
> as I think it is because kernel handles local trafic diferently than
> forwarded
>
> so you cant use imq to shape trafic generated by server
> I am comtinuing development of imq abd I face this problem most of the
> time.


Do you mean because it crashes ?

I seem to be able to shape upstream from my gateway and forward OK using 
IMQ - I know I don't really need it for up because I could mark, and the 
nat patch only works down, but I've been testing the jdg script recently 
and haven't managed a crash yet. I am only on a home network that gets 
shutdown after 18 hours, though.


>
> > I think that sounds even more messy :-)
> > I only wanted to ingress shape with IMQ to ensure that I don't drop
> > UDP or small TCP ACK packets for upload streams. I guess I will just
> > give up on the idea and using ingress policing... Its not so important
> > anyway
>
> as my
>
> > DSL connection is very asymetric (2mbit D/L; 256kbit U/L) and upload
> > shaping is more important.
>
> if only want to shape incoming trafic probably you can use imq quite
> safely,
>
> anyway as I see you dont need it at all you can easily shape all uploads
> anyway
> and since your download speed is high enough you dont need to worry
> about it.
>
> however imq can be usefull to control trafic so that you can download
> with kaza and browse web or play game without high latency.
______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2004-01-06 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-04  0:48 [LARTC] IMQ problems :-( Robert Walker
2004-01-04  2:12 ` Roy
2004-01-04 15:47 ` Robert Walker
2004-01-04 17:33 ` Roy
2004-01-06 21:43 ` Andy Furniss [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=04010621433300.00693@amd \
    --to=andy.furniss@dsl.pipex.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.