Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What is the Difference between Bridging, Switching, Forwarding a frame?

What is the difference between Control Plane Vs Forwarding Plane and Slow path Vs Fast Path? How are the above terms related to these?

Can someone explain how a packet travels from an ingress port (on an I/O card) to an egress port (on another I/O card)? What are the exceptions? Does each packet come to the CPU?

What logic or algorithms are used for making these decions?

share|improve this question

migrated from Feb 10 '10 at 17:52

This question came from our site for professional and enthusiast programmers.

closed as not a real question by Zypher, Murali Suriar, 21st Century Moose, splattne Feb 11 '10 at 7:32

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

The terminology for bridges, switches comes from various OSI layers Datalink layer and n/w & tranport layers respectively. I don't know much about the rest – questzen Feb 10 '10 at 16:41
This should be 3 or 4 separate questions, really... – Murali Suriar Feb 10 '10 at 18:42

This is all manufacturer and device-specific. In some cases, it's even firwmare / OS specific.

Devices that move packets around (Ethernet switches moving Ethernet frames, IP routers moving IP datagrams, ATM switches moving cells) try to do so in the most efficient manner possible. This often means using custom chips (ASICs) with hardware-based algorithms to identify traffic flows and move them.

Often, the features of these hardware-based algorithms are limited (often with respect to policy-based traffic flow manipulation-- security, deep packet inspection, etc) and, when more advanced decision-making is necessary the ASICs will need to involve the device's CPU and firmware to make flow decisions.

Using the CPU and software to make the flow decision is generally much slower than a hardware-only path. In some devices, the CPU can make the decision for the initial packet, and will make an entry into a RAM-based table that the ASICs have access to so that future packets in the same flow can follow a hardware-only path.

Maufacturers aren't going to make the implementation details of their algorithms public because this is typically their "secret sauce" that helps to differentiate their gear in the marketplace. Further, these algorithms are typically dependent on features of the ASICs and underlying hardware that the devices are built upon.

You can infer, by reading up on protocols and learning HOW a packet should flow inside a switching / routing device. What the specific algorithms and optimizations are for a given device, though, aren't typically accessible to you.

share|improve this answer