Testing Dummynet di FreeBSD 4.x.

Perobaan beberapa algoritma limiter "prob" & "queue"  Spek komputer router: - AMD Athlon 750 Mhz. - Memory 256 M. - ...

Perobaan beberapa algoritma limiter "prob" & "queue"

 Spek komputer router:
- AMD Athlon 750 Mhz.
- Memory 256 M.
- Ethernet xl0 100baseTX <full-duplex>.
- Ethernet rl0 100baseTX <full-duplex>.

Spek komputer client:
- AMD 1.2 Duron Ghz.
- Ethernet SIS 10/100.
- Memory 128 M.

Periperal lainnya:
- Swith Compax 16 port.
- UTP Cat-5 (Panjang kabel yg dipakai kira2 78 M).
Sistem Operasi:
- FreeBSD 4.10-Stable.
- Windows XP Proffesional.

Traffic shapper dengan menggunakan "prob"
-----------------------------------------
Traffic shapper yg dipake adalah "Dummynet", di router dilakukan
pembatasan [/etc/rc.firewall] dengan rule set sbb:

${fwcmd} add 1 pipe 1 ip from ${router} to ${client1}
${fwcmd} pipe 1 config bw 64Kbit/s......(1)

${fwcmd} add prob 0.5 pipe 1 ip from ${router} to ${client1}
${fwcmd} pipe 1 config bw 64Kbit/s......(2)

${fwcmd} add prob 0.1 pipe 1 ip from ${router} to ${client1}
${fwcmd} pipe 1 config bw 64Kbit/s......(3)

${fwcmd} add prob 0.9 pipe 1 ip from ${router} to ${client1}
${fwcmd} pipe 1 config bw 64Kbit/s......(4)

Hasil yg didapat secara berurutan:
1. 64Kbit/s =
8 KByte/s => tanpa prob (default prob = 1)
2. 64Kbit/s = 16 KByte/s => prob 0.5
3. 64Kbit/s = 80 KByte/s => prob 0.1
4. 64Kbit/s =
9 KByte/s => prob 0.9

Kesimpulan: Makin besar nilei "prob", makin besar (mendekati 1) droping

paketnya. Makin kecil nilei "prob", makin kecil droping

paketnya.

Hitunganya menggunakan perbandingan terbalik:

Jika prob = 1, maka bw yg didapatkan = 8 KByte/s

Jika prob = 0.5, make bw yg didapatkan = 2 * 8 KByte/s = 16 KByte/s

Jika prob = 0.1, maka bw yg didapatkan = 10 * 8 KByte/s = 80 KByte/s


Traffic shapper dengan menggunakan "queuering" mekanism.
-------------------------------------------------------
Di file yg sama (/etc/rc.firewall), saya buat rule set
untuk nge-limit outbound saja sbb:

${fwcmd} add 1
queue 1 ip from ${router} to ${client-1} via ${eth_1}
${fwcmd} add 2
queue 2 ip from ${router} to ${client-2} via ${eth_1}
${fwcmd} queue 1 config pipe 100 weight 80
${fwcmd} queue 2 config pipe 100 weight 80
${fwcmd} pipe 100 config bw 128Kbit/s

Saya melakukan limiting di router dengan sistem share (ratio)
antara 2 host komputer:
- client-1 mendapatkan extra bandwidth dibanding client-2 karena

${no_queue}-nya lebih besar dibanding client-2.

Saya rubah rule set di /etc/rc.firewall sbb:

${fwcmd} add 1
queue 2 ip from ${router} to ${client-1} via ${eth_1}
${fwcmd} add 2
queue 2 ip from ${router} to ${client-2} via ${eth_1}
${fwcmd} queue 2 config pipe 100 weight 80
${fwcmd} pipe 100 config bw 128Kbit/s

Hasilnya:
- Meskipun pas reloading firewall ada message errors "ipfw:

setsockopt(IP_DUMMYNET_CONFIGURE): Invalid argument" tp _kelihatannya_

bisa jalan.
- client-1 dan client-2 mendapatkan bandwidth yg sama besar, jika

