Refer to the exhibit. R2 is mutually redistributing between EIGRP and BGP. Which configuration is necessary to enable R1 to see routes from R3?

`ebgp-multihop` is used when eBGP neighbors are not directly connected (more than one hop away), which is not the issue preventing iBGP routes from being redistributed to EIGRP in this scenario.

By default, BGP prevents the redistribution of internal BGP (iBGP) routes into an Interior Gateway Protocol (IGP) like EIGRP to avoid routing loops; the `bgp redistribute-internal` command on R2 explicitly overrides this default, allowing iBGP routes from R3 to be injected into R2's EIGRP process, making them visible to R1.

`next-hop-self` is a BGP attribute modification that influences how BGP peers resolve the next hop for BGP routes; it is not relevant for redistributing BGP routes into EIGRP for an EIGRP-only peer like R1.

While R1 and R2 must have matching EIGRP AS numbers to form an EIGRP neighbor relationship, this does not address the specific problem of redistributing iBGP learned routes (from R3) into the EIGRP domain on R2, which requires a specific BGP configuration command.