Minggu, 17 Februari 2013

JEJAK JALUR KERETA API SCS PEKALONGAN - WONOPRINGGO



JEJAK JALUR KERETA API SCS PEKALONGAN - WONOPRINGGO

Jalur Pekalongan – Wonoringgo dibangun oleh perusahaan kereta api belanda SCS(Semarang-Cheribon Stoomtram Maatschappij) dibuka pada tahun 1916 akan tetapi ketika masa pendudukan jepang di indonesia jalur kereta ini di bongkar oleh jepang untuk keperluan perang. sehingga saat ini jalur pekalongan – kedungwuni - wonopringgo sudah lenyap. sebenarnya dipekalongan ada percabangan lain yaitu menuju pelabuhan akan tetapi saya tidak akan membahasnya karena masih ada sisa jalurnya sehingga saya memilih jalur wonopringgo sisanya sudah lenyap.



saya dan teman saya bermaksud untuk mencari jejak jalur tersebut. teman saya mendapat informasi dari orang tua nya yang tinggal di desa gembong tentang lokasi bekas stasiun kedungwuni yang sekarang sudah menjadi kantor notaris PPATK berikut ini fotonya:

tampak depan  



      tampak samping






bangunan difoto tersebut bukanlah bangunan stasiun kedungwuni karena stasiun kedungwuni sudah dibongkar dan kemudian dibangun bangunan seperti diatas.
selain itu didaerah bekas rel biasanya dinamai sepuran sebagai contoh desa gembong sepuran, paesan sepuran, ambokembang sepuran dan pekajangan sepuran. tanah dan rumah didaerah tersebut masih milik PT. KAI saya sempat menanyakan pada salah satu teman yang tinggal didesa pekajangan sebelah barat PT. PISMATEX tentang sertifikat tanah dan teman saya menjawab bahwa tanah didaerah tersebut masih sengketa (bukan hak milik).


desa gembong sepuran


desa paesan / selaos


desa ambokembang sepuran


desa pekajangan sepuran (samping PT. PISMATEX )









selain itu ada bukti yang masih ada yaitu tiang jembatan di sungai cakra. bangunan ini menjadi satu-satunya bangunan yang tersisa.



kemudian bekas bangunan jembatan yang lain yang saya temukan didesa kedungpatangewu.

kemudian melintasi perkebunan tebu yang sekarang dijadikan jalan setapak.



jalan setapak ini banyak ditemukan kerikil/kricak yang biasa digunakan untuk membangun jalur kereta api.

setelah melintasi perkebunan tebu jalur ini melintasi jalan raya kedungwuni – kajen melewati belakang pasar wonopringgo. stasiun wonopringgo sekarang sudah tak berbekas namun saya sempat menanyakan pada orang sekitar bahwa letak stasiun wonopringgo adalah yang saat ini menjadi asrama militer Batalyon Kompi Senapan C 407 wonopringgo.



bukti – bukti lain

bangunan bekas jembatan didaerah pekajangan


jembatan di deerah pekajangan, jembatan ini cukup besar mengingat jalan yang ada hanya jalan setapak yang tidak bisa dilewati mobil


jembatan didaerah perum binagria






Info Stasiun Dan Halte Jalur Pekalongan – Wonopringgo

Ket:
S = Stasiun
H = Halte
+ = Sudah Tidak Aktif/Mati
beginilah jalurnya (lewat google map).







 demikianlah hasil dari penelusuran saya dan teman saya, artikel ini dibuat agar sejarah kereta api dari pekalongan ke wonopringgo tidak hilang termakan zaman mengingat bekas bangunan dan relnya sudah hilang.

Minggu, 17 Juni 2012

EIGRP



Router>en
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#hostname austin
austin(config)#int fa0/0
austin(config-if)#ip add 172.16.10.1 255.255.255.0
austin(config-if)#n shu

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up

austin(config-if)#ex
austin(config)#int s2/0
austin(config-if)#ip add 172.16.20.1 255.255.255.0
austin(config-if)#n shu

