Yes, I'm not sure what the actual hard limit is, will check that on Monday,
but
you can go over 4K, it was just a limit I created.
Jack
On Sat, Apr 21, 2012 at 10:51 PM, Vijay Singh wrote:
> >> FWIW, at my current employer we run with both rxd and txd cranked up to
> 32k
> >> (we had to patch
>> FWIW, at my current employer we run with both rxd and txd cranked up to 32k
>> (we had to patch the driver as you suggested) and have not had any problems
>> doing that for a couple of years now.
John et al, is this limit specific to igb, or is it applicable to the
ixgbe as well. From the 8.x d
On 4/21/12 4:49 AM, Barney Cordoba wrote:
For a variety of reasons I have a client stuck on FreeBSD 7.0 and they're
interested in getting a MB that uses the latest CPUS. They're just using the
console, so there are no graphics; can someone provide insight as to whether
this would be expected t
Hi,
This honestly sounds like it's begging for an
instrumentation/analysis/optimisation project.
What do we need to do?
Adrian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail
On Apr 21, 2012, at 4:41 AM, Dmitry S. Kasterin wrote:
> The "DYNAMIC RULES" section gives the following recommendation:
> ipfw add check-state
> ipfw add deny tcp from any to any established
> ipfw add allow tcp from my-net to any setup keep-state
>
> Is the second rule
On Sat, 21 Apr 2012 15:41:30 +0400, Dmitry S. Kasterin wrote:
[..]
> 9.0-STABLE / custom kernel
>
> > Also, if
> > you choose to use stateful TCP filtering, it is probably best to do it
> > in the manner shown in the ipfw(8) man page under DYNAMIC RULES. This
> > is very different from the w
For a variety of reasons I have a client stuck on FreeBSD 7.0 and they're
interested in getting a MB that uses the latest CPUS. They're just using the
console, so there are no graphics; can someone provide insight as to whether
this would be expected to work without serious problems?
BC
___
>> # sysctl net.inet.ip.fw.dyn_fin_lifetime=4
>> net.inet.ip.fw.dyn_fin_lifetime: 1 -> 4
>> # sysctl net.inet.ip.fw.dyn_rst_lifetime=4
>> net.inet.ip.fw.dyn_rst_lifetime: 1 -> 4
> The thing that jumps out is that all of the blocked packets are of FIN
> packets. I am not sure why they are being deni
