In this series of posts we’ll explore routing operation. Let’s start from the general idea of how could we manage traffic, a move from one location to another…
” This person needs to go back home at the evening! ” means that there’s a one way in return route to and from its office. We could have broadcast multicast or unicast it in one direction (unidirectionally) to get it from A to B if B is still unknown but we couldn’t afford lost him back home (now that we suppose we know about B and A precisely, uniquely)…
Should the one way and return route be the same? if not, then we talk about asymmetric routing. In some cases it’s advantageous to have asymmetric routing. In others, where firewalls per example, are put into play, symmetric routing is more appropriate (return packets should use the established session opening sat up by the initial packets). In asymmetric routing, what is asymmetric? the processing of packets… But if the return packets flow the same way but in the opposite direction, we talk about symmetric routing.
