I am here to gather some advanced knowledge about an Ethernet. For those who have to implement such systems, it is essential to thoroughly consider the establishment of roads. It is not uncommon for over a LAN consisting of several logical sub-network, all connected to the Internet, to feel that everything goes well, so that packets to go from one sub-networks to borrow another road-types, simply because the routing between subnetworks was poorly done. For the user terminal, the user "classic", the default route specified by the DHCP service provider will suffice in the vast majority of cases, especially if no local network, but a little knowledge in principle enable it to better identify potential failures and possibly rectify this without thinking that the relocation of the IP layer is the only possible remedy.
Please provide some more information about the Gateways in IP Routing.!!
Reply With Quote
A bridge, after a period of learning, can spot the MAC addresses of nodes on each side of the bridge. It will not let pass from one side to another as the frames that really need to spend, so the traffic on each side is optimized, provided of course that the general architecture has been thought in the sense. A bridge is very effective if the two networks A and B hardly communicate with them. If A uses the network server services primarily of network B and vice versa, the bridge completely loses its interest, as replaced by a piece of rope.
Bookmarks