<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-3702593834630851973</id><updated>2011-04-21T11:37:46.859-07:00</updated><title type='text'>Agus Priyo</title><subtitle type='html'>welcome my blog</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>11</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-8621952112721498449</id><published>2008-12-26T21:09:00.000-08:00</published><updated>2008-12-26T21:21:27.905-08:00</updated><title type='text'>PPP on Linux</title><summary type='text'>On Linux, PPP functionality is split into two parts: a kernel component that handles the low-level protocols (HDLC, IPCP, IPXCP, etc.) and the user space pppd daemon that handles the various higher-level protocols, such as PAP and CHAP. The current release of the PPP software for Linux contains the PPP daemon pppd and a program named chat that automates the dialing of the remote system.The PPP </summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/8621952112721498449/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=8621952112721498449' title='1 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/8621952112721498449'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/8621952112721498449'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/ppp-on-linux.html' title='PPP on Linux'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-7740150749064532983</id><published>2008-12-26T20:50:00.000-08:00</published><updated>2008-12-26T21:22:23.818-08:00</updated><title type='text'>All About ifconfig</title><summary type='text'>There are many more parameters to ifconfig than we have described so far. Its normal invocation is this:ifconfig interface [address [parameters]]interface is the interface name, and address is the IP address to be assigned to the interface. This may be either an IP address in dotted quad notation or a name that ifconfig will look up in /etc/hosts. If ifconfig is invoked with only the interface </summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/7740150749064532983/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=7740150749064532983' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/7740150749064532983'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/7740150749064532983'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/all-about-ifconfig.html' title='All About ifconfig'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-8249637364905188319</id><published>2008-12-26T20:39:00.000-08:00</published><updated>2008-12-26T20:45:37.854-08:00</updated><title type='text'>Interface Configuration for IP</title><summary type='text'>After setting up your hardware as explained in Chapter 4, Configuring the Serial Hardware, you have to make these devices known to the kernel networking software. A couple of commands are used to configure the network interfaces and initialize the routing table. These tasks are usually performed from the network initialization script each time you boot the system. The basic tools for this process</summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/8249637364905188319/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=8249637364905188319' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/8249637364905188319'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/8249637364905188319'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/interface-configuration-for-ip.html' title='Interface Configuration for IP'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-961336860011437263</id><published>2008-12-26T20:31:00.000-08:00</published><updated>2008-12-26T20:38:05.677-08:00</updated><title type='text'>Writing hosts and networks Files</title><summary type='text'>After you have subnetted your network, you should prepare for some simple sort of hostname resolution using the /etc/hosts file. If you are not going to use DNS or NIS for address resolution, you have to put all hosts in the hosts file. Even if you want to run DNS or NIS during normal operation, you should have some subset of all hostnames in /etc/hosts. You should have some sort of name </summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/961336860011437263/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=961336860011437263' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/961336860011437263'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/961336860011437263'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/writing-hosts-and-networks-files.html' title='Writing hosts and networks Files'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-8448930203034264270</id><published>2008-12-26T20:24:00.000-08:00</published><updated>2008-12-26T20:30:31.057-08:00</updated><title type='text'>IP Addresses</title><summary type='text'>As mentioned in Chapter 1, Introduction to Networking, the IP networking protocol understands addresses as 32-bit numbers. Each machine must be assigned a number unique to the networking environment.[1] If you are running a local network that does not have TCP/IP traffic with other networks, you may assign these numbers according to your personal preferences. There are some IP address ranges that</summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/8448930203034264270/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=8448930203034264270' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/8448930203034264270'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/8448930203034264270'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/ip-addresses.html' title='IP Addresses'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-7109994124454943183</id><published>2008-12-26T20:18:00.000-08:00</published><updated>2008-12-26T20:20:28.096-08:00</updated><title type='text'>Linux Networking</title><summary type='text'>As it is the result of a concerted effort of programmers around the world, Linux wouldn't have been possible without the global network. So it's not surprising that in the early stages of development, several people started to work on providing it with network capabilities. A UUCP implementation was running on Linux almost from the very beginning, and work on TCP/IP-based networking started </summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/7109994124454943183/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=7109994124454943183' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/7109994124454943183'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/7109994124454943183'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/linux-networking.html' title='Linux Networking'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-1824873795364365899</id><published>2008-12-26T20:14:00.000-08:00</published><updated>2008-12-26T20:17:25.722-08:00</updated><title type='text'>UUCP Networks</title><summary type='text'>Unix-to-Unix Copy (UUCP) started out as a package of programs that transferred files over serial lines, scheduled those transfers, and initiated execution of programs on remote sites. It has undergone major changes since its first implementation in the late seventies, but it is still rather spartan in the services it offers. Its main application is still in Wide Area Networks, based on periodic </summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/1824873795364365899/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=1824873795364365899' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/1824873795364365899'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/1824873795364365899'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/uucp-networks.html' title='UUCP Networks'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-9144390986122797257</id><published>2008-12-26T20:11:00.000-08:00</published><updated>2008-12-26T20:14:02.470-08:00</updated><title type='text'>The User Datagram Protocol</title><summary type='text'>Of course, TCP isn't the only user protocol in TCP/IP networking. Although suitable for applications like rlogin, the overhead involved is prohibitive for applications like NFS, which instead uses a sibling protocol of TCP called UDP, or User Datagram Protocol. Just like TCP, UDP allows an application to contact a service on a certain port of the remote machine, but it doesn't establish a </summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/9144390986122797257/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=9144390986122797257' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/9144390986122797257'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/9144390986122797257'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/user-datagram-protocol.html' title='The User Datagram Protocol'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-3215931741063011326</id><published>2008-12-26T19:52:00.000-08:00</published><updated>2008-12-26T20:11:33.664-08:00</updated><title type='text'>The Transmission Control Protocol</title><summary type='text'>Sending datagrams from one host to another is not the whole story. If you log in to quark, you want to have a reliable connection between your rlogin process on erdos and the shell process on quark. Thus, the information sent to and fro must be split up into packets by the sender and reassembled into a character stream by the receiver. Trivial as it seems, this involves a number of complicated </summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/3215931741063011326/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=3215931741063011326' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/3215931741063011326'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/3215931741063011326'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/transmission-control-protocol.html' title='The Transmission Control Protocol'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-7716328432574084948</id><published>2008-12-26T19:49:00.000-08:00</published><updated>2008-12-26T20:07:13.749-08:00</updated><title type='text'>Ethernets</title><summary type='text'>The most common type of LAN hardware is known as Ethernet. In its simplest form, it consists of a single cable with hosts attached to it through connectors, taps, or transceivers. Simple Ethernets are relatively inexpensive to install, which together with a net transfer rate of 10, 100, or even 1,000 Megabits per second, accounts for much of its popularity.Ethernets come in three flavors: thick, </summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/7716328432574084948/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=7716328432574084948' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/7716328432574084948'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/7716328432574084948'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/ethernets.html' title='Ethernets'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3702593834630851973.post-5189950961434766383</id><published>2008-12-26T19:43:00.001-08:00</published><updated>2008-12-26T20:04:37.320-08:00</updated><title type='text'>TCP IP Networks</title><summary type='text'>Modern networking applications require a sophisticated approach to carrying data from one machine to another. If you are managing a Linux machine that has many users, each of whom may wish to simultaneously connect to remote hosts on a network, you need a way of allowing them to share your network connection without interfering with each other. The approach that a large number of modern </summary><link rel='replies' type='application/atom+xml' href='http://aguspriyo.blogspot.com/feeds/5189950961434766383/comments/default' title='Poskan Komentar'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3702593834630851973&amp;postID=5189950961434766383' title='0 Komentar'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/5189950961434766383'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3702593834630851973/posts/default/5189950961434766383'/><link rel='alternate' type='text/html' href='http://aguspriyo.blogspot.com/2008/12/modern-networking-applications-require.html' title='TCP IP Networks'/><author><name>priyoutomo</name><uri>http://www.blogger.com/profile/00439655003586250253</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
