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

            Bug ID: 250552
           Summary: [net] [fib] dangling route table entry after
                    destroying interface
           Product: Base System
           Version: 12.1-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: b...@freebsd.org
          Reporter: zlei.hu...@gmail.com

I'm testing FreeBSD's multiple FIBs feature. Dangling route table entry remains
when deleting ip address from interface after migrating the interface's fib
number. It looks weird.

This can be reproduced on FreeBSD 12.1 RELEASE-p10 and FreeBSD 12.2 RC2.

Steps to repeat: 
On a system with net.fibs=4, Run the following commands:

# ifconfig tap0 create fib 1
# ifconfig tap0 inet 192.0.2.1/24
# netstat -rnf inet -F 1
Routing tables (fib: 1)

Internet:
Destination        Gateway            Flags     Netif Expire
192.0.2.0/24       link#4             U          tap0
192.0.2.1          link#4             UHS         lo0

# ifconfig tap0 fib 2
# ifconfig tap0 inet 192.0.2.1/24 delete
# netstat -rnf inet -F 1
Routing tables (fib: 1)

Internet:
Destination        Gateway            Flags     Netif Expire
192.0.2.1          link#4             UHS         lo0


**** Notice the loopback route table entry 192.0.2.1 remains after deleting
address's of tap0. ****


# ifconfig tap0 destroy
# netstat -rnf inet -F 1
Routing tables (fib: 1)

Internet:
Destination        Gateway            Flags     Netif Expire
192.0.2.1          link#4             UHS         lo0

**** Notice again the loopback route table entry 192.0.2.1 remains after
destroying interface tap0. ****

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Reply via email to