tc qdisc add dev eth0 root handle 1: htb tc class add dev eth0 parent 1:0 classid 1:1 htb rate... tc class add dev eth0 parent 1:1 classid 1:2 htb rate... tc class add dev eth0 parent 1:1 classid 1:3 htb rate...
tc qdisc add dev eth0 parent 1:2 handle 2: htb tc qdisc add dev eth0 parent 1:3 handle 3: htb tc class add dev eth0 parent 2:0 classid 2:1 .... si asa mai departe. Ai prins ideea? laurentiu wrote: >----- Original Message ----- >From: "Alin Nastac" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Wednesday, December 17, 2003 2:37 PM >Subject: [rlug] Re: htb metro > > > > >>e ciudat...poate ca doar ultima versiune de kernel 2.4 + ultima versiune >>de tc functioneaza cu filtre puse in alte noduri decit radacina >> >>incearca asa cum ti-am zis, cu 3 instante de htb pe interfata. >> >> > >ceva indicii??? > > > >>laurentiu wrote: >> >> >> >>>tc filter add dev eth1 parent 1:10 protocol ip prio 1 u32 match ip dst >>>192.168.0.19 flowid 1:100 >>>tc filter add dev eth1 parent 1:20 protocol ip prio 1 u32 match ip dst >>>192.168.0.30 flowid 1:200 >>> >>> >>>tc -s -d filter show dev eth1 parent 1:20 >>>filter protocol ip pref 1 u32 >>>filter protocol ip pref 1 u32 fh 801: ht divisor 1 >>>filter protocol ip pref 1 u32 fh 801::800 order 2048 key ht 801 bkt 0 >>> >>> >flowid > > >>>1:200 >>> match c0a8001e/ffffffff at 16 >>>filter protocol ip pref 1 u32 fh 800: ht divisor 1 >>>filter protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800 bkt 0 >>> >>> >flowid > > >>>1:100 >>> match c0a80013/ffffffff at 16 >>> >>> >>>tc -s -d filter show dev eth1 parent 1:10 >>>filter protocol ip pref 1 u32 >>>filter protocol ip pref 1 u32 fh 801: ht divisor 1 >>>filter protocol ip pref 1 u32 fh 801::800 order 2048 key ht 801 bkt 0 >>> >>> >flowid > > >>>1:200 >>> match c0a8001e/ffffffff at 16 >>>filter protocol ip pref 1 u32 fh 800: ht divisor 1 >>>filter protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800 bkt 0 >>> >>> >flowid > > >>>1:100 >>> match c0a80013/ffffffff at 16 >>> >>> >>>e normal?????? >>> >>> >>> >>> >>> >>>----- Original Message ----- >>>From: "laurentiu" <[EMAIL PROTECTED]> >>>To: <[EMAIL PROTECTED]> >>>Sent: Wednesday, December 17, 2003 1:46 PM >>>Subject: [rlug] Re: htb metro >>> >>> >>> >>> >>> >>> >>>>in documentatie spune ca pot pune filtre in alte noduri decat root, am >>>> >>>> >>>> >>>> >>>luat >>> >>> >>> >>> >>>>si tc-ul de la ei, degeaba, nu vrea sa imi asigneze filtrul decat la >>>> >>>> >1:0, > > >>>> >>>> >>>pe >>> >>> >>> >>> >>>>alt nod nu. >>>> >>>> >>>>----- Original Message ----- >>>>From: "Alin Nastac" <[EMAIL PROTECTED]> >>>>To: <[EMAIL PROTECTED]> >>>>Sent: Wednesday, December 17, 2003 11:40 AM >>>>Subject: [rlug] Re: htb metro >>>> >>>> >>>> >>>> >>>> >>>> >>>>>eu stiu doar o singura cale si anume cea a imq-ului. >>>>> >>>>>spunea cineva ca mai nou htb ar sti sa foloseasca filtrele din alte >>>>>noduri decit din radacina. daca e adevarat, atunci poti clasifica >>>>>functie de handle la un nod intermediar dupa care clasifici cu u32. >>>>> >>>>>ar mai fi o varianta dar asta inseamna ca pui 3 instante de htb per >>>>>interfata. o instanta 1: care separa metropolitana de extern si alte 2 >>>>>(2: si 3:) care clasifica pachetele cu u32. >>>>> >>>>>laurentiu wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>ok, intrebarea a 2-a, cum pot pune un match dst ip si un handle 1 pe >>>>>> >>>>>> >>>>>> >>>>>> >>>>acelasi >>>> >>>> >>>> >>>> >>>>>>filtru? >>>>>> >>>>>> >>>>>>----- Original Message ----- >>>>>>From: "Alin Nastac" <[EMAIL PROTECTED]> >>>>>>To: <[EMAIL PROTECTED]> >>>>>>Sent: Wednesday, December 17, 2003 10:47 AM >>>>>>Subject: [rlug] Re: htb metro >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>>www.lartc.org >>>>>>> >>>>>>>teoretic trebuie sa faci cite 4 clase per client : (uplink, downlink) >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>x >>> >>> >>> >>> >>>>>>>(extern, metropolitan) >>>>>>>practic poti sa fi mai relaxat in reguli, cel putin pe metropolitan. >>>>>>> >>>>>>>laurentiu wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>>Neatza. >>>>>>>>exista pe undeva un how-to pt htb pentru diferentierea >>>>>>>> >>>>>>>> >metropolitan - > > >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>extern?? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>>>sau imi poate spune careva in linii mari cam cum se poate face pt n >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>clienti, sa zicem cu aceeashi banda? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>>>sper ca nu trebuie sa fac 2xn clase :D >>>>>>>> >>>>>>>>Marcarea cu iptables se face, htb diferentiaza pe mark, totul e >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>functional (deocamdata o singura clasa), dar aici m-am blocat, cum sa >>>>>>implementez filtrele si clasele mai departe. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>>>Laurentiu >>>>>>>> >>>>>>>> >>>>>>>>--- >>>>>>>>Detalii despre listele noastre de mail: http://www.lug.ro/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>--- >>>>>>>Detalii despre listele noastre de mail: http://www.lug.ro/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>--- >>>>>>Detalii despre listele noastre de mail: http://www.lug.ro/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>--- >>>>>Detalii despre listele noastre de mail: http://www.lug.ro/ >>>>> >>>>> >>>>> >>>>> >>>>> >>>>--- >>>>Detalii despre listele noastre de mail: http://www.lug.ro/ >>>> >>>> >>>> >>>> >>>> >>>--- >>>Detalii despre listele noastre de mail: http://www.lug.ro/ >>> >>> >>> >>> >>> >>> >> >>--- >>Detalii despre listele noastre de mail: http://www.lug.ro/ >> >> >> > > >--- >Detalii despre listele noastre de mail: http://www.lug.ro/ > > > > --- Detalii despre listele noastre de mail: http://www.lug.ro/
