Speed difference between WAN and LAN

jir591

I've spent a couple of days setting up pfsense. Installed it on a brand new 4 port Protectli. All is good except the internet speed. If I run a speed test at the router through the command line my speed is around 650 - 800 Mbps but if I run a test at on the PC using the same speedtest.net and same test location I get a speed around 200Mpbs. I have gig speed service and my PC that I use for testing has a gig NIC.

So I did a factory reset of pfsense and only have my WAN connect to the ISP and PC connected to the LAN port . Barebones. No switches no other pfsense software tweaking. I get the same speed results

Now if I connect a different router to my PC and run a speed test through the PC I get speeds around 800/Mbps.

This tells me its not a PC NIC issue. But something in Pfsense. Any ideas? Thanks

JKnott

@jir591 said in Speed difference between WAN and LAN:

Now if I connect a different router to my PC and run a speed test through the PC I get speeds around 800/Mbps.
This tells me its not a PC NIC issue. But something in Pfsense. Any ideas? Thanks

Well, here's some recent speedtest results with my pfsense firewall.

jir591

Figured it out. I guess the LAN port must be bad. If I use OPT1 as a LAN, I get high speed.

mer

@jir591
Double check the settings. Most everything autonegotiates, but a lot of times if one end is forced, they can't agree on duplex. That means you get about half what you think.
When you start talking about 1G or higher speeds, cable quality makes a big difference.

I'd plug something (not a switch a single pc) into LAN then do ifconfig on both ends, make sure the speed and duplex match. If they do, then it becomes what was plugged into LAN before and can you figure out the ifconfig of both ends? If they don't match, then "that's your problem" and try different cables.

stephenw10

That ^.

200Mbps is an odd number though. Usually with a link negotiation issue you would see something below 100Mbps or even below 10Mbps depending on what it falls back to.

That looks more like it's negotiating at 1G but seeing errors at a guess.

Steve