The description of switches and bridges is "sort of" correct, "sort of" not.
Bridges typically don't have the capability to filter frames. Switches may have the capability to filter, based on things like access control lists, but that's for a bit later in your networking course.
For right now, consider the following:
A bridge forwards frames from one segment to another segment.
A switch is essentially a multi-port bridge.
To answer your true-or-false questions:
Are the following true or false. Correct them if false:
I can only use either a router or a bridge to connect same protocol following multiple >networks (amongst themselves).
False. You'll typically use switches for this task - in much larger networks, you'll use routers and firewalls between geographically separated sites, but that's beyond the scope of your current studies.
All the devices are gateways falling under different layers of OSI model and have ability >to translate between all the protocols of that layer.(for eg. router is a gateway falling >in network layer and is capable of translating protocols TCP followed by network A to UDP >followed by network B (two of the protocols operating at networking layer) and vice versa)
False. Routers examine Layer 3 packets encapsulated inside Layer 2 frames for network information, and then direct them out interfaces according to their destination. In contrast, a switch looks only at the Layer 2 MAC address to determine its destination. A program (Application Layer) which talks with the UDP protocol will only "talk" on that protocol: the router cannot dynamically change it to "TCP" - it doesn't work that way. The router only encapsulates the data in a format which can traverse links between different Layer 3 networks.
Protocols like TCP and UDP operate at OSI Layer 4 - the "Transport" layer, and they differ in very specific ways and are used for different purposes. For example, UDP has no mechanism to detect whether packets are successfully received at the other end - they might get lost! TCP has a mechanism to detect whether data reaches the other end, and if not, to retransmit the lost packets.
A gateway in general operates in application, session and presentation layer.
False. Gateways operate at Layer 3.
Example: We're going to use a typical home network topology.
Computer A in Los Angeles wants to connect to Website B in New York. Computer A performs a DNS lookup of Website A, which translates to an IP address. Computer A sees that the IP address returned is not on the same network as itself, so it sends the packets to its default gateway. The default gateway is usually a router, which contains a routing table, which tells the router which external networks are reachable through which interfaces - it also has a default route which tells the router which interface or IP address to direct traffic to, if the destination does not appear in its routing table. In this case, because it's a consumer-grade appliance connected to a home network, the gateway sends all packets to unknown destinations upstream to the ISP.
In order to connect two areas, one router has to serve as an area border router (ABR). That router has interfaces in both areas. In other words, the boundary between two areas is a router, not the link between two routers.
In your example, you could configure R1 so that interface f0/0 is in area 1, while the other interfaces are in area 0. That will make R1 the ABR for area 1.
Best Answer
I think bridge works for that. 1. Create a loopback interface in your window system. 2. In GNS3, select a cloud to connect the loopback interface, thus the virtual device(like a router) can ping with your own system.