Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Jonathan Gazeley <jonathan.gazeley@bristol.ac.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: tc n00b
Date: Fri, 03 Aug 2007 15:11:18 +0000	[thread overview]
Message-ID: <46B34596.60306@bristol.ac.uk> (raw)
In-Reply-To: <20070730121432.GB30519@toroid.org>

Hi Nikolay,

Thanks very much for your help - the script is now working. The downlink 
shaping works as expected, but the uplink shaping seems to give 4 times 
more bandwidth than it ought to - so I've just divided the number by 4 
and it is satisfactory.

However, I've now discovered that pings from one of my shaped NAT 
clients, to another LAN machine that usually take <1ms, now take ~3500ms 
when I am using the bandwidth. How can I avoid these enormous queues?

I have cc'd the list in case anyone else has an idea. Have a good 
weekend everyone!

Cheers,
Jonathan

------------------------
Jonathan Gazeley
Wireless & VPN Team
Information Systems & Computing
University of Bristol
------------------------



Nikolay Kichukov wrote:
> Hey,
> sorry for delay. I had some issues with my primary
> internet connection and had to change the primary mail
> host as well.
>
> I looked at the script.
>
> Looks totally fine to me.
>
> If you are not sure where exactly the problem lies,
> try adding ONLY the ingress rules. Test it, see if it
> works. Then tweak if needed the script you sent to me.
>
> tc qdisc add dev $LAN ingress handle ffff:
> tc filter add dev eth0 parent ffff: protocol ip prio 2
> u32 match ip src IPHERE police rate ${UPLINK}kbit
> burst 16kb drop flowid ffff:
>
> Cheers,
> -Nik
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2007-08-03 15:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 12:26 [LARTC] Re: tc n00b Abhijit Menon-Sen
2007-07-30 13:16 ` Jonathan Gazeley
2007-07-30 13:36 ` Jonathan Gazeley
2007-07-30 13:38 ` Abhijit Menon-Sen
2007-07-30 13:55 ` Abhijit Menon-Sen
2007-07-30 13:58 ` Jonathan Gazeley
2007-07-30 14:10 ` Martin Milata
2007-07-31  7:59 ` Nikolay Kichukov
2007-07-31  9:37 ` Jonathan Gazeley
2007-07-31 10:00 ` Nikolay Kichukov
2007-07-31 10:08 ` Jonathan Gazeley
2007-07-31 11:24 ` Nikolay Kichukov
2007-07-31 14:33 ` Nikolay Kichukov
2007-08-03 15:11 ` Jonathan Gazeley [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=46B34596.60306@bristol.ac.uk \
    --to=jonathan.gazeley@bristol.ac.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox