Nick | 1 Oct 2008 18:16
Picon

[quagga-users 9958] Re: BGP over IPv6 routing informations not sent in UPDATE message

Nick wrote:
> Hi,
>
> Recently I was trying to configure two BGP routers with IPv6 
> capabalities. I am using quagga (version 0.99.9) and I am running it 
> on Ubuntu 8.04 system.
>
> I will detail upon my configurations:
>
> There are three virtual machines(all Ubuntu virtual OS) running on 
> Ubuntu base system. The base and one Ubuntu guest (Ubuntu-guest1) are 
> acting as the BGP routers. I divided it to have two AS so that
>
> AS 3 includes -> Host Ubuntu(*) + Ubuntu Guest 3
> AS 4 includes -> Ubuntu Guset1(*) + Ubuntu guest 2
> where * is the BGP routers.
>
> I removed all the irrelevant routes so that it virtually creates 
> dynamic routing. I tested this network setup with IPv4 and it worked 
> perfectly fine in sharing routes and updating the kernel routes in the 
> BGP routers.
>
> So I wanted to test the same netwotk configuration with IPv6 
> capabilities. I changed my interface addresses to have a non-local 
> link address (I chose feco::ac10:0/112).  The  network configuration 
> was fine but I saw that the UPDATE messages  of BGP is always showing 
> IPv4 routes in its NLRI "Network Layer Reachability Information" 
> field. I added a filter at the OUT interface of BGP routers to match 
> IPV6 addresses and then onwards ther is no UPDATE message. I would 
> like to see where I went wrong.
(Continue reading)

Michael Lambert | 1 Oct 2008 12:44
Picon
Favicon

[quagga-users 9959] Re: BGP over IPv6 routing informations not sent in UPDATE message

Hi Nick,

On 1 Oct 2008, at 12:16, Nick wrote:

> Nick wrote:
>> So I wanted to test the same netwotk configuration with IPv6
>> capabilities. I changed my interface addresses to have a non-local
>> link address (I chose feco::ac10:0/112).  The  network configuration
>> was fine but I saw that the UPDATE messages  of BGP is always showing
>> IPv4 routes in its NLRI "Network Layer Reachability Information"
>> field. I added a filter at the OUT interface of BGP routers to match
>> IPV6 addresses and then onwards ther is no UPDATE message. I would
>> like to see where I went wrong.

We ran into what sounds like a similar problem.  After several Google  
searches and much poking around we hit upon the 'neighbor override- 
capability' peer option.  The problem would seem to be in RFC 2283 vs  
RFC 2858 multiprotocol extensions.

Michael

-----
Michael H. Lambert, GigaPoP Coordinator        Phone: +1 412 268-4960
Pittsburgh Supercomputing Center               FAX:   +1 412 268-5832
300 S Craig St, Pittsburgh, PA  15213 USA      lambert@...
Arnold Nipper | 1 Oct 2008 14:01
Picon

[quagga-users 9960] Re: BGP over IPv6 routing informations not sent in UPDATE message

On 01.10.2008 12:44 Michael Lambert wrote

> On 1 Oct 2008, at 12:16, Nick wrote:
> 
>> Nick wrote:
>>> So I wanted to test the same netwotk configuration with IPv6
>>> capabilities. I changed my interface addresses to have a non-local
>>> link address (I chose feco::ac10:0/112).  The  network configuration
>>> was fine but I saw that the UPDATE messages  of BGP is always showing
>>> IPv4 routes in its NLRI "Network Layer Reachability Information"
>>> field. I added a filter at the OUT interface of BGP routers to match
>>> IPV6 addresses and then onwards ther is no UPDATE message. I would
>>> like to see where I went wrong.
> 
> We ran into what sounds like a similar problem.  After several Google  
> searches and much poking around we hit upon the 'neighbor override- 
> capability' peer option.  The problem would seem to be in RFC 2283 vs  
> RFC 2858 multiprotocol extensions.
> 

Nick & Michael,

I ran into the same problem (see thread [quagga-users 9863]). Poking
around with capabilities also didn't help. My plan is to move on to 0.99.10.

Best regards,
Arnold
--

-- 
Arnold Nipper / nIPper consulting, Sandhausen, Germany
email: arnold@...       phone: +49 6224 9259 299
(Continue reading)

Michael Lambert | 1 Oct 2008 16:09
Picon
Favicon

[quagga-users 9961] Re: BGP over IPv6 routing informations not sent in UPDATE message

On 1 Oct 2008, at 08:01, Arnold Nipper wrote:
> Nick & Michael,
>
> I ran into the same problem (see thread [quagga-users 9863]). Poking
> around with capabilities also didn't help. My plan is to move on to  
> 0.99.10.

I have to admit I didn't notice the version Nick was running.  We had  
our (solvable) problems with 0.99.10.

Michael

-----
Michael H. Lambert, GigaPoP Coordinator        Phone: +1 412 268-4960
Pittsburgh Supercomputing Center               FAX:   +1 412 268-5832
300 S Craig St, Pittsburgh, PA  15213 USA      lambert@...

Gmane