Date: Mon, 19 Apr 2021 15:39:32 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 255227] route(8) ignoring ifp parameter after upgrade from 12.2-RELEASE to 13.0-RELEASE Message-ID: <bug-255227-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255227 Bug ID: 255227 Summary: route(8) ignoring ifp parameter after upgrade from 12.2-RELEASE to 13.0-RELEASE Product: Base System Version: 13.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: net@arrishq.net Hi, maybe first how to re-produce things. A 12.2-RELEASE system running Strongswan and using gif interfaces for route-based VPN's between several systems. In rc.conf: cloned_interfaces="gif0" ifconfig_gif0="inet 10.0.1.1 10.0.1.2 netmask 255.255.255.255 inet6 tunnel 2a01:... 2a02:..." Then using Strongswan or ipsec-tools to create (successfully) an ipsec tunnel from 2a01:... to 2a02:... In 12.2-RELEASE and earlier, it was possible setting additional routes via: route add -net 172.16.0.0/24 10.0.1.2 -ifp gif0 To reach hosts in 172.16.0.0/24 without any problem. netstat -rn reported: 172.16.0/24 10.0.1.2 UGS gif0 Creating the same route in 13.0-RELEASE, the route command seems to ignore the ifp parameter and instead creates: 172.16.0/24 10.0.1.2 UGS lo0 Which of course causes problems. Doing a ping -S 10.0.1.1 172.16.0.1 works. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255227-227>