Device proto is enabled? OSPF export/import filters? 26.01.2015 22:01, Andre Nathan пишет:

Hello

I'm trying to setup a simple lab test for OSPFv3 with bird.

The configuration is as follows:

eth1 eth0 eth0 eth1 <net 1>-------|router 1|------------|router 2|------<net 2>

Both routers have on eth0 an fe80 (link-local) address but also an fd77/16 address. The configuration works but the routers export their link-local address as the gateway for their respective networks. For example:

bird> show route fd77:a:b:c::/80 via fe80::21e:67ff:fe7b:31c9 on eth1

How do I override this behavior and export the fd77 address as the gateway address?

Thanks, Andre

On 01/26/2015 07:09 PM, Ondrej Zajicek wrote:

You cannot. OSPFv3 is expected to always generate routes with link-local gateways.

Interesting, I didn't know that. What I'm trying to do is to allow LXC containers in a host to connect to containers in a different host, having the hosts act as gateways; this is what it looks like: +--------+ fd77:a::1 fd77:a::2 +--------+ | host 1 |---------------------------| host 2 | +--------+ +--------+ | fd77:c::1:1 fd77:c::2:1 | | | | fd77:c::1:2 fd77:c::2:2 | +-------------+ +-------------+ | container 1 | | container 2 | +-------------+ +-------------+ I'd like a web page running in container 1, por example, to be able to access a database running in container 2. I expected to be able to insert the route below via OSPF (everything works as expected when I insert them manually): on host 1: route to network fd77:c:2/80 via fd77:a::2 on host 2: route to network fd77:c:1/80 via fd77:a::1 but with OSPF the routes are added with the link-local addresses as gateways so, a container can't reach the other (actually not even a host can reach a container in another host). Can you see a way to make this work? Thanks in advance, Andre