%LINK-5-CHANGED: Interface Serial2/0, changed state to down
austin(config-if)#ex
austin(config)#rou eigrp 10
austin(config-router)#network 172.16.10.0 0.0.0.255
austin(config-router)#network 172.16.20.0 0.0.0.255
austin(config-router)#network 172.16.30.0 0.0.0.255
austin(config-router)#
%LINK-5-CHANGED: Interface Serial2/0, changed state to up

Router>en
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#hostname houston
houston(config)#int fa0/0
houston(config-if)#ip add 172.16.30.1 255.255.255.0
houston(config-if)#n shu

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up

houston(config-if)#ex
houston(config)#int s3/0
houston(config-if)#ip add 172.16.20.2 255.255.255.0
houston(config-if)#clock rate 64000
houston(config-if)#n shu


%LINK-5-CHANGED: Interface Serial3/0, changed state to up
houston(config-if)#ex
houston(config)#rou eigrp 10
houston(config-router)#network 172.16.10.0 0.0.0.255
houston(config-router)#network 172.16.20.0 0.0.0.255
houston(config-router)#
%DUAL-5-NBRCHANGE: IP-EIGRP 10: Neighbor 172.16.20.1 (Serial3/0) is up: new adjacency
houston(config-router)#network 172.16.30.0 0.0.0.255
houston(config-router)#

ip pc 1 = 172.16.10.10
subnet mask = 255.255.255.0
gateway = 172.16.10.1

ip pc 2 = 172.16.30.30
subnet mask = 255.255.255.0
gateway = 172.16.30.1


ping dari pc 1 ke pc 2
ping ke 172.16.30.30

ping dari pc2 ke pc1
ping 172.16.10.10



Minggu, 27 Mei 2012

Topologi Jaringan TELNET


ROUTER1:

Router>en
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#int fa0/0
Router(config-if)#ip add 172.16.3.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
Router(config-if)#exit
Router(config)#int ser2/0
Router(config-if)#ip add 172.16.2.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface Serial2/0, changed state to down
Router(config-if)#exit
Router(config)#ip route 192.168.0.0 255.255.252.0 ser2/0
Router(config)#ip route 172.16.1.0 255.255.255.0 ser2/0
Router(config)#exit

ROUTER2:

Router>en
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#int fa0/0
Router(config-if)#ip add 172.16.1.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
Router(config-if)#exit
Router(config)#int ser3/0
Router(config-if)#ip add 172.16.2.2 255.255.255.0
Router(config-if)#clock rate 64000
Router(config-if)#no shut

Router(config-if)#
%LINK-5-CHANGED: Interface Serial3/0, changed state to up
Router(config-if)#exit
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/0, changed state to up
Router(config)#int ser2/0
Router(config-if)#ip add 192.168.1.2 255.255.255.0
Router(config-if)#clock rate 64000
Router(config-if)#no shut

%LINK-5-CHANGED: Interface Serial2/0, changed state to down
Router(config-if)#exit
Router(config)#
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#ip route 172.16.3.0 255.255.255.0 ser3/0
Router(config)#ip route 192.168.2.0 255.255.255.0 ser2/0
Router(config)#exit

ROUTER3

Router>en
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#int fa0/0
Router(config-if)#ip add 192.168.2.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
Router(config-if)#exit
Router(config)#int ser3/0
Router(config-if)#ip add 192.168.1.1 255.255.255.0
Router(config-if)#no shut

%LINK-5-CHANGED: Interface Serial3/0, changed state to up
Router(config-if)#exit
Router(config)#
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#ip route 172.16.0.0 255.255.252.0 ser3/0
Router(config)#exit
Router#


hasil CMD:

Packet Tracer PC Command Line 1.0
PC>ping 192.168.2.2

Pinging 192.168.2.2 with 32 bytes of data:

Request timed out.
Reply from 192.168.2.2: bytes=32 time=187ms TTL=125
Reply from 192.168.2.2: bytes=32 time=187ms TTL=125
Reply from 192.168.2.2: bytes=32 time=174ms TTL=125

