Comparing Routing Approaches for a Specific Host
A network administrator is reviewing the IPv4 routing table of a Linux workstation to determine how traffic destined for the IP address 192.168.100.50 will be handled. The administrator is considering two approaches to optimize traffic flow to this specific host.
Approach A relies on the existing routing table shown below. Approach B involves adding a new static host route specifically for 192.168.100.50/32 pointing to the gateway 10.1.1.254.
| Destination | Subnet Mask | Gateway | Interface | Metric |
|---|---|---|---|---|
| 0.0.0.0 | 0.0.0.0 | 10.1.1.1 | eth0 | 100 |
| 10.1.1.0 | 255.255.255.0 | On-link | eth0 | 10 |
| 192.168.100.0 | 255.255.255.0 | 10.1.1.254 | eth0 | 50 |
| 192.168.100.0 | 255.255.255.128 | 10.1.1.5 | eth0 | 200 |
Based on the provided routing table, how does the current routing behavior (Approach A) compare to the proposed Approach B?
Currently, traffic to 192.168.100.50 is sent to 10.1.1.254 because it has a lower metric (50) than the /25 route; Approach B would maintain this path but lower the metric.
Currently, traffic to 192.168.100.50 is load-balanced between 10.1.1.254 and 10.1.1.5; Approach B would force all traffic to use only 10.1.1.254.
Currently, traffic to 192.168.100.50 is sent to 10.1.1.5 because of the longest-prefix match; Approach B would redirect this specific traffic to 10.1.1.254.
Currently, traffic to 192.168.100.50 is sent to the default gateway 10.1.1.1 because the destination is on a different subnet; Approach B would bypass the default gateway.
Question Leaderboard
Not enough data yet to show leaderboard.
