Re: OpenBGP & IPv6
* Sylvain Coutant <[EMAIL PROTECTED]> [2006-01-11 00:18]: > 3/ Now "bgpctl show nexthop" shows a nexthop which does not exist. Its IPv4 > address is nothing I know about (and is not the first 32 bits of a v6 > address). ok, you are definately running relatively old code. please try with a -current bgpd (-current bgpd sources should compile on -stable as well). we fixed quite some v6 stuff after 3.8. -- BS Web Services, http://www.bsws.de/ OpenBSD-based Webhosting, Mail Services, Managed Servers, ... Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: OpenBGP & IPv6
> > However, I can't change the > > configuration (reload, neighbour clear), IPv4 is always the only > > capability announced. I believe I need to kill bgpd and restart it for > > the change in the configuration to take effect. I can't for now. > > hmm, there might have been an issue with changing the announced address > families, I vaguely remember fixing something there - tho I don't > remember when. Might have been post-3.8 I finally found that deleting the neighbor from the conf, reloading, adding back the neighbor was able to reset (when not changing groups settings) and works. Now I'm facing several (not so) funny ones : 1/ Routes are not installed because "bgpd[31578]: send_rtmsg: action 1, prefix 3ffe:800::/24: Network is unreachable". I didn't found what was causing that. I killed bgpd and restarted, nothing does. "bgpctl show interfaces" shows the interface as ok/UP. "bgpctl show nexthop" show nothing about the nexthop (others are ..., UP, active, ...). This should be the problem but I don't know how to investigate. 2/ bgpd crashes when the first IPv6 withdraw occurs : Jan 10 23:11:08 r1 bgpd[2945]: neighbor 2001:x: (AS) withdraw 2001:13a8::/48 Jan 10 23:11:08 r1 bgpd[31578]: Lost child: route decision engine terminated; signal 11 [...} Jan 10 23:11:08 r1 bgpd[26296]: session engine exiting Oops :-( 3/ Now "bgpctl show nexthop" shows a nexthop which does not exist. Its IPv4 address is nothing I know about (and is not the first 32 bits of a v6 address). -- Sylvain COUTANT ADVISEO http://www.adviseo.fr/ http://www.open-sp.fr/
Re: OpenBGP & IPv6
* Sylvain Coutant <[EMAIL PROTECTED]> [2006-01-10 18:51]: > > so the neighbor refuses our OPEN messgae because we announce some > > capability it dioesn't like, > I traced frames and had a look at BGP's OPEN frames. I think neighbor > doesn't like the IPv4 capability !! However, I can't change the > configuration (reload, neighbour clear), IPv4 is always the only > capability announced. I believe I need to kill bgpd and restart it for > the change in the configuration to take effect. I can't for now. hmm, there might have been an issue with changing the announced address families, I vaguely remember fixing something there - tho I don't remember when. Might have been post-3.8 -- BS Web Services, http://www.bsws.de/ OpenBSD-based Webhosting, Mail Services, Managed Servers, ... Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: OpenBGP & IPv6
> so the neighbor refuses our OPEN messgae because we announce some > capability it dioesn't like, I traced frames and had a look at BGP's OPEN frames. I think neighbor doesn't like the IPv4 capability !! However, I can't change the configuration (reload, neighbour clear), IPv4 is always the only capability announced. I believe I need to kill bgpd and restart it for the change in the configuration to take effect. I can't for now. BR, -- Sylvain COUTANT ADVISEO http://www.adviseo.fr/ http://www.open-sp.fr/
Re: OpenBGP & IPv6
> Both Cisco based equipmentthere must be something else wrong in the > configuration... Any idea what could be "else" ? ;-) BR, -- Sylvain COUTANT ADVISEO http://www.adviseo.fr/ http://www.open-sp.fr/
Re: OpenBGP & IPv6
The works for me perring with the OCCAID network: www:occaid.net and Hurricane Electric's Tunnel Broker Service: http://tunnelbroker.net Both Cisco based equipmentthere must be something else wrong in the configuration... Glenn > Hi, > >> Try: >> >> announce IPv4 unicast >> announce IPv6 unicast > > Nothing does :( > > > -- > Sylvain COUTANT > > ADVISEO > http://www.adviseo.fr/ > http://www.open-sp.fr/
Re: OpenBGP & IPv6
Hi, > Try: > > announce IPv4 unicast > announce IPv6 unicast Nothing does :( -- Sylvain COUTANT ADVISEO http://www.adviseo.fr/ http://www.open-sp.fr/
Re: OpenBGP & IPv6
* Sylvain Coutant <[EMAIL PROTECTED]> [2006-01-07 11:04]: > 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) : > > state change Idle -> Connect, reason: Start > state change Connect -> OpenSent, reason: Connection opened > state change OpenSent -> OpenConfirm, reason: OPEN message received > received notification: error in OPEN message, unsupported capability so the neighbor refuses our OPEN messgae because we announce some capability it dioesn't like, but the neighbor doesn't tell us which (it should, according to the RFCs, but they're beeing vague (surprised, anyone?) there again). I'd try to make sure I only announce address falimies the neighbor supports. > parse_notification: capa_len 16 exceedsremaining msg length now that's bizarere (except for that I apparently forgot a space in the error msg). either we're subject to a miscalculation, or the message you received from the neighbor is invalid. the (fixed) length of the mandantory parts of the OPEN message you got from the neighbor plus the length of the capabilities following these exceeds the total packet length. -- BS Web Services, http://www.bsws.de/ OpenBSD-based Webhosting, Mail Services, Managed Servers, ... Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: OpenBGP & IPv6
Try:
announce IPv4 unicast
announce IPv6 unicast
Glenn
> 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
> announceself
>
> 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/
Re: OpenBGP & IPv6
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
announceself
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/
OpenBGP & IPv6
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) tunnel broker service. Kudos to Henning for all the good work that went into making this available in v3.8!! I will try and create a quick and dirty web page in the next few days to illustrate how I set this up incase anyone else is interested in trying out... Glenn
