Date: Sat, 16 Jul 2022 16:03:41 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 252596] ping to 255.255.255.255 does not set broadcast MAC Message-ID: <bug-252596-7501-ZBBtZzvDmm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252596-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-252596-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=3D252596 --- Comment #8 from Mike Karels <karels@freebsd.org> --- I have mixed feelings about restoring the checks for INADDR_BROADCAST and INADDR_ANY. The problem with a send to 255.255.255.255 for a broadcast is = that it doesn't allow any way to select the outgoing interface. The in(4) man p= age is out of date on this; the interface selection is now done via routing. T= his means that a send to 255.255.255.255 would often follow the default route, which may or may not be right. A more explicit route can be added, although that seems like a poor way to control an application, and only allows one interface to be used. The application already needs to set the SO_BROADCAST option; setting IP_ONESBCAST and providing a way to specify the destination address doesn't seem like a big increment. Granted, ping will not have a w= ay to do this, but that doesn't seem like a very important use case. If the change you cited was made recently, I might be more worried about compatibility. But it was made almost 6 years ago. --=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-252596-7501-ZBBtZzvDmm>