DNS Speedy anti pornografi

Bagi pelanggan setia telkomspeedy, mungkin banyak yang bingung DNS berapa yang dipakai buat koneksi internet anda. Ada beberapa hal yang bisa koneksi internet lemot, diantaranya seting DNS yang kurang tepat. Berikut ini bang installer akan menguraikan sedikit tips seputar DNS speedy, DNS anti pornografi, dan open DNS.

Beikut ini daftar DNS TELKOM berdasarkan daerah:

DNS Telkomspeedy Nasional

ns1.telkom.net.id
203.130.196.6

ns2.telkom.net.id
222.124.204.34

DNS Telkomspeedy berdasarkan daerah

Jakarta
nsjkt1.telkom.net.id
202.134.0.155

nsjkt2.telkom.net.id
203.130.196.5

nsjkt3.telkom.net.id
203.130.196.155

Bandung
nsbdg1.telkom.net.id
202.134.2.5

Surabaya
nssby1.telkom.net.id
202.134.1.10

Batam
nsbtm1.telkom.net.id
203.130.193.74

nsbtm2.telkom.net.id
61.94.230.13

Semarang
nssmg1.telkom.net.id
203.130.208.18

Medan
nsmdn1.telkom.net.id
203.130.206.250

DNS filter anti pornografi
DNS AWARI (Asosiasi Warung Internet Indonesia)
203.34.118.10 (primary)
203.34.118.12 (secondary)

DNS Nawala
180.131.144.144 (primary)
180.131.145.145 (secondary)

Open DNS (DNS luar)
208.67.220.220
208.67.222.222

Ada banyak sumber tulisan posting di web tentang IP DNS. Ada yang bilang DNS Jakarta 202.134.0.155 yang paling cepet. Beberapa sumber lain mengatakan hal yang berbeda. Bahkan ada yang merekomendasikan IP DNS non-speedy, atau dengan kata lain DNS Server milik perusahaan lain. Untuk hal ini saya kurang setuju, baik dari segi legalitas, maupun kecepatan (setelah melalui proses cek).
Kalaupun pengen pake DNS luar, mending pake Open DNS yang lumayan cepet dan memang benar-benar gratis. Saya sendiri pakai DNS ini di sisi klien sebagai secondary DNS, tentu dengan primary-dns tetep pake punya speedy. Sekedar sebagai backup, hasilnya cukup lumayan. Meski lebih lemot dari IP Telkom, OpenDNS jarang mengalami time-out.
reff from : http://pc-installer.blogspot.com/2010/01/dns-speedy-anti-pornografi.html

Kartu Hilang , dah bayar tetep ngak bisa ngeprint (card2005)

update stdacd
set sta_rcv1_d=13-Mar-2006
where sta_num='PG05040080' /

Paket Flow in Mikrotik its very important

MikroTik RouterOS is designed to be easy to operate in various aspects of network configuration. Therefore creating limitation for individual IP or natting internal clients to a public address or Hotspot configuration can be done without the knowledge about how the packets are processed in the router - you just go to corresponding menu and create necessary configuration.

As it was impossible to get everything in one diagram, Packet flow diagram for Mikrotik RouterOS v3.x was created in 2 parts:

• Bridging or Layer-2 (MAC) where Routing part is simplified to one “Layer-3″ box
• Routing or Layer-3 (IP) where Bridging part is simplified to one “Bridging” box

Analysis

Basic Concepts

- starting point in packets way thought the router facilities. It does not matter what interface (physical or virtual) packet is received it will start its way from here.

- last point in packets way thought the router facilities. Just before the packet is actually sent out.

- last point in packets way to router itself, after this packet is discarded

- starting point for packets generated by router itself

Configurable Facilities

Each and every facilities in this section corresponds with one particular menu in RouterOS. Users are able to access those menu and configure these facilities directly
- /ip firewall connection tracking

- /ip firewall filter

- /ip firewall nat

- /ip firewall mangle

- /queue simple and /queue tree

- /ip ipsec policy

- /ip accounting

- /interface bridge settings - available only for traffic that go thought the bridge. For all other traffic default value is Yes

