[Bug 255227] route(8) ignoring ifp parameter after upgrade from 12.2-RELEASE to 13.0-RELEASE

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Apr 22 08:29:53 UTC 2021


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

Alexander V. Chernikov <melifaro at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|bugs at FreeBSD.org            |melifaro at FreeBSD.org

--- Comment #1 from Alexander V. Chernikov <melifaro at FreeBSD.org> ---
Hi!

Do I understand correctly that creating p2p gif0 interface & trying to use the
remote end as a gateway should trigger the problem?

I'm trying the following with 13-S (don't have 13-R handy, will test later
today):

8:25 [0] m at devel0 s ifconfig gif0
gif0: flags=8011<UP,POINTOPOINT,MULTICAST> metric 0 mtu 1280
        options=80000<LINKSTATE>
        inet 10.0.1.1 --> 10.0.1.2 netmask 0xffffffff
        groups: gif
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
8:25 [0] m at devel0 netstat -4rnW | grep 10.0.1
10.0.1.1           link#4             UHS       152  16384        lo0
10.0.1.2           link#4             UH        149   1280       gif0
8:25 [0] m at devel0 s route add -net 172.16.0.0/24 10.0.1.2
add net 172.16.0.0: gateway 10.0.1.2 fib 0
8:25 [0] m at devel0 netstat -4rnW | grep 172.16.0.0
172.16.0.0/24      10.0.1.2           UGS       153   1280       gif0
8:25 [0] m at devel0 s route delete 172.16.0.0/24
delete net 172.16.0.0 fib 0
8:25 [0] m at devel0 s route add -net 172.16.0.0/24 10.0.1.2 -ifp gif0
add net 172.16.0.0: gateway 10.0.1.2 fib 0
8:25 [0] m at devel0 netstat -4rnW | grep 172.16.0.0
172.16.0.0/24      10.0.1.2           UGS       153   1280       gif0


Meanwhile, could you consider sharing `netstat -4rnW` output (at least for 10.0
routes) after gif0 creation?

Also: could you please clarify the reason of adding `-ifp gif0`?

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


More information about the freebsd-bugs mailing list