handbook,.

Surf in marocco,..

noreply@blogger.com (fakrule bromo) — Fri, 24 Jul 2009 00:30:00 -0700

Morocco? There's no surf in marocco! Really? Check again! Just because the name is not on the surf map, doesn't mean they can't throw a serous 46ft right-hander (even if you gotta face the snake charmer first). And the would be the reason why this flick by pete matthew is titled "Under The Radar". Starting from morocco point break with Mikala Jones, Josh Mulcoy, we then take a big leap to the latest newly discovered surf destination: Mentawai, with a serious session featuring Indo's big guns like Rizal Tanjung, Bol, and Wayan "betet" Merta before cruising back to South Africa to see what Kelly slater can do on 2ft surf. Nice side imagery too, When women in Burkhas in Marocco markets to the hectic back streets of Kuta.

Two different sides of the world fused into an enjoyable surf movie. At least this will help you quench your thirst for riding some waves - something difficult to find with all this crappy weather lately.

EasyHotspot,..

noreply@blogger.com (fakrule bromo) — Mon, 20 Jul 2009 22:13:00 -0700

1. Overview

EasyHotspot is a hotspot billing system, based on OpenSource Technology. EasyHotspot use
Linux as it's operating system, FreeRadius as RADIUS server and PHP MySQL APACHE
trio for LAMP architecture.
EasyHotspot providing pre-configured billing system with web based administration that
readily get action with very minimum effort.
2. Hardware Recruitments
To build a hotspot system using EasyHotspot, you need :
1. PC with minimal spec :
■ Pentium 3 or equal
■ 256 MB RAM
■ 5 GB Free Space HDD
■ 2 network interface (LAN CARD)
■ 1 Wireless Access Point(you don't need wireless router feature but a Wireless AP)
■ Switch/Hub (optional, only for wired user)
3. Installing EasyHotspot
Installing Easyhotspot is easy, just boot up your PC using EasyHotspot CD, and then follow the
instructions. Since EasyHotspot using Xubuntu distro, you can see the installation details at
Xubuntu Documentation.
4. Configuring EasyHotspot
1. Editing Company Info
Easyhotspot Comes with Company Info editable feature. To edit the company info, please
edit the /var/www/system/application/config/easyhotspot.php . Edit the entries according to
your real condition.
2. Setting Language
For now EasyHotspot only support two language (English and Bahasa), you could add your
language by helping us translate it to another language (please send your email to me).
edit the /var/www/system/application/config/config.php
$config['language'] = "english";
3. Setting Homepage
By default, EasyHotspot is only accessible from the server itself (localhost), if you want to
remote your billing system you could tell EasyHotspot to change the homepage from
locahost to your accessible IP Address.
Edit /var/www/system/application/config/config.php, find $config['base_url'] line.
example :
$config['base_url'] = "http://192.168.182.1/";
192.168.182.1 is your EasyHotspot IP address4. Patching (version 0.1 only)
Some people noticed that EasyHotspot is not disconnected expired users when they reached
their limit (packet/octet based). It's happenned because FreeRadius didn't know what to do if
they reached their limit.
Actually there is some instructions written in FreeRadius configuration file, but somehow I
forgot to enable it. To fix it just enable the instructions and save it. This is how to do it:
edit /etc/freeradius/radiusd.conf file and remove # mark on line
5. Setting Your Network
Make sure that you have two interface named eth0 and eth1, if you have eth2, eth3 and so
on please consult the troubleshoot section.
1. internet
Set your eth0 as your internet connection source. It can be dynamic or static. If you have
a dynamic connection, just simply plug in the ethernet cable to eth0 interface, or if you
have a static connection you can configure it by clicking the network icon on system
tray and hit manual configuration.
2. distribution area
eth1 will act as distribution interface. You don't have to configure this interface at all.
Just connect to AP or Switch hub and then let your client connect . Make sure that you
have disabled DHCP, Encryption, and Router feature in your hotspot (if exist).
5. Using EasyHotspot
EasyHotspot comes with preconfigured hotspot system and a web interface to manage all stuffs
that related to bililng activity, such as account generation, invoice, billing plan, etc.
Actor in EasyHotspot web interface consist into :
■ admin : this user handle billing plan, price and system configuration.
■ cashier : this user handle business area, user generation, invoice, view stats
Admin Activity :
All of admin activity needs admin level permission.
1. Creating BillingPlan
BillingPlan is like a template for your voucher. What kind of voucher you want to
generate ? The billing you have created then will be used by the cashier to generate the
vouchers.
2. Setting PostPaid Price
3. Managing cashier account
You can assign/add/edit/delete other people to be a cashier
Cashier Activity :
4. Generate Voucher
Voucher is a prepaid billing system. Voucher could be generated from BillingPlan that
admin have created before. Usually this method used by Cafe, Mall or any other place that
people usually mobile.
5. Postpaid account
Postpaid account is a postpaid billing system. The first step to use this feature, the cashiers
have to create postpaid user, print the voucher and then give it to clients. If the clients
decide to stop, the cashier will close and print invoice by clicking the detail of clients usage.
If the account closed this account would never be used again
6. Important things for your customers :
1. How to Connect the AP / Wired network
Connect your clients by choosing your AP or Switch, in this step EasyHotspot will give
your clients an IP Address.
2. How to log in using printed voucher
To login you need to open the browser and surf to the internet, before you see the page,
you will be prompted to a login page (accept all certificate before).
Enter user name and password that printed on your voucher. Enjoy your surfing =)
3. How to logout
Simply click logout and you will logged out. If you accidentally close the browser,
navigate to : http://192.168.182.1:9220/prelogin
6. Tips
1. Changing interface name
I highly recommend you to make sure that you have 2 interface named eth0 and eth1. eth0
will be act as an internet line and eth1 as a distribution interface. If your interfaces name are
not eth0 and eth1 you should change it.
This is how to do it :
edit the /etc/udev/rules.d/70-persistent-net.rules file
example :
from
SUBSYSTEM=="net", DRIVERS=="?*",
ATTRS{address}=="00:16:d3:5e:8f:f3", NAME="eth3" # PCI device
0x14e4:0x4311 (bcm43xx) SUBSYSTEM=="net", DRIVERS=="?*",
ATTRS{address}=="00:19:7e:a5:45:84", NAME="eth4"
to
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:16:d3:5e:
8f:f3", NAME="eth0"
# PCI device 0x14e4:0x4311 (bcm43xx)
SUBSYSTEM=="net", DRIVERS=="?*",
ATTRS{address}=="00:19:7e:a5:45:84", NAME="eth1"
2. Changing MySQL default password
It would be better to change the default root and easyhotspot user password. You can search
the details of how doing that at mysql documentation. After that don't forget to edit the /var/www/system/application/config/database.php

Network Security Technologies and Protocols

noreply@blogger.com (fakrule bromo) — Tue, 14 Jul 2009 07:41:00 -0700

Description Network security covers such issues as network communication privacy, information confidentiality and integrity over network, controlled access to restricted network domains and sensitive information, and using the public network such as Internet for private communications. To address these issues, various network and information security technologies have been developed by various organizations and technology vendors. Here is a summary of the technologies:
AAA: Authorization, Authentication and Accounting is a technology for intelligently controlling access to network resources, enforcing policies, auditing usage, and providing the information necessary to bill for services. Authentication provides a way of identifying a user, typically by having the user enter a valid user name and valid password before access is granted. The authorization process determines whether the user has the authority to access certain information or some network sub-domains. Accounting measures the resources a user consumes while using the network, which includes the amount of system time or the amount of data a user has sent and/or received during a session, which could be used for authorization control, billing, trend analysis, resource utilization, and capacity planning activities. A dedicated AAA server or a program that performs these functions often provides authentication, authorization, and accounting services.

VPN: Virtual Private Network is a technology allowing private communications by business and individuals, such as remote access to a corporate network or using a public telecommunication infrastructure, such as the Internet. A virtual private network can also be a specially configured network over the public network infrastructure that is only used by one organization. Various network-tunneling technologies such as L2TP have been developed to reach this goal. Using encryption technologies such as IPsec could further enhance information privacy over network and virtual private networks.

Firewall: Firewall is a software program or hardware device that filters the information coming through the Internet connection into a private network or computer system. Firewalls use one or more of three methods to control traffic flowing in and out the network:

Packet filtering - Packets are analyzed against a set of filters. Packets that make it through the filters are sent to the requesting system and all others are discarded.

Proxy service - Information from the Internet is retrieved by the firewall and then sent to the requesting system and vice versa.

