Hi All.
I have a server with two Intel 10G NIC. OS FreeBSD 10.1-Release amd64.
Server works like NFS, samba-server and iSCSI target. Both NICs
aggregated into lagg device and set MTU 9014 to them. There are some
tuning sysctl.conf:
kern.maxfiles=6289601
kern.maxfilesperproc=5660640
kern.maxvno
On Mon, 1 Dec 2014, George Neville-Neil wrote:
On a slight tangent. I ran VIMAGE kernels vs. non VIMAGE kernels for both a
VANILLA kernel and a PF kernel (PF on but no rules) as a quick smoke test
today. The raw forwarding performance was unchanged between kernels with
and without VIMAGE on
On 04.12.2014 13:50, Yuriy Tabolin wrote:
Hi All.
I have a server with two Intel 10G NIC. OS FreeBSD 10.1-Release amd64.
Server works like NFS, samba-server and iSCSI target. Both NICs
aggregated into lagg device and set MTU 9014 to them. There are some
tuning sysctl.conf:
kern.maxfiles=62896
On Wed, Dec 3, 2014 at 12:21 PM, David P. Discher wrote:
> Hey Net -
>
> In probably a poor, cheap choice, I picked up a TP-Link TL-SG2008 Desktop
> Smart Switch, which supports LACP/802.3ad. I’m currently running 10.1-STABLE
> r274577 on the machine I’m testing with. I’m testing right now wit
On Dec 4, 2014, at 12:50 PM, Alan Somers wrote:
>> Not sure if the attachment will work to the list, but here is a pcap
>> attached em1 (sudo tcpdump -i em1 -s 0 -w lacp.pcap). Attaching to the lagg0
>> with tcpdump, filters out the freebsd’s LACP packets, but still sees the
>> TP-Link’s pack
I had wanted to remove the larger cluster sizes from the driver a while
back, but for reasons
I don't remember that code change didn't happen. The new 40G ixl driver
does this, it only
uses standard clusters for anything under 2K, and above that everything
uses 4K.
I would be curious to see if thi
> ===
> I tried that as well, but $device-name is empty.
>
> If I do this:
>
> notify 1000 {
> match "system" "USB";
> match "subsystem" "INTERFACE";
> match "vendor" "0x0b95";
> match "product" "0x1790";
> match "sernum" "249B0DE00C";
> match "type" "ATTACH";
On 12/04/2014 16:10, David P. Discher wrote:
>
> On Dec 4, 2014, at 12:50 PM, Alan Somers wrote:
>
>>> Not sure if the attachment will work to the list, but here is a pcap
>>> attached em1 (sudo tcpdump -i em1 -s 0 -w lacp.pcap). Attaching to the
>>> lagg0 with tcpdump, filters out the freebsd
On 4 December 2014 at 14:24, Martin Hanson wrote:
> It is worth mentioning that the ONLY reason why this worked is because
> the vendor has provided a serial number. Most vendors don't and it
> would not have worked then.
>
> devd NEEDS to be able to see device MAC addresses!
I'm surprised it doe
I managed to get this working.
It is a dirty hack and I REALLY wish FreeBSD would make documentation
as high a priority as the guys at OpenBSD.
It is difficult to locate correct and updated documentation, especially
about devd. Yes, the man page has information about devd, and devd.conf
even come
It is worth mentioning that the ONLY reason why this worked is because
the vendor has provided a serial number. Most vendors don't and it
would not have worked then.
devd NEEDS to be able to see device MAC addresses!
___
freebsd-net@freebsd.org mailing l
On Thu, 4 Dec 2014, Martin Hanson wrote:
I managed to get this working.
It is a dirty hack and I REALLY wish FreeBSD would make documentation
as high a priority as the guys at OpenBSD.
It is difficult to locate correct and updated documentation, especially
about devd. Yes, the man page has inf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I have seen this in the morning when I had an overnight replication
from my laptop to my storage system which transfers a lot of data.
Before the panic there was some message like:
iwn0: iwn_panicked: controller panicked, iv_state = 5; resetti
On Thu, 4 Dec 2014 14:41:11 -0800 Adrian Chadd wrote
> On 4 December 2014 at 14:24, Martin Hanson
> wrote: > It is worth mentioning that the ONLY reason why this worked is
> because > the vendor has provided a serial number. Most vendors don't and it
> > would not have worked then.
> >
> > devd
On Thu, 04 Dec 2014 16:32:04 -0800 "Chris H" wrote
> On Thu, 4 Dec 2014 14:41:11 -0800 Adrian Chadd wrote
>
> > On 4 December 2014 at 14:24, Martin Hanson
> > wrote: > It is worth mentioning that the ONLY reason why this worked is
> > because > the vendor has provided a serial number. Most ven
Thanks Adam -
On Dec 4, 2014, at 1:58 PM, Adam McDougall wrote:
>
> Is the switch side set to "active" for the lacp mode (instead of
> passive)? Also, try:
> sysctl net.link.lagg.0.lacp.lacp_strict_mode=0
>
> If either of those work, I'll explain more, don't have time to dig for
> old email r
16 matches
Mail list logo