client-1 atau client-2 tidak ada aktifitas maka bandwidth-nya jatuh

ke salah satu client-1 dan client-2


Ternyata setelah diganti ${no_queue} => 3 sptnya tidak ada error message lagi.
belom tahu knp bisa gini. Mustinya untuk ${no_queue} mulai dari
_harusnya_ tidak ada masalah.

Aturan syntax yg bisa saya tangkap sbb:
1. Urutan rule musti

- [...ip from...]

- [...queue 1 config pipe...]

- [...pipe 100 config...]
2. Di rule [...ip from...] boleh menggunakan "queue ${no_queue}"

yg sama asalkan rule selanjutnya berbeda dan nileinya musti

lebih besar dari "3".
3. ${no_queue} di rule [...ip from...] boleh sama nileinya dengan

${no_queue} di rule [...queue 1 config pipe...]
4. ${no_queue} di [...queue 1 config pipe...] harus lebih besar dari

${no_queue} di [...ip from...] atau paling kecil nileinya 3.
5. Makin besar nilei ${no_queue} di [...ip from...] maka rule itu yg

diprioritaskan (Dpt bandwidth lebih besar)

Kesimpulan:
- Untuk "prob" bisa di-implementasikan sesuei dengan kebutuhan.
- Sistem spt ini tidak bisa digunakan di warnet dilihat dari

kenyamanan speed links yg bisa tarik menarik seusai dengan ratio jika

queue di-implementasikan. Mungkin dengan quering base on service bisa

dilakukan di warnet. Tetapi dengan hardling limit juga sebetulnya

sudah cukup untuk sebuah warnet.
- Jika perlu feature algorithm (ex: CIR/Burstable) yg lebih spt ALTQ lebih

bisa diharapkan. Kalo ada duit ya pake "ETenv" (Bandwidth Manager)

seharga USD 700 ;p.

Mungkin ada saran/input, sangat welcome banget. Silahkan kirimkan ke
 [email protected] .

COMMENTS

Name

Application Support,19,database server,1,Desktop/XWindow,1,DNS Server,2,Email Server,3,FTP Server,2,General,2,Kernel,2,Networking,8,Proxy Server,4,Security,6,Tips and Trick,5,Web Server,2,
ltr
item
IndoFreeBSD: Testing Dummynet di FreeBSD 4.x.
Testing Dummynet di FreeBSD 4.x.
https://2.bp.blogspot.com/-i9s9QqVonPs/VOt3rfaeLRI/AAAAAAAAAIw/Gy64yUu85BI/s1600/dummynet.gif
https://2.bp.blogspot.com/-i9s9QqVonPs/VOt3rfaeLRI/AAAAAAAAAIw/Gy64yUu85BI/s72-c/dummynet.gif
IndoFreeBSD
https://www.indofreebsd.or.id/2015/02/testing-dummynet-di-freebsd-4x.html
https://www.indofreebsd.or.id/
https://www.indofreebsd.or.id/
https://www.indofreebsd.or.id/2015/02/testing-dummynet-di-freebsd-4x.html
true
1901051463523757307
UTF-8
Loaded All Posts Not found any posts VIEW ALL Readmore Reply Cancel reply Delete By Home PAGES POSTS View All RECOMMENDED FOR YOU LABEL ARCHIVE SEARCH ALL POSTS Not found any post match with your request Back Home Sunday Monday Tuesday Wednesday Thursday Friday Saturday Sun Mon Tue Wed Thu Fri Sat January February March April May June July August September October November December Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec just now 1 minute ago $$1$$ minutes ago 1 hour ago $$1$$ hours ago Yesterday $$1$$ days ago $$1$$ weeks ago more than 5 weeks ago Followers Follow THIS PREMIUM CONTENT IS LOCKED STEP 1: Share to a social network STEP 2: Click the link on your social network Copy All Code Select All Code All codes were copied to your clipboard Can not copy the codes / texts, please press [CTRL]+[C] (or CMD+C with Mac) to copy Table of Content