I was just about to create a new thread when I read :
> I have not seen it discussed much on the list, but OpenBGP works *very*
> well and is easy to setup using Hurricane Electrics free (ipv6-in-ipv4)
I try to setup a BGP peering with upstream and I have (v3.8) :
Jan 7 10:11:19 r2 bgpd[31645]: neighbor 2001:x:21 (x-v6): state change Idle ->
Connect, reason: Start
Jan 7 10:11:19 r2 bgpd[31645]: neighbor 2001:x:21 (x-v6): state change Connect
-> OpenSent, reason: Connection opened
Jan 7 10:11:19 r2 bgpd[31645]: neighbor 2001:x:21 (x-v6): state change
OpenSent -> OpenConfirm, reason: OPEN message received
Jan 7 10:11:19 r2 bgpd[31645]: neighbor 2001:x:21 (x-v6): received
notification: error in OPEN message, unsupported capabil
ity
Jan 7 10:11:19 r2 bgpd[31645]: neighbor 2001:x:21 (x-v6): parse_notification:
capa_len 16 exceedsremaining msg length
Jan 7 10:11:19 r2 bgpd[31645]: neighbor 2001:x:21 (x-v6): state change
OpenConfirm -> Idle, reason: NOTIFICATION received
Upstream told me about capability : "We do 'inet6.unicast' only". Upstream
router is a Juniper.
Relevant configuration is :
network 2001:1b58::/32
group "Upstream" {
set localpref xxx
announce self
neighbor x.x.x.x {
remote-as x
descr x-v4
}
neighbor 2001:x:0021 {
remote-as x
descr x-v6
}
}
Any idea what I've done wrong again ?
BR,
--
Sylvain COUTANT
ADVISEO
http://www.adviseo.fr/
http://www.open-sp.fr/
