Pfsense Struggling big time.



  • pfSense works fine out of the box. My guess is pfSense is faster, and thus allowing you to saturate your Internet connection, resulting in your performance issues. It could be 7am keeping me from noticing, but I do not see where you mentioned how fast torrent was running when the performance issues started and how fast torrent would run on your £15 one. Is your connection being saturated on pfSense? Is your connection being saturated on your £15 router?



  • @Darkvodka34:

    youtube changes from 1080 to 360 and buffers every second. Also everything is cat 6 leads and all nics are 1GB

    OP…cat6 has long, long time been outdated and that could be your bottle neck...switch to CAT 7.



  • CAT5e would even work just fine. CAT6 hasn't been replaced with CAT7, CAT7 just is a newer standard for newer issues like 10Gb.



  • @NollipfSense:

    @Darkvodka34:

    youtube changes from 1080 to 360 and buffers every second. Also everything is cat 6 leads and all nics are 1GB

    OP…cat6 has long, long time been outdated and that could be your bottle neck...switch to CAT 7.

    Spent £300 on cat7 all over the house everything is now on cat 7 same problem. In fact its prob worse.

    even did a 3GB trunk just to the server same story




  • just a little update if I have one single torrent on just 1 I get 25% packet loss. has anyone any ideas this is driving me nuts. I used to be able to have 150 going without issues



  • @Darkvodka34

    Did you ever get this sorted?

    Just swapped out from a Draytek router to a pfsense box (Netgate branded SG-3100)
    My torrent client kills my WAN - like you I am on Virginmedia but the problem did not happen with the Draytek so I assume the connection is not to blame.

    I have found a way to stop this issue but it is not great. Reduce TOTAL number of torrent connections to 10, and connections per second to '1'. This stops my WAN dying but also means I can't pull more than about 500kb/s over torrent.
    I'm on 350 down 20 up, upload speed pinned to 80kb/s.

    Also, setting "optimization" in Settings -> Advanced to "Aggressive" helped massively.

    for reference on the draytek I had it set to 200 connections, 50 active, 5 upload slots and upload pinned to 80kb/s. Speeds were phenomenal, now I can't have more than 10 connections...in total.

    I just thought I'd trawl the net for a fix before I give up and see if it is any better on a SG-2440 (can borrow one to test)



  • @daleus said in Pfsense Struggling big time.:

    @Darkvodka34

    Did you ever get this sorted?

    Just swapped out from a Draytek router to a pfsense box (Netgate branded SG-3100)
    My torrent client kills my WAN - like you I am on Virginmedia but the problem did not happen with the Draytek so I assume the connection is not to blame.

    I have found a way to stop this issue but it is not great. Reduce TOTAL number of torrent connections to 10, and connections per second to '1'. This stops my WAN dying but also means I can't pull more than about 500kb/s over torrent.
    I'm on 350 down 20 up, upload speed pinned to 80kb/s.

    Also, setting "optimization" in Settings -> Advanced to "Aggressive" helped massively.

    for reference on the draytek I had it set to 200 connections, 50 active, 5 upload slots and upload pinned to 80kb/s. Speeds were phenomenal, now I can't have more than 10 connections...in total.

    I just thought I'd trawl the net for a fix before I give up and see if it is any better on a SG-2440 (can borrow one to test)

    A few questions for you:

    1 - Have you logged into the pfSense console (not the webUI, but the serial console) to see if you are getting any error or strange output there?
    2 - Have you logged into pfSense (best to do this via the console, not webUI) and run top to see what the resource utilization is?
    3 - What other packages are you running, or is this a clean, default installation?
    4 - What do you see in your system logs?

    The root cause is most likely a resource issue, and determining where that's actually occurring requires some investigation. The original poster didn't leave much information about his configuration, but there is a chance he could have been saturating his ISPs gear (hence the WAN resetting all the time) and this never manifested because the consumer gear couldn't support the same amount of throughput as pfSense. There was no comparison of resource utilization between both routers, and more than likely the consumer router didn't have close to the amount of reporting you can get from pfSense.



  • Hi Tim,

    I'll get it hooked up via the USB Console port asap, however there's bugger all on any of the weblog interfaces, just notifications that my backup 3G connection resets every x hours, dyndns updated etc.

    I have been monitoring resources and - as you say, not at console level - but it looks spot on.
    I have been playing with it further since my last post and I have some insights that may prove useful for others in the mean time:

    I'm now up to about 25 connections in my torrent client, the trick appears to be keep the amount of 'connection attempts per second' low and now I can pull much better speed.

    I have also set the status -> gateways page to refresh every second, As I have a modem pf is automatically monitoring the first hop to the ISP. You can see when this issue is about to crop up as suddenly the RTT standard deviation will go from about 2ms and start rising, the RTT follows soon thenafter. The standard values are about 10ms and 2ms respectively. At 60ms and another 60ms standard deviation packetloss will occur and sits around 3% for a few minutes then begins jumping until the WAN is useless.

    Pausing the torrent client and going into states and filtering to the torrent box IP and killing all states recovers the connection; standard deviation drops within a few seconds and RTT eventually makes its way back to 10ms or so.

    Right now with it working I checked the diagnostics - > states summary page and noticed that my torrent server appeared to have 372 states, all of which are UDP. I am wondering if it might be worth while forcing my torrent client to use TCP, as if those connections do not work the firewall will automatically clear them out due to my "aggressive" setting mentioned previously. Interestingly during a "problem" time, the number of states overall was not much higher.

    edit
    Clean installation, I have installed speedtest-cli via 'pkg add', which I installed to help assist diagnose this issue, no additional packages installed or filtering/snort/anything like that, Only one non-standard firewall rule on LAN that sends any traffic destined for my work's VPN IP via a gateway group consisting of internet + 3G backup.


  • Netgate Administrator

    So what exactly happens when the WAN is "killed"?
    You can no longer send any traffic over it?
    Does the torrent client continue to send/recv?

    This seems a lot like it's just saturating the link. Those speeds should be well within the capability of the 3100.
    What download/upload throughput does it show when this happens?

    Steve



  • Solved: Bad sg-3100, borrowed a 2440 which is fine.

    Will contact local reseller and return/swap the 3100. I did connect to the console and reinstall via the adi image (usb) which did naff all, must be hardware related.

    I now have hundreds of connections set on the 2440 and I am a happy happy boy, the only thing I was a bit "eurgh" about is that the 2440 has only 1 LAN port opposed to the built in switch of the 3100 and I need 3 lan ports in the immediate vicinity to the firewall, so I had to bridge LAN,OPT1,OPT2 which works perfectly.

    Thanks all.


Log in to reply