Stateful inspection - compares certain key parts of packets passing through with a database of trusted information. Outgoing information from inside the firewall is monitored for specific defining characteristics, and incoming information is then compared with these characteristics. If the comparison yields a reasonable match, the information is allowed through. Otherwise it is discarded.

Protocols The key protocols for AAA and VPN:

Authentication Authorization Accounting Kerberos: Network Authentication Protocol

RADIUS: Remote Authentication Dial In User Service

SSH: Secure Shell Protocol

TACACS: Terminal Access Controller Access Control Protocol (and TACACS+)

Tunneling L2F: Level 2 Forwarding protocol

L2TP: Layer 2 Tunneling Protocol

PPTP: Point to Point Tunneling Protocol

Secured Routing DiffServ: Differentiated Service

GRE: Generic Routing Encapsulation

IPsec: Security Architecture for IP network

IPsec AH: IPsec Authentication Header

IPsec ESP: IPsecEncapsulating Security Payload

IPsec IKE: Internet Key Exchange Protocol

IPsec ISAKMP: Internet Security Association and Key Management Protocol

TLS: Transport Layer Security Protocol

Others Socks: Protocol for sessions traversal across firewall securely

Reference
http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/security.htm
Securities Technologies

Authentication Authorization Accounting	Kerberos: Network Authentication Protocol
RADIUS: Remote Authentication Dial In User Service
SSH: Secure Shell Protocol
TACACS: Terminal Access Controller Access Control Protocol (and TACACS+)
Tunneling	L2F: Level 2 Forwarding protocol
L2TP: Layer 2 Tunneling Protocol
PPTP: Point to Point Tunneling Protocol
Secured Routing	DiffServ: Differentiated Service
GRE: Generic Routing Encapsulation
IPsec: Security Architecture for IP network
IPsec AH: IPsec Authentication Header
IPsec ESP: IPsecEncapsulating Security Payload
IPsec IKE: Internet Key Exchange Protocol
IPsec ISAKMP: Internet Security Association and Key Management Protocol
TLS: Transport Layer Security Protocol
Others	Socks: Protocol for sessions traversal across firewall securely

Voice over IP and VOIP Protocols

noreply@blogger.com (fakrule bromo) — Tue, 14 Jul 2009 07:37:00 -0700

Description Voice over IP (VOIP) uses the Internet Protocol (IP) to transmit voice as packets over an IP network. Using VOIP protocols, voice communications can be achieved on any IP network regardless whether it is Internet, Intranet or Local Area Networks (LAN). In a VOIP enabled network, the voice signal is digitized, compressed and converted to IP packets and then transmitted over the IP network. VOIP signaling protocols are used to set up and tear down calls, carry information required to locate users and negotiate capabilities. The key benefits of Internet telephony (Voice over IP) are the very low cost, the integration of data, voice and video on one network, the new services created on the converged network and simplified management of end user and terminals.
There are a few VOIP protocol stacks which are derived by various standard bodies and vendors, namely H.323, SIP, MEGACO and MGCP.

H.323 is the ITU-T's standard, which was originally developed for multimedia conferencing on LANs, but was later extended to cover Voice over IP. The standard encompasses both point to point communications and multipoint conferences. H.323 defines four logical components: Terminals, Gateways, Gatekeepers and Multipoint Control Units (MCUs). Terminals, gateways and MCUs are known as endpoints.

Session Initiation Protocol (SIP) is the IETF's standard for establishing VOIP connections. SIP is an application layer control protocol for creating, modifying and terminating sessions with one or more participants. The architecture of SIP is similar to that of HTTP (client-server protocol). Requests are generated by the client and sent to the server. The server processes the requests and then sends a response to the client. A request and the responses for that request make a transaction.

Media Gateway Control Protocol (MGCP), an IETF standard based on Cisco and Telcordia proposals, defines communication between call control elements (Call Agents or Media Gateway) and telephony gateways. MGCP is a control protocol, allowing a central coordinator to monitor events in IP phones and gateways and instruct them to send media to specific addresses. In the MGCP architecture, the call control intelligence is located outside the gateways and is handled by the call control elements (the Call Agent). Also, the call control elements (Call Agents) will synchronize with each other to send coherent commands to the gateways under their control. CableLab has adopted the MGCP for its PacketCable embbed clients in VOIP applications and the resulted protocol is called Network Based Signaling Protocol (NCS).

