Mailing List Archive: zebra.conf needed? and how to setup ospf6 authentication?

zebra.conf needed? and how to setup ospf6 authentication?

Jun 25, 2018, 8:24 AM

Post #1 of 4 (1700 views)

Hello Quagga Users

I'm working quit a lot with BGP and tried to avoid OSPF in our network.
Unfortunately this is not so easy and I have to get used to OSPF.

For my y current task (IPv4 and IPv6 DNS Anycast) I setup an Cisco ASR and
two FreeBSD 11.x boxes with quagga. Both BSD boxes (BSDR6 and BSDR7) are
directly connected to the ASR.

I'm using quagga 1.2.4

Why or when do I need the zebra.conf?

This is my current config:

BSDR6 zebra.conf

!

! Zebra configuration saved from vty

! 2018/06/25 16:38:08

!

log stdout

!

interface lo0

!

interface lo1

!

interface lo2

!

interface re0

!

interface re1

!

interface re2

!

ip forwarding

!

!

line vty

!

BSDR6 ospfd.conf

!

! Zebra configuration saved from vty

! 2018/06/25 16:38:08

!

hostname BSDOSPFR6

password asdo

enable password asdasdo

log stdout

!

!

!

interface lo0

!

interface lo1

!

interface lo2

!

interface re0

!

interface re1

!

interface re2

ip ospf authentication message-digest

ip ospf message-digest-key 1 md5 xxxxxx

ip ospf hello-interval 2

ip ospf dead-interval 10

!

router ospf

ospf router-id 10.6.0.2

network 10.6.0.0/24 area 0.0.0.60

network 10.8.0.1/32 area 0.0.0.60

network 10.8.0.2/32 area 0.0.0.60

!

line vty

!

BSD Router 6 Ifconfig (shortend)

pmaechler@BSDR6:~ # ifconfig

re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

status: no carrier

re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

status: no carrier

re2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

inet 10.6.0.2 netmask 0xffffff00 broadcast 10.6.0.255

inet6 fe80::20d:b9ff:fe45:ade%re2 prefixlen 64 scopeid 0x3

inet6 2a00:a680:6000::2 prefixlen 64

status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

inet 10.8.0.1 netmask 0xffffffff

inet6 2a00:a680:8000:8000::1 prefixlen 128

groups: lo

lo2: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

inet 10.8.0.2 netmask 0xffffffff

inet6 2a00:a680:8000:8000::2 prefixlen 128

groups: lo

pmaechler@BSDR6:~ #

The BSD Router 7 has the same setup and the same ip addresses on lo1 and
lo2.

Re2 has two different IP addresses for transport.

Also BSDR6 is in the ospf area 0.0.0.60 and BSDR7 in area 0.0.0.70

Everything is working fine. I can reboot or shutdown a BSD box and only
loose 1 or 2 icmp packets.

So why do I need or what content should my zebra.conf have?

When I restart quagga I get a few message on my console:

Checking ospf6d.conf

OK

Stopping ospf6d.

Waiting for PIDS: 1198.

Checking ospfd.conf

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for lo0

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for lo1

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for lo2

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for re0

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for re1

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for re2

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

OK

Stopping ospfd.

Waiting for PIDS: 1189.

Checking zebra.conf

OK

Stopping zebra.

Waiting for PIDS: 1180.

Checking zebra.conf

OK

Starting zebra.

Checking ospfd.conf

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for lo0

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for lo1

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for lo2

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for re0

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for re1

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for re2

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

OK

Starting ospfd.

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for lo0

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for lo1

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for lo2

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for re0

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for re1

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not find
corresponding OSPF Interface for re2

2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no Link
Parameters for interface

Checking ospf6d.conf

OK

Starting ospf6d.

Can anyone shed some light why I have these messages? Is it because zebra
does not now about my ip setup?

Is it possible to use authentication with OSPF6? If so how? I dind't finde
anything in on the webpage nor in the vtysh cli.

Best regards

Philippe

Re: zebra.conf needed? and how to setup ospf6 authentication? [ In reply to ]

tim at kooky

Jun 25, 2018, 9:27 AM

Post #2 of 4 (1700 views)

Permalink

zebra is the way that routes get from ospf or bgp into the kernel
routing tables.

I think the ospf error messages are because not a real interface.? You
could try using passive mode on those interfaces.? So will advertise the
address into OSPF, but not try to talk OSPF on the interface.

Also, in my view, the zebra part of Quagga is broken for IPv6 and
OSPF6.??? Quagga routes and kernel routing table get out sync and cause
a routing loop.?? This sent me mad and I tried everything.? Tried later
versions.? In the end, I just installed FRR instead, rebooted and it all
worked.

