Hi Hank If I understand correctly you are trying to send bgp routes to a router that have a next hop local to the router?
I think this would contrast with the route selection process and not be accepted.. as the route would not be installable. i.e. The router would route it to itself on the Ge interface and then ? route it to itself in a loop? Maybe I am misunderstanding ... Brian Brian Turnbow +39 02 6706800 [image: CDLAN SPA] [image: CDLAN SPA] <https://www.cdlan.it//> | [image: CDLAN SPA - LinkedIn] <https://it.linkedin.com/company/cdlan> Il giorno lun 10 giu 2024 alle ore 10:09 Hank Nussbacher via cisco-nsp < cisco-nsp@puck.nether.net> ha scritto: > I have a simple iBGP peer defined as follows: > > neighbor 128.139.197.146 > remote-as 378 > update-source Loopback0 > address-family ipv4 unicast > > > I have a GigE interface defined as: > > interface GigabitEthernet0/0/0/43.1 > ipv4 address 192.0.2.1 255.255.255.0 > encapsulation dot1q 1 > > This iBGP peer feeds me /32s with nexthop set as 192.0.2.1/32. Problem > is all routes disappear. > > Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down > St/PfxRcd > 128.139.197.146 0 378 10437 627880 10060119 0 0 > 00:15:41 0 > > > If the feed sets the IP to 192.0.2.2 then the BGP routes appear in the > routing table. If I then change the IP address on interface > GigabitEthernet0/0/0/43.1 to 192.0.2.2 then the routes disappear as well > after having made it into the routing table. > > > I am obviously missing something very simple. Clue-bat welcome. > > > Thanks, > > Hank > > > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
