* Arnoud Vermeer <arnoud.verm...@ams-ix.net> [2009-03-08 21:06]:
> I didn't modify the source code in any way. I'm running the latest 
> version from CVS on an amd64 machine and an i386 machine.
> 
> I have the following configuration:
> 
> AS 6777
> router-id 195.69.145.245
> fib-update no
> log updates
> listen on 195.69.145.245
> listen on 2001:7F8:1::A500:6777:4
> 
> nexthop qualify via bgp
> transparent-as yes
> 
> dump all in "/tmp/all-in-dump-%H%M" 300
> dump all out "/tmp/all-out-dump-%H%M" 300
> 
> group "peers-rs-v6" {
>          announce IPv6 unicast
>          announce IPv4 none
>          softreconfig in yes
>          enforce neighbor-as yes
>          set nexthop no-modify
>          local-address 2001:7F8:1::A500:6777:4
> 
>          neighbor 2001:7f8:1::A500:1200:1 {
>                  descr "AS1200-v6-01"
>                  remote-as 1200
>                  announce all
>                  passive
>          }
> }

so you only have that one neighbor, right?

> 
> The comment about the gracefull restart lead me to think about the 
> following setting:
> 
>       announce capabilities (yes|no)
>               If set to no, capability negotiation is disabled during 
> the es-
>               tablishment of the session.  This can be helpful to connect to
>               old or broken BGP implementations.  The default is yes.
> 
> Doesn't this troggle the graceful update? While reading the announce 

no. you can't turn it on, yet. which reminds me that I wanted to add
buttons for specific capabilities...

> part of the manual, I noticed the following:
>       announce (all|none|self|default-route)
>               If set to none, no UPDATE messages will be sent to the 
> neighbor.
>               If set to default-route, only the default route will be 
> announced
>               to the neighbor.  If set to all, all generated UPDATE messages
>               will be sent to the neighbor.  This is usually used for 
> transit
>               AS's and IBGP peers.  The default value for EBGP peers is 
> self,
>               which limits the sent UPDATE messages to announcements of 
> the lo-
>               cal AS.  The default for IBGP peers is all.
> 
> I also have announce all, in my configuration, because it is a route 
> server I'm working on. Could this be the setting that is responsible for 
> the UPDATE?

sure. but the root issue here is that we're apparently sending out
bullshit in this case for yet unknown reasons.

-- 
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam

Reply via email to