wah masih berlanjut ya tututnya.
wah masih berlanjut ya tututnya.
mantaf banget share-nya agan Doni...
keep share bro......!!
ini hasil murni dr tutor om doni&akang,imer,akbar lana,ubur cumi,siber,kweteng+comot sana sini dan ud running 2 bln lancar jaya mohon koreksi na dr para suhu2 dkk
Ijin bookmark dulu gan, soalnya gi puasa neh... lieur banyakan baca tutor2 yg keren abizz...
adoohh... mantra-mantra ini emang layak untuk dilakoni..
Ini masuikin di mikrotiknya gimana yaa??? masih ga mudeng sayaCode:add comment="MANGLE PROXY" disabled=no down-script= \nip fi na en num=3\r\ \nip proxy set enable=yes\r\ \n" host=192.168.4.2 interval=1s timeout=1s up-script="ip fi na en num=2\r\ \nip fi na dis num=3\r\ \nip proxy set enable=no\r\ \n"
\nip ga di kenal ama mikrotik....
mohon pencerahannya dong....
rules diatas saya pakai untuk 1 line ISP dengan urutan NAT belokin port 80 ke proxy no 3.
mendingan yang LB PCC dari Local pakek classifier src-address ajaHere are what the different field options mean for the purpose of packet matching, these are the fields that will be fed into the hashing algorithm (and, for the purpose of spreading load across links, decide what link a packet will be put on). Remember that a hash function will always produce the same input when it's fed the same output:
* src-address: The source address of a client will always be the same, so all traffic from a particular client will always match the same PCC matcher, and will always be put on the same link.
* dst-address: The destination address of a specific server will always be the same, so all traffic to that server (say, the Mikrotik Wiki) will always match the same PCC matcher, and will always be put on the same link.
* both-addresses: The source and destination IP pair between the same client and server will always be the same, so all traffic between one specific client and a specific server (say, your laptop and the Mikrotik Wiki) will always match the same PCC matcher, and will always be put on the same link.
* src-port: Source ports of clients are usually randomly chosen when the connection is created, so across many connections different source ports will be fed into the hash function, and different PCC matchers will match and traffic will go across different links. However, some client protocols always choose the same source port, and servers behind your router will mostly likely always use the same service port to send traffic back to their clients. A web server behind your router would send most traffic from its HTTP (80) and HTTPS (443) ports, and that traffic would always match the same PCC matcher and would be put on the same link.
* dst-port: Destination ports of clients are usually well defined service ports, all HTTP (80) traffic between your clients and servers on the Internet would always match the same PCC matcher, and would be put on the same link. However, the same clients doing HTTPS (443) traffic could match a different PCC matcher, and would go across a different link.
* both-ports: Since the client port is (usually) randomly chosen, the combination of the two ports is (usually) random and will spread load across links.
* src-address-and-port: Same caveat as src-port.
* dst-address-and-port: Same caveat as dst-port.
* both-addresses-and-ports: This is the most random way to spread traffic across links, since it has the most number of variables.
jadi seperti penggroupan client
jadi gk perlu lagi buat routing static untuk game online atau poker
Last edited by wakumbaba; 12-10-2010 at 03:00.
hmm... enaknya kalo pake tutor ini untuk pembagain bw per client enakan pake apa yah pake Simple Queues atau pake Queue Tree
There are currently 2 users browsing this thread. (0 members and 2 guests)