I don't think OSPF6 authentication is possible.

I'm surprised you can't manage what you want to do with BGP

Read this:

https://docs.cumulusnetworks.com/display/DOCS/Border+Gateway+Protocol+-+BGP#BorderGatewayProtocol-BGP-ConfiguringBGPUnnumberedInterfaces

This is what I would use rather than OSPF if my network allowed.

Basically BGP links between routers without any IP address on the link
interfaces. BGP on an interface rather than a setup peer. ? Works for V4
and V6, but over V6 connection. ?? Unfortunately I run a HP network
switch that does OSPF but not unnumbered BGP.??

Tim

On 25/06/18 16:24, Philippe Maechler wrote:
>
> Hello Quagga Users
>
> ?
>
> I?m working quit a lot with BGP and tried to avoid OSPF in our
> network. Unfortunately this is not so easy and I have to get used to OSPF.
>
> ?
>
> For my y current task (IPv4 and IPv6 DNS Anycast) I setup an Cisco ASR
> and two FreeBSD 11.x boxes with quagga. Both BSD boxes (BSDR6 and
> BSDR7) are directly connected to the ASR.
>
> ?
>
> I?m using quagga 1.2.4
>
> ?
>
> Why or when do I need the zebra.conf?
>
> ?
>
> This is my current config:
>
> ?
>
> BSDR6 zebra.conf
>
> !
>
> ! Zebra configuration saved from vty
>
> !?? 2018/06/25 16:38:08
>
> !
>
> log stdout
>
> !
>
> interface lo0
>
> !
>
> interface lo1
>
> !
>
> interface lo2
>
> !
>
> interface re0
>
> !
>
> interface re1
>
> !
>
> interface re2
>
> !
>
> ip forwarding
>
> !
>
> !
>
> line vty
>
> !
>
> ?
>
> BSDR6 ospfd.conf
>
> !
>
> ! Zebra configuration saved from vty
>
> !?? 2018/06/25 16:38:08
>
> !
>
> hostname BSDOSPFR6
>
> password asdo
>
> enable password asdasdo
>
> log stdout
>
> !
>
> !
>
> !
>
> interface lo0
>
> !
>
> interface lo1
>
> !
>
> interface lo2
>
> !
>
> interface re0
>
> !
>
> interface re1
>
> !
>
> interface re2
>
> ip ospf authentication message-digest
>
> ip ospf message-digest-key 1 md5 xxxxxx
>
> ip ospf hello-interval 2
>
> ip ospf dead-interval 10
>
> !
>
> router ospf
>
> ospf router-id 10.6.0.2
>
> network 10.6.0.0/24 area 0.0.0.60
>
> network 10.8.0.1/32 area 0.0.0.60
>
> network 10.8.0.2/32 area 0.0.0.60
>
> !
>
> line vty
>
> !
>
> ?
>
> BSD Router 6 Ifconfig (shortend)
>
> pmaechler@BSDR6:~ # ifconfig
>
> re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>
> ??????? status: no carrier
>
> re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>
> ??????? status: no carrier
>
> re2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>
> ??????? inet *10.6.0.2* netmask 0xffffff00 broadcast 10.6.0.255
>
> ????????inet6 fe80::20d:b9ff:fe45:ade%re2 prefixlen 64 scopeid 0x3
>
> ????????inet6 *2a00:a680:6000::2* prefixlen 64
>
> ????????status: active
>
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>
> lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>
> ??????? inet 10.8.0.1 netmask 0xffffffff
>
> ????????inet6 2a00:a680:8000:8000::1 prefixlen 128
>
> ????????groups: lo
>
> lo2: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>
> ??????? inet 10.8.0.2 netmask 0xffffffff
>
> ????????inet6 2a00:a680:8000:8000::2 prefixlen 128
>
> ????????groups: lo
>
> pmaechler@BSDR6:~ #
>
> ?
>
> The BSD Router 7 has the same setup and the same ip addresses on lo1
> and lo2.
>
> Re2 has two different IP addresses for transport.
>
> Also BSDR6 is in the ospf area 0.0.0.60 and BSDR7 in area 0.0.0.70
>
> ?
>
> ?
>
> ?
>
> ?
>
> Everything is working fine. I can reboot or shutdown a BSD box and
> only loose 1 or 2 icmp packets.
>
> So why do I need or what content should my zebra.conf have?
>
> ?
>
> ?
>
> When I restart quagga I get a few message on my console:
>
> Checking ospf6d.conf
>
> OK
>
> Stopping ospf6d.
>
> Waiting for PIDS: 1198.
>
> Checking ospfd.conf
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for lo0
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for lo1
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for lo2
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for re0
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for re1
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for re2
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> OK
>
> Stopping ospfd.
>
> Waiting for PIDS: 1189.
>
> Checking zebra.conf
>
> OK
>
> Stopping zebra.
>
> Waiting for PIDS: 1180.
>
> Checking zebra.conf
>
> OK
>
> Starting zebra.
>
> Checking ospfd.conf
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for lo0
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for lo1
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for lo2
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for re0
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for re1
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for re2
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> OK
>
> Starting ospfd.
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for lo0
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for lo1
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for lo2
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for re0
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for re1
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> 2018/06/25 17:06:19 OSPF: MPLS-TE(initialize_linkparams) Could not
> find corresponding OSPF Interface for re2
>
> 2018/06/25 17:06:19 OSPF: OSPF MPLS-TE: Abort update TE parameters: no
> Link Parameters for interface
>
> Checking ospf6d.conf
>
> OK
>
> Starting ospf6d.
>
> ?
>
> Can anyone shed some light why I have these messages? Is it because
> zebra does not now about my ip setup?
>
> ?
>
> ?
>
> ?
>
> ?
>
> Is it possible to use authentication with OSPF6? If so how? I dind?t
> finde anything in on the webpage nor in the vtysh cli?
>
> ?
>
> ?
>
> Best regards
>
> ?
>
> Philippe
>
> ?
>
>
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users@lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users

Re: zebra.conf needed? and how to setup ospf6 authentication? [ In reply to ]

pmaechler-ml at glattnet

Jun 25, 2018, 11:10 PM

Post #3 of 4 (1699 views)

Permalink

Good Day Tim and Quagga Users

> zebra is the way that routes get from ospf or bgp into the kernel routing tables.

Ah, ok so I don't need to configure zebra, since I don’t get any routes into the BSD Boxes, just announcing

> I think the ospf error messages are because not a real interface. You could try using passive mode on those interfaces. So will advertise the address into OSPF, but not try to talk OSPF on the interface.
I tried that with no luck, still get the messages. I'll just ignore them for now ????

> Also, in my view, the zebra part of Quagga is broken for IPv6 and OSPF6. Quagga routes and kernel routing table get out sync and cause a routing loop.
> This sent me mad and I tried everything. Tried later versions. In the end, I just installed FRR instead, rebooted and it all worked.
FRR would just be an alternative to quagga? Behind Quagga and FRR is still ospfd and ospf6d, bgpd... I'll try my luck with quagga and if we get problems or worse, I'll remember your advice and try FRR

> I don't think OSPF6 authentication is possible.
That’s sad. I'll hope they add support for it in the future

> I'm surprised you can't manage what you want to do with BGP
Well, I'm sure it is possible, maybe even easier to implement it with bgp. The reason I can't do it with bgp has to do with our network design/policy. So it's a layer 8-11 problem

Thanks for your insights.

Best regards
Philippe

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users

Re: zebra.conf needed? and how to setup ospf6 authentication? [ In reply to ]

tim at kooky

Jun 26, 2018, 2:20 AM

Post #4 of 4 (1699 views)

Permalink

On 26/06/18 07:10, Philippe Maechler wrote:
> Ah, ok so I don't need to configure zebra, since I don’t get any routes into the BSD Boxes, just announcing

you might need zebra running to tell ospf what interfaces are around.
I'm not so sure in this area. But I agree, no config.

One thing Zebra is good at is using it to set up any static routes.
Then add interface detect. Then if you pull the cable, the static
routes get deleted.

(I don't know what FreeBSD is like, but on linux, unplug the network
cable and static routes stay in the routing table and live.)

>
>> Also, in my view, the zebra part of Quagga is broken for IPv6 and OSPF6. Quagga routes and kernel routing table get out sync and cause a routing loop.
>> This sent me mad and I tried everything. Tried later versions. In the end, I just installed FRR instead, rebooted and it all worked.
> FRR would just be an alternative to quagga? Behind Quagga and FRR is still ospfd and ospf6d, bgpd... I'll try my luck with quagga and if we get problems or worse, I'll remember your advice and try FRR
>

FRR is a fork of Quagga by cumulus networks. Development is very
active. https://github.com/FRRouting/frr

Also see https://man.openbsd.org/ospf6d from
http://www.openbgpd.org/ I presume will also work on FreeBSD.

It might be that my issues were already fixed in a later Quagga. But
I'd had enough of compiling, needed to go home, and the FRR debian
packages were just there.

Tim