Hello, From a user perspective, the simple (tcpri) and complex TC configs offers two rather distinct choices. A user can very well be OK with only using the simple way and that''s very fine. Then again, even in doing so, the more complex config options are available. What is the interplay between the two as far as having some parameters configured in both at the same time ? So far I only see that if interfaces are configured in tcinterfaces then some priorities will be deferred when the tcpri is used. I have re-read several times the explanation in tcpri but can''t figure it out clearly. What would be a typical, concerte example of this interaction ? - Thanks! ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails
On 04/23/2011 07:40 AM, lanas wrote:> Hello, > > From a user perspective, the simple (tcpri) and complex TC configs > offers two rather distinct choices. A user can very well be OK with > only using the simple way and that''s very fine. Then again, even in > doing so, the more complex config options are available.No they are not. The type of TC available is determined by the TC_ENABLED setting in shorewall.conf: - TC_ENABLED=Simple enables simple traffic shaping - TC_ENABLED=Internal enables complex traffic shaping> What is the interplay between the two as far as having some > parameters configured in both at the same time ?You cannot.> So far I only see that if interfaces are configured in tcinterfaces > then some priorities will be deferred when the tcpri is used.If an interface is configured in tcinterfaces, then traffic leaving that interface will be prioritized based on the TOS field in the ip header. Optionally, you can police the incoming traffic rate and limit the outgoing rate.> I have re-read several times the explanation in tcpri but can''t > figure it out clearly. What would be a typical, concerte example of > this interaction ?Here is my own tcpri file: #BAND PROTO PORT(S) ADDRESS INTERFACE COMMENT All DMZ traffic in band 3 by default 3 - - 70.90.191.124/31 COMMENT Bit Torrent is in band 3 3 ipp2p:all bit COMMENT But give a boost to DNS queries 2 udp 53 COMMENT And place echo requests in band 1 to avoid false line-downs 1 icmp 8 In this example, I am declaring that all traffic from 70.90.191.124/31 as well as Bit Torrent traffic (from any address) should go into the lowest priority band, but I''m giving a boost to DNS queries and in all cases, I want echo requests to go into the highest priority band. The latter was intended to insure that LSM pings (see the Shorewall multi-ISP documentation) were given high priority. HTH, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails
On Sat, 23 Apr 2011 08:08:13 -0700, Tom Eastep <teastep@shorewall.net> wrote :> No they are not. The type of TC available is determined by the > TC_ENABLED setting in shorewall.conf: > > - TC_ENABLED=Simple enables simple traffic shaping > - TC_ENABLED=Internal enables complex traffic shapingThanks for pointing this out !> > What is the interplay between the two as far as having some > > parameters configured in both at the same time ? > > You cannot.I''m afraid it is still not sharply clear. Why would there be a mention of tcinterfaces (which, as far as I see it belongs to the complex TC configuration as tcpri is a self-contained TC simple configuration) in tcpri documentation regarding an interaction possibility of tcinterfaces with the tcpri configuration ? I mean, since it''s either ''simple'' or ''internal'' then why would a configuration in the other would matter ?> > So far I only see that if interfaces are configured in tcinterfaces > > then some priorities will be deferred when the tcpri is used. > > If an interface is configured in tcinterfaces, then traffic leaving > that interface will be prioritized based on the TOS field in the ip > header. Optionally, you can police the incoming traffic rate and > limit the outgoing rate.> Here is my own tcpri file:Thanks again, this is very useful. ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails
On Apr 23, 2011, at 8:27 AM, lanas wrote:> > I''m afraid it is still not sharply clear. Why would there be a mention > of tcinterfaces (which, as far as I see it belongs to the complex TC > configuration as tcpri is a self-contained TC simple configuration) in > tcpri documentation regarding an interaction possibility of tcinterfaces > with the tcpri configuration ? I mean, since it''s either ''simple'' or > ''internal'' then why would a configuration in the other would matter ?tcinterfaces and tcpri are the config files of *SIMPLE TC*. See http://www.shorewall.net/simple_traffic_shaping.html. tcdevices, tcclasses, tcfilters and tcrules are the config files of *COMPLEX TC*. See http://ipv6.shorewall.net/traffic_shaping.htm. -Tom Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails
On Sat, 23 Apr 2011 08:56:21 -0700, Tom Eastep <teastep@shorewall.net> wrote :> tcinterfaces and tcpri are the config files of *SIMPLE TC*. See > http://www.shorewall.net/simple_traffic_shaping.html.Thanks. In tcinterfaces, if the optional interface type is not specified, what would be the effect on the configuration ? ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails
On Apr 23, 2011, at 10:47 AM, lanas wrote:> On Sat, 23 Apr 2011 08:56:21 -0700, > Tom Eastep <teastep@shorewall.net> wrote : > >> tcinterfaces and tcpri are the config files of *SIMPLE TC*. See >> http://www.shorewall.net/simple_traffic_shaping.html. > > Thanks. In tcinterfaces, if the optional interface type is not > specified, what would be the effect on the configuration ? >With no interface type, SFQ treats each ''flow'' equally. When ''External'', is specified, each source IP addresses is treated equally. When ''Internal'' is specified, each destination IP address is treated equally. -Tom Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails
On Sat, 23 Apr 2011 13:29:01 -0700, Tom Eastep <teastep@shorewall.net> wrote :> On Apr 23, 2011, at 10:47 AM, lanas wrote:> > Thanks. In tcinterfaces, if the optional interface type is not > > specified, what would be the effect on the configuration ? > > With no interface type, SFQ treats each ''flow'' equally. When > ''External'', is specified, each source IP addresses is treated > equally. When ''Internal'' is specified, each destination IP address is > treated equally.Thanks ! I think this could constitute a nice addition to the tcinterfaces documentation page for anyone not familiar with SFQ. Thanks again - much appreciated. ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails