have you considered that there might not be a relevant patch because FreeBSD’s
implementation isn’t affected?
Jim
> On Apr 2, 2015, at 9:15 PM, Eitan Adler wrote:
>
> + FreeBSD lists since I haven't seen any relevant patches (although I
> might have missed them).
>
> -- Forwarded mess
+ FreeBSD lists since I haven't seen any relevant patches (although I
might have missed them).
-- Forwarded message --
From: D.S. Ljungmark
Date: 2 April 2015 at 10:19
Subject: [oss-security] CVE Request : IPv6 Hop limit lowering via RA messages
To: oss-secur...@lists.openwall.com
Hello Gleb,
Thanks for sharing the details.
>From looking at the wiki page it's not exactly clear what your plan is
regarding the accessor functions as they stand today (if_get*/if_set*
after drvapi change was made). I briefly glanced through some of the code
changes but that takes time so it'd be
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199096
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
I want to use netstat -R on stable10 and following 2 commits are needed
to be MFC'd for that:
https://svnweb.freebsd.org/base?view=revision&revision=266418
https://svnweb.freebsd.org/base?view=revision&revision=266448
r266418 adds a field to 'struct inpcb' but it uses a spare field so I
_think_ it
On 03/23/15 14:40, Karim Fodil-Lemelin wrote:
Hi,
Your patch seems to work as well as mine, albeit completely swinging the
other way now since your copying a lot more from the packet header with
the call to m_dup_pkthdr() (including the M_COPYFLAGS, vlan tags, etc..).
I think this is fine, one
Hi,
So I've changed the configuration last night, eliminating the possibility that
the issue was LACP. All traffic was handled by the single igb interface. It
didn't help, at all.
This morning the interface stopped working, without any form of messages and
started working again after a few m
On Thu, 2 Apr 2015, William Waites wrote:
On Thu, 02 Apr 2015 10:07:29 +0900, "Paul S." said:
> [pmacct's] use of 'return' (with no args) on functions that are
> meant to return an int flat out makes it unable to compile on
> FreeBSD.
Yes, I found that surprising that any modern C co
On Thu, 02 Apr 2015 10:07:29 +0900, "Paul S." said:
> [pmacct's] use of 'return' (with no args) on functions that are
> meant to return an int flat out makes it unable to compile on
> FreeBSD.
Yes, I found that surprising that any modern C compiler would tolerate
that at all.
>
