Jason Hellenthal wrote:
Off the top of my head I don't know of another OS that does this.
But yes agreed changing that behavior would probably effect a lot of people in
a negative way at this point.
Not to mention script breakage.
But a tunable in the stack somewhere would be awesome to chang
Also relevant is this patch
http://patchwork.diac24.net/patch/494/mbox/
I guess it seems like more of a workaround than a fix though.
On Jun 17, 2013, at 12:18 PM, "Li, Qing" wrote:
> Hi,
>
> I tried to keep the route messages to be legacy compatible due to reported
> breakage at th
Hi,
I tried to keep the route messages to be legacy compatible due to reported
breakage at the time. Let me revisit the code and get back to you.
I haven't run the quagga code for years, so please don't mind me request
some information from you offline.
--Qing
we're in the process of upgrading from fbsd 7 to 9 and noticed a change
in behavior that might be problematic for us.
We use quagga to establish bgp sessions with a router. We have it set
to redistribute kernel routes.
Zebra seems to drop anything that doesn't have the 'GATEWAY' flag set on
a ro
Thanks, but this does not work.
ix0:
port 0xece0-0xecff mem
0xdf36-0xdf37,0xdf3c-0xdf3f,0xdf33c000-0xdf33 irq 45
at device 0.1 on pci6
ix0: Using MSIX interrupts with 9 vectors
ix0: Unsupported SFP+ Module
ix0: Hardware Initialization Failure
device_attach: ix0 attach returned
Cool. Any idea of when soon might be?
And about that list of supported SFP+ modules?
Is any Intel 10-GBASE-SR SFP+ module guaranteed to work with this card
and driver?
-Boris
On 06/09/13 22:09, Jack Vogel wrote:
> There will be a driver update soon with the way it should be done, it will
> be i
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
Ermal,
On Fri, Jun 14, 2013 at 03:05:16PM +0200, Ermal Lu?i wrote:
E> >> I'm afraid we can't grow mbuf packet header with 8 bytes just to satisfy
E> >> the ALTQ codel algo, which would definitely have a limited usage among
E> >> FreeBSD users. Thus, "enqueue_time" should go into mbuf_tags(9) not
