Showing posts with label Networking. Show all posts
Showing posts with label Networking. Show all posts

Tuesday, February 7, 2012

Shared IP addresses...


The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP
address space for private internets:

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255


127.0.0.1, 127.0.0.0 is a local host ip v4
and ::1 is a local host ipv6 address..

Monday, November 14, 2011

802.XX Standards

802.XX standards came into existence by IEEE. Various IEEE standards for the same are:-


Ø 802.1 is an internetworking standard for compatibility of different LANs and MANs across protocols.

Ø 802.2 Logical link control (LLC) is the upper sublayer of the data link layer which is non-architecture-specific, that is remains the same for all IEEE-defined LANs.

Ø Ethernet LAN (802.3),

Ø Token ring LAN (802.4),


Ø Token bus LAN (802.5).

Ø 802.6 is distributed queue dual bus (DQDB) designed to be used in MANs.

Interesting, isn't it ?

Sunday, September 25, 2011

Connection Oriented Versus Connection less

There are 3 terms.
1. Circuit Switched N/w
2. Datagram N/w
3. Virtual Circuit N/w.

All the 3 types of network can be established by using same infrastructure. but in each case, every node behaves differently. Lets see what each type of network does.

1. Circuit Switched N/w :
    Infrastructure is considered to be consisting of many physical links which are connected using switches. Each link is divided into channels.
    So, the link is like a road on high way. And the channels are lane on the road. this analogy is sufficient to understand the meaning of channel and its significance also.
   
   In Circuit Switched N/w before the call is established or before the data transmission, intermediate route is determined and is reserved for the same purpose. So, link x's channel y is reserved for a particular duration of time for a specific data transfer. Before the time ends even if channel is idle, it is considered as busy and no one else can access it.

   This gives the guarantee regarding QoS of the data. As far as reliability is concerned, it depends on whether the intermediate links are active during entire session. Even if one channel fails or one link fails the entire set up fails and need to be closed. And here the links are truly dedicated to particular connection.

    Hence it is considered as fully dedicated. So the major disadvantage of the system is that resource utilization is poor, as can be seen from the idea of protocol itself. Connection establishment and teardown both requires certain amount of time.

2. Datagram N/w:
    As the above mentioned protocol is very very poor in terms of resource utilization, another better technique is decided i.e. Datagram n/w. In this technique, the entire n/w is considered to be  same as above, set of physical links and nodes. Each node has its routing table. Now, when the request is sent, it can go from anywhere, it just has to reach the desitnation. Each node can see where to route the packet and can forward them accordingly.

   The end user is expected to have a high buffer size so that incoming packets if reached in any order can be assembled. Hence, generally a minimum and maximum allowed time for the packet is always decided so that it goes to destination without buffer overflow.

   The major advantage of the system is that, Resource utilization is very high. And the reliability is maximum as the packet will reach destinaiton as long as there is at least one path possible. The major disadvantage of the system is that QoS cannot be guaranteed. Infact it may vary over a period of time. So, for initial 3 minutes you may get very clear sound quality and after that the sound is not even audible. So, for certain important data transmission, where QoS is very important , it cannot be used much. No time is required for Connection establishment and teardown.


3. Virtual Circuit N/w:
    Virtual Circuit is the combination of above 2 in one. So, like the Circuit switched a virtual circuit is set up but the same circuit can be shared among many types of data transmission. So, all the pkts going from source to destination goes through same set of nodes. But different set of packets may go through same set of nodes if desired. Also if certain link fails then packet stram can be forwarded to another node and the node can be changed accordingly.

    This makes it possible to give very high Reliability and optimum uses of resources is possible. QoS, if desired can be provided for the data transmission. Connection establishment and teardown both requires certain amount of time.


If you want to share something more about the same, please do add more to it. !!!

Tuesday, September 13, 2011

Connection versus Session

Often people who are studying the networking are confused with the concept of What is difference between connection and session.

Connection and Session are different Things Altogether

A connection is a transport level connection between two peers, used to send and receive Diameter messages.
A session is a logical concept at the application layer, and is shared between an access device and a server, and is identified via the Session-Id AVP.


+--------+            +---------+             +----------+
| Client |             | Relay |              | Server |
+--------+            +---------+             +----------+


           <---------->           <----------->
     peer connection A    peer connection B


<------------------------------------------------------------>
                      User session x







[From RFC 3588]

ASCII Encoding

ASCII Characters are only 7 bit in size for representation.
Still 1 byte per character is used for storage.

Because,

Additional one bit stores the parity.



So, the 8 bit code has Error Detection Capability up to one bit but no error correction capability.

Various Well known Services and their Port numbers


Port-      TCP/UDP             Protocol
7                                           Echo
20           TCP                       FTP—data transfer
21           TCP                       FTP—control

22                                         SSH
23                                         Telnet
25           TCP                       Simple Mail Transfer Protocol (SMTP)

53           TCP, UDP              Domain Name System (DNS)
67                                          DCHP Server
68                                          DHCP Client

69                                          TFTP (Initialization)
80           TCP, UDP              Hyper Text Transfer Protocol (HTTP)
109         TCP                        Post Office Protocol v2 (POP2)

110         TCP                        Post Office Protocol v3 (POP3)
443         TCP                        HTTPS (HTTP Over SSL/TLS)
465         TCP                        SMTP over SSL

546                                         DHCP Client(IP v6)
547                                         DHCP Server(IP v6)
587         TCP                        E-mail message submission (SMTP)

Thanks to Meraj Khan and Chankey Pathak, my friends for suggesting more port numbers.