From: dusth@comcast.net
Date: Sun Nov 13 2005 - 13:05:55 GMT-3
I think what he mig mean w/ this config:
int tunnel14
ip unnumber lo0
tunnel source s0/0 - connect to your internal net
tunnel dest r4:s0/0 - r1 connection to your internal net
route-map bgp
match bgproutes
set int tunnel14
and same config on the other end
Godswill, please validate your command if i understand you correctly. I still can not lab this up yet. My 16mon old daughter takes all my last several days time:)
Dustin
-------------- Original message --------------
> > Using a ip local policy-map & route-map, then setting the next hop to
> > 'interface tunnel14' would have been the preferred solution, but for some
> > reason that is not working in my lab.
>
> Having re-read the email I sent, I see I worded it badly - this is
> what I meant. I'm ingtrigued that it didn't work for you. I'll try
> to lab it up.
>
> > The solution that will work is to set the tunnel source to a local interface
> > (eg ethernet or serial, must be advertised by IGP) & the tunnel destination
> > ip to the remote router's local interface (advertised by IGP). Then let IGP
> > advetise the loopback0 of both routers and do a bgp neighbor peering using
> > the loopback0 ip address of the other router and also using the bgp multihop
> > option, this worked for me even without the multihop option.
>
> I think I'm misunderstanding you. What makes this force BGP traffic
> down the tunnel? Do you mean that traffic to the loopback0 is routed
> via the tunnel according to the IGP, whereas traffic destined for
> other interfaces follows the usual IGP rules?
>
> cheers
> Danny
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3