Problem with traffic after upgrade 2.5.2 to 2.6.0

pki79

Hi.
I have big trouble with traffic after upgrading to 2.6.0.
The problem is not clear to me, but my phone system (freepbx) can not contact to all voip servers, ping stop working on many devices, (router can be pinged, LAN too, nothing behind WAN), simple http and https is working, some streaming sites does not show video.

Shortly after pfsense 2.6.0 finish booting all traffic works fine for few seconds, then it stopps.

Hardware is APU2 with SATA SSD, some VLANS, Captive Portal, openvpn, no special packages or addons.

First I updated via the webgui, then i gave a try with a fresh install recovering the existing config (which was fine because i loaded 2.5.2. back and the working config). Third try was a fresh install of 2.6.0 and then loading the config (from 2.5.2). In all situations the effect is exactly the same.

Any ideas? I was not sure for this topic to post in upgrade or here.

stephenw10

This is the correct location because the upgrade itself is not failing.

Do you see traffic blocked in the firewall logs when this happens?

If it all traffic affected or only traffic through the captive portal?

Either way you should install the System Patches package and apply the listed recommended patch for Captive Portal that addresses this: https://redmine.pfsense.org/issues/12834

Steve

pki79

@stephenw10 OMG, that seems to be this point, UDP traffic not going throu. I use captive portal for all devices with a MAC whitelist. How can this be on a stable version? Is this not going to be fixed in 2.6.1 or similar?

Gertjan

@pki79 said in Problem with traffic after upgrade 2.5.2 to 2.6.0:

this not going to be fixed in 2.6.1

No need.

@stephenw10 said in Problem with traffic after upgrade 2.5.2 to 2.6.0:

you should install the System Patches

See this as an 'order' from Netgate - not an option ;)
There will be a update (patch) waiting for you. Check also if you need the other build in patches.
The subject has been dealt with when 2.6.0 came out. There were some 'portal' issues, and a solution was prepared.

stephenw10

Yeah, it's fixed in 2.7 and it's a simple patch for 2.6 that can be applied.

Because it doesn't affect traffic to the firewall itself most CP installs continued to work fine. DNS functions normally. If you are passing alternative DNS servers though it will fail without the patch. And of course any other traffic. So we first saw reports on VPNs not passing for example.

Steve

pki79

@stephenw10 Thank You, i got it :)