[Xorp-users] Complex BGP. mBGP and PIM-SM setup

[Atanu Ghosh]

Hi,

On I-BGP peerings we don't *normally* rewrite the nexthop, I suspect that
the connected route nexthop is being propagated to the peer (Maybe this
is the problem with multiple address on an interface). The one case
where we will rewrite the nexthop on an I-BGP peering is when the
nexthop matches the peers address.

In the policy statement in the then clause you could try explicitly
setting the nexthop that you want.

   policy {
    	policy-statement to-bgp {
 		term export {
 			from {
 				protocol: "connected"
 				network4: <public_cidr>
 			} to {
 				neighbor: 10.10.26.14
 			} then {
			        nexthop4: 10.10.26.7
				accept
 			}
 		}
 	}

	Atanu. 

>>>>> "Otto" == Otto Solares <solca at guug.org> writes:

    Otto> On Fri, Jun 23, 2006 at 12:33:28PM -0700, Pavlin Radoslavov
    Otto> wrote:
    >> > c. I want to export to my next router via BGP my > public
    >> Internet CIDR so I have this but it > doesn't work (quagga do
    >> export it correctly > but problem with quagga is that it doesn't
    >> > handle PIM so I have to pair it with pimd which > is not as
    >> good as Xorp for tracking IGMP and > it has lot less parameters
    >> to tune):
    >> > 
    >> > policy { > policy-statement to-bgp { > term export { > from { >
    >> protocol: "connected" > network4: <public_cidr> > } to { >
    >> neighbor: 10.10.26.14 > } then { > accept > } > } > } > }
    >> > 
    >> > bgp { > export: "to-bgp"
    >> > 
    >> > bgp-id: 10.10.26.7 > local-as: 65103
    >> > 
    >> > peer 10.10.26.14 { > local-ip: 10.10.26.7 > as: 65103 >
    >> next-hop: 10.10.26.7
    >> > 
    >> > ipv4-unicast: true > ipv4-multicast: true > } > }
    >> 
    >> First, could you try "network4 <= <public_cidr>" statement
    >> instead of "network4: <public_cidr>" .
    >> 
    >> If this doesn't help, for testing purpose could you remove the
    >> "to" statement and see whether it works.

    Otto> Using "network <= 168.234.203.0/25" statement exports every
    Otto> connected route.  Using "network4: 168.234.203.0/25" works but
    Otto> I discover the problem: As you can see I have "next-hop:
    Otto> 10.10.26.7", the peer router said my next hop is a public IP:
    Otto> 168.234.203.2 so I think Xorp is ignoring the next-hop
    Otto> statement in BGP.

    Otto> Thank you.

    Otto> -otto

    Otto> _______________________________________________ Xorp-users
    Otto> mailing list Xorp-users at xorp.org
    Otto> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users