Re: kern/176281: [ixgbe] [patch] Update ixgbe to 2.4.10 (latest official driver)

Synopsis: [ixgbe] [patch] Update ixgbe to 2.4.10 (latest official driver) Responsible-Changed-From-To: freebsd-net->jfv Responsible-Changed-By: araujo Responsible-Changed-When: Wed Feb 20 07:50:01 UTC 2013 Responsible-Changed-Why: jfv@ is the Intel guy! :) http://www.freebsd.org/cgi/query-pr.cgi

Re: kern/176281: [ixgbe] [patch] Update ixgbe to 2.4.10 (latest official driver)

Old Synopsis: [driver] Update ixgbe to 2.4.10 (latest official driver) New Synopsis: [ixgbe] [patch] Update ixgbe to 2.4.10 (latest official driver) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Feb 20 05:31:31 UTC 2013 Respons

Re: [PATCH] Add a new TCP_IGNOREIDLE socket option

Hi Sephe, On 02/20/13 13:37, Sepherosa Ziehau wrote: > On Wed, Feb 20, 2013 at 9:46 AM, Lawrence Stewart wrote: >> *crickets chirping* >> >> Time to move this discussion forward... >> >> >> If any robust counter-arguments exist, now is the time for us to hear >> them. I haven't read anything thus

Re: [PATCH] Add a new TCP_IGNOREIDLE socket option

On Wed, Feb 20, 2013 at 9:46 AM, Lawrence Stewart wrote: > *crickets chirping* > > Time to move this discussion forward... > > > If any robust counter-arguments exist, now is the time for us to hear > them. I haven't read anything thus far which convinces me that we should > not provide knobs to t

Re: [PATCH] Add a new TCP_IGNOREIDLE socket option

*crickets chirping* Time to move this discussion forward... On 02/14/13 12:36, Lawrence Stewart wrote: > On 02/14/13 01:48, Andre Oppermann wrote: >> On 13.02.2013 15:26, Lawrence Stewart wrote: >>> On 02/13/13 21:27, Andre Oppermann wrote: On 13.02.2013 09:25, Lawrence Stewart wrote: >

Re: NDP prefix list locking

On Tue, Feb 19, 2013 at 01:47:55PM -0800, Vijay Singh wrote: > Mark, is this the panic you were hitting? It was a double free, so I was seeing panics in different parts of the kernel - in my case it was kqueue and netgraph, among other places. I only managed to track it down to the prefix list cod

Possible optimization in ether_output()

Hi, this patch gives a modest performance improvement here @work. Please consider. [/u/vijay/bsd/CODE/cur/sys/net]# svn diff if_ethersubr.c Index: if_ethersubr.c === --- if_ethersubr.c (revision 247012) +++ if_ethersubr.c (w

Re: NDP prefix list locking

Mark, is this the panic you were hitting? PANIC : Bad list head 0xff800057e720 first->prev != head cpuid = 6 KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x3e panic() at panic+0x479 nd6_prelist_add() at nd6_prelist_add+0x236 prelist_remove() at prelist_remove+0x4c5 nd6_ra_input() at

Re: Wallclock vs monotonic time in v6 expiry times?

Hi-- On Feb 19, 2013, at 10:42 AM, Alex Yong wrote: > I've been looking around in the IPv6 code recently and I noticed that > time_second seems to be the clock of choice for calculating expiry times > for prefixes, routers and addresses. Is there any specific reason it uses > wall clock time and

Wallclock vs monotonic time in v6 expiry times?

Hi, I've been looking around in the IPv6 code recently and I noticed that time_second seems to be the clock of choice for calculating expiry times for prefixes, routers and addresses. Is there any specific reason it uses wall clock time and not time_uptime as this makes more sense to me? I'm ref

Re: Netflow v9 with ng_netflow and nfdump

Ok. well, as long as you're situated in a place that lets you see the MAC addresses, you should be ok. You just need to hack the netflow module to include the source/destination mac address. adrian ___ freebsd-net@freebsd.org mailing list http://lists.

Re: Netflow v9 with ng_netflow and nfdump

On 02/19/2013 06:02 PM, Adrian Chadd wrote: .. I assume that your netflow collector is positioned correctly so it can see the actual client MAC, rather than the MAC of the L3 gateway device? Yes, we've checked with tcpdump. The mirror port simply copies the packets as they flow from our client

Re: Netflow v9 with ng_netflow and nfdump

.. I assume that your netflow collector is positioned correctly so it can see the actual client MAC, rather than the MAC of the L3 gateway device? adrian On 19 February 2013 02:49, Jan Markus wrote: > Hello, > > our Ministry of the interior now requires that IP traffic logs must contain > MAC

Re: Netflow v9 with ng_netflow and nfdump

On 19.02.2013 14:49, Jan Markus wrote: > Hello, Hello. > > our Ministry of the interior now requires that IP traffic logs must > contain MAC addresses of our clients. I am trying to fulfil this with > Netflow v9 which (allegedly) should contain the MAC addresses of IP flows. Netflow version 9 is

IPv6 Toolkit v1.3.1 released!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks, Thought you might be interested in this one... We are pleased to release the SI6 Networks' IPv6 Toolkit v1.3.1: a security assessment and trouble-shooting toolkit for the IPv6 protocol suite. The toolkit is available at:

Netflow v9 with ng_netflow and nfdump

Hello, our Ministry of the interior now requires that IP traffic logs must contain MAC addresses of our clients. I am trying to fulfil this with Netflow v9 which (allegedly) should contain the MAC addresses of IP flows. But with no success so far... We have a mirror port on our core switch a