- /interface bridge filter

- /interface bridge nat

Automated processes and decisions

- check if the actual input interface is a port for bridge OR checks if input interface is bridge

- allow to capture traffic witch otherwise would be discarded by connection tracking - this way our Hotspot feature are able to provide connectivity even if networks settings are in complete mess

- bridge goes thought the MAC address table in order to find a match to destination MAC address of packet. When match is found - packet will be send out via corresponding bridge port. In case of no match - multiple copies of packet will be created and packet will be sent out via all bridge ports

- this is a workaround, allows to use “out-bridge-port” before actual bridge decision.

- router goes thought the route n order to find a match to destination IP address of packet. When match is found - packet will be send out via corresponding port or to the router itself . In case of no match - packet will be discarded.

- this is a workaround that allows to set-up policy routing in mangle chain output

- indicates exact place where Time To Live (TTL) of the routed packet is reduced by 1. If it become 0 packet will be discarded

- self explainatory

- check if the actual output interface is a port for bridge OR checks if output interface is bridge

- undo all that was done by hotspot-in for the packets that is going back to client.

Examples

Bridging with use-ip-firewall=yes

Routing - from Ethernet to Ethernet interface

Routing from one Bridge interface to different Bridge interface

IPsec encryption

IPsec decryption

reff from : http://blog.nuxer.net/2009/06/12/paket-flow-in-mikrotik/

Paket Flow in Mikrotik its very important

MikroTik RouterOS is designed to be easy to operate in various aspects of network configuration. Therefore creating limitation for individual IP or natting internal clients to a public address or Hotspot configuration can be done without the knowledge about how the packets are processed in the router - you just go to corresponding menu and create necessary configuration.

As it was impossible to get everything in one diagram, Packet flow diagram for Mikrotik RouterOS v3.x was created in 2 parts:

• Bridging or Layer-2 (MAC) where Routing part is simplified to one “Layer-3″ box
• Routing or Layer-3 (IP) where Bridging part is simplified to one “Bridging” box

Analysis

Basic Concepts

- starting point in packets way thought the router facilities. It does not matter what interface (physical or virtual) packet is received it will start its way from here.

- last point in packets way thought the router facilities. Just before the packet is actually sent out.

- last point in packets way to router itself, after this packet is discarded

- starting point for packets generated by router itself

Configurable Facilities

Each and every facilities in this section corresponds with one particular menu in RouterOS. Users are able to access those menu and configure these facilities directly
- /ip firewall connection tracking

- /ip firewall filter

- /ip firewall nat

- /ip firewall mangle

- /queue simple and /queue tree

- /ip ipsec policy

- /ip accounting

- /interface bridge settings - available only for traffic that go thought the bridge. For all other traffic default value is Yes

- /interface bridge filter

- /interface bridge nat

Automated processes and decisions

- check if the actual input interface is a port for bridge OR checks if input interface is bridge

- allow to capture traffic witch otherwise would be discarded by connection tracking - this way our Hotspot feature are able to provide connectivity even if networks settings are in complete mess

- bridge goes thought the MAC address table in order to find a match to destination MAC address of packet. When match is found - packet will be send out via corresponding bridge port. In case of no match - multiple copies of packet will be created and packet will be sent out via all bridge ports

- this is a workaround, allows to use “out-bridge-port” before actual bridge decision.

- router goes thought the route n order to find a match to destination IP address of packet. When match is found - packet will be send out via corresponding port or to the router itself . In case of no match - packet will be discarded.

- this is a workaround that allows to set-up policy routing in mangle chain output

- indicates exact place where Time To Live (TTL) of the routed packet is reduced by 1. If it become 0 packet will be discarded

- self explainatory

- check if the actual output interface is a port for bridge OR checks if output interface is bridge

- undo all that was done by hotspot-in for the packets that is going back to client.

Examples

Bridging with use-ip-firewall=yes

Routing - from Ethernet to Ethernet interface

Routing from one Bridge interface to different Bridge interface

IPsec encryption

IPsec decryption

rerr from : http://blog.nuxer.net/2009/06/12/paket-flow-in-mikrotik/