https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193246
Ronald Klop ronald-li...@klop.ws changed:
What|Removed |Added
CC|
Thank you!
On 2014-9-4, at 17:48, Luigi Rizzo ri...@iet.unipi.it wrote:
On Thu, Sep 04, 2014 at 11:58:28AM +, Eggert, Lars wrote:
Hi Luigi,
I'm allocating extra rings and/or extra buffers via the nr_arg1/nr_arg3
parameters for NIOCREGIF.
Once I've done that, how do I actually
Hi Adrian,
I confirmed with the support staff of the room where the server is, that
the ambient temperature was normal.
On 04/09/2014 22:46, Marcelo Gondim wrote:
On 04/09/2014 20:48, Adrian Chadd wrote:
Hi,
The only time this has happened to me is because the card overheated.
Can you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193246
--- Comment #10 from Craig Rodrigues rodr...@freebsd.org ---
Ronald,
Thanks for the tip.
java -Djava.net.preferIPv4Stack=true MulticastTest
seems to work around the problem.
I would still like to see FreeBSD fixed so that this
Hi,
I've tested the attached patch with success and would like to have some
feedback from other FreeBSD network developers. The problem is that the
current TSO limitation only limits the number of bytes that can be
transferred in a TSO packet and not the number of mbuf's.
The current
Hi,
But is the airflow in the unit sufficient?
I had this problem at a previous job - the box was running fine, the
room was very cold, but the internal fans in the server were set to
be very quiet. It wasn't enough to keep the ixgbe NICs happy. I had
to change the fan settings to just always
On 05/09/2014 16:49, Adrian Chadd wrote:
Hi,
But is the airflow in the unit sufficient?
I had this problem at a previous job - the box was running fine, the
room was very cold, but the internal fans in the server were set to
be very quiet. It wasn't enough to keep the ixgbe NICs happy. I had
There are some concerns if we use this with devices that ixl supports:
- The maximum fragment size is 16KB-1, which isn't a power of 2.
- You can't get the maximum TSO size for ixl devices by multiplying the
maximum number of fragments by the maximum size.
Instead the number of fragments is
On 09/05/14 23:19, Eric Joyner wrote:
There are some concerns if we use this with devices that ixl supports:
- The maximum fragment size is 16KB-1, which isn't a power of 2.
Hi Eric,
Multiplying by powers of two are more fast, than non-powers of two. So
in this case you would have to use
Hans Petter Selesky wrote:
On 09/05/14 23:19, Eric Joyner wrote:
There are some concerns if we use this with devices that ixl
supports:
- The maximum fragment size is 16KB-1, which isn't a power of 2.
Hi Eric,
Multiplying by powers of two are more fast, than non-powers of two.
So
Hans Petter Selasky wrote:
Hi,
I've tested the attached patch with success and would like to have
some
feedback from other FreeBSD network developers. The problem is that
the
current TSO limitation only limits the number of bytes that can be
transferred in a TSO packet and not the number
On 09/06/14 00:09, Rick Macklem wrote:
Hans Petter Selesky wrote:
On 09/05/14 23:19, Eric Joyner wrote:
There are some concerns if we use this with devices that ixl
supports:
- The maximum fragment size is 16KB-1, which isn't a power of 2.
Hi Eric,
Multiplying by powers of two are more
Hans Petter Selasky wrote:
On 09/06/14 00:09, Rick Macklem wrote:
Hans Petter Selesky wrote:
On 09/05/14 23:19, Eric Joyner wrote:
There are some concerns if we use this with devices that ixl
supports:
- The maximum fragment size is 16KB-1, which isn't a power of 2.
Hi Eric,
Hans Petter Selasky wrote this message on Fri, Sep 05, 2014 at 20:37 +0200:
I've tested the attached patch with success and would like to have some
feedback from other FreeBSD network developers. The problem is that the
current TSO limitation only limits the number of bytes that can be
I would like to use sshuttle (http://github.com/apenwarr/sshuttle) on
FreeBSD.
I have it working for TCP connections, but it does not properly tunnel DNS
requests. The documentation for sshuttle says that ipfw forward rules
will not properly forward UDP packets, and so when it runs on
Hello,
For many years I would build FreeBSD firewalls and they would be very,
very simple - I just set gateway_enable=yes in rc.conf and everything
just worked.
However, these firewalls *always* had real, routable IPs no both sides.
Both interfaces had real, routable IPs.
Now I have a
On 05/09/2014 17:17, Marcelo Gondim wrote:
On 05/09/2014 16:49, Adrian Chadd wrote:
Hi,
But is the airflow in the unit sufficient?
I had this problem at a previous job - the box was running fine, the
room was very cold, but the internal fans in the server were set to
be very quiet. It wasn't
17 matches
Mail list logo
