zebra ipv6 bgp peering

matthew zeier matthew@intelenet.net
Wed, 20 Sep 2000 22:48:02 -0700



Ugh.

I must not have my network statement right.  

After doing a 

	no ipv6 bgp network 3ffe:1900::/48

I seem to have been able to establish this peering.  

On Wed, Sep 20, 2000 at 10:05:19PM -0700, Pat Jensen wrote:
> 
> I am successfully peering with a Cisco router (probably a 7000 series) at
> Sprint with Zebra (on both FreeBSD and OpenBSD).
> Was fairly easy to setup since I knew a little bit about setting up BGP on
> IOS .. the commands are almost the same.
> The only problem I had was I botched up Sprint's ASN .. I couldn't start a
> session successfully.
> 
> My configuration is:
> 
> router bgp 65535
>  bgp router-id 10.0.0.1
> !
> ipv6 bgp network  3ffe:2900:e006::/48
> ipv6 bgp neighbor 3ffe:2900:e:6::1 remote-as 65535
> !
> ipv6 access-list  all permit any
> 
> Hope it helps!
> 
> -Pat
> 
> matthew zeier wrote:
> 
> > Has anyone successfully gotten zebra to peer with a v6 peer?
> >
> > I'm trying to peer with 3Com -
> >
> > router bgp 5693
> >  bgp router-id 206.82.192.10
> >  ipv6 bgp network 3ffe:1900::/48
> >  ipv6 bgp neighbor 3ffe:1900:3::1 remote-as 561
> >  ipv6 bgp neighbor 3ffe:1900:3::1 description 3Com IPv6
> >  ipv6 bgp neighbor 3ffe:1900:3::1 soft-reconfiguration inbound
> >
> > I'm getting the following in my log:
> >
> > BGP: 3ffe:1900:3::1 [Update:RECV] 3ffe:3800::13:0/112 nexthop:
> > 129.213.128.90 mp_nexthop: 3ffe:1900:3::1(fe80::200:81ff:fed5:805a)
> > aspath: 561 237 12199 ?
> > BGP: 3ffe:1900:3::1 [Update:RECV] 3ffe:2e00::/24 nexthop: 129.213.128.90
> > mp_nexthop: 3ffe:1900:3::1(fe80::200:81ff:fed5:805a) aspath: 561 6175
> > 4554 3748 ?
> > BGP: 3ffe:1900:3::1 [Update:RECV] 3ffe:1800::/24 nexthop: 129.213.128.90
> > mp_nexthop: 3ffe:1900:3::1(fe80::200:81ff:fed5:805a) aspath: 561 6175
> > 4697 ?
> > BGP: 3ffe:1900:3::1 [Update:RECV] 2001:208::/35 nexthop: 129.213.128.90
> > mp_nexthop: 3ffe:1900:3::1(fe80::200:81ff:fed5:805a) aspath: 561 10566
> > 7610 ?
> > BGP: 3ffe:1900:3::1 [Notify:RECV] UPDATE Message Error (Invalid NEXT_HOP
> > Attribute.)
> >
> > I'm not clear if this is a zebra issue or some incompatibility with a
> > 3Com router.  If anyone's successfully using zebra, please let me know.
> > I'm running this on OpenBSD 2.7.
> >
> > --
> > matthew zeier -  "There ain't no rules around here. We're trying to
> > accomplish something." - Thomas Edison


-- 
matthew zeier -  "There ain't no rules around here. We're trying to
accomplish something." - Thomas Edison