Friday, December 30, 2005
satuan baru ?
http://juriglinux.blogspot.com/2005/12/kibibyte-hehe-terdengar-lucu.html
Friday, December 23, 2005
BGP analysis
its very nice tool for bgp analysis :
http://bgpinspect.merit.edu
Thursday, December 22, 2005
FWD: Python Creator Guido van Rossum now working at Google
Wah si Guido sekarang kerja untuk Google !
PF
PF (packet filter) OpenBSD diporting ke win32 sehingga bisa run di Windows Env !
Wednesday, December 21, 2005
dimanakah F root dan I root server mirror Indonesia ?
saya traceroute dari server co-location di Jalawave:
----------------------------
> traceroute f.root-servers.net
traceroute to f.root-servers.net (192.5.5.241), 64 hops max, 44 byte packets
1 202.51.232.34 (202.51.232.34) 0.315 ms 0.409 ms 0.527 ms
2 202.51.232.40 (202.51.232.40) 2.107 ms 4.035 ms 2.640 ms
3 202.51.232.217 (202.51.232.217) 2.812 ms 4.564 ms 2.963 ms
4 202.51.232.81 (202.51.232.81) 3.018 ms 27.596 ms 6.075 ms
5 202.51.232.65 (202.51.232.65) 5.807 ms 3.934 ms 7.227 ms
6 202.155.18.133 (202.155.18.133) 84.174 ms 197.697 ms 66.692 ms
7 202.155.0.181 (202.155.0.181) 16.273 ms 75.213 ms 123.386 ms
8 202.155.27.29 (202.155.27.29) 29.233 ms 13.654 ms 14.424 ms
9 202.155.137.233 (202.155.137.233) 12.985 ms * *
10 202.155.7.246 (202.155.7.246) 19.108 ms 14.730 ms 10.009 ms
11 202.93.46.73 (202.93.46.73) 22.245 ms 51.734 ms 22.851 ms
12 212.184.27.237 (212.184.27.237) 436.060 ms 542.829 ms 533.709 ms
13 ams-e4.AMS.NL.net.DTAG.DE (62.154.15.2) 458.495 ms 417.171 ms 422.051 ms
14 * * *
15 f.root-servers.net (192.5.5.241) 619.080 ms 661.207 ms 677.276 ms
> traceroute i.root-servers.net
traceroute to i.root-servers.net (192.36.148.17), 64 hops max, 44 byte packets
1 202.51.232.34 (202.51.232.34) 0.303 ms 0.282 ms 0.412 ms
2 202.51.232.40 (202.51.232.40) 7.500 ms 2.853 ms 5.250 ms
3 202.51.232.217 (202.51.232.217) 18.424 ms 2.337 ms 2.426 ms
4 202.51.232.81 (202.51.232.81) 23.352 ms 2.239 ms 2.097 ms
5 202.51.232.65 (202.51.232.65) 6.809 ms 7.791 ms 3.125 ms
6 202.155.18.133 (202.155.18.133) 6.964 ms 20.684 ms 4.632 ms
7 202.155.0.181 (202.155.0.181) 15.082 ms 17.354 ms 8.242 ms
8 202.155.27.29 (202.155.27.29) 14.287 ms 12.809 ms 9.197 ms
9 202.155.137.233 (202.155.137.233) 11.218 ms 20.514 ms 21.808 ms
10 202.155.7.246 (202.155.7.246) 7.312 ms 9.893 ms 14.765 ms
11 202.93.46.73 (202.93.46.73) 42.181 ms 29.334 ms 28.316 ms
12 212.184.27.237 (212.184.27.237) 805.018 ms 706.079 ms 947.472 ms
13 cixp-gw20.GVA.CH.net.DTAG.DE (62.154.5.122) 489.962 ms 509.809 ms *
14 ge-0-1.r1.gen.dnsnode.net (192.65.185.235) 311.743 ms 343.156 ms 356.474 ms
15 192.36.148.17 (192.36.148.17) 317.398 ms 306.346 ms 305.875 ms
----------------------------------------------------
katanya local node F dan I sudah ada di Indonesia tapi kenyataannya sekarang merujuk ke global node
BIND-9.3.2 release
-------------------------------------
Date: Wed, 21 Dec 2005 15:43:31 +1100
From: Mark Andrews
To: bind-announce at isc dot org
Subject: BIND 9.3.2 is now available.
BIND 9.3.2 is a maintenance release for BIND 9.3.
BIND 9.3.2 can be downloaded from
ftp://ftp.isc.org/isc/bind9/9.3.2/bind-9.3.2.tar.gz
The PGP signature of the distribution is at
ftp://ftp.isc.org/isc/bind9/9.3.2/bind-9.3.2.tar.gz.asc
The signature was generated with the ISC public key, which is
available at
A binary kit for Windows NT 4.0 and Windows 2000 is at
ftp://ftp.isc.org/isc/bind/contrib/ntbind-9.3.2/BIND9.3.2.zip
ftp://ftp.isc.org/isc/bind/contrib/ntbind-9.3.2/BIND9.3.2.debug.zip
The PGP signature of the binary kit for Windows NT 4.0 and Windows 2000 is at
ftp://ftp.isc.org/isc/bind/contrib/ntbind-9.3.2/BIND9.3.2.zip.asc
ftp://ftp.isc.org/isc/bind/contrib/ntbind-9.3.2/BIND9.3.2.debug.zip.asc
A list of changes made since 9.3.0 follows. For earlier changes,
see the file CHANGES in the distribution.
-----------------------------------------------
so guys, if you run BIND, please update your BIND !
press release TEIN2 Project
http://www.tein2.net/server/show/conWebDoc.1630
semoga ITB sukses dng TEIN2 Project !
Tuesday, December 20, 2005
xorp tutorial presentation
nice presentation from Mark Handley
Planet
http://www.planetplanet.org/
rupanya ada juga planet FreeBSD : http://planet.xbsd.org/ dan
masih banyak planet yang lain :-)
ZFS
ZFS, filesystem dari SUN ini tampaknya sangat menjanjikan :-)
sehingga membuat Matt Dillon (DragonflyBSD Project) berjanji
akan segera mem-porting ZFS ke Dragonfly BSD (http://leaf.dragonflybsd.org/mailarchive/kernel/2005-12/msg00040.html)
Protecting SSH from known_hosts Address Harvesting
kayaknya perlu disubmit juga nih known_host server diseluruh itb :-)
OpenSSH cutting edge
----cite----
The upcoming OpenSSH version 4.3 will add support for tunneling. What type of uses is this feature suited for?
Damien Miller: Reyk and Markus' new tunneling support allows you to make a real VPN using OpenSSH without the need for any additional software. This goes well beyond the TCP port forwarding that we have supported for years - each end of a ssh connection that uses the new tunnel support gets a tun(4) interface which can pass packets between them. This is similar to the type of VPN supported by OpenVPN or other SSL-VPN systems, only it runs over SSH. It is therefore really easy to set up and automatically inherit the ability to use all of the authentication schemes supported by SSH (password, public key, Kerberos, etc.)
The tunnel interfaces that form the endpoints of the tunnel can be configured as either a layer-3 or a layer-2 link. In layer-3 mode you can configure the tun(4) interfaces with IP or IPv6 addresses and route packets over them like any other interface - you could even run a dynamic routing protocol like OSPF over them if you were so inclined. In layer-2 mode, you can make them part of a bridge(4) group to bridge raw ethernet frames between the two ends.
A practical use of this might be securely linking back to your home network while connected to an untrusted wireless net, being able to send and receive ICMP pings and to use UDP based services like DNS.
Like any VPN system that uses a reliable transport like TCP, an OpenSSH's tunnel can alter packet delivery dynamics (e.g. a dropped transport packet will stall all tunnelled traffic), so it probably isn't so good for things like VOIP over a lossy network (use IPsec for that), but it is still very useful for most other things.
-----end cite------