FIOS > ONT > pfSense = nojoy
-
Hmm, so appears to be a WAN side problem.
I would try swapping the bce NIC for one of the ems if you can.
-
-
Hmm, and it is linking as expected at 1G (auto)? With no errors/collisions?
Do you have any traffic shaping applied?
-
My Internet speed is Down50 and Up10 but it is a little bit more coming over the line (63 Down and ~13 Upload)
and my speedtest server is ~180 Kilometer (1k = 1000 meter) away. Test is done under a pimped and tuned APU4D4, but it has only some tuneable´s and the cpu
is not anymore on 600MHz - 1000MHz, it is now on
1000MHz - 1400MHz. But this is ways under your
Xeon E3-12xx @3,0GHz CPU! You should be able
to route one pure GBit/s up and down with your
cpu in my eyes. Perhaps it has something to do
with your rules set and/or iDS/IPS or perhaps
pfblocker-NG could be involved? I am running here a
pfSesen that is turned into a full UTM, with mSATA, modem and WiFi card, plus snort, ClamAV & Squid & SquidGuard & pfBlocker-NG, so with your hardware
you should be able to serve a small company as I see it.[22.05-RELEASE][root@home.arpa]/root: speedtest-cli Retrieving speedtest.net configuration... Testing from Deutsche Telekom AG (xxx.xxx.xxx.xxx.)... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by Spacken.net (Hagen) [179.48 km]: 39.099 ms Testing download speed................................................................................ Download: 57.90 Mbit/s Testing upload speed...................................................................................................... Upload: 11.27 Mbit/s -
link is normal 1G auto there are some errors on the LAN interface.
no traffic shaping.reseat the NIC, pfblocker/snort disable all yields the same results.
-
buffer bloat limiter was the issue.
-limiter adjusted for the new connection.resolved.
-
@propeto13 said in FIOS > ONT > pfSense = nojoy:
buffer bloat limiter was the issue.
-limiter adjusted for the new connection.resolved.
Perhaps you will be so friendly and say exactly what and where you were setting up? Only for other find later that threat here over google or the forum search.
-
You have to set the expected available bandwidth on the WAN when configuring Limiters for buffer bloat because in order to control it you need the Limiter to be the throttling point in the link.
So if you then change the WAN to some higher bandwidth you have to reconfigure the Limiter to match that or you will be stuck at the previous values. As OP found.
Steve
-
@stephenw10
Well said, thank you for clarifying this to me. -
