Cara Membatasi Upload di MikroTik (Backup Cloud, Google Drive, Sync)

AI Insights

Generate a summary and suggested tags for this post.

Upload sering diabaikan padahal paling sering bikin koneksi mati. Bandwidth ISP mayoritas asimetris (download besar, upload kecil) — jadi kalau upload penuh, download & ping ikut lemot. Solusinya: batasi upload di MikroTik.

Efek Batasi Upload

Kenapa Upload Penuh Bikin Semua Lemot?

TCP butuh ACK dari sisi kita untuk konfirmasi paket. Kalau upload penuh, ACK ketahan — akibatnya:

Ping naik (500ms+)
Download berhenti karena server nunggu ACK
Zoom/Meet putus-putus
Web page loading super lambat

Contoh nyata: PC sedang sync Google Drive 50GB, seluruh kantor mendadak koneksi "putus" — padahal cuma upload yang penuh.

Pilih Metode: Simple Queue vs Queue Tree

Simple Queue → cukup untuk limit per user/IP
Queue Tree → butuh Mangle di chain postrouting (out-interface = WAN)

Mangle Chain Postrouting untuk Upload

Metode 1: Simple Queue

/queue simple
add name="User-Kasir" target=192.168.88.10/32 max-limit=1M/5M

Format upload/download → 1M upload, 5M download. Simple, langsung jalan.

Metode 2: Queue Tree untuk Upload (Advanced)

/ip firewall mangle
add chain=postrouting out-interface=wan1 src-address=192.168.88.0/24 \
    action=mark-packet new-packet-mark=upload-lan passthrough=no

/queue tree
add name=UploadLAN parent=wan1 packet-mark=upload-lan \
    max-limit=10M priority=5

Kenapa parent=wan1 (interface)? Karena upload = trafik keluar MikroTik, harus di-shape di sisi interface WAN.

Metode 3: Batasi Upload Backup Cloud

Google Drive, OneDrive, Dropbox pakai server yang bisa di-address-list:

/ip firewall address-list
add list=cloud-backup address=drive.google.com
add list=cloud-backup address=onedrive.com
add list=cloud-backup address=dropbox.com

/ip firewall mangle
add chain=postrouting dst-address-list=cloud-backup action=mark-packet \
    new-packet-mark=cloud-upload passthrough=no

/queue tree
add name=CloudUpload parent=wan1 packet-mark=cloud-upload max-limit=2M priority=7

Backup jalan pelan-pelan, tidak ganggu meeting.

Rekomendasi Limit per Skenario

Rekomendasi Limit Upload

Kombinasikan dengan Scheduler

Backup boleh full speed setelah jam kerja:

/system scheduler
add name=cloud-fast start-time=18:00:00 interval=1d \
    on-event="/queue tree set CloudUpload max-limit=20M"
add name=cloud-slow start-time=08:00:00 interval=1d \
    on-event="/queue tree set CloudUpload max-limit=2M"

Common Mistake

Kesalahan	Akibat	Solusi
Salah chain (prerouting)	Rule tidak jalan	Pakai postrouting
Salah in/out interface	Rule tidak match	Upload = out-interface WAN
Format max-limit terbalik	Download yang dibatasi	Ingat upload/download
Tidak batasi upload sama sekali	Ping tinggi terus-terusan	Selalu batasi upload

Kesimpulan

Batasi upload di MikroTik = wajib untuk koneksi asimetris (kebanyakan ISP di Indonesia). Cara termudah pakai Simple Queue — cukup atur max-limit upload lebih kecil dari kapasitas ISP (misal ISP 10 Mbps upload → limit 8 Mbps). Untuk advanced, pakai Queue Tree dengan mangle di chain postrouting. Kombinasikan dengan Scheduler biar backup cloud jalan cepat di luar jam kerja.