Date: Sat, 18 Feb 2023 13:21:01 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 269643] ping: UDP connect: No route to host Message-ID: <bug-269643-7501-FHWfJQOyCU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-269643-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-269643-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269643 Mike Karels <karels@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karels@freebsd.org --- Comment #2 from Mike Karels <karels@freebsd.org> --- (In reply to crypt47 from comment #0) > After update from F12 to F13.1 the ping behavior has changed, because it'= s now requires -4/-6 option to resolve names: > ping ya.ru > ping: UDP connect: No route to host The problem is that ya.ru has both IPv4 and IPv6 addresses, ping is default= ing to IPv6, and the host on which the command was run has IPv6 configured but cannot route to ya.ru. ping -4 ya.ru should work. ping, like many other utilities, now supports both IPv6 and IPv4, along with -4 and -6 options.=20 Perhaps your script should use ping -4. btw, ping6 is just ping -6. --=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-269643-7501-FHWfJQOyCU>