On Thu, 6 Nov 2014, Adam Thompson wrote:
Ok, recap again...
- this affects multiple protocols, not just NFS. I've now confirmed
it affects SSH as well.
- this only occurs when the server is behind pfSense and the client
is on the "outside" of the firewall.
- this problem does not occur in the other direction through pfSense
(LAN->WAN).
- to repeat myself, NFS works fine at ~1gbps between the same client
and server without pfSense in the middle.
Ergo, I conclude it's something pfSense-related. Haven't had a
chance to turn off of scrub yet.
I know you said that the CPU runs at ca. 5% load, but personally I'd
be unsure of a P-III-class machine at LAN speeds. What bus connection
do the NICs use? PCI? EISA? A 32-bit PCI bus operating at 33 MHz has a
theoretical maximum bandwidth of 133 Mb/s, and the 64-bit expansion
did little to improve that in any practical way. Plus, pre-MSI PCI
devices notoriously shared interrupts, slowing down device-to-devce
transfers. (And just to be cranky, I'll ask if any of the NICs in
shared PCI/ISA slots, which would squeeze performance even further.)
Have you tested that hardware in a routing capacity with non-pfSense
software?
Does the pfSense box have good DNS service?
Is the cabling flaky?
Is the pfSense box routing between subnets or just bridging? If the
former, what's there when pfSense is not "in the middle"? Another
router? Just a switch?
--
Paul Heinlein
[email protected]
45°38' N, 122°6' W
_______________________________________________
List mailing list
[email protected]
https://lists.pfsense.org/mailman/listinfo/list
