Poor WAN Performance Between Reboots
-
@stephenw10 I appreciate all of these helpful replies.
When I tax the beelink by doing a speedtest-cli within pfSense the CPU reports 2923mhz current and 806mhz max. CPU temp is currently 59C which is around 25 degrees above ambient. Memory usage is very low at 6%. The power mgmt in the beelink BIOS is set to whatever was decided at the factory, let me know if you think I should enable high performance mode or increase the TDP within the BIOS. I have reached out to beelink to ask about a BIOS update and am still waiting on a response.
I called my ISP again this morning, I suspected there was something 'off' about their modem's bridge mode. The tech unbridged the modem, factory reset it, he disabled the wifi, dhcp and all the other services. From his end he left the modem in an unactivated state : if you look at the modem now it is asking me to go online to activate but in this un-activated status my PPPOE in pfSense has been rock solid for the past 10 hours! The tech was calling this 'unofficial bridge mode'. I'm crossing my fingers that this was an issue with the modem all along but I'm going to wait a week or so before I consider this case-closed.
I don't believe I have any double-nat issues with the modem in this state but I honestly don't know how I can prove that.
As of this writing fast.com is saying that I am getting 2.7gbs down and 2.3gbs up, speedtest reports that I am getting 2316 and 2292 - I am perfectly happy with these speeds.
Thank you all for your quick and helpful replies, as one final question - would I be able to squeeze any additional performance out of this beelink by purchasing a pfplus license?
-
@tjs4ever said in Poor WAN Performance Between Reboots:
I don't believe I have any double-nat issues with the modem in this state but I honestly don't know how I can prove that.
Take a look at your assigned WAN address. Is it an RFC1918 address or is it public? RFC1918 would indicate you are double-nat'ed. A public address and you are good to go.
-
@WN1X The WAN interface IPv4 IP is the same IP address that I get when I visit https://whatismyipaddress.com/ using any of my (Nord exempt) client devices, so I take this to be correct then.
There's also the Gateway IPv4 address but it is a different value and I cannot ping it. I think this is yet another quirk with my ISP. A while back I had to change my gateway monitoring to use quad-8 for the monitoring IP - it just didn't ping one day.
-
@tjs4ever No double-nat there. You should be good now.
-
This post is deleted! -
You might be able to get more performance by tweaking the power/thermal management settings in the BIOS. Check the threads for N100 devices.
Since you're using PPPoE you should also get better performance by using the new if_pppoe driver in 2.8-beta.
-
So my first order of business this morning was to run some new speedtests and I am back to gigabit speeds on the WAN.
I checked ifconfig and the interface is connected as 1000baseT
It looks like I'm back to square 1. I'm going to swap out the cable that connects the modem to my pfSense to rule out a bad cable.
-
What NIC type are you using to connect the WAN?
You can probably set to negotiate the link at 2.5G only.
-
@stephenw10 the beelink is using dual Intel I225-V
Where can I hard-code the link speed for the WAN interface? I see that option under LAN but not under WAN settings.
-
@tjs4ever Interfaces->PORT1WAN Speed & Duplex.
-
@WN1X no such setting available under WAN, is it because it's PPPOE?
LAN has it.
The other interfaces : WAN and the two interfaces setup for my Nord have no such option.
-
Assign the parent NIC as a new interface and set it there. You can leave it as IP types none or set it to the modem/ONT subnet if you want to access that.
-
@tjs4ever Someone using PPPOE will need to assist you.
-
@stephenw10 thanks, I think I figured it out. I assigned a new interface, kept the default name of OPT3. I had to enable it though, when disabling I lost WAN immediately. I left the IP type as none and hard-coded the speed to 2500base-T. I guess I need to just wait another day or two and see what happens.