Ping statistics for 192.168.2.2:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 174ms, Maximum = 187ms, Average = 182ms

PC>ping 172.16.2.2

Pinging 172.16.2.2 with 32 bytes of data:

Reply from 172.16.2.2: bytes=32 time=94ms TTL=254
Reply from 172.16.2.2: bytes=32 time=94ms TTL=254
Reply from 172.16.2.2: bytes=32 time=78ms TTL=254
Reply from 172.16.2.2: bytes=32 time=93ms TTL=254

Ping statistics for 172.16.2.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 78ms, Maximum = 94ms, Average = 89ms

PC>ping 172.16.2.1

Pinging 172.16.2.1 with 32 bytes of data:

Reply from 172.16.2.1: bytes=32 time=63ms TTL=255
Reply from 172.16.2.1: bytes=32 time=62ms TTL=255
Reply from 172.16.2.1: bytes=32 time=62ms TTL=255
Reply from 172.16.2.1: bytes=32 time=49ms TTL=255

Ping statistics for 172.16.2.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 63ms, Average = 59ms

PC>ping 172.16.1.2

Pinging 172.16.1.2 with 32 bytes of data:

Reply from 172.16.1.2: bytes=32 time=93ms TTL=254
Reply from 172.16.1.2: bytes=32 time=94ms TTL=254
Reply from 172.16.1.2: bytes=32 time=94ms TTL=254
Reply from 172.16.1.2: bytes=32 time=93ms TTL=254

Ping statistics for 172.16.1.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 93ms, Maximum = 94ms, Average = 93ms

PC>ping 172.16.1.1

Pinging 172.16.1.1 with 32 bytes of data:

Reply from 172.16.1.1: bytes=32 time=94ms TTL=254
Reply from 172.16.1.1: bytes=32 time=93ms TTL=254
Reply from 172.16.1.1: bytes=32 time=94ms TTL=254
Reply from 172.16.1.1: bytes=32 time=78ms TTL=254

Ping statistics for 172.16.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 78ms, Maximum = 94ms, Average = 89ms

PC>ping 172.16.2.1

Pinging 172.16.2.1 with 32 bytes of data:

Reply from 172.16.2.1: bytes=32 time=62ms TTL=255
Reply from 172.16.2.1: bytes=32 time=63ms TTL=255
Reply from 172.16.2.1: bytes=32 time=47ms TTL=255
Reply from 172.16.2.1: bytes=32 time=62ms TTL=255

Ping statistics for 172.16.2.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum = 63ms, Average = 58ms

PC>ping 172.16.2.2

Pinging 172.16.2.2 with 32 bytes of data:

Reply from 172.16.2.2: bytes=32 time=93ms TTL=254
Reply from 172.16.2.2: bytes=32 time=94ms TTL=254
Reply from 172.16.2.2: bytes=32 time=94ms TTL=254
Reply from 172.16.2.2: bytes=32 time=93ms TTL=254

Ping statistics for 172.16.2.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 93ms, Maximum = 94ms, Average = 93ms

PC>ping 172.16.3.1

Pinging 172.16.3.1 with 32 bytes of data:

Reply from 172.16.3.1: bytes=32 time=63ms TTL=255
Reply from 172.16.3.1: bytes=32 time=58ms TTL=255
Reply from 172.16.3.1: bytes=32 time=63ms TTL=255
Reply from 172.16.3.1: bytes=32 time=47ms TTL=255

Ping statistics for 172.16.3.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum = 63ms, Average = 57ms

PC>ping 172.16.3.2

Pinging 172.16.3.2 with 32 bytes of data:

Reply from 172.16.3.2: bytes=32 time=0ms TTL=128
Reply from 172.16.3.2: bytes=32 time=15ms TTL=128
Reply from 172.16.3.2: bytes=32 time=16ms TTL=128
Reply from 172.16.3.2: bytes=32 time=16ms TTL=128

Ping statistics for 172.16.3.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 16ms, Average = 11ms

PC>