https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211872
--- Comment #9 from Mike Karels ---
Created attachment 173814
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173814&action=edit
Proposed patch
I have attached a patch to ip6_output.c, which was missing invalidation code
present
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211872
Mike Karels changed:
What|Removed |Added
Status|New |In Progress
Assignee|freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211962
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|freebsd-b.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211836
Kubilay Kocak changed:
What|Removed |Added
Assignee|freebsd-net@FreeBSD.org |a...@freebsd.org
Keyword
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211962
Matt Joras changed:
What|Removed |Added
CC||matt.jo...@gmail.com
--- Comment #2 f
I want to test a change to broadcast packet handling and I want to confirm
that 255.255.255.255 is still handled correctly. Are there any command-line
tools in FreeBSD that can send to the broadcast address? ping
255.255.255.255 does not work correctly, unfortunately.
_
On Thu, Aug 18, 2016 at 4:48 PM, Paul A. Procacci
wrote:
> You should be able to ping the local subnet.
> Alternatively you can use net/arping.
>
> ~Paul
>
I'm specifically looking to test the handling of 255.255.255.255, so a
local broadcast address is out. Unfortunately, arping doesn't seem t
On 18/08/2016 21:55, Ryan Stone wrote:
On Thu, Aug 18, 2016 at 4:48 PM, Paul A. Procacci
wrote:
You should be able to ping the local subnet.
Alternatively you can use net/arping.
~Paul
I'm specifically looking to test the handling of 255.255.255.255, so a
local broadcast address is out. U
Hello!
Is netcat [nc(1)] an option? It doesn't seem to have any objections to
doing this, but I don't have a setup to test it properly with at the
moment.
Thanks,
Kyle Evans
On Thu, Aug 18, 2016 at 2:29 PM, Ryan Stone wrote:
> I want to test a change to broadcast packet handling and I want to
