[Bug 287244] [fib_algo] inet.80 (radix4_lockless#865) rebuild_fd_flm: table rebuild failed (route add 255.255.255.255/32 -reject -fib 80)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287244

            Bug ID: 287244
           Summary: [fib_algo] inet.80 (radix4_lockless#865)
                    rebuild_fd_flm: table rebuild failed  (route add
                    255.255.255.255/32 -reject -fib 80)
           Product: Base System
           Version: 14.2-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: paige@paige.bio

Upon adding this route: 

route add 255.255.255.255/32 -reject -fib 80

This caused: 

[fib_algo] inet.80 setup_fd_instance: radix4_lockless algo instance setup
failed, failures=1
[fib_algo] inet.80 (radix4_lockless#865) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.80 (radix4_lockless#865) rebuild_fd: sync rebuild failed
[fib_algo] inet.80 setup_fd_instance: radix4_lockless algo instance setup
failed, failures=2
[fib_algo] inet.80 (radix4_lockless#865) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.80 (radix4_lockless#865) rebuild_fd: sync rebuild failed
[fib_algo] inet.80 setup_fd_instance: radix4_lockless algo instance setup
failed, failures=3
[fib_algo] inet.80 (radix4_lockless#865) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.80 (radix4_lockless#865) rebuild_fd: sync rebuild failed
[fib_algo] inet.80 setup_fd_instance: radix4_lockless algo instance setup
failed, failures=4
[fib_algo] inet.80 (radix4_lockless#865) rebuild_fd_flm: table rebuild failed

I had to narrow it down from a list: 

route_fib80_no_privnet1="192.0.0.0/24 -reject -fib 80"
route_fib80_no_privnet2="192.168.0.0/16 -reject -fib 80"
route_fib80_no_privnet3="10.0.0.0/8 -reject -fib 80"
route_fib80_no_privnet4="172.16.0.0/12 -reject -fib 80"
route_fib80_no_privnet5="192.0.2.0/24 -reject -fib 80"
route_fib80_no_privnet6="169.254.0.0/16 -reject -fib 80"
route_fib80_no_privnet7="127.0.0.0/8 -reject -fib 80"
route_fib80_no_privnet8="100.64.0.0/10 -reject -fib 80"
route_fib80_no_privnet9="192.88.99.0/24 -reject -fib 80"
route_fib80_no_privnet10="198.51.100.0/24 -reject -fib 80"
route_fib80_no_privnet11="203.0.113.0/24 -reject -fib 80"
route_fib80_no_privnet12="198.18.0.0/15 -reject -fib 80"
route_fib80_no_privnet13="224.0.0.0/4 -reject -fib 80"
route_fib80_no_privnet14="223.252.0.0/24 -reject -fib 80"
route_fib80_no_privnet15="240.0.0.0/4 -reject -fib 80"
# route_fib80_no_privnet16="255.255.255.255/32 -reject -fib 80"
route_fib80_no_privnet17="0.0.0.0/8 -reject -fib 80"

apparently you really can assign this as an address 

ifconfig lo127 create 255.255.255.255/32 fib 127
ifconfig lo128 create 0.0.0.255/32 fib 128

lots of stupid things that nobody would ever do (I wonder if you can spoof them
though?)

-- 
You are receiving this mail because:
You are the assignee for the bug.