getting to YES with closure re: identifying,prioritizing

RouterOS Wireless Networking
1

Bittorrent is a major factor on our wireless netork and we’d like to make sure interactive subscribers are treated well and that non-interactive subscribers still get best effort service.

What I don’t get (read: I’ve only had one cup of coffee so far this morning) is why if you can drop or mangle it, you can’t queue it.

I looked elsewhere for confirming/disagreeing viewpoints. Not being a proof by induction devotee or abuser, I stopped at three; there was no doubt expressed in other references, no ifs ands or buts in the other literature. Just straight forward.

Is Janis correct in that it can be done (by qualified folks); if not, why can’t it be done (by qualified folks)?

If it can’t be done, are we saying it is a Linux limitation or a RouterOS limitation? I doubt Linux is the limitation because a major player is using Linux to supplement the OS for their routers.

rgds/ldv

Neeraj_k’s original post which opened this recent thread was:

Normis is held in great respect, along with everyone else quoted, including the original poster:

[/quote]
[/quote]

=====Genesis=====

Looking at a customer facing FE0/1 on a distribution router at a wireless pop:

 FastEthernet0/1
                            Input                    Output
                            -----                    ------
   Protocol                 Packet Count             Packet Count
                            Byte Count               Byte Count
                            30sec Bit Rate (bps)     30sec Bit Rate (bps)
                            30sec Max Bit Rate (bps) 30sec Max Bit Rate (bps)
   ------------------------ ------------------------ ------------------------
   http                     33386114                 41506060
                            12947627315              48962691283
                            241000                   929000
                            2783000                  13076000
   bittorrent               31216340                 22069622
                            32378369610              8094153680
                            10000                    1000
                            4137000                  5895000
   h323                     8141040                  8869654
                            6619098541               5081481705
                            0                        0
                            1624000                  3392000
   gnutella                 10144605                 10598448
                            3190792138               7069611738
                            6000                     6000
                            1007000                  2870000
   smtp                     1476012                  2153958
                            636255197                702547996
                            1000                     12000
                            1173000                  1598000
   pop3                     1144245                  1655044
                            110616900                1182300378
                            1000                     6000
                            602000                   1213000
   ftp                      185410                   138717
                            224842849                50409831
                            0                        0
                            1065000                  472000
   skype                    2924281                  3306808
                            767707166                972825768
                            3000                     4000
                            678000                   739000
   secure-http              1362219                  1387027
                            352306436                902920285
                            12000                    66000
                            78000                    1317000
   ipsec                    2222784                  2725508
                            411995180                508356380
                            9000                     14000
                            582000                   710000
   rtsp                     571107                   859992
                            44031000                 1139835728
                            0                        0
                            32000                    1176000
   sqlnet                   2417                     6799
                            1839805                  7219644
                            0                        0
                            69000                    779000
   rtcp                     1127479                  626793
                            137337283                104729620
                            0                        0
                            136000                   684000
   novadigm                 27432                    46061
                            6100888                  42078593
                            0                        0
                            106000                   562000
 --More--
2

from bittorrent_pdlm_readme.pdf

In the following example, BitTorrent file transfer traffic is given one percent of the available bandwidth
for all traffic entering fastethernet 1/0:
class-map bittorrent
 match protocol bittorrent
policy-map limit-bittorrent
  class p2p
   bandwidth percent 1
interface fastethernet 1/0
service-policy input limit-bittorrent

read about QoS on your Cisco router and you can make all you want :wink: