Build for Debian MIPS
Hi, I am currently using BIRD 1.6.3 on an Edgerouter Pro. The CPU architecture is MIPS and the OS is based on Debian Stretch. Because of the latter, I can use the Debian package repos to install BIRD 1.6.3, however I would like to upgrade to BIRD 2 which does not have a package built. I noticed there is another repo (located at http://bird.network.cz/debian) which maintains BIRD 2 for Debian Stretch, however those packages are not built for the MIPS architecture. I tried building the package myself in a virtual system emulated with qemu, but the build failed with the following error: > obj/lib/fletcher16_test 2>/dev/null && touch obj/lib/fletcher16_test.ok > obj/lib/fletcher16_test: t_fletcher16_compute 0.007899378s > [FAIL] > obj/lib/fletcher16_test: t_fletcher16_checksum 0.004199340s > [FAIL] > obj/lib/fletcher16_test 0.015348769s > [FAIL] > Makefile:180: recipe for target 'obj/lib/fletcher16_test.ok' failed > make[1]: *** [obj/lib/fletcher16_test.ok] Error 1 > make[1]: Leaving directory '/root/src/debian/bird2-2.0.7' > dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2 > debian/rules:21: recipe for target 'build' failed > make: *** [build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > debuild: fatal error at line 1116: > dpkg-buildpackage -rfakeroot -us -uc -b failed Would it be possible to add MIPS as a build target for the bird.network.cz repo? Thanks, Ross
Re: IPv4 route via IPv6 next hop: Netlink: Network unreachable
On Wed, Apr 1, 2020 at 2:56 PM Ondrej Zajicek wrote: > On Wed, Apr 01, 2020 at 02:56:54PM +0200, Nico Schottelius wrote: > > > > Hello, > > > > I'm running 2.0.7 on Linux 5.4.18-0-lts (Alpine) > > and I receive the route 193.228.143.0/24 from > > 2a0a:e5c0:1:9::2. However it is never set into the kernel, with the > > error message "Netlink: Network unreachable" in syslog. > > > > Has anyone seen this problem recently? I'm not sure if this is really a > > bird2 problem or not, to be honest: > > Hello > > BIRD 2.0.7 does not support properly putting IPv4 routes with IPv6 next > hops to kernel, you can try git master branch (or apply commit > 53401bef63013dfee01b65d071ffbd88e457539f to v2.0.7). Or wait for 2.0.8, > which will be released hopefully this month. > > > The kernel reports many messages like this in dmesg: > > [4541983.369058] netlink: 'bird': attribute type 5 has an invalid length. > > > > However, I am also puzzled that manually adding the route seems to fail: > > Probably older iproute2 tools? > Yes, you may be getting the Busybox implementation of 'ip'. Try 'apk add --no-cache iproute2'. Best wishes, Neil
Re: IPv4 route via IPv6 next hop: Netlink: Network unreachable
On Wed, Apr 01, 2020 at 02:56:54PM +0200, Nico Schottelius wrote: > > Hello, > > I'm running 2.0.7 on Linux 5.4.18-0-lts (Alpine) > and I receive the route 193.228.143.0/24 from > 2a0a:e5c0:1:9::2. However it is never set into the kernel, with the > error message "Netlink: Network unreachable" in syslog. > > Has anyone seen this problem recently? I'm not sure if this is really a > bird2 problem or not, to be honest: Hello BIRD 2.0.7 does not support properly putting IPv4 routes with IPv6 next hops to kernel, you can try git master branch (or apply commit 53401bef63013dfee01b65d071ffbd88e457539f to v2.0.7). Or wait for 2.0.8, which will be released hopefully this month. > The kernel reports many messages like this in dmesg: > [4541983.369058] netlink: 'bird': attribute type 5 has an invalid length. > > However, I am also puzzled that manually adding the route seems to fail: Probably older iproute2 tools? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Re: IPv4 route via IPv6 next hop: Netlink: Network unreachable
Hello.
Check output of 'ip route get 2a0a:e5c0:1:9::2` first.
On Wed, 1 Apr 2020 at 16:00, Nico Schottelius
wrote:
>
>
> Hello,
>
> I'm running 2.0.7 on Linux 5.4.18-0-lts (Alpine)
> and I receive the route 193.228.143.0/24 from
> 2a0a:e5c0:1:9::2. However it is never set into the kernel, with the
> error message "Netlink: Network unreachable" in syslog.
>
> Has anyone seen this problem recently? I'm not sure if this is really a
> bird2 problem or not, to be honest:
>
> The kernel reports many messages like this in dmesg:
> [4541983.369058] netlink: 'bird': attribute type 5 has an invalid length.
>
> However, I am also puzzled that manually adding the route seems to fail:
>
> [14:44] router1.place6:/var/log# ip route add 193.228.143.0/24 via inet6
> 2a0a:e5c0:1:9::2
> RTNETLINK answers: Invalid argument
> [14:45] router1.place6:/var/log# ip route add 193.228.143.0/24 nexthop via
> inet6 2a0a:e5c0:1:9::2
> RTNETLINK answers: Invalid argument
> [14:45] router1.place6:/var/log# ip route add 193.228.143.0/24 nexthop via
> inet6 2a0a:e5c0:1:9::2 dev bond0.25
> RTNETLINK answers: Invalid argument
> [14:45] router1.place6:/var/log#
>
> bird status:
>
> bird> show route all protocol bluecmd_v6
> Table master4:
> 193.228.143.0/24 unicast [bluecmd_v6 14:31:15.880] ! (100) [AS206858i]
> via 2a0a:e5c0:1:9::2 on bond0.25
> Type: BGP univ
> BGP.origin: IGP
> BGP.as_path: 206858
> BGP.next_hop: 2a0a:e5c0:1:9::2
> BGP.local_pref: 100
>
> Table master6:
> 2a10:11c0:114::/48 unicast [bluecmd_v6 14:31:15.880] * (100) [AS206858?]
> via 2a0a:e5c0:1:9::2 on bond0.25
> Type: BGP univ
> BGP.origin: Incomplete
> BGP.as_path: 206858
> BGP.next_hop: 2a0a:e5c0:1:9::2 fe80::21c:73ff:fe2c:6eca
> BGP.local_pref: 100
> bird>
>
> bird2 config:
>
> protocol bgp bluecmd_v6 {
> local as 209898;
> neighbor 2a0a:e5c0:1:9::2 as 206858;
> direct;
>
> ipv4 {
> extended next hop;
>
> import filter from_inside_customer;
> export filter only_default_route;
> };
>
> ipv6 {
> import filter from_inside_customer;
> export filter only_default_route;
> };
>
> default bgp_local_pref pref_normal;
> }
>
> syslog:
>
> Apr 1 14:31:15 router1 daemon.warn bird: Netlink: Network unreachable
> Apr 1 14:31:22 router1 daemon.warn bird: Netlink: Network unreachable
> Apr 1 14:31:42 router1 daemon.warn bird: Netlink: Network unreachable
> ...
>
>
> Bird / Kernel / etc.:
>
> [14:33] router1.place6:/var/log# bird --version
> BIRD version 2.0.7
> [14:35] router1.place6:/var/log# uname -a
> Linux router1 5.4.18-0-lts #1-Alpine SMP Thu, 06 Feb 2020 09:27:36 UTC x86_64
> GNU/Linux
> [14:36] router1.place6:/var/log#
>
> For reference is also attached the configuration of the opposite side
> (Arista 7050):
>
> router bgp 206858
>vrf PUBLIC
> router-id 193.228.143.0
> neighbor 2a0a:e5c0:1:9::5 remote-as 209898
> neighbor 2a0a:e5c0:1:9::5 next-hop-self
> neighbor 2a0a:e5c0:1:9::5 maximum-routes 0
> !
> address-family ipv4
> bgp next-hop address-family ipv6
> neighbor 2a0a:e5c0:1:9::5 activate
> neighbor 2a0a:e5c0:1:9::5 next-hop address-family ipv6 originate
> network 193.228.143.0/24
> !
> address-family ipv6
> neighbor 2a0a:e5c0:1:9::5 activate
> network 2a10:11c0:114::/48
>
> linthal-core(vrf:PUBLIC)(config-router-bgp-vrf-PUBLIC)#show ipv6 bgp
> neighbors 2a0a:e5c0:1:9::5 advertised-routes detail
>
> BGP routing table information for VRF PUBLIC
> Router identifier 193.228.143.0, local AS number 206858
> Update wait-install is disabled
> BGP routing table entry for 2a10:11c0:114::/48
> Paths: 1 available
> 206858
> 2a0a:e5c0:1:9::2 from - (193.228.143.0)
> Origin INCOMPLETE, metric -, localpref -, weight -, valid, local, best
> Rx SAFI: Unicast
> BGP routing table entry for 193.228.143.0/24
> Paths: 1 available
> 206858
> - from - (193.228.143.0)
> Origin IGP, metric -, localpref -, weight -, valid, local, best
> Rx SAFI: Unicast
>
>
> Any pointer in the right direction would be appreciated!
>
> Cheers,
>
> Nico
>
>
> --
> Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
--
Anton Danilov.
Re: IPv4 route via IPv6 next hop: Netlink: Network unreachable
Alpine sounds like containerized nastyness...
Check: Can you set a static route manually?
Nico Schottelius schrieb am Mi., 1. Apr.
2020, 15:00:
>
> Hello,
>
> I'm running 2.0.7 on Linux 5.4.18-0-lts (Alpine)
> and I receive the route 193.228.143.0/24 from
> 2a0a:e5c0:1:9::2. However it is never set into the kernel, with the
> error message "Netlink: Network unreachable" in syslog.
>
> Has anyone seen this problem recently? I'm not sure if this is really a
> bird2 problem or not, to be honest:
>
> The kernel reports many messages like this in dmesg:
> [4541983.369058] netlink: 'bird': attribute type 5 has an invalid length.
>
> However, I am also puzzled that manually adding the route seems to fail:
>
> [14:44] router1.place6:/var/log# ip route add 193.228.143.0/24 via inet6
> 2a0a:e5c0:1:9::2
> RTNETLINK answers: Invalid argument
> [14:45] router1.place6:/var/log# ip route add 193.228.143.0/24 nexthop
> via inet6 2a0a:e5c0:1:9::2
> RTNETLINK answers: Invalid argument
> [14:45] router1.place6:/var/log# ip route add 193.228.143.0/24 nexthop
> via inet6 2a0a:e5c0:1:9::2 dev bond0.25
> RTNETLINK answers: Invalid argument
> [14:45] router1.place6:/var/log#
>
> bird status:
>
> bird> show route all protocol bluecmd_v6
> Table master4:
> 193.228.143.0/24 unicast [bluecmd_v6 14:31:15.880] ! (100) [AS206858i]
> via 2a0a:e5c0:1:9::2 on bond0.25
> Type: BGP univ
> BGP.origin: IGP
> BGP.as_path: 206858
> BGP.next_hop: 2a0a:e5c0:1:9::2
> BGP.local_pref: 100
>
> Table master6:
> 2a10:11c0:114::/48 unicast [bluecmd_v6 14:31:15.880] * (100) [AS206858?]
> via 2a0a:e5c0:1:9::2 on bond0.25
> Type: BGP univ
> BGP.origin: Incomplete
> BGP.as_path: 206858
> BGP.next_hop: 2a0a:e5c0:1:9::2 fe80::21c:73ff:fe2c:6eca
> BGP.local_pref: 100
> bird>
>
> bird2 config:
>
> protocol bgp bluecmd_v6 {
> local as 209898;
> neighbor 2a0a:e5c0:1:9::2 as 206858;
> direct;
>
> ipv4 {
> extended next hop;
>
> import filter from_inside_customer;
> export filter only_default_route;
> };
>
> ipv6 {
> import filter from_inside_customer;
> export filter only_default_route;
> };
>
> default bgp_local_pref pref_normal;
> }
>
> syslog:
>
> Apr 1 14:31:15 router1 daemon.warn bird: Netlink: Network unreachable
> Apr 1 14:31:22 router1 daemon.warn bird: Netlink: Network unreachable
> Apr 1 14:31:42 router1 daemon.warn bird: Netlink: Network unreachable
> ...
>
>
> Bird / Kernel / etc.:
>
> [14:33] router1.place6:/var/log# bird --version
> BIRD version 2.0.7
> [14:35] router1.place6:/var/log# uname -a
> Linux router1 5.4.18-0-lts #1-Alpine SMP Thu, 06 Feb 2020 09:27:36 UTC
> x86_64 GNU/Linux
> [14:36] router1.place6:/var/log#
>
> For reference is also attached the configuration of the opposite side
> (Arista 7050):
>
> router bgp 206858
>vrf PUBLIC
> router-id 193.228.143.0
> neighbor 2a0a:e5c0:1:9::5 remote-as 209898
> neighbor 2a0a:e5c0:1:9::5 next-hop-self
> neighbor 2a0a:e5c0:1:9::5 maximum-routes 0
> !
> address-family ipv4
> bgp next-hop address-family ipv6
> neighbor 2a0a:e5c0:1:9::5 activate
> neighbor 2a0a:e5c0:1:9::5 next-hop address-family ipv6 originate
> network 193.228.143.0/24
> !
> address-family ipv6
> neighbor 2a0a:e5c0:1:9::5 activate
> network 2a10:11c0:114::/48
>
> linthal-core(vrf:PUBLIC)(config-router-bgp-vrf-PUBLIC)#show ipv6 bgp
> neighbors 2a0a:e5c0:1:9::5 advertised-routes detail
>
> BGP routing table information for VRF PUBLIC
> Router identifier 193.228.143.0, local AS number 206858
> Update wait-install is disabled
> BGP routing table entry for 2a10:11c0:114::/48
> Paths: 1 available
> 206858
> 2a0a:e5c0:1:9::2 from - (193.228.143.0)
> Origin INCOMPLETE, metric -, localpref -, weight -, valid, local,
> best
> Rx SAFI: Unicast
> BGP routing table entry for 193.228.143.0/24
> Paths: 1 available
> 206858
> - from - (193.228.143.0)
> Origin IGP, metric -, localpref -, weight -, valid, local, best
> Rx SAFI: Unicast
>
>
> Any pointer in the right direction would be appreciated!
>
> Cheers,
>
> Nico
>
>
> --
> Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
>
IPv4 route via IPv6 next hop: Netlink: Network unreachable
Hello,
I'm running 2.0.7 on Linux 5.4.18-0-lts (Alpine)
and I receive the route 193.228.143.0/24 from
2a0a:e5c0:1:9::2. However it is never set into the kernel, with the
error message "Netlink: Network unreachable" in syslog.
Has anyone seen this problem recently? I'm not sure if this is really a
bird2 problem or not, to be honest:
The kernel reports many messages like this in dmesg:
[4541983.369058] netlink: 'bird': attribute type 5 has an invalid length.
However, I am also puzzled that manually adding the route seems to fail:
[14:44] router1.place6:/var/log# ip route add 193.228.143.0/24 via inet6
2a0a:e5c0:1:9::2
RTNETLINK answers: Invalid argument
[14:45] router1.place6:/var/log# ip route add 193.228.143.0/24 nexthop via
inet6 2a0a:e5c0:1:9::2
RTNETLINK answers: Invalid argument
[14:45] router1.place6:/var/log# ip route add 193.228.143.0/24 nexthop via
inet6 2a0a:e5c0:1:9::2 dev bond0.25
RTNETLINK answers: Invalid argument
[14:45] router1.place6:/var/log#
bird status:
bird> show route all protocol bluecmd_v6
Table master4:
193.228.143.0/24 unicast [bluecmd_v6 14:31:15.880] ! (100) [AS206858i]
via 2a0a:e5c0:1:9::2 on bond0.25
Type: BGP univ
BGP.origin: IGP
BGP.as_path: 206858
BGP.next_hop: 2a0a:e5c0:1:9::2
BGP.local_pref: 100
Table master6:
2a10:11c0:114::/48 unicast [bluecmd_v6 14:31:15.880] * (100) [AS206858?]
via 2a0a:e5c0:1:9::2 on bond0.25
Type: BGP univ
BGP.origin: Incomplete
BGP.as_path: 206858
BGP.next_hop: 2a0a:e5c0:1:9::2 fe80::21c:73ff:fe2c:6eca
BGP.local_pref: 100
bird>
bird2 config:
protocol bgp bluecmd_v6 {
local as 209898;
neighbor 2a0a:e5c0:1:9::2 as 206858;
direct;
ipv4 {
extended next hop;
import filter from_inside_customer;
export filter only_default_route;
};
ipv6 {
import filter from_inside_customer;
export filter only_default_route;
};
default bgp_local_pref pref_normal;
}
syslog:
Apr 1 14:31:15 router1 daemon.warn bird: Netlink: Network unreachable
Apr 1 14:31:22 router1 daemon.warn bird: Netlink: Network unreachable
Apr 1 14:31:42 router1 daemon.warn bird: Netlink: Network unreachable
...
Bird / Kernel / etc.:
[14:33] router1.place6:/var/log# bird --version
BIRD version 2.0.7
[14:35] router1.place6:/var/log# uname -a
Linux router1 5.4.18-0-lts #1-Alpine SMP Thu, 06 Feb 2020 09:27:36 UTC x86_64
GNU/Linux
[14:36] router1.place6:/var/log#
For reference is also attached the configuration of the opposite side
(Arista 7050):
router bgp 206858
vrf PUBLIC
router-id 193.228.143.0
neighbor 2a0a:e5c0:1:9::5 remote-as 209898
neighbor 2a0a:e5c0:1:9::5 next-hop-self
neighbor 2a0a:e5c0:1:9::5 maximum-routes 0
!
address-family ipv4
bgp next-hop address-family ipv6
neighbor 2a0a:e5c0:1:9::5 activate
neighbor 2a0a:e5c0:1:9::5 next-hop address-family ipv6 originate
network 193.228.143.0/24
!
address-family ipv6
neighbor 2a0a:e5c0:1:9::5 activate
network 2a10:11c0:114::/48
linthal-core(vrf:PUBLIC)(config-router-bgp-vrf-PUBLIC)#show ipv6 bgp neighbors
2a0a:e5c0:1:9::5 advertised-routes detail
BGP routing table information for VRF PUBLIC
Router identifier 193.228.143.0, local AS number 206858
Update wait-install is disabled
BGP routing table entry for 2a10:11c0:114::/48
Paths: 1 available
206858
2a0a:e5c0:1:9::2 from - (193.228.143.0)
Origin INCOMPLETE, metric -, localpref -, weight -, valid, local, best
Rx SAFI: Unicast
BGP routing table entry for 193.228.143.0/24
Paths: 1 available
206858
- from - (193.228.143.0)
Origin IGP, metric -, localpref -, weight -, valid, local, best
Rx SAFI: Unicast
Any pointer in the right direction would be appreciated!
Cheers,
Nico
--
Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
