Hello.
I try to use quagga-1.2.4 on ArchLinux (linux kernel-5.3.10,
iproute2-5.3.0) and get a problem: zebra does not import special routes
like "blackhole" from the Linux kernel, but zebra itself can install and
remove them .
For example, if I add a route to the Linux console:
ip r add blackhole 192.0.2.0/24
then if you look at the routes in zebra, then this route will not be
shown there:
dell_zebra# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, P - PIM, A - Babel, N - NHRP,
> - selected route, * - FIB route
K * 0.0.0.0/0 via 192.168.74.254, br0 inactive, src 192.168.74.34
C>* 127.0.0.0/8 is directly connected, lo
C>* 192.168.72.0/31 is directly connected, ipip0
C>* 192.168.74.0/24 is directly connected, br0
K>* 192.168.74.254/32 is directly connected, br0
zebra, however, receives a message about adding a route through a
netlink socket when I add a route; strace utility output:
recvmsg(6, {msg_name={sa_family=AF_NETLINK, nl_pid=0,
nl_groups=0x000040}, msg_namelen=12, msg_iov=[.{iov_base={{len=44,
type=RTM_NEWROUTE, flags=NLM_F_EXCL|NLM_F_CREATE, seq=1573711432,
pid=20978}, {rtm_family=AF_INET, rtm_dst_len=24, rtm_src_len=0,
rtm_tos=0, rtm_table=RT_TABLE_MAIN, rtm_protocol=RTPROT_BOOT,
rtm_scope=RT_SCOPE_UNIVERSE, rtm_type=RTN_BLACKHOLE, rtm_flags=0},
[{{nla_len=8, nla_type=RTA_TABLE}, RT_TABLE_MAIN}, {{nla_len=8,
nla_type=RTA_DST}, inet_addr("192.0.2.0")}]}, iov_len=8192}],
msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 44
Question: can zebra correctly handle special routes like blackhole,
defined directly in the linux console?
Thank you.
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
I try to use quagga-1.2.4 on ArchLinux (linux kernel-5.3.10,
iproute2-5.3.0) and get a problem: zebra does not import special routes
like "blackhole" from the Linux kernel, but zebra itself can install and
remove them .
For example, if I add a route to the Linux console:
ip r add blackhole 192.0.2.0/24
then if you look at the routes in zebra, then this route will not be
shown there:
dell_zebra# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, P - PIM, A - Babel, N - NHRP,
> - selected route, * - FIB route
K * 0.0.0.0/0 via 192.168.74.254, br0 inactive, src 192.168.74.34
C>* 127.0.0.0/8 is directly connected, lo
C>* 192.168.72.0/31 is directly connected, ipip0
C>* 192.168.74.0/24 is directly connected, br0
K>* 192.168.74.254/32 is directly connected, br0
zebra, however, receives a message about adding a route through a
netlink socket when I add a route; strace utility output:
recvmsg(6, {msg_name={sa_family=AF_NETLINK, nl_pid=0,
nl_groups=0x000040}, msg_namelen=12, msg_iov=[.{iov_base={{len=44,
type=RTM_NEWROUTE, flags=NLM_F_EXCL|NLM_F_CREATE, seq=1573711432,
pid=20978}, {rtm_family=AF_INET, rtm_dst_len=24, rtm_src_len=0,
rtm_tos=0, rtm_table=RT_TABLE_MAIN, rtm_protocol=RTPROT_BOOT,
rtm_scope=RT_SCOPE_UNIVERSE, rtm_type=RTN_BLACKHOLE, rtm_flags=0},
[{{nla_len=8, nla_type=RTA_TABLE}, RT_TABLE_MAIN}, {{nla_len=8,
nla_type=RTA_DST}, inet_addr("192.0.2.0")}]}, iov_len=8192}],
msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 44
Question: can zebra correctly handle special routes like blackhole,
defined directly in the linux console?
Thank you.
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users