bump/me too

Have you tried a different browser or client pc?  This seems like a software issue on the client side to me.

If you are going to be opening up walls anyway, pull cat6 to any place you think you might need connectivity.  Even if you go wireless, you'll need to plug those access points in somewhere.

This is by far the best on-line community I have ever been involved with.

Agreed.  Many times I will bring non-pfsense issues to the 'general discussion' forum here even before posting to the appropriate forum.  The knowledge, willingness to help and etiquette here are fantastic.

If you have a way to pull the config file from the dlink and paste it here in text form perhaps someone can pinpoint the problem.

Somewhat related.  Our fiber ISP left an old Cisco 1841 to act as our gateway.  It only has 100m ports and we have 100m bandwidth from them.  It uses OSPF to connect back to their colo location then out to the internet.  I haven't played with pfSense and the Quagga OSPF package yet, but it's certainly on my to do list.  Not sure if a little dlink box might have OSPF, but perhaps there is more to the config than just a vlan.

I lost faith in DLink when they published firmware that had a known issue of 'VLANs do not work'.   Their next firmware that listed VLANs as one of the 'corrected issues' bricked our switches.  Not much fun.  So yes, that is when I was stung by DLink.  Clearly I haven't gotten over it.

I had horrible luck with DLink up until about three years ago when our company bit the bullet and went Cisco.  Would much prefer to use Netgear or the Linksys 'small business' stuff they market as Cisco.  I have several GS108T that never have lost a beat.  Did have one that had a faulty power plug that would wiggle loose.  Just replaced it with a Linksys SE2800 (or whatever the model # used to be) and all is well.

Just ran some tests over our tunnel and then to the same pfsense box over the public internet.  Results as follows:
Public Internet:
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  8.75 MBytes  73.4 Mbits/sec
[  3]  1.0- 2.0 sec  10.0 MBytes  83.9 Mbits/sec
[  3]  2.0- 3.0 sec  10.0 MBytes  83.9 Mbits/sec
[  3]  3.0- 4.0 sec  10.2 MBytes  86.0 Mbits/sec
[  3]  4.0- 5.0 sec  10.1 MBytes  84.9 Mbits/sec
[  3]  5.0- 6.0 sec  10.0 MBytes  83.9 Mbits/sec
[  3]  6.0- 7.0 sec  10.2 MBytes  86.0 Mbits/sec
[  3]  7.0- 8.0 sec  10.2 MBytes  86.0 Mbits/sec
[  3]  8.0- 9.0 sec  10.1 MBytes  84.9 Mbits/sec
[  3]  9.0-10.0 sec  10.1 MBytes  84.9 Mbits/sec
[  3]  0.0-10.0 sec   100 MBytes  83.9 Mbits/sec

OVPN Tunnel:
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  6.25 MBytes  52.4 Mbits/sec
[  3]  1.0- 2.0 sec  7.38 MBytes  61.9 Mbits/sec
[  3]  2.0- 3.0 sec  7.38 MBytes  61.9 Mbits/sec
[  3]  3.0- 4.0 sec  7.88 MBytes  66.1 Mbits/sec
[  3]  4.0- 5.0 sec  6.50 MBytes  54.5 Mbits/sec
[  3]  5.0- 6.0 sec  7.12 MBytes  59.8 Mbits/sec
[  3]  6.0- 7.0 sec  2.12 MBytes  17.8 Mbits/sec
[  3]  7.0- 8.0 sec  2.75 MBytes  23.1 Mbits/sec
[  3]  8.0- 9.0 sec  5.25 MBytes  44.0 Mbits/sec
[  3]  9.0-10.0 sec  7.00 MBytes  58.7 Mbits/sec
[  3]  0.0-10.0 sec  59.8 MBytes  50.1 Mbits/sec

Like ReneG we see minimal CPU usage on either end of the p2p link.  Both sides have 100m uplinks and latency between the two sites is approximately 12-20ms and 11 hops total.  Both ends of our link are on bare metal hardware and have IPFF enabled.

What is your WAN address showing in pfsense?

I would disconnect the cable modem WAN port and reboot it without being connected.  Let the DOCSIS stuff link up and do its thing before you connect the network cable back to your pfsense box.  My TW modem sometimes serves a local address from DHCP if your router requests an IP before the modem boot up is complete.  This usually corrects itself, but is probably worth a shot.

The other day I found that our Sarg Reports folder had grown to takeover all available space on our box.  I uninstalled the package as we never used it and ran an 'rm' command from the console.  It finished in about an hour.  During that time I just left the box alone, and my shell cursor was at a blank line.  When the process finished, I got the regular prompt again.  Everything was good.

Today I am working with a much larger data set on a Nas4Free box and had to delete a larger amount of files and folders (deduplicated data store from PHDVirtual Backup).  It's been running for a few hours now and the box is still unresponsive.  Is there a better way to delete millions of files en masse?  Should I expect that other services will freeze during this operation as they have now or is this normal in a BSD/*nix envinronment?

What shell commands did you run to generate your test?  We also have 100m connections on both ends of our p2p vpn and I feel that we are getting sub-par performance.  I would like to test our link in a similar manner.

Hate to hijack the thread, but what is with providers forcing their interfaces in the first place?  I can see this practice starting back in the days before auto-negotiation, but when is the SOP going to change to ports being set to auto-negotiate unless directed otherwise by the client?  We just went through a minor crisis traced back to a carrier forcing an interface to 100m full duplex when it was connected to our Cisco switch which auto-negotiated 1g-full.

I just experienced a similar problem just now.  We changed internet providers, I adjusted much of the information on the interface that our p2p oVPN was using, WAN IP address, interface name, and default routes.  In the end I realized this was happening and was able to correct it by selecting a different interface on from the OVPN interface dropdown, saving, then reverting back to the correct interface and saving again.  Ultimately realized this was an issue when I tried to restart the service and noticed that it failed.  The log showed that the service was unable to bind to my old WAN IP which was now no longer a part of this pfSense box.

Make sure you have the appropriate 'allow OVPN' rules created on both ends of the connection.  I think this is what ended up being the cause of similar problems I had when I got our p2p OVPN  going.

Me too - Our CP quit working several months back.  Users were not being redirected to the CP login page and as such could not authenticate unless they manually browsed to the auth page.  As a result we simply disabled the CP for the time being.  Would love to see this resolved.