OpenVZ Forum: Support » *SOLVED* quagga on FC5 and RHEL4

Home » General » Support » *SOLVED* quagga on FC5 and RHEL4

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

*SOLVED* quagga on FC5 and RHEL4 [message #6283]

Wed, 13 September 2006 12:05

teleport
Messages: 2
Registered: September 2006

Junior Member

Hi all,

I have troubles with quagga and FC5 (kernel: 2.6.15-1.2054_FC5.026test006) and RHEL4 ( CentOS 4.4, kernel: 2.6.9-023stab016.2). Quagga routing daemon (zebra) can not insert routes into kernel. Error is:

2006/09/13 14:57:17 ZEBRA: netlink_route_multipath() (single hop): RTM_NEWROUTE 10.0.1.0/24, type IPv4 nexthop
2006/09/13 14:57:17 ZEBRA: netlink_route_multipath() (single hop): nexthop via 192.168.11.23 if 4
2006/09/13 14:57:17 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24), seq=6
2006/09/13 14:57:17 ZEBRA: netlink-cmd error: Operation not permitted, type=RTM_NEWROUTE(24), seq=6, pid=0

Ospf and bgp daemons works fine. Selinux is disabled. Everything work fine, except quagga. Is there a solution for this problem?

Thank You.

[Updated on: Wed, 04 October 2006 06:03] by Moderator

Report message to a moderator

Re: quagga on FC5 and RHEL4 [message #6284 is a reply to message #6283]

Wed, 13 September 2006 12:12

dim
Messages: 344
Registered: August 2005

Senior Member

Could you strace it?
http://wiki.openvz.org/Stracing_a_program
Please, post it's output somewhere as well as kernel version.

http://static.openvz.org/openvz_userbar_en.gif

Report message to a moderator

Re: quagga on FC5 and RHEL4 [message #6431 is a reply to message #6283]

Sun, 17 September 2006 17:46

teleport
Messages: 2
Registered: September 2006

Junior Member

There is strace. Same pc, same config ( included in tar.gz ), only running kernel differs.

Attachment: centos_2.6.9-42.0.2.EL.tar.gz
(Size: 4.41KB, Downloaded 674 times)
Attachment: openvz_ovzkernel-2.6.9-023stab016.2.tar.gz
(Size: 4.09KB, Downloaded 651 times)

Report message to a moderator

Re: quagga on FC5 and RHEL4 [message #7069 is a reply to message #6283]

Mon, 02 October 2006 21:45

poelzi
Messages: 1
Registered: October 2006

Junior Member

I ran into the same problem the last two days. I just learning bgp so it was kinda hard to find Smile

i managed to run quagga (bgpd + zebra) inside a vz instance with some hackts. 0.99.5 is the version i used and i had to change the configure parameters:

        ./configure \
                --prefix=/usr \
                --libexecdir=/usr/lib/quagga \
                --sbindir=/usr/lib/quagga \
                --sysconfdir=/etc/quagga \
                --localstatedir=/var/run/quagga \
                --enable-exampledir=$(T)/usr/share/doc/quagga/examples/ \
                \
                $(USE_SNMP) \
                --enable-vtysh \
                --enable-isisd \
                --disable-capabilities \
                --enable-watchquagga \
                --enable-ospf-te \
                --enable-opaque-lsa \
                --enable-user=root \
                --enable-group=root \
                --enable-ipv6 \
                --enable-ospfclient=yes \
                --enable-ospfapi=yes \
                --enable-multipath=64 \
                --enable-vty-group=quaggavty \
                --enable-configfile-mask=0640 \
                --enable-logfile-mask=0640 \
                --enable-rtadv \
                --enable-tcp-md5 \
                --disable-netlink \
                --with-libpam

netlink doesn't work and gets only permission denied returns. because using ioctl with capabilities didn' work eigher. Then I found that capabilities seems to be broken here, running zebra as root without capabilies compiled in, works fine. Here on ubuntu, zebra runs default under user quagga.
zebra seems to request capabilities NET_ADMIN, SYS_ADMIN and NET_RAW when i remember correctly. For my tests i gave the instance all available und running capabilities (hope this didn't screw something up). At the beginning I only gave these three and some other caps to the instance, so quagga could continue after trying cap_set_proc, which worked.

Not sure if it matters, but some of the interface in the instance are vpn tun and tap devices. On one tap device is bgpd running.

kindly regards
daniel

Report message to a moderator