Re: [pfSense] Latency issues with 2.2.25 Release

[Chris Buechler]

On Wed, Nov 11, 2015 at 9:47 AM, Wade Blackwell  wrote:
> Good morning list,
>I recently upgraded to *2.2.5-RELEASE * (amd64) on a VMware stack
> and noticed that my Wan latency shot up by about 100ms rtt. Nothing else on
> the box had changed. I reverted to a pre-upgrade snapshot and the latency
> went back down to 10-12 ms rtt. Anyone seen anything like this with the
> update to 2.2.5?
>

Not that I've seen or heard of. Latency as measured by what?
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Latency issues with 2.2.25 Release

[Jon Gerdes]

On Wed, 2015-11-11 at 07:47 -0800, Wade Blackwell wrote:
> Good morning list,
>I recently upgraded to *2.2.5-RELEASE * (amd64) on a VMware
> stack
> and noticed that my Wan latency shot up by about 100ms rtt. Nothing
> else on
> the box had changed. I reverted to a pre-upgrade snapshot and the
> latency
> went back down to 10-12 ms rtt. Anyone seen anything like this with
> the
> update to 2.2.5?
> 
> -W
> 
> Wade Blackwell

Wade

I have several 2.2.5 upgrades from earlier versions.  Here's one:

[2.2.5-RELEASE][r...@pf1.blueloop.net]/root: ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=8.658 ms

The above is in a VMware 5.5 (current patch level) ESXi host on a four
node cluster.  The ESXis are a bit variable in power but it makes no
difference to the RTT

So, are you absolutely sure nothing else changed?  Same host, exactly
the same network path at your end, no funny workloads at the same time
as your upgrade?  No other changes?  Did you leave a VM snapshot
running?  Backups? etc etc.

Have a look at your rrd graphs on the reverted system and see if there
is a pattern that matches the time you did the upgrade.

Incidentally, what version did you back rev to?  Also how are you
measuring WAN RTT time?  What is your WAN anyway?

There are a lot of questions to answer before you can diagnose a fault
in an OS upgrade ...

If you have a spare WAN IP, clone the pfSense VM give it a WAN IP and a
separate VLAN to play with.  You can detatch the vNICs and use the
console to avoid address conflicts.  

Put a test client VM on the test VLAN.  Upgrade the pfSense box and see
how you go.  You can torture the clone to your hearts content until you
get to the bottom of the problem.  If you don't have a spare external
IP you can always put the clone "behind" the live one - ie put its WAN
on your LAN.  Remove NAT on the clone and add a static route on the
real one for your test VLAN via the clone.

If you have a virty setup - use it!

Cheers
Jon
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[pfSense] Latency issues with 2.2.25 Release

[Wade Blackwell]

Good morning list,
   I recently upgraded to *2.2.5-RELEASE * (amd64) on a VMware stack
and noticed that my Wan latency shot up by about 100ms rtt. Nothing else on
the box had changed. I reverted to a pre-upgrade snapshot and the latency
went back down to 10-12 ms rtt. Anyone seen anything like this with the
update to 2.2.5?

-W

Wade Blackwell
Solutions Architect
(D) 805.457.8825
(C) 805.400.8485
(S) coc.wadeblackwell
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold