Date: Fri, 24 May 2019 10:09:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 238098] Setting the -g option to ping6 doesn't work Message-ID: <bug-238098-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238098 Bug ID: 238098 Summary: Setting the -g option to ping6 doesn't work Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: nicolas.masse@stormshield.eu Created attachment 204589 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D204589&action= =3Dedit Set rt and ifp variables when opts->ip6po_nexthop is present Since I migrated to FreeBSD11.2, the -g option of ping6 is broken. The comm= and does always return the error "ping6: sendmsg: No route to host". Having a llok at the code, it seems that this regression was caused by the commit https://svnweb.freebsd.org/base?view=3Drevision&revision=3D286195, w= ere the handling of the IPV6_NEXTHOP option was changed. The bug seems to be caused by the fact that when exiting the bloc who check= the presence of the flag opts->ip6po_nexthop, the variables rt and ifp aren't s= et anymore. Setting rt and ifp seems to fix the problem (see the attached diff). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238098-227>