High latency and packet loss HELP!! [not solved]

[johnpoz]

"20mbps connection on all"

So these are the same ISP just 3 different connections via cable?  So your trying to understand when you PEG your pipe via a speed test why dpinger reports high latency to and from google dns since that is what you have for your monitoring IP and whatever that 65.183 address is..

If you Fill your pipe - then yes the pings used by dpinger are going to show latency and loss.. To get around that you would have to shape so you do not saturate your pipe..  And I am curious if this is the same ISP and cable you would be sharing the connection, etc.

[tripplex]

@johnpoz:

To get around that you would have to shape so you do not saturate your pipe.

How can i shape it in 2.3.4_p1?

[Derelict]

With three WANs into one LAN I don't think you can.

Not downloads anyway.

No decent ISP would buffer like that sending to you.

[johnpoz]

I don't use 2.3.4 any more I am on 2.4, according to Derelict there is a bug in the nat+limiter.. So go to 2.4  its going to be Release on monday or something I think ;)

So for example here is my gateway while running speed test..  Just using the fq_codel that is available in 2.4

So you notice the ping times do go up for my cable connection wan_dhcp, and the tunnel from HE response goes up as well - this is expected since its going over the same wan.. But do not see any loss and latency is only slightly increased..

[Derelict]

https://redmine.pfsense.org/issues/4326

That generally means you can use limiters on LAN but not WAN, because there is usually NAT on WAN, and often not on LAN.

[tripplex]

@johnpoz:

I don't use 2.3.4 any more I am on 2.4, according to Derelict there is a bug in the nat+limiter.. So go to 2.4  its going to be Release on monday or something I think ;)

So for example here is my gateway while running speed test..  Just using the fq_codel that is available in 2.4

So you notice the ping times do go up for my cable connection wan_dhcp, and the tunnel from HE response goes up as well - this is expected since its going over the same wan.. But do not see any loss and latency is only slightly increased..

What are the settings for fq_codel and where should i set it? can you send screen shot and details how to accomplish this. I am going to update to 2.4 from 2.3.4_p1 is that ok?

[johnpoz]

see the fq_codel thread… All the info you need is there..

https://forum.pfsense.org/index.php?topic=126637.0

But sure can send you screenshots if you want.  Also just use the cron job to put the info back in on upgrade vs the file edit mode..  See the thread all info needed is in there.

[tripplex]

can i just update to 2.4 from 2.3.4_p1? Will it cause any issues?

getting this while updating to 2.4.0:
pkg: cached package pear-Net_Growl-2.7.0: size mismatch, cannot continue
Failed

[johnpoz]

Normal advice for packages when updating is to remove them, update then put your packages back..

What package is using growl?  I just looked through the package manager and do not see that listed in either the packages I have installed or available packages.

Well I do see it in pfsense..

[2.4.0-RC][root@pfsense.local.lan]/root: pkg info pear-Net_Growl-2.7.0         
pear-Net_Growl-2.7.0
Name          : pear-Net_Growl
Version        : 2.7.0
Installed on  : Fri Mar 31 07:43:42 2017 CDT
Origin        : net/pear-Net_Growl
Architecture  : FreeBSD:11:amd64
Prefix        : /usr/local
Categories    : net pear
Licenses      : BSD2CLAUSE
Maintainer    : garga@FreeBSD.org
WWW            : https://pear.php.net/package/Net_Growl/
Comment        : Send notifications to Growl
Annotations    :
        repo_type      : binary
        repository    : pfSense
Flat size      : 1.03MiB
Description    :
Growl is a MACOSX application that listen to notifications sent by
applications and displays them on the desktop using different display
styles. Net_Growl offers the possibility to send notifications to Growl
from your PHP application through network communication using UDP.

WWW: https://pear.php.net/package/Net_Growl/
[2.4.0-RC][root@pfsense.local.lan]/root:

[Derelict]

Codel won't do any good if the buffering is in the ISP network, which it must be because pfSense won't buffer bloat like that without significant effort.

There is no way to shape on pfSense LAN because he is trying to load balance 3 20Mbit connections into 60Mbit and there is no way for the shaper to know which WAN is saturated when sending out LAN.

He needs to limit downloads on each WAN interface to something that will reduce the buffer bloat in his crappy crappy ISP network.

The only way I can think of to do that on each WAN independently is a limiter on each WAN. That requires 2.4.

It is unknown if 2.4 will introduce something that doesn't work for you. Probably not. 2.4.0-RELEASE should be real soon now.

If you have a 2.3.4_1 installer ready and a current backup you can get back to where you are in about 10 minutes.

[Derelict]

@tripplex:

can i just update to 2.4 from 2.3.4_p1? Will it cause any issues?

getting this while updating to 2.4.0:
pkg: cached package pear-Net_Growl-2.7.0: size mismatch, cannot continue
Failed

What, exactly, did you do there to initiate that upgrade?

[johnpoz]

Yeah I fail to understand such a odd ball setup?  If you want 60mbps - why not just get a pipe that big?  So you have 3 cable providers in your area but nothing fatter than 20mbps?

I just ordered 500/50 to be installed on wed! ;)  Big jump from my 75/10 connection and cheaper too.  Sad part is my pfsense VM can not route that that speed, so until I update my vm host or pull trigger on sg3100.. Which wife would kill me on cost of either option right at the moment… So I had to order a unifi usg :( cheapest option that I could find that could handle the speed.. But looks like openvpn and ipv6 tunnels going to be a PITA vs the easy clickity clickity of pfsense..  And didn't tell her about that cost, just that needed new modem to handle the new speed..  So prob in for some shit when she sees the amazon bill ;) hehehehe

[tripplex]

ok i got it updated 2.4.0 now i am going to set the limiters on the wan.

Is the attached settings correct? because it isn't working to limit the wan speed.


[johnpoz]

no dude no.. Did you not read the thread I pointed too.

[tripplex]

there are so much things there i can't find what i needed gonna read through it all.

[Derelict]

Remove the shaper. You need to use limiters.

[tripplex]

after creating the limiter where shall i put it on the wan tab of the firewall rule and how is it suppose to be configured i.e. the firewall rule with limiter?

[Derelict]

On a floating match rule on WAN out.


[Derelict]

I used 18/5 just to demonstrate this:

[2.4.0-RC][root@pfSense-b]/root: speedtest-cli
Retrieving speedtest.net configuration…
Testing from Cox ()...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by LV.Net (Las Vegas, NV) [13.99 km]: 18.701 ms
Testing download speed…............................................................................
.Download: 17.23 Mbit/s
Testing upload speed...
Upload: 5.15 Mbit/s

[tripplex]

Its working but no more latency issue when i drop the bandwidth to 10 mbps but i still get packet loss and eventually the interface goes offline.

Am i right to feel this is a hardware problem?