Full cache thunder

[josueflat]

saludos, quisiera saber porque el mk no da full cache a un cliente, ejemplo lo limito a 256k y no le entrega full cache si no que el thunder lo limita y le entrega a 256k si le subo la velocidad el thunder le da mas velocidad alguien le a pasado esto? y si tienen la solución se lo agradeceré

[ingjaab]

hola como lo has configurado el mikrotik ya sea por interface o grupo

[josueflat]

hola como lo has configurado el mikrotik ya sea por interface o grupo

lo tengo configurado tal esta en este foro con esta regla ahora bien si alguien tiene otra regla favor publicarla

/ip firewall filter
add action=accept chain=forward comment="Acepta thunder 3.1.x" disabled=no \
    src-address=192.168.10.0/30
/ip firewall nat
add action=dst-nat chain=dstnat comment="Redirect Thunder 3.1.x" disabled=no \
    dst-port=80 protocol=tcp src-address=!192.168.10.2 to-addresses=\
    192.168.10.2 to-ports=3128
/ip firewall mangle
add action=mark-connection chain=postrouting comment="THUNDER CACHE FULL(TC 3.\
    1.x) =======================================================================\
    ===============================" content="X-Cache: HIT from Thunder" \
    disabled=no new-connection-mark=thunder-connection passthrough=yes \
    protocol=tcp src-address=192.168.10.2
add action=mark-packet chain=postrouting connection-mark=thunder-connection \
    disabled=no new-packet-mark=thunder-packs passthrough=yes
add action=mark-connection chain=postrouting comment="(TC 3.1.x)=========\
    ==========================================================================\
    ==================================" content="X-Cache: HIT from proxy.routero-os.com" \
    disabled=no new-connection-mark=proxy-hits passthrough=yes src-address=192.168.10.2\
    protocol=tcp
add action=mark-packet chain=postrouting connection-mark=proxy-hits disabled=\
    no new-packet-mark=proxy-squid passthrough=yes
/queue tree
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
    max-limit=4M name="T-cache_hits" packet-mark=proxy-squid parent=\
    global-out priority=4 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
    max-limit=4M name=ThunderCache packet-mark=thunder-packs parent=\

[josueflat]

estube googleando y encontre esto que creen de lo que dice este tipo sera verdad

Reglas Full-Cache, ThunderCache 3.1.2, Optimizadas.
// Prefiero en lugar de usar estas reglas originales según JOEMG:


ip firewall mangle
add action=mark-connection chain=postrouting comment="THUNDER CACHE FULL(TC 3.\
    1) =======================================================================\
    ===============================" content="X-Cache: HIT from Thunder" \
    disabled=no new-connection-mark=thunder-connection passthrough=yes \
    protocol=tcp src-address=192.168.10.2
add action=mark-packet chain=postrouting connection-mark=thunder-connection \
    disabled=no new-packet-mark=thunder-packs passthrough=yes
add action=mark-connection chain=postrouting comment="TOS 12 (TC 3.1)=========\
    ==========================================================================\
    ==================================" disabled=no dscp=12 \
    new-connection-mark=proxy-hits passthrough=yes protocol=tcp src-address=\
    192.168.10.2
add action=mark-packet chain=postrouting connection-mark=proxy-hits disabled=\
    no new-packet-mark=proxy-squid passthrough=yes



Para hacer full cache usar estas:

en IP>Firewall> Mangle

add action=mark-connection chain=prerouting comment=\
    "MARCO TODO LO QUE SALE DEL CACHE DEL DISCO RIGIDO" content=\
    "X-Cache: HIT" disabled=no new-connection-mark=conn-thunder passthrough=\
    yes
add action=mark-packet chain=prerouting comment="" connection-mark=\
    conn-thunder disabled=no new-packet-mark=CACHE-HIT passthrough=yes
add action=mark-packet chain=prerouting comment=PROXY-TOS connection-mark=\
    conn-thunder disabled=no dscp=12 new-packet-mark=CACHE-HIT passthrough=no
add action=jump chain=prerouting comment="" disabled=no jump-target=\
    "TERMINO DE PROCESAR" packet-mark=CACHE-HIT
add action=accept chain="TERMINO DE PROCESAR" comment="" disabled=no

en Queue tree
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \

    max-limit=0 name=CON_PROXY_FULL packet-mark=CACHE-HIT parent=global-out \
    priority=8 queue=proxy

en Queue type
add kind=pcq name=proxy pcq-classifier="" pcq-limit=50 pcq-rate=0 \
    pcq-total-limit=2000

[ingjaab]

bueno como quiereas por interace o por grupo , si por interface solo en la primera regla de jomelg pones out las interface de cada salida de clientes y nat , nada mas para que no te hagas problemas , ahora si deseas hacerlo por grupo:

Debe ya comienza con volar filter rules chain=forward en su lugar pones chain=input, cambias src-address=192.168.10.0/30 por src-address=192.168.10.2, y mangle chain=postrouting lo cambias por chain=forward y opciones advance pone el addres list las ip que quieres que salga  y nat boorras esto src-address=!192.168.10.2 que no tiene sentido en su lugar pones in - interface = lan ( o wifi ) si tienes mas interfaces copias y pones la
in -interface = ether4