All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rani Ahmed <rani79@idm.net.lb>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping per IP in PPPoE borrowing or sharing Uplink or
Date: Thu, 20 Apr 2006 08:38:25 +0000	[thread overview]
Message-ID: <44474881.7010100@idm.net.lb> (raw)
In-Reply-To: <443FB946.6050205@idm.net.lb>

thanks for your help. but i am not that much used to tc. i use tcng. so 
how should i write that in tcng?
Anton Glinkov wrote:

>If they are all on the same ethernet device, you can match them with:
>tc filter add dev ${DEVICE} parent 1: protocol all u32 \
>match u16 0x8864 0xFFFF at -2 flowid 1:${ID}
>
>8864 is the PPP session ethernet protocol
>
>you can play around with u32 if you want to match tos or ports and stuff..
>
>  
>
>>helo again. I think this question i am asking is worth:
>>
>>we know that pppoe-server creates a pppX device on each connection done
>>to it.
>>So, when i have to shape, i have to shape each pppX connection device on
>>itself alone.
>>What i know is that the borrowing method on one device by itself,  e.g.
>>ppp0, alone using HTB or the like. this means that i have to create for
>>another device, e.g. ppp1, its own HTB or CBQ tree.
>>
>>So, how can i in PPPoE technology setup sharing or borrowing between all
>>the pppX devices so it won't let network starvation problem float on
>>surface?
>>
>>Thanks.
>>
>>    
>>
>
>  
>

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2006-04-20  8:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 15:01 [LARTC] Shaping per IP in PPPoE borrowing or sharing Uplink or Rani Ahmed
2006-04-14 15:20 ` Martin A. Brown
2006-04-15  8:39 ` Anton Glinkov
2006-04-20  8:38 ` Rani Ahmed [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=44474881.7010100@idm.net.lb \
    --to=rani79@idm.net.lb \
    --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.