The Media Gateway Control Protocol (Megaco) is a result of joint efforts of the IETF and the ITU-T (ITU-T Recommendation H.248). Megaco/H.248 is a protocol for the control of elements in a physically decomposed multimedia gateway, which enables separation of call control from media conversion. Megaco/H.248 addresses the relationship between the Media Gateway (MG), which converts circuit-switched voice to packet-based traffic, and the Media Gateway Controller, which dictates the service logic of that traffic. Megaco/H.248 instructs an MG to connect streams coming from outside a packet or cell data network onto a packet or cell stream such as the Real-Time Transport Protocol (RTP). Megaco/H.248 is essentially quite similar to MGCP from an architectural standpoint and the controller-to-gateway relationship, but Megaco/H.248 supports a broader range of networks.

The SS7/C7 is the traditional signaling protocol for the circuit switched voice networks. To integrate the SS7/C7 network with the IP network, a group of protocols are defined, namely SIGTRAN (Signaling Transpor protocol). The key transport protocol in the SIGTRAN stack, the Stream Control Transmission Protocol (SCTP), has been applied in a much broader base after its creation.

In the past few years, the VOIP industry has been working on addressing the following key issues:

Quality of voice -- As IP was designed for carrying data, it does not provide real time guarantees but only provides best effort service. For voice communications over IP to become acceptable to users, the packet delay and getter needs to be less than a threshold value.

Interoperability -- In a public network environment, products from different vendors need to operate with each other for Voice over IP to become common among users.

Security -- Encryption (such as SSL) and tunneling (L2TP) technologies have been developed to protect VOIP signaling and bear traffic.

Integration with Public Switched Telephone Network(PSTN) -- While Internet telephony is being introduced, it will need to work in conjunction with PSTN in the foreseeable future. Gateway technologies are being developed to bridge the two networks.

Scalability -- VOIP systems need to be flexible enough to grow to the large user market for both private and public services. Many network management and user management technologies and products are being developed to address the issue.

Key VOIP Protocols

Signaling

ITU-T H.323 H.323: Packet-based multimedia communications (VoIP) architecture

H.225: Call Signaling and RAS in H.323 VOIP Architecture

H.235: Security for H.323 based systems and communications

H.245: Control Protocol for Multimedia Communication

T.120: Multipoint Data Conferencing Protocol Suite

IETF Megaco / H.248: Media Gateway Control protocol

MGCP: Media Gateway Control Protocol

RTSP: Real Time Streaming Protocol

SIP: Session Initiation Protocol

SDP: Session Description Protocol

SAP: Session Announcement Protocol

CableLab NCS: Netowrk-based Call Signaling Protocol

Cisco Skinny SCCP: Skinny Client Control Protocol

Media/CODEC G.7xx: Audio (Voice) Compression Protocols (G.711, G.721, G.722, G.723, G.726, G.727. G.728, G.729)

H.261: Video CODEC for Low Quality Videoconferencing

H.263: Video CODEC for Medium Quality Videoconferencing

H.264 / MPEG-4: Video CODEC for High Quality Video Streaming

Video CODEC for Medium Quality VideoconferencingRTP: Real Time Transport Protocol

RTCP: RTP Control Protocol

Others COPS: Common Open Policy Service

SIGTRAN: Signaling Transport protocol stack for SS7/C7 over IP

SCTP: Stream Control Transmission Protocol

TRIP: Telephony Routing Over IP

Sponsor Source VOIP protocols are defined by IETF, ITU-T and some vendors.

Reference
http://www.cis.ohio-state.edu/~jain/refs/ref_voip.htm
Voice Over IP and IP Telephony References

Signaling
ITU-T H.323	H.323: Packet-based multimedia communications (VoIP) architecture
H.225: Call Signaling and RAS in H.323 VOIP Architecture
H.235: Security for H.323 based systems and communications
H.245: Control Protocol for Multimedia Communication
T.120: Multipoint Data Conferencing Protocol Suite
IETF	Megaco / H.248: Media Gateway Control protocol
MGCP: Media Gateway Control Protocol
RTSP: Real Time Streaming Protocol
SIP: Session Initiation Protocol
SDP: Session Description Protocol
SAP: Session Announcement Protocol
CableLab	NCS: Netowrk-based Call Signaling Protocol
Cisco Skinny	SCCP: Skinny Client Control Protocol
Media/CODEC	G.7xx: Audio (Voice) Compression Protocols (G.711, G.721, G.722, G.723, G.726, G.727. G.728, G.729)
H.261: Video CODEC for Low Quality Videoconferencing
H.263: Video CODEC for Medium Quality Videoconferencing
H.264 / MPEG-4: Video CODEC for High Quality Video Streaming
Video CODEC for Medium Quality VideoconferencingRTP: Real Time Transport Protocol
RTCP: RTP Control Protocol
Others	COPS: Common Open Policy Service
SIGTRAN: Signaling Transport protocol stack for SS7/C7 over IP
SCTP: Stream Control Transmission Protocol
TRIP: Telephony Routing Over IP

Cisco Protocols

noreply@blogger.com (fakrule bromo) — Tue, 14 Jul 2009 07:32:00 -0700

Description Cisco Systems plays an active role in the IETF committees to bring Cisco technology initiatives into the standards track. At the same time, Cisco created many proprietary protocols, which are mostly included in the IOS, the operating system of Cisco products. In this book, we have selected the most frequently used Cisco protocols to introduce.
CDP: Cisco Discovery Protocol
CGMP: Cisco Group Management Protocol
DISL: Dynamic Inter-Switch Link Protocol
DTP: Cisco Dynamic Trunking Protocol
EIGRP: Enhanced Interior Gateway Routing Protocol
HSRP: Hot Standby Router Protocol
IGRP: Interior Gateway Routing Protocol
ISL: Cisco Inter-Switch Link Protocol
NetFlow: Cisco traffic mamagement protocol
RGMP: Cisco Router Port Group Management Protocol
TACACS and TACACS+: Terminal Access Controller Access Control Protocol
VTP: Cisco VLAN Trunking Protocol
XOT: Cisco X.25 Over TCP Protocol

Wide Area Network and WAN Protocols

noreply@blogger.com (fakrule bromo) — Tue, 14 Jul 2009 07:14:00 -0700

Description A Wide Area Network (WAN) is a computer network covering multiple distance areas, which may spread across the entire world. WANs often connect multiple smaller networks, such as local area networks (LANs) or metro area networks (MANs). The world's most popular WAN is the Internet. Some segments of the Internet are also WANs in themselves. A wide area network may be privately owned or rented from a service provider, but the term usually connotes the inclusion of public (shared user) networks.

A virtual private network (VPN) riding on the public switched data network (PSDN) is often used by organizations for their private and secured communications. VPN uses encryption and other techniques to make it appear that the organisation has a dedicated network while making use of the shared infrastructure of the WAN.

WANs generally utilize different networking technologies and equipment than do LANs. Key technologies often found in WANs include SONET, Frame Relay, X.25, ATM, and PPP.

WAN technologies and protocols are mostly data link layer (layer 2) protocols which are defined by many organizations over time. The key organizations in this space are IETF for PPP, ITU-T for ATM, Frame Relay, ISO for X.25 and SONET.

Key Protocols The key WAN protocols are listed as follows:

Table 0501.
WAN	Wide Area Network
ATM	ATM: Asynchronous Transfer Mode Reference Model
	ATM Layer
	AAL: ATM Adaptation Layer Type 0-5 reserved for variable bit rate video transfer.
	ATM UNI: ATM Signaling User-to-Network Interface
	LANE-NNI: LAN Emulation - Network to Network Interface
	LANE-UNI: LAN Emulation - User to Network Interface
	MPOA: Multi Protocol Over ATM
	PNNI: Private Network-to-Network Interface
	Q.2931: ATM Signalling User Interface
SONET/SDH	Synchronous Optical Network and Synchronous Digital Hierarchy
SONET/SDH	EoS: Ethernet over SONET/SDH
Broadband Access	DOCSIS: Data Over Cable Service Interface Specification
	BISDN: Broadband Integrade Service Digital Network
	ISDN: Integrated Services Digital Network
	Q.931: ISDN network layer interface protocol
	LAPD: ISDN Link Access Protocol Channel D (Q.921)
	xDSL: Digital Subscriber Line Technologies (DSL, IDSL, ADSL, HDSL, SDSL, VDSL, G.Lite)
PPP	PPP: Point-to-Point Protocols
	BAP: PPP Bandwidth Allocation Protocol
	BACP: PPP Bandwidth Allocation Control Protocol
	BCP: PPP Bridging Control Protocol
	CHAP: Challenge Handshake Authentication Protocol
	EAP: PPP Extensible Authentication Protocol
	LCP: PPP Link Control Protocol
	MultiPPP: MultiLink PPP (MP)
	NCP: PPP Network Control Protocol
	PAP: Password Authentication Protocol
	PPPoE: PPP over Ethernet
	PPPoA: PPP over ATM AAL5
	PoS: Packet Over SONET/SDH
X.25	HDLC: High Level Data Link Control protocol
	LAPB: Link Access Procedure Balanced for x.25
	X.25: ITU-T WAN communication protocol
Frame Relay	Frame Relay: WAN protocol for internetworking at layer 2
Frame Relay	LAPF: Link Access Procedure/Protocol (ITU Q.922)
Other	IBM SDLC: Synchronous Data Link Control protocol

Related Protocols LAN, MAN, TCP/IP

TCP/IP Protocols

noreply@blogger.com (fakrule bromo) — Tue, 14 Jul 2009 07:09:00 -0700

The TCP/IP protocol suite establishes the technical foundation of the Internet. Development of the TCP/IP started as DOD projects. Now, most protocols in the suite are developed by the Internet Engineering Task Force (IETF) under the Internet Architecture Board (IAB), an organization initially sponsored by the US government and now an open and autonomous organization. The IAB provides the coordination for the R&D underlying the TCP/IP protocols and guides the evolution of the Internet. The TCP/IP protocols are well documented in the Request For Comments (RFC), which are drafted, discussed, circulated and approved by the IETF committees. All documents are open and free and can be found online in the IETF site listed in the reference.

TCP/IP architecture does not exactly match the OSI model. Unfortunately, there is no universal agreement regarding how to describe TCP/IP with a layered model. It is generally agreed that TCP/IP has fewer levels (from three to five layers) than the seven layers of the OSI model. In this document, we force TCP/IP protocols into the OSI 7 layers structure for comparison purpose.

The TCP/IP suite's core functions are addressing and routing (IP/IPv6 in the networking layer) and transportation control (TCP, UDP in the transport layer).

IP - Internet Protocol Addressing of network components is a critical issue for information routing and transmission in network communications. Each technology has its own convention for transmitting messages between two machines within the same network. On a LAN, messages are sent between machines by supplying the six bytes unique identifier (the "MAC" address). In an SNA network, every machine has Logical Units with their own network addresses. DECNET, AppleTalk, and Novell IPX all have a scheme for assigning numbers to each local network and to each workstation attached to the network.

On top of these local or vendor specific network addresses, IP assigns a unique number to every network device in the world, which is called an IP address. This IP address is a four-byte value in IPv4 that, by convention, is expressed by converting each byte into a decimal number (0 to 255) and separating the bytes with a period. In IPv6, the IP address has been increased to 16 bytes. Details of the IP and IPv6 protocols are presented in separate documents.

TCP - Transmission Control Protocol TCP provides a reliable stream delivery and virtual connection service to applications through the use of sequenced acknowledgment with retransmission of packets when necessary. TCP provides stream data transfer, transportation reliability, efficient flow control, full-duplex operation, and multiplexing. Check the TCP section for more details. In the follwoing TCP/IP protocol stack table, we list all the protocols according to their functions in mapping to the OSI 7 layers network communication reference model.

However, the TCP/IP architecture does not follow the OSI model closely, for example, most TCP/IP applications directly run on top of the transport layer protocols, TCP and UDP, without the presentation and session layers in between.

TCP/IP Protocol Stack

Application Layer

BOOTP: Bootstrap Protocol
DCAP: Data Link Switching Client Access Protocol
DHCP: Dynamic Host Configuration Protocol
DNS: Domain Name Systems
FTP: File Transfer Protocol
Finger: User Information Protocol
HTTP: Hypertext Transfer Protocol
S-HTTP: Secure Hypertext Transfer Protocol (S-HTTP)
IMAP & IMAP4: Internet Message Access Protocol
IPDC: IP Device Control
IRCP (IRC): Internet Relay Chat Protocol
LDAP: Lightweighted Directory Access Protocol
MIME (S-MIME): Multipurpose Internet Mail Extensions (Secure MIME)
NAT: Network Address Translation
NNTP: Network News Transfer Protocol
NTP: Network Time Protocol
POP & POP3: Post Office Protocol (version 3)
rlogin: Remote Login in Unix
RMON: Remote Monitoring MIBs in SNMP
SLP: Service Location Protocol
SMTP: Simple Mail Transfer Protocol
SNMP: Simple Network Management Protocol
SNTP: Simple Network Time Protocol
Syslog Protocol
TELNET: TCP/IP Terminal Emulation Protocol
TFTP: Trivial File Transfer Protocol
URL: Uniform Resource Locator
XMPP: Extensible Messaging and Presence Protocol
X-Window: X Window or X Protocol or X System

Presentation Layer LPP: Lightweight Presentation Protocol

Session Layer RPC: Remote Procedure Call protocol

Transport Layer

ITOT: ISO Transport Over TCP/IP
RDP: Reliable Data Protocol
RUDP: Reliable UDP
TALI: Transport Adapter Layer Interface
TCP: Transmission Control Protocol
UDP: User Datagram Protocol
Van Jacobson: Compressed TCP

Network Layer Routing

BGP/BGP-4: Border Gateway Protocol
EGP: Exterior Gateway Protocol
IP: Internet Protocol
IPv6: Internet Protocol version 6
ICMP/ICMPv6: Internet Control Message Protocol
IRDP: ICMP Router Discovery Protocol
Mobile IP: IP Mobility Support Protocol for IPv4 & IPv6
NARP: NBMA Address Resolution Protocol
NHRP: Next Hop Resolution Protocol
OSPF: Open Shortest Path First
RIP (RIP2): Routing Information Protocol
RIPng: RIP for IPv6
RSVP: Resource ReSerVation Protocol
VRRP: Virtual Router Redundancy Protocol

Multicast

BGMP: Border Gateway Multicast Protocol
DVMRP: Distance Vector Multicast Routing Protocol
IGMP: Internet Group Management Protocol
MARS: Multicast Address Resolution Server
MBGP: Multiprotocol BGP
MOSPF: Multicast OSPF
MSDP: Multicast Source Discovery Protocol
MZAP: Multicast-Scope Zone Announcement Protocol
PGM: Pragmatic General Multicast Protocol
PIM-DM: Protocol Independent Multicast - Dense Mode
PIM-SM: Protocol Independent Multicast - Sparse Mode

MPLS Protocols

MPLS: Multi-Protocol Label Switching
CR-LDP: Constraint-Based Label Distribution Protocol
LDP: Label Distribution Protocol
RSVP-TE: Resource ReSerVation Protocol-Traffic Engineering
GMPLS: Generalized Multi-Protocol Lable Switching

Data Link Layer

ARP and InARP: Address Resolution Protocol and Inverse ARP
IPCP and IPv6CP: IP Control Protocol and IPv6 Control Protocol
RARP: Reverse Address Resolution Protocol
SLIP: Serial Line IP

Related protocol suites LAN, MAN, WAN, SAN, Security/VPN

Sponsor Source IETF, DARPA, ISO

TCP and UDP Port Numbers

noreply@blogger.com (fakrule bromo) — Tue, 14 Jul 2009 06:45:00 -0700

Description TCP and UDP are both transport protocols above the IP layer, which are interfaces between IP and upper-layer processes. TCP and UDP protocol port numbers are designed to distinguish multiple applications running on a single device with one IP address from one another.

Since many network applications may be running on the same machine, computers need something to make sure the correct software application on the destination computer gets the data packets from the source machine, and to make sure replies get routed to the correct application on the source computer. This is accomplished through the use of the TCP or UDP "port numbers". In the TCP and UDP header, there are "Source Port" and "Destination Port" fields which are used to indicate the message sending process and receiving process identities defined. The combination of the IP address and the port number is called "socket".

There are three port ranges defined by IETF IANA: the Well Known Ports, the Registered Ports, and the Dynamic and/or Private Ports.

The Well Known Ports are in the range of 0 to 1023, which are assigned by the IANA. In most cases, they can only be used by system (or root) processes or by programs executed by privileged users.
The Registered Ports are in the range of 1024 to 49151, which are not controlled by IANA. They are commonly used by ordinary user processes or programs executed by ordinary users.
The Dynamic and/or Private Ports are in the range of 49152 to 65535, which are typically used as source port by a TCP or UDP client, to communicate with a remote TCP or UDP server, using a well-known port as destination port.

Partial TCP UDP Port Numbers (Well-Known Ports)

Port No.	Protocol	Service Name	Aliases	Comment
1	TCP	tcpmux		TCP Port Service Multiplexer
2	TCP/UDP	compressnet		Management Utility
3	TCP/UDP	compressnet		Compression Process
7	TCP/UDP	echo		Echo
13	TCP/UDP	daytime		Daytime
19	TCP/UDP	chargen	ttytst source	Character generator
20	TCP	ftp-data		File Transfer
21	TCP	ftp		FTP Control
22	TCP	ssh		SSH remote login protocol
23	TCP	telnet		Telnet
25	TCP	smtp	mail	Simple Mail Transfer
37	TCP/UDP	Time		Time
39	UDP	RLP	resource	Resource Location Protocol
42	UDP	nameserver	name	Host Name Server
43	TCP	nicname	whois	Who Is
49	UDP	TACACS		TACACS: Login Host Protocol
53	TCP/UDP	domain	DNS	Domain Name Server
67	UDP	bootps	dhcps	Bootstrap Protocol Server
68	UDP	bootpc	dhcpc	Bootstrap Protocol Client
69	UDP	TFTP		Trivial File Transfer Protocol
70	TCP	gopher		Gopher
79	TCP/UDP	finger		Finger
80	TCP/UDP	http	www,http	World Wide Web
88	TCP/UDP	kerberos	krb5	Kerberos
101	TCP	hostname	hostnames	NIC Host Name Server
102	TCP	iso-tsap		ISO-TSAP Class 0
107	TCP	rtelnet		Remote Telnet Service
110	TCP	Pop3	postoffice	Post Office Protocol- Version 3
111	TCP/UDP	sunrpc	rpcbind portmap	SUN Remote Procedure Call
113	TCP	Auth	ident tap	Authentication Sevice
117	TCP	Uucppath		UUCP Path Service
118	TCP	sqlserv		SQL Services
119	TCP	nntp	usenet	Network News Transfer Protocol
123	UDP	Ntp		Network Time Protocol
135	TCP/UDP	epmap	loc-srv	DCE endpoint resolution
137	TCP/UDP	netbiosns	nbname	NETBIOS Name Service
138	UDP	netbiosdgm	nbdatagram	NETBIOS Datagram Service
139	TCP	netbiosssn	nbsession	NETBIOS Session Service
143	TCP	Imap	imap4	Internet Message Access Protocol
158	TCP	pcmailsrv	repository	PC Mail Server
161	UDP	snmp	snmp	SNMP
162	UDP	snmptrap	snmptrap	SNMP TRAP
170	TCP	Printsrv		Network PostScript
194	TCP	irc		Internet Relay Chat Protocol
213	UDP	ipx		IPX over IP
389	TCP	ldap		Lightweight Directory Access Protocol
401	TCP/UDP	UPS		Uninterruptible Power Supply
443	TCP/UDP	https	MCom	http protocol over TLS/SSL
445	TCP/UDP	CIFS		Kerberos (v5)
464	TCP/UDP	kpasswd		Message
500	UDP	isakmp	ike	Internet Key Exchange (IPSec)
513	TCP	login		Remote Login
513	UDP	who	whod	Database of who's logged on, average load
514	TCP	cmd	shell	Automatic Authentication
514	UDP	syslog
515	TCP	printer	spooler	Listens for incoming connections
517	UDP	talk		Establishes TCP Connection
120	TCP	efs		Extended File Name Server
520	UDP	Routing	router routed	RIPv.1, RIPv.2
521	UDP	Routing	router routed	RIPng
525	UDP	Timed	timeserver	Timeserver
530	TCP/UDP	Courier	rpc	RPC
531	TCP	conference	chat	IRC Chat
532	TCP	netnews	readnews	Readnews
533	UDP	Netwall		For emergency broadcasts
540	TCP	Uucp	uucpd	Uucpd
543	TCP	Klogin		Kerberos login
544	TCP	Kshell	krcmd	Kerberos remote shell
550	UDP	newrwho	new-who	New-who
554	UDP	rtsp		Real Time Stream Control Protocol
556	TCP	remotefs	rfs rfs_server	Rfs Server
560	UDP	rmonitor	rmonitord	Rmonitor
561	UDP	monitor
636	TCP	Ldaps	sldap	LDAP over TLS/SSL
749	TCP/UDP	kerberosadm		Kerberos administration
750	UDP	Kerberos-iv		Kerberos version IV
1080	TCP/UDP	socks		socks
1812	TCP	RADIUS		RADIUS
1813	TCP	RADIUS		RADIUS accounting

Reference Links

http://www.iana.org/assignments/port-numbers
TCP and UDP port numbers