Skip to main content

Crossover Cable Network

What Is Crossover Cable Network?
A crossover cable network is a computer network with two computers connected with a crossover cable. If you have two computers at home, and want to share files, programs, and printers, the crossover cable network is the easiest and cheapest solution for you.
Requirements:
  • Two computers with network supported.
  • A crossover network cable.
Most of today's home computers is coming with network card installed. No need to purchase network cards separately. But you need to purchase a crossover network cable separately. You can find it in most of the computer stores.
A crossover network cable is different than the normal straight network cable. It has two pair of lines crossed over from one end to the other end. The following two diagrams show you the differences.
A normal straight network cable has 8 positions at both ends. There are 8 lines connecting to both ends to exactly the same positions:
   End A                        End B        Note
   Position 1 <---------------> Position 1
   Position 2 <---------------> Position 2
   Position 3 <---------------> Position 3
   Position 4 <---------------> Position 4   Not used
   Position 5 <---------------> Position 5   Not used
   Position 6 <---------------> Position 6
   Position 7 <---------------> Position 7   Not used
   Position 8 <---------------> Position 8   Not used
A crossover network cable has 8 positions at both ends, same as the normal straight cable. But there are 2 pairs of lines crossed over. The first crossed pair of lines connects position 1 from one end to position 3 on the other end. The second crossed pair of lines connects position 2 from one end to position 5 on the other end:
   End A                        End B        Note
   Position 1 <------   ------> Position 1
                     \ /   
   Position 2 <--     X     --> Position 2
                 \   / \   /
   Position 3 <---\--   --/---> Position 3
                   \     /
   Position 4 <-----\---/-----> Position 4   Not used
                     \ /   
   Position 5 <-------X-------> Position 5   Not used
                     / \
   Position 6 <------   ------> Position 6

   Position 7 <---------------> Position 7   Not used

   Position 8 <---------------> Position 8   Not used


Comments

Popular posts from this blog

Sexy C#

Download samples   Table of Contents   1.   Introduction  2.   Background    3.   Sexy Features 3.1.   Extension Methods   3.2.   Anonymous Type   3.3.   Delegate   3.4.   Lambda Expression 3.5.   Async-Await Pair   3.6.   Generics   4.   Conclusion   1. Introduction     C#  is a very popular programming language. It is mostly popular in the .NET arena. The main reason behind that is the C# language contains so many useful features. It is actually a multi-paradigm programming language. Q.   Why do we call C# a muti-paradigm programming language? A.  Well, C# has the following characteristics:  Strongly typed   Object Oriented  Functional  Declarative Programming  Imperative Programming   Component based Programming Dynamic Programming ...

Kubernetes – init containers, CNI and more

Certain questions about Kubernetes seem to come up again and again: What’s up with this init container stuff? What’s a CNI plugin? Why is Kubernetes complaining about pods not finishing initialisation? Kubernetes is a complex system with a simple overall purpose: run user  workloads  in a way that permits the authors of the workloads to not care (much) about the messy details of the hardware underneath. The workload authors are supposed to be able to just focus on Pods and Services; in turn, Kubernetes is meant to arrange things such that workloads get mapped to Pods, Pods get deployed on Nodes, and the network in between looks flat and transparent. This is simple to state, but  extremely  complex to implement in practice. (This is an area where Kubernetes is doing a great job of making things complex for the Kubernetes implementors so that they can be easier for the users – nicely done!) Under the hood, Kubernetes is leaning heavily on a number of technologies to ma...

Python Subprocess Module

Subprocess A running program is called a  process . Each process has its own system state, which includes memory, lists of open files, a program counter that keeps track of the instruction being executed, and a call stack used to hold the local variables of functions. Normally, a process executes statements one after the other in a single sequence of control flow, which is sometimes called the main thread of the process. At any given time, the program is only doing one thing. A program can create new processes using library functions such as those found in the os or subprocess modules such as  os.fork() ,  subprocess.Popen() , etc. However, these processes, known as  subprocesses , run as completely independent entities-each with their own private system state and main thread of execution. Because a subprocess is independent, it executes concurrently with the original process. That is, the process that created the subprocess can go on to work on other thing...