It's a bit cumbersome to manage as a patch:
https://github.com/NextBSD/NextBSD/tree/HEAD_MERGE/iflib
git clone https://github.com/NextBSD/NextBSD.git -b HEAD_MERGE/iflib
make sure to use the HEAD_MERGE/iflib branch not the default one.
-M
On Tue, May 10, 2016 at 10:58 PM, David Somayajulu
wr
Thanks for info.
Is there a link to the latest patch which I can apply to CURRENT in the
meantime ?
Thanks
David S.
-Original Message-
From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On
Behalf Of K. Macy
Sent: Tuesday, May 10, 2016 12:31 PM
To: hiren panchasara
sepherosa_gmail.com added a comment.
In https://reviews.freebsd.org/D5872#130813, @lstewart wrote:
> In https://reviews.freebsd.org/D5872#130806, @sepherosa_gmail.com wrote:
>
> > In https://reviews.freebsd.org/D5872#130805, @lstewart wrote:
> >
> > > In https://reviews.freebsd.org
sepherosa_gmail.com updated this revision to Diff 16171.
sepherosa_gmail.com added a comment.
Change if(..) {panic} into assertion and wrap the assertion using macro.
CHANGES SINCE LAST UPDATE
https://reviews.freebsd.org/D5872?vs=15642&id=16171
REVISION DETAIL
https://reviews.freebsd.org/
I'm waiting on erj to commit his ixl update. It will go in immediately
following that with an ixgbe and ixl driver. It would have also included a
bxe driver, but the original bxe driver is too flaky to even test that
cabling is OK and my 10GbaseT version frequently had unrecoverable dmae
errors. It
+ Kip, Scott.
On 05/10/16 at 04:46P, David Somayajulu wrote:
> Hi All,
> I have a couple of questions on iflib :
>
> 1. Are there plans to incorporate iflib into CURRENT. If yes, will it
> make it into FreeBSD11 release ?
Yes. The library itself (without any drivers) is being prepared for
Hi All,
I have a couple of questions on iflib :
1. Are there plans to incorporate iflib into CURRENT. If yes, will it
make it into FreeBSD11 release ?
2. Where can I get the latest patch of iflib for FreeBSD_CURRENT ?
Thanks
David S (davi...@freebsd.org)
At Tue, 10 May 2016 10:26:59 +0300,
Dmitry Sivachenko wrote:
> Sometimes ping6 command writes the following warning to stderr:
>
> ping6: failed to get receiving hop limit
>
> I can easily reproduce this with
> for n in `jot - 1 1000` ; do /sbin/ping6 -n -c 5 $HOST > /dev/null ; done
>
> It is ve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166255
--- Comment #10 from eu...@grosbein.net ---
(In reply to elofu17 from comment #9)
AFAIK, there is no such thing as "vlan promiscuous mode" in FreeBSD and only
parent interface can be placed to such mode. Not all vlans should get traffic
pro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166255
elof...@hotmail.com changed:
What|Removed |Added
CC||elof...@hotmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208977
--- Comment #1 from slindgren ---
Correction, it's about LRO (large receive offload), not RLO.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.o
Hello,
Sometimes ping6 command writes the following warning to stderr:
ping6: failed to get receiving hop limit
I can easily reproduce this with
for n in `jot - 1 1000` ; do /sbin/ping6 -n -c 5 $HOST > /dev/null ; done
It is very likely that even 100 repetitions is enough to catch this.
Other
12 matches
Mail list logo
